Plural Browser Privacy Policy
Last updated: 20 August 2026 Effective date: 20 August 2026
This Privacy Policy explains what personal data we collect when you buy, activate, and use Plural Browser, why we collect it, and the choices you have. It describes how Plural Browser actually works.
1. Who we are (Controller)
Apt Stack Consulting LLC ("we", "us", "our") is the controller of the personal data described in this policy.
- Legal entity: Apt Stack Consulting LLC, a New Mexico limited liability company.
- Privacy contact: hello@aptstack.com
Our services are delivered through:
- pluralbrowser.com, marketing website
- app.pluralbrowser.com, account and billing dashboard
- api.pluralbrowser.com, the licence API the browser talks to
- Plural Browser, the desktop application (macOS and Windows)
2. Your browsing stays on your device
Plural Browser gives each tab its own isolated identity: separate cookies, storage, fingerprint, and proxy assignment. All of that lives locally, on your own computer.
We have verified this against our own source code:
- Your browsing profiles, cookies, local storage, saved fingerprints, and proxy assignments are stored on your device. They are not uploaded to, synced to, or stored on our servers. We do not have a copy of them and cannot see them.
- When the browser activates a licence, it sends us only three fields: your
client_id, yourclient_secret, and a hashed machine identifier (see §3). It does not send us your raw hardware ID, your browsing data, your proxy list, or your identities. - When the browser renews a licence, it sends only your current signed licence token. No browsing data is transmitted.
- We deliberately do not log successful activations or renewals as per-user activity, and we run no open/click tracking in our emails. We do not build a record of what you browse or when you use the product.
In short, we collect what we need to sell you a licence, bill you, and enforce one-device-per-licence, and not a profile of your browsing.
3. What we collect and why
3.1 Account and licence data
| Data | Purpose | Lawful basis (GDPR Art. 6) |
|---|---|---|
| Email address | Create your account, send your licence key, sign you in via magic link, provide support | Contract (Art. 6(1)(b)) |
| Organisation record (organisation name, your membership/role) | Associate your licence and billing with your account | Contract (Art. 6(1)(b)) |
| Hashed device/machine identifier: a one-way SHA-256 hash computed on your device; we never receive the underlying hardware identifier | Enforce our one-device-per-licence rule and let you manage/reset your device | Legitimate interests (Art. 6(1)(f)): preventing licence sharing / fraud |
| Licence activation records: activation timestamp, last-seen timestamp, device nickname (if you set one), activation status | Operate and enforce your licence; show your active device in the dashboard | Contract (Art. 6(1)(b)); legitimate interests (Art. 6(1)(f)) |
Licence key credentials: a public client_id and a stored HMAC hash of your client_secret (we do not store the secret in the clear) | Authenticate the browser to the licence API | Contract (Art. 6(1)(b)) |
To be precise about the hashed machine identifier: it is produced by hashing a platform identifier on your machine before anything is sent, so our activation records are not a hardware inventory. We hold a hash, not your device's real ID.
3.2 Subscription and billing data
| Data | Purpose | Lawful basis |
|---|---|---|
| Plan, subscription status, current billing-period end | Provision the right entitlements; manage renewals and access | Contract (Art. 6(1)(b)) |
| Stripe customer ID and subscription ID | Link your account to your Stripe subscription | Contract (Art. 6(1)(b)) |
| Billing event ledger (records of Stripe webhook events we process) | Reconcile payments; prevent duplicate/out-of-order processing; keep financial records | Legitimate interests (Art. 6(1)(f)); legal obligation (Art. 6(1)(c)) for tax/accounting |
Card data is handled entirely by Stripe. We do not receive or store your full card number, CVC, or expiry. Payment card processing happens on Stripe's systems. See Stripe's privacy policy: https://stripe.com/privacy.
3.3 Sign-in and security data
| Data | Purpose | Lawful basis |
|---|---|---|
| Magic-link sign-in tokens: stored only as a hash; single-use; short expiry | Let you sign in to the dashboard without a password | Contract (Art. 6(1)(b)) |
| Dashboard session identifiers: stored only as a hash of the session cookie | Keep you signed in to app.pluralbrowser.com | Contract (Art. 6(1)(b)) |
| Audit / event logs: records of security- and billing-relevant actions (e.g. licence denials, staff and billing changes). We do not log routine successful activations or renewals. Retained ~180 days, then automatically deleted. | Security, fraud prevention, support, and accountability | Legitimate interests (Art. 6(1)(f)); legal obligation (Art. 6(1)(c)) |
| IP address and standard request metadata at the API and websites | Processed at our infrastructure/edge layer (Cloudflare) to route, secure, and rate-limit requests and defend against abuse | Legitimate interests (Art. 6(1)(f)) |
Note on IP addresses: our own application does not store your IP address in our database as part of your account record. IP address and connection metadata are handled at the network/edge layer by our hosting provider (Cloudflare) as part of delivering and securing the service, and may appear in short-lived operational logs.
3.4 Marketing and download data
| Data | Purpose | Lawful basis |
|---|---|---|
| Email address you provide to download Plural from our website, or to receive updates | Deliver the download, and send product news, updates, offers, and service messages about Plural | Consent (Art. 6(1)(a)) |
To download Plural from pluralbrowser.com you provide an email address, and by doing so you agree we may email you about Plural, including product updates, offers, and other marketing, as well as service messages. We do not accept disposable or temporary email addresses. You can unsubscribe from marketing at any time using the link in any such email or by contacting us at hello@aptstack.com, and we will stop sending it; we may still send essential service messages relating to a purchase you have made.
We do not sell your data, and we do not use third-party advertising or cross-site tracking. We do not collect special-category (sensitive) data. Marketing emails are sent only with your consent, and you can opt out at any time.
4. Cookies
We keep cookies to a minimum.
- app.pluralbrowser.com (dashboard): an essential session cookie to keep you signed in. This is strictly necessary for the service and is not used for tracking or analytics.
- pluralbrowser.com (marketing site): the marketing site runs no scripts and uses no analytics or advertising cookies.
We do not use advertising cookies or cross-site tracking.
5. Who we share data with (processors / sub-processors)
We do not sell your personal data. We share it only with service providers ("processors") who help us run the service, under data-processing terms.
| Processor | What they do | Data involved |
|---|---|---|
| Stripe | Payment processing and subscription billing | Email, billing details, card data (held by Stripe, not us), subscription identifiers |
| Cloudflare | Hosting of our API and websites (Cloudflare Workers) and our database (Cloudflare D1); email routing/edge; edge security | All account/licence/billing data stored in our database; IP and request metadata at the edge |
| Resend | Transactional email delivery (licence keys, magic links), sent from notifications.pluralbrowser.com | Your email address and the contents of transactional emails |
We may also disclose data where required by law, to enforce our terms, or to protect our rights, users, or the public.
We do not sell personal data and do not "share" it for cross-context behavioural advertising as those terms are defined under California law (CCPA/CPRA).
6. International transfers
We process data in the United States. Our processors (Stripe, Cloudflare, Resend) may process data in the United States and other countries. Where personal data of individuals in the EEA or UK is transferred outside those regions, the transfer relies on our processors' standard safeguards, such as the EU Standard Contractual Clauses, where applicable.
7. How long we keep data
- Account, licence, and subscription data: for as long as your account is active, and afterwards as needed for our legitimate business and legal (e.g. tax/accounting) obligations.
- Audit / event logs: automatically deleted after approximately 180 days.
- Magic-link and session tokens: short-lived; expired and used tokens are cleared.
- Billing records: retained as required by applicable tax and accounting law.
When we no longer need your data, we delete or anonymise it.
8. Your rights
8.1 If you are in the EEA / UK (GDPR / UK GDPR)
You have the right to: access your data; correct it; delete it ("right to be forgotten"); restrict or object to processing; data portability; and to withdraw consent where we rely on it. You also have the right to lodge a complaint with your local supervisory authority.
8.2 If you are in California (CCPA / CPRA)
You have the right to: know what personal information we collect and why; access and delete it; correct it; and to opt out of sale or sharing. We do not sell or share your personal information, so there is nothing to opt out of. We will not discriminate against you for exercising your rights.
8.3 How to exercise your rights
Email us at hello@aptstack.com. We will verify your request (typically via the email address on your account) and respond within the timeframe required by law. You can also delete much of your account and device data yourself from the dashboard at app.pluralbrowser.com. Because your browsing profiles live only on your device, you can remove them at any time by deleting them locally; we never held a copy.
9. Children
Plural Browser is not intended for, and we do not knowingly collect data from, anyone under 18. If you believe a minor has provided us personal data, contact us and we will delete it.
10. Security
- Passwords do not exist in our system. We use magic-link sign-in and short-lived, hashed tokens, so there is no password store to breach.
- Sensitive values are stored hashed, not in the clear: session cookies, magic-link tokens, and licence secrets are all held as hashes; the device identifier is hashed on your machine before it reaches us.
- Card data never touches our servers; Stripe handles it.
- Access to administrative systems is restricted to authorised staff.
No system is perfectly secure, but we design to hold as little sensitive data as possible.
11. Data breach
If a breach affects your personal data, we will notify affected users and any relevant supervisory authority as required by law. To report a security concern, contact hello@aptstack.com.
12. Changes to this policy
We may update this policy. If we make material changes, we will update the "Last updated" date and, where appropriate, notify you by email or in the dashboard. Continued use of the service after an update means you accept the revised policy.
13. Contact us
Apt Stack Consulting LLC, a New Mexico limited liability company Email: hello@aptstack.com