Privacy Policy

The short version

We do not receive your code. The analysis runs in your browser. There is no upload endpoint and no server-side processing of your files. You can verify this yourself: open your browser's developer tools, go to the Network tab, filter to requests that are not to this domain, and use the Service. The list will be empty unless you have opted in to advertising.

We set no tracking cookies, run no analytics, and use no advertising identifiers by default.

What is processed about you is limited to what any website hosted behind Cloudflare necessarily processes: your IP address, at the network edge, for the purpose of routing your request and applying rate limits. See §3.

1. Scope and who we are

This Policy describes how ContextBridge ("we", "us") handles information in connection with the ContextBridge Service. It applies to the website and the client-side application. It does not apply to third-party services you choose to send generated documents to — those are governed by their own policies, and you should read them, because they are AI providers that may retain and train on what you submit.

For the purposes of Vietnam's Law No. 91/2025/QH15 on Personal Data Protection (in force 1 January 2026) and Decree No. 356/2025/ND-CP, and of the EU GDPR where it applies, we are the data controller for the limited personal data described in §3. Contact: hello@contextbridge.app.

We have not appointed a data protection officer because we process no personal data beyond the technical data described below and employ no staff for that purpose. Where a jurisdiction requires a named contact, the address above serves that function.

2. Information we do NOT collect

This list is as important as the list of what we do collect, because it defines the boundary of the product.

• Your source code. Never transmitted. Parsed locally by WebAssembly in your tab.
• Your file contents, file names or directory structure. Never transmitted. They appear only in documents generated in your own browser, which leave your machine only if you choose to download, copy or share them.
• Your queries. The question you type to scope a bundle is used to rank files locally. It is never sent anywhere.
• Accounts, because there are none. No name, no email address, no username, no password.
• Tracking cookies, advertising identifiers, or cross-site identifiers. None are set by us.
• Analytics. We run no analytics product, first-party or third-party, by default.
• The contents of documents you send to AI providers. That happens between your browser and them. We are not in the path and have no visibility of it.

3. Information that is processed, and why

Operating any website requires some technical processing. This is all of it:

(a) IP address and connection metadata, by Cloudflare. The Service is hosted on Cloudflare Pages. To route your request, Cloudflare necessarily processes your IP address, the requested URL, a timestamp, your user-agent string and the referring page. This is standard for every website behind Cloudflare and is not something we can disable while using their infrastructure. Cloudflare processes it as our infrastructure provider under its own terms and privacy policy.

(b) Rate-limit counters. To enforce the fair-use limits in our Terms, we maintain short-lived counters keyed by a hashed form of your IP address combined with the network's autonomous system number. Counters are stored in Cloudflare KV with a time-to-live and expire automatically.

(c) Strictly necessary local storage. Your browser's localStorage holds two values, both set by your own actions and neither transmitted to us: your language preference, and your advertising opt-in/opt-out choice.

(d) Voluntary support and outbound links. If you click a support link (Ko-fi, GitHub Sponsors, Open Collective) or an affiliate link, you leave the Service and the third party's privacy policy applies. We receive no personal data from that click. Referrer information is limited by our Referrer-Policy to the origin only.

• *Purpose:* delivering the site; preventing abuse; applying rate limits.
• *Legal basis:* legitimate interests — the Service cannot function otherwise (GDPR Art. 6(1)(f)); under Vietnamese law, processing necessary for the performance of a service you have requested.
• *Our access:* we do not receive raw visitor logs. Aggregate request counts are visible in our Cloudflare dashboard.
• *Purpose:* keeping a free service free, by preventing automated abuse.
• *Legal basis:* legitimate interests (GDPR Art. 6(1)(f)).
• *Retention:* the hourly counter expires after 1 hour; the daily counter after 24 hours. Nothing is retained beyond that. We do not export, join or analyse these counters.
• *Why a hash:* the counter needs to distinguish one source from another. It does not need to know your address, so we store a keyed digest rather than the address itself.
• *Purpose:* remembering a choice you made, so the site does not ask again.
• *Legal basis:* strictly necessary storage, which is exempt from consent requirements under the EU ePrivacy Directive and equivalent regimes.

3A. Optional cross-device transfer: encrypted, ephemeral, off by default

Nothing is transferred unless you explicitly ask. The application has no sync, no cloud save and no background upload. What follows runs only when you press "Continue on another device" and copy the resulting link.

When you do: the session — an analysis report containing file paths, symbol names, line ranges and dependency edges, not file contents — is compressed and encrypted on your device with AES-256-GCM, using a key generated on your device. The ciphertext is stored under a random 128-bit identifier for at most 14 days, after which it is deleted automatically.

If you never use this feature, none of the above happens, and the only processing remains what §3(a)-(c) describe.

• The decryption key is placed in the URL fragment (after the #). Fragments are not sent to servers, do not appear in server or CDN logs, and are not included in referer headers. We never receive the key.
• What we can see: that a blob exists, its size, its identifier and its expiry. What we cannot see: its contents, which project it describes, or which languages it covers.
• The link is the credential. Anyone holding it can decrypt the blob, which is why the interface offers "delete from server" and why you should send it only through channels you trust. Deleting it, or waiting out the 14 days, destroys it.
• Restoring on another device fetches the ciphertext and decrypts it locally. At no point does plaintext exist on our infrastructure.

4. Advertising — disabled by default

No advertising is loaded unless you opt in. This is a deliberate design decision, not a configuration accident: an advertising script is a tracker, and a tracker on this page would contradict the central claim the product makes.

If advertising is enabled and you have opted in:

Our stated preference is for advertising that does not use behavioural tracking or cross-site identifiers — content-targeted networks such as EthicalAds, or self-hosted house placements. If we cannot fund the Service that way, we will say so here rather than quietly adopting trackers.

• The opt-in is an explicit action recorded in your browser's localStorage. Absent that record, no third-party script is requested at all.
• The opt-out is a single action, is persisted, and stops all third-party requests on subsequent visits.
• Our Content-Security-Policy is updated before any provider is enabled, and the specific origins permitted are listed in that policy, which you can read in the page source.
• We will name the provider on this page before enabling it. At the time of writing, no provider is enabled and no advertising origin appears in our Content-Security-Policy.

5. Cookies

We set no cookies. Not first-party, not third-party, not session, not persistent. The Service uses localStorage for the two preferences described in §3(c) because, unlike cookies, they are not attached to any request and therefore cannot be read by an intermediary.

Cloudflare may set cookies necessary for the security and operation of its network, as described in its own privacy policy. Those are outside our control and are not used for our purposes.

See the Cookie Policy for the full table.

6. Children

The Service is a developer tool and is not directed at children. We do not knowingly collect personal data from anyone under 13 (or the equivalent minimum age in your jurisdiction), and because we collect no personal data beyond §3, there is no dataset from which such information could be retrieved.

If you believe a child has provided us personal data, contact us and we will delete it.

7. International transfers

The Service is hosted on Cloudflare's global network. Requests are served from the data centre nearest to you, and Cloudflare's processing may involve transfers between jurisdictions.

Because the only personal data involved is the technical data in §3, and because your source code is never transmitted at all, no transfer of substantive personal data arises from using the Service.

Where Vietnamese law requires an impact-assessment dossier for cross-border transfer of personal data of Vietnamese citizens, our position is that the data described in §3 is technical connection data processed by our infrastructure provider under its own compliance programme; we have not created a separate dossier because we hold no such dataset. This is a judgement call and is flagged in docs/LEGAL.md as one to confirm with Vietnamese counsel.

8. Your rights

Depending on where you live, you may have rights of access, rectification, erasure, restriction, objection, and data portability, and rights in relation to automated decision-making.

In practice, for this Service, most of these are satisfied by the architecture rather than by a process:

To exercise any right, or to ask a question, write to hello@contextbridge.app. We will respond within 30 days.

You also have the right to lodge a complaint with your local data protection authority. In Vietnam, that is the Cyber Security and High-Tech Crime Prevention Department of the Ministry of Public Security. In the EU, your national supervisory authority.

• Access / portability: the only data we hold about you is a short-lived rate-limit counter, which is not meaningfully portable. Everything you produced is already on your machine.
• Erasure: counters expire automatically within 24 hours. Your language and advertising preferences are in your browser's localStorage and you can clear them at any time via your browser settings, or with one click in the application.
• Objection: you may object to the legitimate-interests processing in §3(b). The practical effect is that we would exempt your address from rate limiting, which we will do on request where it does not expose the Service to abuse.
• Withdrawal of consent: advertising opt-in can be withdrawn at any time and takes effect immediately.

9. Security

We apply controls proportionate to what we hold, which is close to nothing:

No system is perfectly secure. If you identify a vulnerability, please report it to the address on our security page rather than exploiting it.

• A Content-Security-Policy that permits no third-party origin by default, so a compromised dependency cannot silently exfiltrate data.
• No server-side code that handles your input, which removes an entire class of injection vulnerability from the data path.
• Transport encryption (TLS) enforced by Cloudflare for all requests.
• Client-side rendering that escapes all user-derived strings, so a maliciously named file in a repository you analyse cannot execute script in your browser.
• Dependency auditing in continuous integration.

10. Data breaches

Given that we hold no substantive personal data and no user content, the realistic breach scenario for this Service is limited to the technical data in §3 and to the integrity of the client-side bundle.

Notwithstanding that, we commit to the following: if we become aware of a breach affecting personal data we control, we will assess it, notify the competent authority within 72 hours of detection where Vietnamese Law 91/2025/QH15 or the GDPR requires, and notify affected individuals where the breach is likely to result in a high risk to their rights and interests.

If the client-side bundle were ever compromised — that is, if we shipped code that transmitted user data — we would treat that as a breach, disclose it here and in the changelog, and describe the affected versions.

11. Retention

We do not maintain any long-term dataset about users of the Service.

• Rate-limit counters: 1 hour and 24 hours respectively, then automatically deleted.
• Language and advertising preferences: in your browser, until you clear them.
• Generated documents: in your browser's memory, until you close the tab. Never persisted by us.
• Visitor logs: held by Cloudflare under its own retention schedule. We do not retain copies.

12. Changes to this Policy

If we change this Policy in a way that materially expands what we process, we will update the date at the top of this page and, where practical, display a notice in the application before the change takes effect.

We will not enable advertising, analytics or any third-party script without first amending this Policy and, where required, obtaining your consent. That commitment is the reason the advertising default is off.

13. Contact

Data protection questions and rights requests: hello@contextbridge.app

Abuse and legal process: abuse@contextbridge.app

Please write in English or Vietnamese. We will respond within 30 days.