Legal
Privacy Policy
How AuraDoc processes personal data and documents, for what purposes and for how long, which cloud storage providers it connects to, and what rights you have under the data protection law that applies to you, such as the GDPR, the UK GDPR, the LGPD or the CCPA/CPRA.
Last revised on
1. Data we process
Processing covers three distinct categories:
- Account data — name, email address, organization, credentials in encrypted form, and language and theme preferences
- Customer content — uploaded documents and everything derived from them: text extracted by OCR, structured fields, search vectors (embeddings) and conversation history
- Technical and usage data — access logs, IP address, device identification, active sessions and quota usage metrics
2. Controller, purposes and legal basis
The controller of the personal data described in this policy is AuraDoc, the provider of the platform. For privacy questions and requests, including those addressed to our data protection officer, write to contact@auradoc.ai.
We process account data and customer content because this is necessary to perform the service agreement with you.
Technical data is processed on the basis of our legitimate interest in ensuring security, preventing fraud, detecting abuse and sizing the infrastructure, always limited to what is necessary for those purposes.
Marketing communications, where they exist, depend on consent, which can be withdrawn at any time.
3. Artificial intelligence and subprocessors
AI features may send excerpts of documents to language model providers for processing. Only the content needed for the requested operation is sent.
When the customer configures their own keys (BYOK), processing takes place under the customer's account with the chosen provider, and that provider's policies apply.
We do not sell personal data and we do not use it to train our own models.
Our subprocessors fall into these categories: hosting and storage infrastructure, artificial intelligence model providers (only when you use an AI feature), payment processing and transactional email delivery. The current list is available on request at contact@auradoc.ai.
4. Cloud storage accounts (Google Drive, OneDrive, SharePoint, Dropbox, Box)
When you connect a Google Drive account to AuraDoc, AuraDoc only accesses the folders and files you choose to sync or import.
For Google Drive, AuraDoc requests only the drive.file permission, plus your basic sign-in information (name, email address and profile picture). With it, AuraDoc can open only the files you pick in the Google file picker or that AuraDoc itself creates, and cannot see the rest of your Drive.
We use this data to: list your folders; download the files you choose to run OCR, data extraction, search and translation; detect new or changed files; and, when you ask, create destination folders, upload the processed PDFs back to your Drive and move to the Drive trash the files you delete in AuraDoc with the cloud option ticked.
When you use an AI feature on these files, only the necessary content is sent to the configured model provider, solely to provide that feature.
Access tokens are stored encrypted on our servers and deleted when you disconnect the account. We do not sell Google data, use it for advertising, or use it to train artificial intelligence models.
AuraDoc's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
You can revoke access at any time in Integrations → Disconnect, or in your Google account permissions.
AuraDoc also connects to Microsoft OneDrive, Microsoft SharePoint, Dropbox and Box. The same rules apply to them: AuraDoc only opens the folders and files you select, access tokens are stored encrypted and deleted when you disconnect, and the data is never sold, used for advertising or used to train artificial intelligence models. Permissions requested by each provider and how to revoke them:
- OneDrive — Files.Read.All and offline_access to list and download the files you choose and keep the connection active; Files.ReadWrite only if you turn on saving results back to the cloud. Revoke in Integrations → Disconnect or in the app permissions of your Microsoft account.
- SharePoint — Sites.Read.All to list sites and libraries and download the files you choose; Sites.ReadWrite.All only if you turn on saving results back to the cloud. Revoke in Integrations → Disconnect or ask your Microsoft 365 administrator to remove the app’s consent.
- Dropbox — account_info.read, files.metadata.read and files.content.read to identify the account, list folders and download the files you choose; files.content.write only if you turn on saving results back to the cloud. Revoke in Integrations → Disconnect or in Dropbox under Settings → Connected apps.
- Box — root_readwrite to list, download and, when you ask, upload files in the folders you choose, and manage_webhook to detect new or changed files. Revoke in Integrations → Disconnect or in Box under Account settings → Apps.
5. Security
Technical and organizational measures applied continuously:
- Encryption in transit with TLS; credentials, access tokens and BYOK keys are encrypted at rest
- Logical isolation per organization, with role-based access control
- Two-factor authentication and management of active sessions, which users can revoke themselves
- Audit log of relevant operations on documents and settings
- Periodic backups and monitoring of service integrity
6. Retention and deletion
Documents and derived data are kept while the account is active. Deleting a document also removes the extracted text, the structured fields and the associated search vectors.
After the account is closed, customer content is deleted within 30 days, unless a legal retention obligation applies. Audit and billing records may be kept for the periods required by applicable law.
7. Your rights
Wherever you live, you can ask us for confirmation that we process your data, access, correction, deletion, portability, restriction of or objection to processing, information about who we share it with, and withdrawal of consent. We do not sell personal data or share it for cross-context behavioral advertising.
Send requests to contact@auradoc.ai. We answer within the deadline set by the law that applies to you, and some rights can be exercised directly in the account settings. You may also lodge a complaint with the data protection authority of your country.
Depending on where you live, these rights come from laws such as the following, and we also respect equivalent laws in other countries:
- European Union and European Economic Area — General Data Protection Regulation (GDPR)
- United Kingdom — UK GDPR and Data Protection Act 2018
- Brazil — General Data Protection Law (LGPD, Law No. 13,709/2018)
- California, United States — California Consumer Privacy Act, as amended by the California Privacy Rights Act (CCPA/CPRA)
- Canada — Personal Information Protection and Electronic Documents Act (PIPEDA)
- Japan — Act on the Protection of Personal Information (APPI)
- China — Personal Information Protection Law (PIPL)
8. International transfers
AuraDoc’s main servers are located in the European Union (Germany). Some subprocessors, including artificial intelligence model providers, may process data in other countries, such as the United States.
When personal data leaves the European Economic Area, the United Kingdom or Switzerland, we rely on adequacy decisions or on the European Commission’s Standard Contractual Clauses (with the UK addendum where applicable), plus additional safeguards where needed. For transfers from Brazil we use the mechanisms of the LGPD, including the standard contractual clauses approved by the ANPD, and for other countries the equivalent mechanisms of local law.
9. Cookies and local storage
We use cookies and the browser's local storage to keep the authenticated session and to preserve preferences such as language and theme. We do not use behavioral advertising cookies.
10. AuraDoc PDF Editor (web, Windows, macOS and Android)
The AuraDoc PDF Editor works in the browser at auradoc.ai/edit-pdf and as the AuraDoc Editor app for Windows, macOS and Android. The rest of this policy applies to it as well; this section adds what is specific to the editor:
- On your device — opening, viewing, editing, annotating, filling in, signing, organizing and saving PDFs, and the other tools that run on the device, work entirely on your device; in the Windows, macOS and Android apps they also work without an internet connection. Those files are not sent to AuraDoc. The apps read and write only the files you choose in the system's open and save dialogs.
- Online tools — some tools are run by AuraDoc's servers. Only when you start one is the document, or the file you pick for it, sent to our servers over an encrypted connection, and the result comes back to the editor. They require an AuraDoc account, and the server checks your plan, quota and credits on every request.
- Artificial intelligence — AI tools, such as summary and translation, are available only on paid plans and stay locked on free accounts and trials. When you use one, the document goes to our servers and only the content needed is passed to an AI model provider, as described in section 3.
- Text recognition (OCR) — online OCR sends the document to our servers like any online tool. Offline OCR, for subscribers, recognizes the text on your device and uploads nothing; its language models come with the app or are downloaded once from auradoc.ai and kept on the device.
- Sign-in — the basic editing features need no account. To sign in, the apps open the AuraDoc sign-in page in your system browser, protected with PKCE, and our servers then give the app a session for your account. The editor reads your name, email address, plan and usage balance from our servers to show which tools you can use.
- Where the session is kept — on Windows and macOS the session tokens are stored in the operating system's keychain (Windows Credential Manager, macOS Keychain); on Android they are encrypted with a key held in the Android Keystore. In the browser, the editor uses the same session as the AuraDoc website. Signing out removes the session from the device and revokes it on our servers.
- Autosave — so you can recover unsaved work if the window closes unexpectedly, the editor keeps a recovery copy of the open document and its edits in the local storage of the browser or app (IndexedDB) on your device. It is never uploaded, and it is deleted when you save, open another file or discard the recovery. Language and theme preferences are also kept in local storage.
- Updates — at start-up, the Windows and macOS apps ask auradoc.ai whether a newer version exists. The request carries only the platform, processor architecture and installed version, with no document or account data. An update is installed only after you accept it and only if its digital signature is valid.
- No tracking — the editor contains no advertising, analytics or crash-reporting component and sends no usage or diagnostic data. Our servers keep the access logs described in section 1 for the requests the editor makes to them.
- Deleting your data — to delete your account and the data kept on our servers, use the Privacy page of the AuraDoc dashboard (dashboard.auradoc.ai/dashboard/privacy) or write to contact@auradoc.ai; deletion follows section 6. Files saved on your device are not touched by this: you delete them yourself.
11. Changes to this policy
Material revisions are announced by email or by a notice on the platform before they take effect. The date of the latest revision is shown at the top of this page.