Privacy policy

Written from the real data flows: what the desktop app sends, what this website collects, and what Creem handles because it sells the license.

Applies to Document Desk 0.2.0 · Updated 21 November 2026

1. In one table

What Where it goes Why
Your PDFs, their text, file names, folder paths, rules and exports Nowhere. They stay on your computer. Not collected
License key, random device ID, app version, timestamp The license service on jaredtao.com, forwarded to Creem To activate and verify your license
IP address and request metadata for the license service Cloudflare (hosting) and the rate limiter To keep the service up and abuse out
Website visits: IP address, user agent, requested URL Cloudflare To serve the site and protect it
Order and payment details Creem, as merchant of record To take payment, issue the receipt and the license key
Support emails you send The support mailbox, forwarded through Cloudflare Email Routing To answer you

2. The desktop application

Document Desk processes documents locally. Importing, hashing, text extraction, rule matching, review and export all happen on your Windows machine. The application does not upload your documents, their text, file names, folder paths, rules, hashes or exports, and it contains no analytics, no telemetry and no crash reporting in 0.2.0.

The only network request the application makes is license activation and verification, described next. If that request is blocked, document processing still works.

3. License activation and verification

When you activate or verify a license, the application sends exactly these fields to the license service:

The license service forwards that request to Creem, which issued the key, and returns only a status to your application. The service does not log license keys in plain text. It keeps a short-lived counter per IP address so that one client cannot flood it; those counters expire after about one minute.

Creem stores the license and activation records needed to run license keys: which key was activated, on which instance, and when. That is what makes the two-device limit work and what lets a revoked license stop working.

Why this is allowed: the request is necessary to perform the contract entered into by buying or activating a license. Keeping the service available and rate-limited is the publisher’s legitimate interest in protecting it.

4. This website

jaredtao.com is a static site hosted on Cloudflare. There is no server-side application behind the pages. Cloudflare processes standard request data — IP address, user agent, requested address, timestamp and similar technical fields — in order to deliver the pages and protect the site from abuse. Cloudflare acts as hosting provider and processes that data on the publisher’s instructions and under its own terms.

This site does not run analytics, advertising pixels, session recording or A/B testing, and it does not load fonts, scripts or images from third-party servers. There is no contact form: the site has no form that collects data.

The site’s pages are served from Cloudflare’s global network, so request data may be processed outside the country you are in.

5. Orders and payments

Creem acts as merchant of record for license sales. Creem takes the payment and collects the data needed to process it, including your name, email address, billing details and payment instrument. This site never receives your card number.

The publisher receives the order information Creem provides to sellers — typically the buyer’s email address, the product, the amount, the order reference and the license key issued — so that support questions, refunds and device seats can be handled. Creem’s own privacy policy governs the payment data it holds; ask support and the current version will be pointed out.

6. Email

If you email [email protected], the message, your address and anything you attach are received. Cloudflare Email Routing forwards the message to a mailbox. Please do not send customer documents or payment card details; they are not needed and would be stored in an ordinary mailbox.

7. How long records are kept

8. Who else is involved

Personal data is not sold, and it is not shared for advertising.

8a. Where data is processed

Cloudflare runs a global network and may process requests in the region nearest to you or in the United States. Creem processes payment and license data in the regions it uses as merchant of record. The support mailbox is hosted by Google. Where data moves from the EEA, UK or Switzerland to a country without an adequacy decision, the providers rely on standard contractual clauses or an equivalent transfer mechanism; ask support for the current mechanism if you need it for a specific transfer.

9. Your rights

Depending on where you live, you may have the right to ask what personal data is held about you, to have it corrected, to have it deleted, to object to a particular use, or to receive a copy in a portable format. Write to [email protected] and the request will be answered within the period the applicable law allows. You can also complain to your local data-protection authority.

Two limits are worth stating plainly: records Creem must keep as merchant of record cannot be deleted here — ask Creem for those — and a license key alone cannot identify you if you write from a different address than the one used at checkout.

10. Cookies

The product pages set no analytics or advertising cookies. Cloudflare may set strictly necessary security cookies while serving the site. The site-wide cookie notice has the detail.

11. Changes

If the data flows change — for example if a future version adds crash reporting or an analytics service — this page will be updated before that version ships, and the date at the top will change. The privacy policy for the version you are running is the one that applied when you installed it.

12. Contact

[email protected] — privacy requests, data questions and security reports.