Back

Privacy Policy

Effective date: April 5, 2026 · Last updated: April 5, 2026

Irisbrige is an open-source iOS client plus a lightweight project website. This Privacy Policy describes the behavior that can be inferred directly from the current repository and this site implementation.

1. Information We Do Not Collect by Default

Irisbrige does not run its own account system, and the current codebase does not copy your personal profile or conversation data into a separate first-party application backend just to use the app. The repository does not include advertising SDKs or third-party analytics SDKs. By default, the project is not designed to collect from you through our own service:

your name, email address, phone number, or marketing profile
advertising identifiers or cross-app tracking data
extra copies of chat content uploaded only for analytics
location data unrelated to the Relay workflow itself

2. Data Stored Locally on Your Device

Irisbrige does store local state required for the mobile Relay workflow. Based on the current repository, that local state may include:

Device identity: a stable device_id and an Ed25519 private key, with the private key stored in the iOS Keychain.
Server and preference data: known Relay servers, selected server state, appearance settings, and transport settings stored in UserDefaults.
Thread cache and logs: per-server cached thread snapshots, recent directories, and log data kept on-device to restore history and support debugging.
APNs token snapshot: if iOS provides an APNs device token, the app may keep it locally until it can be synced to Relay.

3. Communication with Relay, edge, and Downstream Services

Irisbrige is meant to talk to the Relay environment that you configure or pair with. Pairing calls, challenge requests, authenticated WebSocket traffic, thread RPC calls, approval responses, and directory requests go to the Relay you selected. That Relay, its edge process, and any downstream Codex App Server may process data according to their own operational policies. You should review those environments separately.

4. Push Notifications and APNs

If you grant notification permission, iOS may provide an APNs device token to the app. In the current codebase, that token can be uploaded to Relay through an authenticated device endpoint. Whether APNs is actually enabled and how notification payloads are handled depends on the Relay or edge environment you connect to.

5. Site Hosting and Third-Party Platforms

This project site is built in a Cloudflare Workers-style structure and links to GitHub. If the site is deployed on Cloudflare, or if you click through to the repository or issue tracker, those platforms may process standard request metadata or visit data under their own policies. The site itself does not embed extra ad-tracking scripts.

hosting providers such as Cloudflare may process basic request metadata needed to serve the page
GitHub may process visit activity when you open the repository, issues, or source links

6. No Sale of Personal Data

Based on the current repository and this site implementation, the project does not implement an advertising network and does not contain logic to sell personal data to third parties.

7. Children's Privacy

This project is not specifically designed for children. If you need to use it in a regulated environment, you should separately evaluate whether your chosen Relay or edge deployment is appropriate.

8. Changes to This Policy

If the project's actual behavior changes in a material way, this policy should be updated to reflect the new boundaries and the effective date on this page.

9. Contact

If you have questions about this Privacy Policy, the recommended contact path is the public issue tracker for the repository:

GitHub Issues