Bridge1 Privacy Policy
Effective: August 24, 2026 · Last updated: August 31, 2026
Bridge1 is developed and published by Dojoit, Inc. ("Dojoit," "we," "us," or "our"). This Privacy Policy explains what information Dojoit collects when you download and use Bridge1, how we use it, and the choices you have. By downloading, installing, or using Bridge1, you agree to the practices described in this Policy.
Overview
Bridge1 is a downloadable desktop application that runs on your own computer. It works as a local gateway: it connects AI coding tools you already use (such as Claude Code, Claude Desktop, Codex CLI, OpenCode, Hermes Agent, and others) to AI models that run locally, on that same machine.
When you run models locally through Bridge1, your prompts, conversations, and model outputs stay on your own device. That content flows directly between your local AI client and the model running on your machine. Dojoit does not operate a server that receives, stores, or has access to it. This is the most important thing to understand about how Bridge1 handles your content.
If we later offer features that run models on our own servers rather than on your device, those features necessarily involve sending content to us to process. We will describe how that content is handled in this Policy before any such feature becomes available, and features of that kind will be clearly identified as cloud-based when you use them.
Information We Collect
We aim to collect only what we need to operate and improve Bridge1. The categories below describe what Dojoit's own infrastructure may receive:
Device and version information. When Bridge1 contacts our servers — for example to check whether a newer version is available, or to check for updated model catalog information — we receive technical details such as your app version, operating system, and hardware architecture (for example, macOS on Apple Silicon).
Log and connection data. Like most internet services, our servers automatically receive and may record standard connection information when your device contacts them, including your IP address and the date and time of the request. We use this to deliver responses, apply rate limits, prevent abuse, and keep our systems secure and reliable.
Beta activation. During Bridge1's early-access period, you may be asked to enter an invite code. Activating a device sends a randomly generated device identifier and the invite code you entered to our server. No email address or account is required to activate Bridge1.
Waitlist (optional). If you don't have an invite code, you may choose to join a waitlist to be notified when one becomes available. This collects the email address you voluntarily provide.
Feedback and bug reports (optional). If you choose to send us feedback or report a bug from within the app, we receive the message you write, along with basic technical details such as your app version and platform. If you opt in to attach diagnostics, we also receive a limited, redacted summary of recent request activity, such as timing and status. We do not receive the content of your prompts, conversations, or code through this feature, even when you opt in to attach diagnostics.
Where information described above is collected together — for example, a device identifier recorded alongside connection data — the resulting record may be capable of being associated with you indirectly, and we treat it as personal data accordingly.
Bridge1 does not require you to create an account or log in, and does not currently collect payment information. If we introduce a paid product or feature, we will describe any additional information collected, such as payment details handled by a payment processor, in an updated version of this Policy before that feature becomes available.
How We Use Information We Collect
We use the information described above to:
- Tell you when a Bridge1 update is available and deliver the correct version for your system;
- Provide updated model catalog information to the app;
- Operate the early-access invite and activation system;
- Notify you when an invite code becomes available, if you've joined the waitlist;
- Respond to feedback and bug reports, and diagnose, fix, and improve Bridge1; and
- Maintain the security, integrity, and reliability of our systems, including preventing abuse.
We do not use this information for advertising, and we do not use it to build a profile of you beyond what's needed for the purposes above.
We Do Not Train AI Models on Your Data
Dojoit does not use your prompts, conversations, code, or model outputs to train, fine-tune, or evaluate any AI model. This applies to everything Bridge1 routes.
Data Sharing and Disclosure
Dojoit does not sell your Personal Data.
We may share information described in this Policy with:
- Service providers. Third-party infrastructure and hosting providers, such as Cloudflare, that operate the servers behind our update, activation, waitlist, and feedback systems, and that process information on our behalf.
- Business transfers. In connection with, or during negotiations of, any merger, sale of company assets, financing, or acquisition of all or part of Dojoit's business, or in the event of a bankruptcy or similar proceeding.
- Legal requirements. Where we believe in good faith that disclosure is necessary to comply with a legal obligation, protect and defend our rights or property, investigate possible wrongdoing, protect the safety of our users or the public, or protect against legal liability.
- Affiliates. With any entity that controls, is controlled by, or is under common control with Dojoit.
Because content you process through locally running models never reaches our servers, that content is not available to us to share in any of the circumstances above.
Data Retention
We keep Personal Data for as long as reasonably necessary for the purposes described in this Privacy Policy, while we have a business need to do so, or as required by law (for example, for tax, legal, or accounting purposes), whichever is longer. In practice, for Bridge1 this generally means:
- Activation records are retained while the early-access activation program remains active. We delete them on request, and we expect to remove them after the program ends.
- Waitlist email addresses are retained until you redeem an invite code, ask us to remove you, or the waitlist closes, whichever happens first.
- Feedback and bug reports are retained indefinitely today, so we can act on them and spot patterns across reports; we delete them on request.
- Log and connection data, including the IP address a request came from, is retained for security, abuse-prevention, and reliability purposes. We have not yet set an automatic expiry on it; we delete it on request.
If you ask us to delete data we hold about you, we will remove it from our production systems; a copy may persist for a limited time in backups until those backups naturally cycle out.
Data Bridge1 stores on your own computer
Everything in this section stays on your machine. None of it is sent to us, and we cannot see it.
- Conversation content used for compaction. When a conversation grows near a model's context limit, Bridge1 summarises the earlier part so the chat can continue. To do that it writes the relevant conversation content to a file on your computer, in plain text, so a summary can be reused instead of regenerated. These files are stored in Bridge1's own application-support folder with owner-only permissions, are capped in age, count and total size, and are deleted automatically as newer ones arrive. You can delete them at any time from Settings → Storage in the app. Note that removing Bridge1 does not remove them: they live in
~/Library/Application Support/com.dojoit.bridge1/, and you can delete that folder yourself. - Model weights, engine binaries and caches. Downloaded models and the prefix caches that make repeat prompts fast are stored locally and can be reclaimed from the same Settings → Storage screen.
We mention this because the data is real and it is yours to manage, not because it leaves your computer. It does not.
Your Rights and Choices
You may ask us to access, correct, or delete the information described in this Policy by contacting us using the details below. Because Bridge1 doesn't use accounts, we'll ask for the relevant identifier — for example, your device identifier, visible in Bridge1's settings, or the email address you used to join the waitlist — so we can locate the right record.
You can decline to join the waitlist or send feedback at any time; both features are optional.
Depending on where you live, you may have additional rights under applicable law, such as the right to request a copy of your data, to object to or restrict certain processing, or to withdraw consent. If you are in the European Economic Area, the United Kingdom, or Switzerland, you also have the right to lodge a complaint with your local data protection supervisory authority.
Where we process Personal Data of individuals in the European Economic Area, the United Kingdom, or Switzerland, we do so on the basis of our legitimate interests in operating, securing, and improving Bridge1, to perform our agreement with you, to comply with legal obligations, or with your consent where required.
Children's Privacy
Bridge1 is intended for users aged 18 and older, as described in our Terms of Service. Our Service is not directed to children, and Dojoit does not knowingly collect Personal Data from children under the age of 13. If we learn that we have collected Personal Data from a child under 13, we will take steps to delete that information.
International Data Transfers
Dojoit is based in the United States. If you are located outside the United States, your Personal Data will be transferred to, stored, and processed in the United States and, for certain features, other countries where our service providers or their infrastructure operate. Where required by applicable law, we rely on appropriate safeguards for such transfers, such as the European Commission's Standard Contractual Clauses.
Security
We implement commercially reasonable technical, administrative, and organizational measures to protect Personal Data from loss, misuse, and unauthorized access, disclosure, alteration, or destruction. However, no Internet or email transmission is ever fully secure or error free, and we cannot guarantee absolute security.
Because content processed through locally running models is not stored on our servers, the security of that content depends primarily on your own device and the AI client and model backend you've configured. Securing your own machine is your responsibility.
Third-Party Services
Bridge1 works with third-party services you choose to use alongside it, and can retrieve resources from third parties on your behalf:
- Model downloads. When you set up a model, Bridge1 downloads model files directly from third-party sources such as Hugging Face or GitHub. Those providers receive your IP address and request details as part of serving the download, and their own privacy policies govern that. Model files you download are also subject to their own licenses.
- Client applications. AI coding tools you connect to Bridge1 are separate products with their own terms and privacy policies, and may independently contact their own vendors' servers.
We encourage you to review the privacy policy of any third-party service before using it.
Changes to This Policy
We may change this Policy from time to time. When we do, we will post the updated version on this page and update the "Last updated" date above, unless another type of notice is required by applicable law. We encourage you to review this Policy periodically.
Contact Us
If you have questions about this Privacy Policy or Bridge1's data practices, contact us at:
Dojoit, Inc. Attn: Legal 760 Newhall Drive #1054 San Jose, CA 95110 legal@dojoit.com