xieyao/opencode-mobile
1
0
Fork 0
Code Issues Pull Requests Actions 3 Packages Projects Releases Wiki Activity

docs+consent: disclose activation analytics honestly across consent modal, privacy policy, and store docs (#81)

Browse Source 
The app ships PostHog activation-funnel analytics gated behind the same
consent flag as Sentry, but the consent modal, Settings toggle, privacy
policy, and Play Data safety draft only mentioned crash reporting. Fix
the disclosure everywhere:

- TelemetryConsentModal: body + bullets + a11y labels now cover anonymous
  usage analytics (PostHog EU) alongside crash reports
- Settings: toggle renamed 'Crash Reports & Usage Analytics', description
  names both Sentry and PostHog
- Privacy policy (md + html + live gh-pages mirror): new section 3a with
  the full event/property table, PostHog EU destination, anonymous-ID
  statement, decline/revoke (drop-on-revoke) semantics; sections 4-7, 9
  and the Apple nutrition-label addendum updated for analytics
- play-listing.md: Data safety draft declares App interactions + Device
  or other IDs (opt-in, default OFF, shared with PostHog/Sentry)
- docs/playstore.md: Data safety row flipped to re-verify with pointer
  to the new design record
- docs/analytics.md: new design record — event schema, consent gating
  incl. buffered-event drop on revoke, disclosure surfaces to keep in
  sync, verification checklist (all TODO)
- website privacy page metadata mentions analytics opt-in

Closes #63


Claude-Session: https://claude.ai/code/session_01NJKAQ6HAikWGQK7PGZ5Y4E

Co-authored-by: engineer <engineer@gray-knight-m1.local>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Den
2026-07-17 03:28:00 -07:00
committed by GitHub
parent b52fa52a4c
commit 63f3ec3c7e
10 changed files with 569 additions and 75 deletions
Download Patch File Download Diff File Expand all files Collapse all files

54
distribution/play-listing.md
View File

@@ -73,12 +73,12 @@ Then open the app, tap Connect, paste your server URL, and you're in. Your AI co
OpenCode Mobile is MIT licensed. Source code, issue tracker, and community at github.com/dzianisv/opencode-mobile. Contributions welcome.
<b>PRIVACY</b>
OpenCode Mobile does not collect your code, prompts, or AI responses. All traffic goes directly from the app to YOUR opencode server — never through our infrastructure. Optional Sentry crash reporting collects only device model, OS version, and stack traces (no message content).
OpenCode Mobile does not collect your code, prompts, or AI responses. All traffic goes directly from the app to YOUR opencode server — never through our infrastructure. With your opt-in consent we use Sentry for crash diagnostics and PostHog for anonymous usage analytics (no PII, no message content, off by default). Diagnostic reports you share are also delivered to our support inbox.
Support: support@agentlabs.cc
Issues: github.com/dzianisv/opencode-mobile/issues
```
(3366/4000 chars)
(3474/4000 chars)
> Supersedes the prior draft, which named a dated model ("GPT-4") and was missing the directory picker and reasoning-effort features shipped since. Model references are now version-free by design ("Claude, GPT, Gemini, or any other model") so this copy doesn't go stale again as model names change.
@@ -162,10 +162,10 @@ Issues: github.com/dzianisv/opencode-mobile/issues
Suggested path: `https://dzianisv.github.io/opencode-mobile/privacy/`
Privacy policy must cover:
- What data is collected (Sentry crash diagnostics: device model, OS version, stack trace; no user content)
- How data is used (debugging crashes only)
- Third-party SDKs (Sentry — link to https://sentry.io/privacy/)
- Data retention (Sentry default 90 days)
- What data is collected (Sentry crash diagnostics: device model, OS version, stack trace; PostHog usage analytics: activation-funnel events with coarse properties; Chatwoot shared support reports: scrubbed diagnostic reports sent only when the user taps "Share Report"; no user content in any of them)
- How data is used (debugging crashes; measuring whether new users successfully connect/activate; responding to user-initiated support reports)
- Third-party SDKs (Sentry — https://sentry.io/privacy/; PostHog — https://posthog.com/privacy) and our own self-hosted Chatwoot support inbox (support.agentlabs.cc — not a third-party vendor)
- Data retention (Sentry default 90 days; PostHog standard retention; Chatwoot support conversations retained until resolved, then periodically purged)
- User rights (delete request via email, contact us)
- Contact: support@agentlabs.cc
@@ -176,20 +176,47 @@ Operator: VIBE TECHNOLOGIES, LLC, 519 S Henderson St, Seattle WA 98108-4522 USA
We do not collect your code, prompts, AI responses, server URLs, or chat history.
We collect (via Sentry SDK for crash reporting):
We collect, only with your opt-in consent (single toggle, default OFF):
Via Sentry SDK (crash reporting):
- Device model, OS version, app version
- Stack traces of crashes and unhandled errors
- App breadcrumbs (function names, screen names — no message bodies)
Data is sent to Sentry (sentry.io) and retained per Sentry defaults (~90 days).
Via PostHog SDK (anonymous usage analytics, EU region):
- Activation-funnel events: app_opened, connection_form_submitted,
connection_attempted, connection_succeeded, connection_failed,
message_sent, response_received
- Only coarse properties (e.g. mode=quick/advanced, error_class=timeout);
never server URLs, prompts, code, or raw error text
Via our own Chatwoot support inbox (support.agentlabs.cc), only when you tap
"Share Report":
- The same diagnostic report shown in the OS share sheet: connection
classification, probe results, device info, and recent app logs
- Every URL and every hostname/IP probed this session is redacted first —
your server address never reaches this inbox
- A random per-install identifier links follow-up reports into the same
support conversation; not linked to your name, email, or account
Data is sent to Sentry (sentry.io, ~90 days retention), PostHog
(eu.i.posthog.com, standard retention), and our Chatwoot instance
(support.agentlabs.cc, retained until the conversation is resolved and
periodically purged thereafter).
Third-party services:
- Sentry — crash reporting. https://sentry.io/privacy/
- PostHog — usage analytics. https://posthog.com/privacy
Data sharing: none beyond Sentry.
Self-hosted infrastructure:
- Chatwoot support inbox (support.agentlabs.cc) — we operate this
ourselves; it is not a third-party vendor.
Data sharing: none beyond Sentry, PostHog, and our own Chatwoot support inbox.
User rights:
- Email support@agentlabs.cc to request deletion of crash records associated with your device.
- Email support@agentlabs.cc to request deletion of crash records, analytics
records, or shared support-report conversations associated with your device.
Contact: support@agentlabs.cc
```
@@ -203,7 +230,7 @@ Google requires this before publishing. Answers for OpenCode Mobile current stat
| Question | Answer |
|---|---|
| Does your app collect or share any of the required user data types? | Yes |
| Is all of the user data collected by your app encrypted in transit? | Yes (HTTPS to Sentry) |
| Is all of the user data collected by your app encrypted in transit? | Yes (HTTPS to Sentry, PostHog, and our Chatwoot support inbox) |
| Do you provide a way for users to request that their data is deleted? | Yes — via support@agentlabs.cc |
### Data types collected
@@ -211,8 +238,9 @@ Google requires this before publishing. Answers for OpenCode Mobile current stat
| Data type | Collected? | Shared? | Optional? | Purpose | Encrypted in transit? |
|---|---|---|---|---|---|
| App crash logs (Diagnostics) | Yes | Yes (Sentry) | **Yes (opt-in, default OFF)** | App functionality, diagnostics | Yes |
| App performance / interactions | No | – | – | – | – |
| Device or other IDs | No | – | – | – | – |
| App interactions (App activity) | Yes | Yes (PostHog) | **Yes (opt-in, default OFF, same toggle)** | Analytics (activation funnel: app opened, connection attempted/succeeded/failed, message sent, response received) | Yes |
| Device or other IDs | Yes | Yes (Sentry/PostHog anonymous IDs) | **Yes (opt-in, default OFF)** | Diagnostics, analytics — random app-generated IDs, not linked to identity | Yes |
| User-submitted diagnostic reports (Diagnostics) | Yes | Yes (delivered to our own self-hosted Chatwoot support inbox) | **Yes (opt-in, default OFF, same toggle; also requires the user to manually tap "Share Report")** | Customer support — troubleshooting a connection failure or crash the user chose to report; server address always redacted first | Yes |
| Personal info (name, email, etc.) | No | – | – | – | – |
| Financial info | No | – | – | – | – |
| Health / fitness | No | – | – | – | – |

190
distribution/privacy-policy.html
View File

@@ -97,8 +97,9 @@
<div class="highlight-box">
<strong>Summary:</strong> 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.
opencode server. With your consent, we use Sentry for anonymous crash diagnostics, PostHog
for anonymous usage analytics, and — only when you tap &quot;Share Report&quot; — deliver a
scrubbed copy of that diagnostic report to our support inbox.
</div>
<h2>1. Who We Are</h2>
@@ -178,20 +179,153 @@
No server hostname or port number ever leaves your device via Sentry.
</p>
<h2>3a. Data We Do Collect (Usage Analytics)</h2>
<p>
With the same explicit consent (a single opt-in covers both crash reporting and analytics),
we collect a small set of anonymous usage events via <strong>PostHog</strong> to understand
whether new users successfully connect to their server and start using the app
(an "activation funnel").
</p>
<table>
<thead>
<tr>
<th>Event</th>
<th>When it fires</th>
<th>Properties</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>app_opened</code></td>
<td>Once per app session, after consent</td>
<td><code>is_first_open</code> (true/false)</td>
</tr>
<tr>
<td><code>connection_form_submitted</code></td>
<td>You tap Connect/Save with a server URL entered</td>
<td><code>mode</code> ("quick" or "advanced")</td>
</tr>
<tr>
<td><code>connection_attempted</code></td>
<td>A connection test starts</td>
<td><code>source</code> ("onboarding" or "edit_test")</td>
</tr>
<tr>
<td><code>connection_succeeded</code></td>
<td>The connection test succeeds</td>
<td><code>source</code></td>
</tr>
<tr>
<td><code>connection_failed</code></td>
<td>The connection test fails</td>
<td><code>source</code>, <code>error_class</code> (a coarse category such as "timeout" or
"unauthorized" — never the raw error text)</td>
</tr>
<tr>
<td><code>message_sent</code></td>
<td>You send a message to an agent session</td>
<td>—</td>
</tr>
<tr>
<td><code>response_received</code></td>
<td>An agent response finishes</td>
<td>—</td>
</tr>
</tbody>
</table>
<p>
What analytics events <strong>never</strong> contain: your server URL, hostname, IP address,
or port; prompts, messages, or AI responses; code or file contents; tokens or credentials;
raw error messages. Connection failures are reduced to a fixed list of coarse categories
before being sent.
</p>
<p>
Analytics data is sent to PostHog's <strong>EU region</strong> (<code>eu.i.posthog.com</code>)
and is identified only by a random, app-generated anonymous ID — not linked to your name,
email, or any account.
</p>
<p>
If you decline consent, no analytics is initialised and nothing is sent. If you revoke
consent later, analytics stops immediately and any events still buffered on the device are
discarded, not uploaded.
</p>
<h2>3b. Data We Do Collect (Shared Support Reports)</h2>
<p>
When a connection fails or the app crashes, you can tap <strong>Share Report</strong> to open
your device's normal share sheet with a diagnostic report. If you have granted the same
consent that covers crash reporting and analytics, a copy of that report is <em>also</em>
delivered directly to our support inbox, hosted on our own <strong>Chatwoot</strong> instance
(<code>support.agentlabs.cc</code>) — this is infrastructure we operate ourselves, not a
third-party SaaS vendor.
</p>
<table>
<thead>
<tr>
<th>Data type</th>
<th>What is included</th>
<th>What is NOT included</th>
</tr>
</thead>
<tbody>
<tr>
<td>Diagnostic summary</td>
<td>Connection classification (e.g. "server unreachable"), probe results, timing</td>
<td>—</td>
</tr>
<tr>
<td>Device info</td>
<td>Device model, OS version, app version</td>
<td>Serial number, IMEI, advertising ID</td>
</tr>
<tr>
<td>Recent app logs</td>
<td>Recent internal log lines (screen names, function-level breadcrumbs)</td>
<td>Message bodies, prompts, AI responses</td>
</tr>
<tr>
<td>Your server address</td>
<td>—</td>
<td>Never included — every URL and every hostname/IP the app probed this session is redacted before the report leaves your device</td>
</tr>
</tbody>
</table>
<p>
A random, per-install identifier (stored locally via secure device storage) links follow-up
reports from the same install into the same support conversation so we can reply to an
ongoing issue. This identifier is not linked to your name, email, or account — we only learn
contact details if you volunteer them in your own reply.
</p>
<p>
Sharing a report is always a manual, explicit action — it is never sent automatically or in
the background. It is only delivered to the support inbox if you have granted consent; if you
decline or revoke consent, tapping <strong>Share Report</strong> still opens your device's
normal share sheet, but nothing reaches our support inbox.
</p>
<h2>4. Consent and Control</h2>
<p>
Crash reporting is <strong>opt-in and off by default</strong>. The first time you launch
the app you will see a consent prompt. You can change this at any time:
Crash reporting, usage analytics, and support-inbox delivery of shared reports are all
<strong>opt-in and off by default</strong>, controlled by a single consent decision. The
first time you launch the app you will see a consent prompt. You can change this at any time:
</p>
<ul>
<li>Open the app → <strong>Settings</strong> → <strong>Privacy</strong> →
<strong>Crash reporting</strong> toggle.</li>
<li>If you decline, Sentry is never initialised. If you turn reporting off later, the active SDK is closed and no new events are captured.</li>
<strong>Crash Reports &amp; Usage Analytics</strong> toggle.</li>
<li>If you decline, neither Sentry nor PostHog is ever initialised, and shared reports are
never delivered to our support inbox (only your device's normal share sheet is used).
If you turn the toggle off later, both SDKs are shut down, no new events are captured,
analytics events still buffered on the device are dropped without being sent, and future
shared reports stop reaching the support inbox.</li>
</ul>
<h2>5. Third-Party Services</h2>
<p>
We use one third-party service for diagnostics:
We use two third-party services, both consent-gated:
</p>
<ul>
<li>
@@ -200,20 +334,37 @@
Data is sent to Sentry's US-based servers and retained for approximately 90 days
per Sentry's default data-retention policy.
</li>
<li>
<strong>PostHog</strong> — anonymous usage analytics (the activation-funnel events listed
in section 3a).<br>
Privacy policy: <a href="https://posthog.com/privacy" target="_blank" rel="noopener">posthog.com/privacy</a><br>
Data is sent to PostHog's EU-region servers (<code>eu.i.posthog.com</code>).
</li>
</ul>
<p>
We use no advertising networks, analytics platforms, social SDKs, or any other
We use no advertising networks, social SDKs, or any other
third-party data collection services. The app contains no ads and no ad SDKs.
</p>
<p>
We also operate our own <strong>Chatwoot</strong> support-inbox instance
(<code>support.agentlabs.cc</code>, described in section 3b) to receive diagnostic reports
you explicitly choose to share. Unlike Sentry and PostHog, this is infrastructure we run
ourselves rather than a third-party vendor, but data sent to it still leaves your device and
is retained by us as described below.
</p>
<h2>6. Data Retention</h2>
<p>
Crash reports sent to Sentry are retained for approximately 90 days, after which they are
automatically deleted per Sentry's retention defaults.
automatically deleted per Sentry's retention defaults. Usage analytics events sent to
PostHog are retained per PostHog's standard retention policy. Shared support reports
delivered to our Chatwoot inbox are retained until the associated support conversation is
resolved and periodically purged thereafter; email support@agentlabs.cc to request earlier
deletion of a specific report.
</p>
<p>
We do not operate our own servers that store your data; there is no VIBE TECHNOLOGIES
back end involved in normal app usage.
Beyond that support inbox, we do not operate our own servers that store your data; there is
no other VIBE TECHNOLOGIES back end involved in normal app usage.
</p>
<h2>7. Your Rights</h2>
@@ -221,11 +372,13 @@
You have the right to:
</p>
<ul>
<li><strong>Opt out</strong> — disable crash reporting at any time in Settings → Privacy.</li>
<li><strong>Opt out</strong> — disable crash reporting, usage analytics, and support-inbox
delivery of shared reports at any time in Settings → Privacy.</li>
<li><strong>Request deletion</strong> — email <a href="mailto:support@agentlabs.cc">support@agentlabs.cc</a>
with subject "Data deletion request" and we will request deletion of any crash events
associated with your device from Sentry. Include your device model and approximate date
range to help us identify your records.</li>
(Sentry), analytics events (PostHog), and shared support-report conversations (Chatwoot)
associated with your device. Include your device model and approximate date range to
help us identify your records.</li>
<li><strong>Access</strong> — request a summary of what diagnostic data (if any) we hold
about your device by emailing the same address.</li>
</ul>
@@ -243,7 +396,8 @@
<h2>9. Security</h2>
<p>
All diagnostic data is transmitted over HTTPS (TLS 1.2+) to Sentry. We do not transmit
All diagnostic and analytics data — including shared support reports — is transmitted over
HTTPS (TLS 1.2+) to Sentry, PostHog, and our Chatwoot support inbox. 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.
</p>
@@ -296,13 +450,15 @@
<tbody>
<tr><td style="border:1px solid #e2e8f0;padding:8px;">Contact Info</td><td style="border:1px solid #e2e8f0;padding:8px;">No</td><td style="border:1px solid #e2e8f0;padding:8px;">N/A</td><td style="border:1px solid #e2e8f0;padding:8px;">No</td></tr>
<tr><td style="border:1px solid #e2e8f0;padding:8px;">Location</td><td style="border:1px solid #e2e8f0;padding:8px;">No</td><td style="border:1px solid #e2e8f0;padding:8px;">N/A</td><td style="border:1px solid #e2e8f0;padding:8px;">No</td></tr>
<tr><td style="border:1px solid #e2e8f0;padding:8px;">Identifiers (Device ID)</td><td style="border:1px solid #e2e8f0;padding:8px;">Yes (Sentry anonymous ID, with consent)</td><td style="border:1px solid #e2e8f0;padding:8px;">No</td><td style="border:1px solid #e2e8f0;padding:8px;">No</td></tr>
<tr><td style="border:1px solid #e2e8f0;padding:8px;">Identifiers (Device ID)</td><td style="border:1px solid #e2e8f0;padding:8px;">Yes (Sentry / PostHog anonymous IDs, with consent)</td><td style="border:1px solid #e2e8f0;padding:8px;">No</td><td style="border:1px solid #e2e8f0;padding:8px;">No</td></tr>
<tr><td style="border:1px solid #e2e8f0;padding:8px;">Usage Data — Product Interaction</td><td style="border:1px solid #e2e8f0;padding:8px;">Yes (PostHog activation events, with consent)</td><td style="border:1px solid #e2e8f0;padding:8px;">No</td><td style="border:1px solid #e2e8f0;padding:8px;">No</td></tr>
<tr><td style="border:1px solid #e2e8f0;padding:8px;">Diagnostics — Crash Data</td><td style="border:1px solid #e2e8f0;padding:8px;">Yes (Sentry, with consent)</td><td style="border:1px solid #e2e8f0;padding:8px;">No</td><td style="border:1px solid #e2e8f0;padding:8px;">No</td></tr>
<tr><td style="border:1px solid #e2e8f0;padding:8px;">Diagnostics — Performance Data</td><td style="border:1px solid #e2e8f0;padding:8px;">Yes (Sentry, with consent)</td><td style="border:1px solid #e2e8f0;padding:8px;">No</td><td style="border:1px solid #e2e8f0;padding:8px;">No</td></tr>
<tr><td style="border:1px solid #e2e8f0;padding:8px;">Diagnostics — Other Diagnostic Data</td><td style="border:1px solid #e2e8f0;padding:8px;">Yes (shared support reports delivered to our Chatwoot inbox, only when the user taps "Share Report" with consent)</td><td style="border:1px solid #e2e8f0;padding:8px;">No</td><td style="border:1px solid #e2e8f0;padding:8px;">No</td></tr>
<tr><td style="border:1px solid #e2e8f0;padding:8px;">All other categories</td><td style="border:1px solid #e2e8f0;padding:8px;">No</td><td style="border:1px solid #e2e8f0;padding:8px;">N/A</td><td style="border:1px solid #e2e8f0;padding:8px;">No</td></tr>
</tbody>
</table>
<p><strong>App Store Connect summary:</strong> Data Linked to You: <em>None</em>. Data Not Linked to You: <em>Crash Data, Performance Data</em> (when user consents). Tracking: <em>No</em>.</p>
<p><strong>App Store Connect summary:</strong> Data Linked to You: <em>None</em>. Data Not Linked to You: <em>Crash Data, Performance Data, Product Interaction, Other Diagnostic Data</em> (when user consents). Tracking: <em>No</em>.</p>
<footer>
&copy; 2026 VIBE TECHNOLOGIES, LLC. OpenCode Mobile is MIT-licensed open-source software.

74
distribution/privacy-policy.md
View File

@@ -4,7 +4,7 @@
**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.
> **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. With your consent, we use Sentry for anonymous crash diagnostics, PostHog for anonymous usage analytics, and — only when you tap "Share Report" — deliver a scrubbed copy of that diagnostic report to our support inbox.
---
@@ -48,34 +48,78 @@ With your explicit consent (shown at first launch), we collect anonymous crash d
URL scrubbing: before any event is sent to Sentry, our code strips all server URLs, authentication tokens, and query parameters. No server hostname or port number ever leaves your device via Sentry.
## 3a. Data We Do Collect (Usage Analytics)
With the same explicit consent (there is a single opt-in covering both crash reporting and analytics), we collect a small set of anonymous usage events via **PostHog** to understand whether new users successfully connect to their server and start using the app (an "activation funnel").
Events collected, with their only properties:
| Event | When it fires | Properties |
|---|---|---|
| `app_opened` | Once per app session, after consent | `is_first_open` (true/false) |
| `connection_form_submitted` | You tap Connect/Save with a server URL entered | `mode` ("quick" or "advanced") |
| `connection_attempted` | A connection test starts | `source` ("onboarding" or "edit_test") |
| `connection_succeeded` | The connection test succeeds | `source` |
| `connection_failed` | The connection test fails | `source`, `error_class` (a coarse category such as "timeout" or "unauthorized" — never the raw error text) |
| `message_sent` | You send a message to an agent session | — |
| `response_received` | An agent response finishes | — |
What analytics events **never** contain: your server URL, hostname, IP address, or port; prompts, messages, or AI responses; code or file contents; tokens or credentials; raw error messages. Connection failures are reduced to a fixed list of coarse categories before being sent.
Analytics data is sent to PostHog's **EU region** (`eu.i.posthog.com`) and is identified only by a random, app-generated anonymous ID — not linked to your name, email, or any account.
If you decline consent, no analytics is initialised and nothing is sent. If you revoke consent later, analytics stops immediately and any events still buffered on the device are discarded, not uploaded.
---
## 3b. Data We Do Collect (Shared Support Reports)
When a connection fails or the app crashes, you can tap **Share Report** to open your device's normal share sheet with a diagnostic report. If you have granted the same consent that covers crash reporting and analytics, a copy of that report is *also* delivered directly to our support inbox, hosted on our own **Chatwoot** instance (`support.agentlabs.cc`) — this is infrastructure we operate ourselves, not a third-party SaaS vendor.
| Data type | What is included | What is NOT included |
|---|---|---|
| Diagnostic summary | Connection classification (e.g. "server unreachable"), probe results, timing | — |
| Device info | Device model, OS version, app version | Serial number, IMEI, advertising ID |
| Recent app logs | Recent internal log lines (screen names, function-level breadcrumbs) | Message bodies, prompts, AI responses |
| Your server address | — | Never included — every URL and every hostname/IP the app probed this session is redacted before the report leaves your device |
A random, per-install identifier (stored locally via secure device storage) links follow-up reports from the same install into the same support conversation so we can reply to an ongoing issue. This identifier is not linked to your name, email, or account — we only learn contact details if you volunteer them in your own reply.
Sharing a report is always a manual, explicit action — it is never sent automatically or in the background. It is only delivered to the support inbox if you have granted consent; if you decline or revoke consent, tapping **Share Report** still opens your device's normal share sheet, but nothing reaches our support inbox.
---
## 4. Consent and Control
Crash reporting is **opt-in and off by default**. On first launch you will see a consent prompt. You can change this at any time:
Crash reporting, usage analytics, and support-inbox delivery of shared reports are all **opt-in and off by default**, controlled by a single consent decision. On first launch you will see a consent prompt. You can change this at any time:
- Open the app → **Settings** → **Privacy** → **Crash reporting** toggle.
- If you decline, Sentry is never initialised. If you turn reporting off later, the active SDK is closed and no new events are captured.
- Open the app → **Settings** → **Privacy** → **Crash Reports & Usage Analytics** toggle.
- If you decline, neither Sentry nor PostHog is ever initialised, and shared reports are never delivered to our support inbox (only your device's normal share sheet is used). If you turn the toggle off later, both SDKs are shut down, no new events are captured, analytics events still buffered on the device are dropped without being sent, and future shared reports stop reaching the support inbox.
---
## 5. Third-Party Services
We use one third-party service for diagnostics:
We use two third-party services, both consent-gated:
- **Sentry** — crash and error monitoring.
- Privacy policy: https://sentry.io/privacy/
- Data is sent to Sentry's US-based servers and retained for approximately 90 days per Sentry's default data-retention policy.
- **PostHog** — anonymous usage analytics (the activation-funnel events listed in section 3a).
- Privacy policy: https://posthog.com/privacy
- Data is sent to PostHog's EU-region servers (`eu.i.posthog.com`).
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.
We use no advertising networks, social SDKs, or any other third-party data collection services. The app contains no ads and no ad SDKs.
We also operate our own **Chatwoot** support-inbox instance (`support.agentlabs.cc`, described in section 3b) to receive diagnostic reports you explicitly choose to share. Unlike Sentry and PostHog, this is infrastructure we run ourselves rather than a third-party vendor, but data sent to it still leaves your device and is retained by us as described below.
---
## 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.
Crash reports sent to Sentry are retained for approximately 90 days, after which they are automatically deleted per Sentry's retention defaults. Usage analytics events sent to PostHog are retained per PostHog's standard retention policy. Shared support reports delivered to our Chatwoot inbox are retained until the associated support conversation is resolved and periodically purged thereafter; email support@agentlabs.cc to request earlier deletion of a specific report.
We do not operate our own servers that store your data; there is no VIBE TECHNOLOGIES back end involved in normal app usage.
Beyond that support inbox, we do not operate our own servers that store your data; there is no other VIBE TECHNOLOGIES back end involved in normal app usage.
---
@@ -83,8 +127,8 @@ We do not operate our own servers that store your data; there is no VIBE TECHNOL
You have the right to:
- **Opt out** — disable crash reporting at any time in Settings → Privacy.
- **Request deletion** — email support@agentlabs.cc with subject "Data deletion request" and we will request deletion of any crash events associated with your device from Sentry.
- **Opt out** — disable crash reporting, usage analytics, and support-inbox delivery of shared reports at any time in Settings → Privacy.
- **Request deletion** — email support@agentlabs.cc with subject "Data deletion request" and we will request deletion of any crash events (Sentry), analytics events (PostHog), and shared support-report conversations (Chatwoot) associated with your device.
- **Access** — request a summary of what diagnostic data (if any) we hold about your device by emailing the same address.
Residents of the EU/EEA/UK may exercise rights under GDPR/UK GDPR. California residents may exercise rights under the CCPA.
@@ -99,7 +143,7 @@ OpenCode Mobile is a developer tool intended for users aged 18 and over. We do n
## 9. Security
All diagnostic data is transmitted over HTTPS (TLS 1.2+) to Sentry. We do not transmit any data over unencrypted connections.
All diagnostic and analytics data — including shared support reports — is transmitted over HTTPS (TLS 1.2+) to Sentry, PostHog, and our Chatwoot support inbox. We do not transmit any data over unencrypted connections.
---
@@ -151,14 +195,14 @@ The following table maps our data practices to Apple's official App Privacy cate
| Browsing History | Any | No | N/A | No |
| Search History | Any | No | N/A | No |
| Identifiers | User ID | No | N/A | No |
| Identifiers | Device ID | Yes (Sentry anonymous ID) | No — not linked to Apple ID or personal info | No |
| Identifiers | Device ID | Yes (Sentry / PostHog anonymous IDs) | No — not linked to Apple ID or personal info | No |
| Purchases | Any | No | N/A | No |
| Usage Data | Product interaction | No | N/A | No |
| Usage Data | Product interaction | Yes (PostHog activation events, with consent) | No | No |
| Diagnostics | Crash Data | Yes (Sentry, with consent) | No | No |
| Diagnostics | Performance Data | Yes (Sentry, with consent) | No | No |
| Diagnostics | Other Diagnostic Data | No | N/A | No |
| Diagnostics | Other Diagnostic Data | Yes (shared support reports delivered to our Chatwoot inbox, only when the user taps "Share Report" with consent) | No | No |
**Summary for App Store Connect App Privacy section**:
- Data Linked to You: **None**
- Data Not Linked to You: **Crash Data, Performance Data** (Sentry diagnostics, when user consents)
- Data Not Linked to You: **Crash Data, Performance Data** (Sentry diagnostics, when user consents), **Product Interaction** (PostHog activation events, when user consents), **Other Diagnostic Data** (shared support reports via Chatwoot, when user consents)
- Tracking: **No**