Privacy Policy

Your document stays with you.

Local file processing. Online accounts and payments. Here is where that boundary sits, and what information crosses it.

Last updated: 8 November 2026

Files and purchase fingerprints

We remember an unlock, not a copy of your document.

The viewer reads and processes files on your device. It does not upload file bytes, file names, attachment names, document text or certificate details to our servers. Previews and downloads are made in your browser. Closing the file releases the viewer’s working resources; reloading the page requires selecting the file again. Files you download remain on your device until you remove them.

When you are signed in, the browser sends a SHA-256 fingerprint to check full access, unlock a file or authorise an export. For a detached P7S, the fingerprint identifies the signature and original together. Guest viewing does not send this fingerprint.

Our server converts the received fingerprint into a keyed HMAC-SHA256 value. A One file unlock stores that value with your account, format, payment reference and unlock or revocation dates. The raw SHA-256 is processed for the request, not stored in the unlock record. Pro access checks do not create a One file unlock record. The stored key identifies matching content; it is not a document backup or anonymous data. To restore access, choose the same file again while signed in.

Account and activity records

No document content does not mean no personal data.

An account holds your name, email, login identifier, password hash if you set a password, language, account status, plan and unlock balance, and registration and sign-in information including IP addresses and dates. If you use Google sign-in, we receive your verified email, Google identifier, name and available profile picture URL. Displaying that picture can contact Google’s image service.

For opening, unlocking and exporting, we record an account ID or guest identifier, IP address, time, originating page URL (including its query string), language, action, status and access level. Technical fields include format, container type, size, document/attachment/signature counts, page counts, processing time, warning and error codes, and export type and size. Signed-in activity can be associated with your account email in administration and reporting.

Authentication security records contain IP addresses, login/email or account identifiers, attempt types and times. Password recovery stores a hashed reset token and its expiry and use status. Server and application logs may contain request URLs, IP addresses and technical errors. Avoid putting personal information or document text in a URL.

If you email support, your email service sends us your address and the message you choose to send. Please send an error code and a short description, never your document or an unredacted screenshot.

Why we use these records

Access, billing, troubleshooting and protection against abuse.

Account, entitlement and purchase records let us provide the service you request and perform our contract with you. Security and operational records support our legitimate interests in preventing abuse, diagnosing failures and maintaining the service. Financial records may also be needed for applicable accounting, tax and legal obligations.

Access is determined automatically from account status, package limits, confirmed payments and matching unlocks. Contact us if you believe an access decision is incorrect. Optional analytics depends on the tags configured in Google Tag Manager; the current loading behaviour is described below and in the Cookies Policy.

Payments and service providers

Checkout is online, even though document processing is local.

Paddle is the Merchant of Record for Paddle purchases and handles checkout, payment details, tax and billing. We send account and purchase information needed to create checkout, and receive payment and subscription updates. Our records include checkout and provider references, amounts, currency, status, refund information, subscription dates and payment-event payloads. Card entry takes place in the provider’s checkout, not a UnwrapDoc card form.

The payment integration also supports Polar if selected by the operator. The provider is identified during checkout. Providers handle their own records under their privacy notices. Optional Google sign-in uses Google’s authentication service; recovery emails use the configured mail service.

Authorised administrators can access account, usage and payment records. Protected operational reporting can expose those records, including email and IP, to our connected management system. Hosting and email services process the data needed to run the site and support. Provider processing can occur outside your country, including outside the EEA; their notices describe locations and applicable transfer safeguards. This page does not promise EU-only storage.

Google Tag Manager and analytics

Analytics is separate from the server’s usage log.

When a Google Tag Manager container is configured, the site loads it and makes product events available to it: steps such as selecting a file, reaching a preview, seeing an error, starting checkout, confirming a payment and exporting. Event fields use format and error codes, counts, size bands, language, device category and page path. Our event code does not deliberately include file names, content, certificate details, email addresses or file fingerprints.

A request to Google still exposes network and browser information such as your IP address. Tags within the container can collect additional information and set cookies according to their configuration. The site currently has no built-in consent banner or analytics opt-out: a configured container loads immediately. With no container ID, the GTM snippets and product analytics script are absent. Removing cookies alone does not prevent future network requests.

How long information stays

Cookie expiry and database deletion are different things.

The viewer does not retain uploaded documents on the server because it does not upload them. The session cookie has a 30-day lifetime; guest and language cookies have a 365-day lifetime. Browser restoration and server session cleanup can affect when a session actually ends.

Authentication attempts older than 24 hours are eligible for occasional cleanup when new attempts are recorded. This is not a guaranteed 24-hour deletion deadline. Reset tokens expire for use, but their database rows are not automatically removed on expiry.

There is currently no automatic time-based purge for accounts, usage history, unlocks, checkout/payment events or credit records. They remain until separately removed; deleting an account through Settings does not erase these rows. No fixed retention period is currently published for support correspondence, hosting logs or backups. Contact us to ask about a particular record or request erasure. Payment providers apply their own retention rules, including legal recordkeeping.

Account deletion and your rights

Closing an account is not the same as erasing all its records.

Settings → Delete account marks the account as deleted, signs you out and prevents future password or Google sign-in. The account and related records remain for administration and payment reporting. Cancel a renewing subscription in the billing portal before deleting the account: deletion does not cancel it. For personal-data erasure, contact us separately.

Where the GDPR applies, you may request access and a copy of your data, correction, erasure, restriction of processing or portability where applicable, and object to processing based on legitimate interests. Where processing relies on consent, you can withdraw it without affecting earlier lawful processing. Rights have conditions and exceptions, including required legal recordkeeping. You can also complain to your local data protection authority.

Use the contact below for a privacy request. Describe the request and use your account email where possible; we may need to verify your identity. Do not attach a signed document as proof of identity. You can edit your name and language in Settings, and review your own activity, purchases and unlocks in your account.

Privacy questions?

Contact UnwrapDoc about the information described in this policy. Please keep documents and sensitive file contents out of your message.

contacts@unwrapdoc.com