Documents
Privacy Policy
Draft
Drafted by the product team; requires legal review before public launch. Version of October 31, 2026.
Summary
- In local mode (the default) your documents are processed in the browser and are never sent to our servers.
- In cloud mode and for AI, a file or text is sent only after your explicit action and deleted on our side after 60 minutes.
- We do not store file names or contents — neither in the database nor in logs.
- For the free plan limit we use a hash of device characteristics. The characteristics themselves never leave the browser.
- We use no third-party advertising or analytics scripts, and no third-party cookies without your consent.
1. Scope of this policy
This policy describes how the Lockpage service (website, web app and API, the "Service") processes user data. Data controller: [legal entity name, registration number, address] — to be specified before public launch. Data questions: support@lockpage.tools.
2. Your documents
Local mode
The file you choose in a tool is read into the browser tab's memory and processed on your device. Its contents and name are not sent to the server. Before you download the result, the browser sends us only operation metadata: tool, mode, page count and size in bytes. We need them for the usage limit and the activity log.
Cloud mode
On paid plans you can turn on cloud processing for a single operation. Before uploading, the interface warns you about the transfer. Source files are deleted right after processing, the result after 60 minutes from job creation, or earlier if you delete it yourself. The database keeps a service record of the job: tool, status, number and size of files, time. It contains no file names.
AI tools
For AI summary and document chat, the browser extracts text from the selected pages and sends only the text to the server. We pass it to the model provider (see section 7) and store neither the text nor the answer; only the text length is logged.
API
When you call the API, files are sent to the server by definition. They are processed in memory, never written to disk and not kept after the response. We record the number of documents, data volume in bytes and request status to calculate cost (100 documents per month free).
3. What data we process
| Data | Purpose | Retention |
|---|---|---|
| Email, name, password hash | Account, sign-in, invoices | As long as the account exists |
| Plan, subscription status, Stripe customer ID, invoices | Payments and access to features | As long as the account exists; invoices as required by accounting law |
| Team, roles, invitations (token hash) | Business plan features | As long as the team exists |
| Device hash, IP subnet (/24 or /48), period, document count | Free plan limit, abuse prevention | As long as needed for the limit, up to 13 months |
| Anti-fraud service signals (device hash, subnet, event type) | Detecting automated requests | 7 days |
| Activity log: action, tool, mode, pages, size, subnet | Security, reports for team admins | 12 months |
| Ad impressions: creative, time, one-time token | Confirming a view before download | 90 days |
| API keys (hash and prefix), API usage | API access and billing | As long as the key exists; usage as required by accounting law |
| Enterprise requests: name, email, company, message | Replying to your request | 24 months or until you ask us to delete it |
We do not store full IP addresses — only the subnet. We do not process special categories of data, except when you send them yourself in cloud mode or to AI; such data is deleted within the periods in section 2.
4. Device hash
The free plan gives 2 documents per day per device. The limit is counted per device, not per email, so it can't be bypassed by creating new addresses. To do this the browser computes a SHA-256 hash of device characteristics: canvas rendering output, graphics adapter vendor and model (WebGL), audio context parameters, CPU core count, memory size, screen parameters, time zone and installed fonts.
- The characteristics are processed only in the browser; only the resulting hash is sent to the server.
- The characteristics cannot be recovered from the hash. We do not use third-party fingerprinting services.
- The hash is used only for the free plan limit and abuse prevention: not for advertising, profiling or tracking on other sites. It is not shared with third parties.
- If many requests from different devices come from one network, the browser may receive a computational task (Proof-of-Work) for a few seconds. It does not block access.
- Retention: as long as needed for the limit, up to 13 months.
For users in the EU/EEA and the UK, access to information on the device is governed by Art. 5(3) of the ePrivacy Directive and PECR. The consent flow and an alternative way to count the limit for those who decline will be finalized before the EU launch. [Requires legal review.]
5. Cookies
We use cookies as follows:
authjs.session-token— a signed session token after sign-in, up to 30 days;authjs.csrf-tokenandauthjs.callback-url— protection of sign-in forms and returning you to the right page, for the session.
Optional analytics cookies are only set if you accept them in the cookie banner; you can change your choice at any time via "Cookie settings" in the footer. We use no advertising or third-party tracking cookies.
6. Advertising
There is no advertising on the site right now. If we turn it on, creatives will be our own or from direct partners and hosted on our servers. Third-party ad networks, pixels and trackers are not used, and there is no targeting based on your data.
7. Subprocessors
| Company | What it does | Data it receives |
|---|---|---|
| Stripe, Inc. | Payments, subscriptions, invoices | Email, name, card details (entered on Stripe's side), order amount and items |
| Anthropic, PBC | Claude model for AI summary and chat | Only the extracted document text and your questions, when you run an AI tool |
| Vercel Inc. (hosting) and Neon (database) | Hosting the Service and the database | Account and service data from section 3; temporary cloud mode files |
Deletion of text on Anthropic's side is governed by its commercial API terms and our agreement; we guarantee deletion on our side. The final list of subprocessors and storage regions will be confirmed before launch. [Requires founder and legal review.]
8. Your rights
- Get information about the data we hold about you and a copy of it.
- Correct inaccurate data — in profile settings or via support.
- Delete your account — in settings. Deleting the account also deletes the subscription, API keys and account-linked counters. Invoices are kept for the period required by law.
- Withdraw consent, object to processing, or restrict processing.
- Lodge a complaint with a supervisory authority: in the EU/EEA your national data protection authority, in the UK the ICO; California residents have rights under the CCPA/CPRA.
Send requests to support@lockpage.tools. We reply within 30 days.
9. Data security
Passwords are stored as bcrypt hashes, API keys and invitation tokens as SHA-256 hashes. Connections are encrypted with TLS. Database access is restricted. More about the architecture on the Security.
10. Children
The Service is intended for professional use and is not designed for people under 16.
11. Changes
We will notify you of material changes by email and on this page at least 14 days before they take effect.