Roam.io
Roam In. Roam Out.

Analytics Notice

DRAFT — LEGAL REVIEW REQUIRED. This text is an implementation draft for product behaviour, not legal advice and not a counsel-approved policy.
Operator: Aman Pareek
Jurisdiction: India
Effective: 2026-09-01
Contact: amanprk4@gmail.com

DRAFT — Optional analytics

Product analytics are optional and consent-gated. Expo EAS Observe and browser Web Vitals dispatch stay disabled until you opt in. There is no expo-insights client package in Roam.io; the app does not auto-send ungatable launch events through Insights.
When you allow analytics, Observe may receive privacy-safe native signals such as anonymous installation identifiers, launches, sessions, coarse foreground engagement, platform and app version, filtered route patterns, performance timings, and allowlisted product event counts. On web, Supabase may receive fixed CLS, FCP, INP, LCP, and TTFB records containing only numeric measurements, rating, navigation type, app version, coarse viewport size, a random metric identifier, and a filtered route pattern. Supabase infrastructure may process ordinary request metadata such as IP address. Trip content, resolved route identifiers, query strings, messages, documents, booking details, AI prompts or outputs, emails, usernames, display names, user-agent strings, and free-form user text are not intentionally sent in the analytics payload.
You can turn analytics off at any time in Privacy & Data. Turning off disables further Observe and Web Vitals dispatch for that account. Signed-out usage remains off. Analytics never block core trip planning features. This notice is a draft pending legal review.