← All notes

Privacy in practice

Before you install: a practical privacy checklist for Chrome extensions

Check permissions, stored data, deletion controls and publisher details before trusting a browser extension — with Jambu as a transparent example.

By Jambu3 min read

Painted illustration of a hand marking a paper checklist beside a laptop showing abstract privacy settings.

A reassuring tagline isn't enough to decide whether a browser extension belongs in your day. A better starting point is a short set of questions: what can it access, what does it actually keep, where does that information go, and how can you stop using it? The same questions should apply to Jambu.

1. Read the permissions before approving them

Google's installation guidance tells users to approve only extensions they trust. Some extensions show a permissions or data-access prompt when you add them. Chrome's developer documentation explains that developers declare permissions for extension features and that some permissions trigger warnings. See sources [1] and [2] below.

A permission describes access an extension may have; it does not, by itself, tell you everything the publisher stores or how the service uses it. Ask whether the requested access has a clear connection to the feature. This article does not inspect Jambu's extension code or certify its permissions, so check the current installation prompt rather than assuming a specific permission list from this page.

2. Separate access from collection and storage

Look for precise nouns in the privacy policy. 'We respect privacy' is less useful than a list of collected fields. For Jambu, the published policy says activity information is limited to the active domain, timestamps, session duration and idle state. The active domain is stored rather than the full URL. That is less granular, but a domain can still be sensitive information.

The policy says Jambu does not collect page contents, keystrokes, passwords, credentials, form inputs, private messages, screenshots or clipboard contents. Activity information is used for routine learning and intervention timing. These are the publisher's documented practices, not findings from an independent audit.

3. Find out where data lives

Don't assume that an extension's presence in your browser means everything stays on your device. Jambu's policy names Supabase for its database and authentication, and Render for API hosting. It does not define fixed retention periods. Those are material details to weigh, especially if a local-only tool is what you need.

4. Check your exit options

Google documents how to turn an extension off or remove it in Chrome's Manage extensions page. Disabling or uninstalling browser software is a different action from deleting information held by its service. Don't assume one automatically does the other.

  • Check whether you can pause the product without deleting your account.
  • Look for a data export option and a way to delete stored history.
  • Find the account-deletion option and read what associated data it covers.
  • If retention isn't specified, ask the publisher rather than inventing a deadline.

Jambu's policy provides for exporting data, deleting activity history and deleting your account and associated data at any time. It also offers pause and snooze controls. The early-access email list is separate: the policy says you can request removal through the privacy contact.

5. Look for an accountable publisher

Check that the product name, website and policy belong together, and that there is a contact for questions. Jambu is published by an individual, not a separate legal entity; the privacy contact is shubsara@gmail.com. Transparency about those facts is more useful than implying credentials or certifications that haven't been established.

A simple decision, not a perfect score

An illustrative decision might be: the feature is useful, the access is understandable, and the stored information fits your comfort level — or it doesn't, so you don't install it. Neither choice needs defending. On a work or school browser, check your organisation's rules too; Google notes that managed computers may block extensions.

Use this checklist to ask clearer questions, not to treat any extension as automatically safe. If a policy is vague or a permission unexplained, it is reasonable to wait for a satisfactory answer.

Sources & further reading

Curious about the details? Read how Jambu works or our privacy policy.

Build a healthier work rhythm.

Jambu is a Chrome extension, in public beta. Add it once and it starts learning your rhythm quietly.

Add to Chrome

Public Beta v0.1.0 · Care, not surveillance

Not on Chrome right now? Get early access by email.

No spam. Unsubscribe anytime. Your data stays yours.