Privacy Notice

The short version

Prots IntelliSense performs autocomplete locally. The licensing service does not receive text you type, screen contents, learned phrases, candidate lists, clipboard contents, or application-window contents. It receives only the small amount of account, entitlement, security, and billing data described below.

Controller and contact

The data controller is Maciej Wajda, operator of Prots. Contact support@prots-ai.com for privacy questions. Service address: Belgijska 6, 54-404 Wrocław, Poland.

Data used by the licensing website

• Automatic trial: Prots stores the first-use time, a random installation ID, a private random access credential, and a clock record on your PC, protected by Windows. It starts without an account or email. When online, it sends the credential, installation ID, app version, and first-use time to register the trial. The server stores keyed credential hashes, an encrypted recovery copy, installation hashes, and access dates. No hardware fingerprint is created.
• Purchase recovery: the email from the payment provider is normalized and HMAC-hashed, with a masked display such as m***@example.com. Prots stores that hash and display, not the raw address. Restoring access requires confirmation through that mailbox. For recovery and older email-based trials, the raw address exists in Worker memory and is passed to the transactional email provider for delivery.
• App-to-browser purchase: a single-use random link expires after 10 minutes. Opening it creates a secure, HTTP-only browser cookie lasting one hour, used only to connect checkout to your installation. The database stores hashes of these credentials and the matching access ID. Expired records are removed by scheduled cleanup within one day.
• Entitlement: a hash and final five characters of the license key, an AES-256-GCM encrypted recovery copy bound to the entitlement, accepted Terms/EULA versions and document hashes, plan, state, trial, beta, or paid-through dates, and a random entitlement ID. Encryption and hashing keys are held separately from D1.
• Browser sign-in: a random request ID, hashed desktop polling credential, hashed email code, send and verification attempt counts, and the matching account ID. Requests expire after 10 minutes; scheduled cleanup removes expired records within one day. The browser never receives the desktop credential or access key.
• Activation: a SHA-256 hash of a random installation UUID, app version during the request, timestamps, and whether the device was deactivated. No hardware fingerprint is created.
• Abuse prevention: Cloudflare Turnstile processes ordinary browser and connection signals to verify a short-lived challenge. Prots stores daily keyed hashes derived from the Cloudflare connection address for beta access, activation, refresh and deactivation limits and, for recovery, the normalized address hash, plus attempt counts. The raw connection address, raw email in the throttle table, and browser user-agent are not stored there.
• Payment: Stripe customer, subscription and Checkout session identifiers, payment state, paid-through date, accepted paid-document versions, offer currency/amount/interval, and acceptance/completion times. Card details are entered on Stripe and are not handled by Prots.
• Operational logs: Cloudflare and Stripe may process ordinary request, security, and delivery logs under their own processor terms.

Why it is processed

Entitlement and billing processing is necessary to provide the beta or paid service (GDPR Article 6(1)(b)). Fraud prevention, service security, and limited operational logging rely on legitimate interests (Article 6(1)(f)). Tax, accounting, and lawful requests rely on legal obligations (Article 6(1)(c)). Prots does not use licensing data for advertising or unrelated profiling.

Recipients and international transfers

Cloudflare hosts the site, database, anti-bot challenge, and release files. Stripe processes checkout, subscription management, tax-related checkout information, and payment events. The configured transactional-email provider processes the recipient address, message, delivery metadata, and ordinary security logs. The current adapter is for Resend; Resend states that even Ireland-dispatched mail has account metadata, logs, and API records stored in the United States. These providers may process data outside Poland or the EEA using the safeguards described in their data-processing terms, such as adequacy decisions or standard contractual clauses. No data is sold.

Retention

• Daily abuse-throttle entries: no longer than 30 days.
• Device activations: an installation becomes inactive after 30 days without a check-in, then its row is deleted no later than 30 days afterward; explicit deactivation starts that deletion period immediately.
• Webhook deduplication records: no longer than 24 months.
• Checkout consent that never completes: no longer than 30 days.
• Trial and open-beta entitlements: while access is administered, then only as long as needed for account recovery, disputes, abuse prevention, and binding legal duties.
• Billing records, if paid access opens later: while the subscription is administered, then only as long as needed for disputes and binding tax, accounting, or consumer-law duties.
• Application content and learned state: local on the user’s PC, under the user’s control.

Your rights

Subject to the GDPR, you may request access, correction, erasure, restriction, portability, or object to legitimate-interest processing. You may complain to the Polish supervisory authority, the President of the Personal Data Protection Office (UODO), or another competent EEA authority. Some records may need to be retained where law requires it.

Cookies and changes

Prots does not install advertising or analytics cookies in this build. Cloudflare Turnstile and Stripe may use strictly necessary security, checkout, and fraud-prevention storage. Transactional email tracking must remain disabled. Material changes will be dated here; a new acceptance will be requested when required.