PRIVACY POLICY
Your account, explained.
Last updated October 7, 2026.
Docr’d is made by Relyt Works LLC (“Docr’d”, “we”, “us”). This policy explains what information we handle when you use the Docr’d website, web app, desktop app, and cloud services, why, who helps us process it, and the choices you have. We are the controller of the personal information described here. Questions are welcome at privacy@getdocrd.com.
The short version: the desktop app keeps your library on your computer and needs no account. If you choose cloud features, we store and process your documents to provide them. We do not sell your information, show ads, or use your documents to train machine-learning models.
What we collect
Account information
Your email address, the sign-in method you use (an emailed one-time code or, where offered, Apple or Google), sign-in and session records, and your plan and access status. If you sign in with Apple or Google, we receive your email address and a provider identifier from them; we do not receive your password. New accounts have no Docr’d password; if yours was created with one, our sign-in provider keeps it only in hashed form.
Your library
With cloud features, the documents you upload or sync, and what you create around them: annotations, notes, reading position, outlines, research maps, corrections, and library organization. Without an account, this stays on your computer and we never see it.
Usage and billing records
Counts of OCR pages against your allowance, the estimated cost of the cloud work your account requests (OCR, Ask, and research discovery) to apply fair-use limits, storage used, and the identifiers needed to match purchases to your account. Payment card details go directly to Stripe; we never receive them.
Technical information
Our hosting and sign-in providers process network information such as IP address, request time, and browser type to deliver and protect the service. Our own application logs are deliberately minimal and are designed not to record document contents, file names, or paths.
Messages
What you send us when you write to support.
How we use it, and our legal bases
- To provide the service you asked for (performance of our contract with you): signing you in, storing and syncing your library, running OCR and research requests, applying allowances and fair-use limits, and fulfilling purchases.
- To keep the service secure and reliable (our legitimate interests): preventing abuse, enforcing limits, debugging, backups, and recovery.
- To communicate with you (contract and legitimate interests): sign-in codes and notices about your account, billing, or changes to our terms. We do not send marketing email without your consent.
- To understand visits to our public website (your consent): optional Google Analytics, as described below.
- To meet legal obligations, such as tax and accounting rules and lawful requests.
We do not make decisions about you by automated means that have legal or similarly significant effects.
On this browser
Signing in stores session credentials in your browser’s local storage so you can return without entering a new code each time. An HTTP-only session cookie also authenticates requests to the app API. These are strictly necessary for authentication. Optional analytics cookies are used only with your permission, as described below; we do not use advertising cookies. Sign out when you finish on a shared device.
Website analytics
With your permission, Google Analytics measures visits and button clicks on the public website so we can understand which pages bring people to Docr’d. We send public page paths, page titles, the referring website’s origin, and fixed names for actions such as choosing to create an account or download the app. Google also receives technical information such as your IP address and browser and device details when your browser contacts it. We remove query strings and fragments from the page information we send.
We do not load Google Analytics before you allow it. It does not run on account, sign-in, payment, admin, or research workspace pages, or in the desktop or iOS apps. We do not send it account identifiers, email addresses, document contents, library activity, or search terms. Advertising features and Google signals are disabled.
We remember your choice in this browser and ask again after six months. If you allow analytics, its first-party cookies expire after six months. You can decline, or withdraw permission at any time using Analytics choices in the website footer. Withdrawing stops analytics and removes its cookies from this site. A browser that sends Global Privacy Control or Do Not Track keeps analytics off. Your choice does not affect access to Docr’d.
Google Analytics keeps user-level and event-level data for two months. Returning visits do not restart that retention period. Aggregate reports can remain available for longer.
Documents and cloud storage
Web PDFs are stored in a private Cloudflare R2 bucket. Supabase manages account identity. Railway runs the same library engine as the desktop app, with a separate persistent library for each account. Document files and consistent library backups are stored in R2. The API checks your identity before serving account data. The service validates PDF contents and can access uploaded files: web uploads are not end-to-end encrypted. Moving a document to Trash preserves it until you permanently delete it. Permanent deletion removes its current stored files and updates the cloud backup.
With cloud access, the web workspace and signed-in desktop exchange supported library records and managed files through cloud sync. The desktop library stays local until you sign in and connect an account with cloud access. Synced data is encrypted, and account recovery gives the service custody of the decryption key; this is not encryption that excludes the service operator.
Sync and device privacy
The sync relay receives account and library identifiers, random operation and blob identifiers, encrypted byte lengths, and request timing and access patterns. The service can recover the keys and decrypt synced content to restore your account and serve the web reader. Access to your email inbox, or to an Apple or Google account you sign in with, can therefore grant access to your synced library. Encryption does not protect content on an unlocked or compromised device. Signing out or revoking a session does not erase files already downloaded to a device.
Optional network features
When available, Ask requires your separate consent before sending questions and selected source text to OpenAI through Docr’d’s gateway. Building a semantic index sends text from PDFs and reconstructed blocks in the scope you choose; answering sends your question and retrieved excerpts, rather than the PDF files or images. Embeddings are cached in your library workspace and are not synced. Ask conversations (your questions, the answers and their cited excerpts) are saved in your library and sync like notes when sync is on; you can delete them individually or all at once. Drafting a synthesis cell uses the same consent and sends the theme’s name, the synthesis’s description and excerpts retrieved from that paper’s reconstruction; the draft is saved in your library as a suggestion with its cited excerpts and syncs with the synthesis. You can turn Ask off without affecting local reading, keyword search or export. Provider attempts count toward your plan’s fair-use limit, including failed attempts. OpenAI may retain API data for abuse monitoring under its API data policy.
Online metadata lookup is enabled by default and can be disabled in Settings. It sends document identifiers or a recovered title and byline to bibliographic providers, together with a contact email address that those providers ask for so they can reach the sender of a request; it does not send document bodies or evidence excerpts. When you are signed in, that contact address is your account email, and in the desktop app you can change it in Settings. This lookup is separate from cloud sync, so turning sync off does not disable it. Research discovery sends your search terms and paper identifiers, with the same contact address, to bibliographic providers.
If you run hosted OCR, the document is uploaded to our OCR compute provider, the pages you select are processed, and the results are returned; on the free tier we ask for your consent to remote processing first. If you configure your own remote OCR backend, the pages go to that backend under its terms. OCR does not run on your device.
Read aloud downloads its voice model once from Hugging Face and then runs on your device; document text is not sent to a voice provider. The desktop app checks for updates through Cloudflare. These requests reveal your IP address and the app or model version requested, not your library.
Error reports
The website, the web workspace, and released desktop and iOS apps send crash and error reports and sampled performance timings to Sentry so we can find and fix faults, and so do our servers: the library API, its backup job, the hosted OCR service, and the download service. A report contains the error and its stack trace, page or request timings, the app version, and browser, operating system or device details. The web workspace adds your account identifier, not your email address; server reports add neither. Reports do not include document contents, uploaded files, request bodies, search terms or other query strings, cookies, console output or screenshots, and folder paths are shortened so they do not name your user account. An error message may still quote a file name or other text it was handling. We do not use these reports for advertising or usage analytics.
Payments
Subscriptions and page packs are sold through Stripe Managed Payments using Stripe’s embedded checkout. Stripe is the merchant of record and an independent controller of the payment information you give it; its privacy policy applies to that information. We send Stripe your account identifier and store checkout, subscription, and order identifiers so purchases reach the right account. We do not receive card details. Saved-card changes open Link, Stripe’s order management service. Refund requests go to Link support, where Stripe reviews them under its refund policy. You can also email us for help or to ask us to issue a refund through Stripe, as described in our refund terms. Stripe may ask us for information about a request. We receive refund status from Stripe to update your purchase records and allowances.
Who processes information for us
We share information only with providers that help us run Docr’d, under contracts that limit their use of it, and when the law requires it:
- Supabase: account identity, sign-in sessions, service databases, and encrypted sync records.
- Resend: delivery of sign-in and account email.
- Apple and Google: sign-in, only if you choose them.
- Google Analytics: optional public-website visit and button-click measurement, after you consent, as described above. See Google’s privacy policy.
- Vercel: website and web app hosting.
- Railway: the library API and per-account library engine, and billing, allowance, and purchase records.
- Cloudflare R2: document files, sync data, and backups. Cloudflare also serves installer downloads and update checks.
- Cloudflare Turnstile: when you ask the website for a sign-in, sign-up, or recovery code, a check that the request comes from a person rather than an automated script. It sees your IP address and technical details of your browser, and is not used for advertising.
- Modal: compute for hosted OCR.
- OpenAI: optional Ask answers and embeddings after you consent, as described above.
- Hugging Face: the read-aloud voice model download, as described above.
- Sentry: crash and error reports and sampled performance timings, as described above.
- Stripe, including Link: payments, tax, receipts, transaction support, and refund review and processing, as described under Payments.
- Bibliographic providers such as OpenAlex, Crossref, DataCite, arXiv, Europe PMC, Semantic Scholar, Unpaywall, Open Library, Google Books, NASA NTRS, and the ASME, API, ISO, and IEC standards catalogs: metadata lookup and research discovery, as described above.
We do not sell personal information or share it for cross-context behavioral advertising. If the business is reorganized or sold, your information may transfer to the successor, which must continue to honor this policy; we will tell you beforehand.
International transfers
We and our providers operate primarily in the United States. If you use Docr’d from elsewhere, your information is transferred to and processed in the United States and other countries where our providers operate. Where required, we rely on recognized safeguards for those transfers, such as the European Commission’s standard contractual clauses in our providers’ data processing terms. You can request information about the safeguards that apply to your data and a copy of them by writing to privacy@getdocrd.com.
Retention and recovery
We keep account information while your account is open, and your cloud library until you delete its contents or your account. Removing a local download, pausing sync, or signing out does not delete the cloud copy. If a paid plan ends, we give at least 30 days’ email notice before deleting cloud content from an account that no longer has cloud access.
Deleted content can remain in encrypted disaster backups. We schedule disaster backups every six hours. Our recovery-point policy keeps the latest 4 successful recovery points, 7 daily, and 4 weekly recovery points. A deleted item can leave those backups only after no retained recovery point references it and backup cleanup completes. Cleanup runs after a successful backup, at most once per 24 hours; failed backups or cleanup can delay removal. These recovery-point counts are not a fixed maximum number of days after deletion, and backup retention currently has no guaranteed maximum duration.
Earlier synced versions remain until history cleanup can safely discard them. Cleanup runs only for libraries with history cleanup enabled and older sync clients no longer writing to them, so some libraries retain earlier versions for longer. When you delete your account in Account settings, we cancel any active plan, refund unused plan time and page packs through Stripe, and delete the account, its cloud library, and its sync history from our live systems right away; copies in encrypted disaster backups leave as described above. For a deletion request by email, we review the remaining cloud copies, sync history, and backups and explain any retention that still applies. Deleting content does not erase copies already downloaded to your devices. We keep billing and tax records for as long as the law requires, and minimal records needed to prevent abuse or resolve disputes.
Security
We use encryption in transit, encryption at rest with our storage providers, per-account isolation, short-lived signed access to files, and least-privilege service credentials. No system is perfectly secure. Independent security review and live backup-restore qualification are gates we are completing before general availability, and we will notify you and the relevant authorities of a breach affecting your information as the law requires.
Your choices and rights
You can use the desktop app without an account, turn off online metadata lookup, export your library, delete documents, cancel a plan, change your account email, delete your account, and sign out at any time. Email changes and account deletion are in Account settings.
Depending on where you live, including the EEA, the UK, and U.S. states such as California, you may have the right to access, correct, delete, or receive a portable copy of your personal information; to object to or restrict certain processing; to withdraw consent; and not to be discriminated against for using these rights. To exercise them, write to privacy@getdocrd.com from your account email address. We may need to verify that you own the account, and we respond within the time the law allows, normally within 30 days. You may also complain to your local data protection authority, though we hope you will let us try to help first.
Your browser may send a Global Privacy Control signal. We honor that signal by keeping optional website analytics off. We do not sell or share personal information for advertising.
Children
Docr’d is not directed to children, and you must be at least 16 to create an account. If you believe a child has given us personal information, contact us and we will delete it.
We store the date and declaration version when you confirm the account or purchase age requirement. We do not ask for or store your date of birth or identity documents for this confirmation.
Changes to this policy
We will post changes here with a new date. If a change materially affects how we handle your information, we will email you before it takes effect.
Contact
Relyt Works LLC, 1925 Lovett Avenue, STE 7 278, Bismarck, ND 58504, USA · privacy@getdocrd.com. For questions, or if you can’t change your email or delete your account in Account settings, write from your account email address. See also our Terms of Service.