Built to protect context,
not collect your life.

1. Who we are

PreOops is provided by Erwin Bogaert, Belgium. You can reach us at [email protected] or [email protected].

2. What the extension processes

To warn you before things get mixed up, PreOops builds a local picture of your contexts. Depending on how you use it, it may process:

• Contexts you create — names, colours and optional nesting (e.g. “Work › Client A”).
• Linked signals — the associations PreOops learns or you confirm: website addresses, specific documents (like a Google Doc or Drive folder), repositories, account identifiers (e.g. an email address or username you use to sign in), filenames, recipients and keywords.
• What you act on — when a check runs, it looks at the page address, the filename of a file you attach, the recipient of a message, the account in a login field, or which context text was copied in. These are compared to your signals locally.
• Settings and feedback — strictness level, protection toggles, pause state, and whether you chose “continue anyway” or “cancel” on a warning.

Processing means matching against your signals on your device. PreOops does not run recognition on a server.

3. What is stored, and where

• On your device — contexts, learned signals, suggestions, your activity log and settings are stored in the extension’s local storage.
• Session only — the clipboard source tag (which context a copy came from) and the warning cooldown live in session storage and disappear when the browser closes.
• Optional Chrome sync — if you enable “Sync across devices”, contexts and settings are stored in your Chrome sync storage, governed by your Google account. Activity, suggestions and session data are never synced.

We — the makers — do not operate a server that receives any of this data.

4. What we do NOT collect

• Passwords — PreOops looks at account and username fields to recognise which account you use; it does not read password fields, and no credential is ever transmitted.
• Authentication tokens or session cookies — the extension does not request access to them.
• Clipboard contents — it never stores or inspects what you copy, only the context it came from.
• Email or message contents — nothing you write is stored or uploaded.
• Your browsing history — there is no history upload; the extension only sees pages where it is enabled, to learn and to warn.
• Files — filenames may be checked; file contents are never opened, copied or transmitted.
• Browser session cloning of any kind.

5. Browser permissions, in plain language

• Storage — keep your contexts, signals and settings on your device.
• Active tab & scripting — show the status indicator and run checks on sites you enable.
• Context menus — the right-click “Link this site to a context” action.
• Tab groups — optional: tint tab groups with your context colour.
• Optional host access — off by default. PreOops asks per site, or for all sites only if you switch on “Run on every website”. You can revoke this in Chrome at any time.

6. Website analytics

This website does not use analytics or tracking cookies. We deliberately keep it that way: we can’t collect what we never ask for. If this changes, this policy will be updated before anything is enabled.

7. Payments

Paid plans are processed by Lemon Squeezy. When you purchase, the payment provider processes your payment details under its own privacy policy — PreOops never sees your card number. The extension itself is local-first: the only outbound request it makes is a licence check to Lemon Squeezy when you activate or re-verify Pro — that request carries only the key you pasted, never your content, history or files.

8. Data deletion

• Delete a single learned signal or suggestion in the dashboard.
• “Forget everything” per context removes all its signals and suggestions.
• The dashboard’s reset option clears all local data.
• Uninstalling the extension removes its local storage. Chrome-synced data can be removed via your Google account’s sync settings.

9. Chrome Web Store compliance

PreOops’s use of information received from Chrome APIs adheres to the Chrome Web Store Program Policies, including the Limited Use requirements: data is used only to provide the features described, never for advertising, never sold, and never transferred except via the optional Chrome sync you control.

10. Children

PreOops is a general-audience productivity tool and is not directed at children under 16.

11. Changes to this policy

If we change how data is handled, we will update this page and note the date above. Material changes will also be announced in the extension’s release notes.

12. Contact

Questions about privacy? Email [email protected]. For legal requests: Erwin Bogaert, Belgium — [email protected].