diff --git a/docs/privacy/index.html b/docs/privacy/index.html new file mode 100644 index 0000000..76cf148 --- /dev/null +++ b/docs/privacy/index.html @@ -0,0 +1,313 @@ + + + + + + OpenCode Mobile — Privacy Policy + + + + +
+

OpenCode Mobile — Privacy Policy

+

+ Effective date: 2026-05-24  |  + Operator: VIBE TECHNOLOGIES, LLC  |  + App: OpenCode Mobile (cc.agentlabs.opencode) +

+
+ +
+ Summary: OpenCode Mobile does not collect your code, prompts, AI responses, + server URLs, or any chat content. All AI traffic goes directly from the app to your own + opencode server. We use Sentry only for anonymous crash diagnostics, and only with your + consent. +
+ +

1. Who We Are

+

+ OpenCode Mobile is developed and distributed by VIBE TECHNOLOGIES, LLC, + a Washington State limited liability company.
+ Address: 519 S Henderson St, Seattle, WA 98108-4522, USA
+ Contact: support@vibebrowser.app +

+

+ The app is open-source (MIT license). Source code: + github.com/dzianisv/opencode-mobile. +

+ +

2. Data We Do NOT Collect

+

+ We want to be explicit about what we never collect, transmit to our servers, or share with + third parties: +

+ +

+ All communication between the app and your AI coding agent travels directly between your + device and your self-hosted opencode server. VIBE TECHNOLOGIES, LLC never sees this traffic. +

+ +

3. Data We Do Collect (Crash Diagnostics)

+

+ With your explicit consent (shown at first launch), we collect anonymous crash diagnostic + data via Sentry to help us identify and fix bugs. +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Data typeWhat is capturedWhat is NOT captured
Device infoDevice model (e.g. "Pixel 7"), OS version, screen resolution, app versionDevice serial number, IMEI, advertising ID
Crash / error reportsStack traces, exception types and messages, source file names and line numbersVariable values at time of crash, no user data in scope
BreadcrumbsScreen names and function call sequence leading to the crash (e.g., "navigated to session screen")Message bodies, server URLs, prompt text — all stripped before upload by our URL-scrubbing filter
App version and buildVersion string and build number—
+ +

+ URL scrubbing: before any event is sent to Sentry, our code strips all server URLs, + authentication tokens, and query parameters. Stack traces are checked for embedded URLs. + No server hostname or port number ever leaves your device via Sentry. +

+ +

4. Consent and Control

+

+ Crash reporting is opt-in and off by default. The first time you launch + the app you will see a consent prompt. You can change this at any time: +

+ + +

5. Third-Party Services

+

+ We use one third-party service for diagnostics: +

+ +

+ We use no advertising networks, analytics platforms, social SDKs, or any other + third-party data collection services. The app contains no ads and no ad SDKs. +

+ +

6. Data Retention

+

+ Crash reports sent to Sentry are retained for approximately 90 days, after which they are + automatically deleted per Sentry's retention defaults. +

+

+ We do not operate our own servers that store your data; there is no VIBE TECHNOLOGIES + back end involved in normal app usage. +

+ +

7. Your Rights

+

+ You have the right to: +

+ +

+ Residents of the EU/EEA/UK may exercise rights under GDPR/UK GDPR. California residents + may exercise rights under the CCPA. To do so, contact us at the email above. +

+ +

8. Children

+

+ OpenCode Mobile is a developer tool intended for users aged 18 and over. We do not + knowingly collect any data from children under 13 (or under 16 in the EU). If you believe + a child has submitted data, please contact us and we will delete it promptly. +

+ +

9. Security

+

+ All diagnostic data is transmitted over HTTPS (TLS 1.2+) to Sentry. We do not transmit + any data over unencrypted connections. Your opencode server traffic uses whatever transport + security your server provides — we recommend HTTPS for all self-hosted deployments. +

+ +

10. Changes to This Policy

+

+ If we make material changes to this policy, we will update the effective date at the top + of this page and, where feasible, notify users via an in-app notice. The latest version + is always available at: + + vibebrowser.app/opencode-mobile/privacy + +

+ +

11. Contact

+

+ VIBE TECHNOLOGIES, LLC
+ 519 S Henderson St
+ Seattle, WA 98108-4522
+ USA
+ Email: support@vibebrowser.app +

+ +
+ +

Apple-Specific Addendum (iOS / App Store)

+

This addendum addresses Apple's specific privacy disclosure requirements for iOS apps distributed through the Apple App Store.

+ +

App Tracking Transparency (ATT)

+

OpenCode Mobile does not use Apple's App Tracking Transparency (AppTrackingTransparency) framework. The app does not:

+ +

No ATT permission prompt is ever shown to users because there is nothing to track.

+ +

Apple Privacy Nutrition Label Data Categories

+

The following maps our data practices to Apple's official App Privacy categories (as required in App Store Connect):

+ + + + + + + + + + + + + + + + + +
Apple CategoryCollected?Linked to identity?Used for tracking?
Contact InfoNoN/ANo
LocationNoN/ANo
Identifiers (Device ID)Yes (Sentry anonymous ID, with consent)NoNo
Diagnostics — Crash DataYes (Sentry, with consent)NoNo
Diagnostics — Performance DataYes (Sentry, with consent)NoNo
All other categoriesNoN/ANo
+

App Store Connect summary: Data Linked to You: None. Data Not Linked to You: Crash Data, Performance Data (when user consents). Tracking: No.

+ + + + +