Privacy Policy

Effective 5 November 2026

This policy explains how DevLearn Dynamics (“we”, “us”) collects, uses and protects personal data when you use eArchifyDocs, our secure document library and electronic signature service, including the eArchifyDocs app, the signing page sent to recipients, and our sign-up and payment pages.

Who is responsible for your data

For account, billing and website data, DevLearn Dynamics is responsible (the data controller). Documents and the information in them belong to the organisation that uploads them: the organisation decides what is stored and who may see it, and we process that content on its behalf and on its instructions.

What we collect

  • Account details: name, email address, password (stored only as a one-way hash), role, and optionally department and employee ID.
  • Organisation and billing details: organisation name, contact person, phone number, country, company and VAT numbers, invoices and payments. Bank account details given at sign-up are stored encrypted and shown only in masked form.
  • Documents and signatures: files you upload, their titles, abstracts and keywords (including text read from scanned pages), envelope recipients’ names and email addresses, and the signatures, initials, stamps and field values recipients add.
  • Activity and security records: sign-ins, document views, access requests, signing events, IP address and browser type. These keep accounts secure and give organisations an audit trail.
  • From Google, if you sign in with Google: your name, email address and Google account identifier (see the next section).

Google user data

If you choose “Sign in with Google”, we receive your name, email address and Google account identifier from Google. We use them only to identify you and sign you in to your eArchifyDocs account, or to create the account when you start a free trial. We do not request access to your Gmail, Drive, contacts or any other Google data, we do not sell this information, and we do not use it for advertising.

eArchifyDocs’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

How we use data

  • To provide the service: storing and showing documents, enforcing access rules, sending documents for signature and producing sealed signed copies.
  • To send service emails: invitations, sign-in and signing codes, signing progress, completion notices, invoices and account notices.
  • To bill organisations and handle payments.
  • To keep the service secure: preventing misuse, detecting suspicious activity and investigating problems.
  • To meet legal obligations, such as keeping financial records.

We do not sell personal data, and we do not use documents or their contents for advertising or to train AI models.

Service providers we use

ProviderWhat for
Google Cloud (Cloud Run, Cloud Storage)Running the service and storing files
NeonThe database holding accounts, document details and records
HostingerSending service emails
PaddleTaking card payments as our reseller; card details go directly to Paddle and never reach us
Google (Sign-In, reCAPTCHA)Optional Google sign-in, and checking that trial sign-ups are made by a person

These providers process data only to provide their service to us, in secure data centres that may be outside the country where you live. Where data is transferred between countries, we rely on the safeguards the law requires, such as standard contractual clauses. Text recognition (OCR) of scanned documents runs on our own servers.

Cookies and browser storage

We use one essential cookie, which keeps you signed in and can’t be read by scripts on the page. The app also keeps your short-lived sign-in token, basic profile and last-activity time in your browser’s storage so it can sign you out after inactivity. We use no advertising or analytics cookies. Paddle’s payment pages may set their own cookies to process a payment.

How long we keep data

We keep data for as long as the organisation’s account is active. Organisations decide how long their documents are kept. When an account is closed, its data is deleted or anonymised within a reasonable period, except records we must keep by law (such as invoices) and the evidence attached to signed documents, which is kept for as long as it may be needed to prove a signature.

Security

Data is encrypted in transit and at rest. Sign-ins are short, limited to one browser at a time and end after inactivity; documents open only in a protected, watermarked viewer, and every view is logged. No system is perfectly secure, but we work to protect your data and will notify affected customers of a breach as the law requires.

Your rights

Depending on where you live, you may have the right to access, correct, delete or receive a copy of your personal data, and to object to or restrict how it is used. If your account belongs to an organisation, contact its administrator first — they control most of your data. You can also write to us at earchifydocs@devlrdynamics.com. You may complain to your local data protection authority.

Children

eArchifyDocs is a business service and is not intended for anyone under 18.

Changes to this policy

We may update this policy. We will change the effective date above and, for significant changes, tell account administrators by email before they take effect.

Contact

DevLearn Dynamics. Email: earchifydocs@devlrdynamics.com.