Privacy Policy

1. Scope

This policy describes how Trip‑O (the website at https://trip-o.net, including www.trip-o.net and the Vercel deployment aliases) processes information when you use the service.

2. Data we collect

• Usage / product analytics: page views and product funnel events (see §4). We assign an anonymous ID in your browser (tripo_anon_id in localStorage).
• Location: if you use “Near me” / nearby features, the app may request your device location (browser geolocation). Coordinates are used on your device to rank nearby places. We do not require account signup for the consumer plan flow. Precise GPS is not required to create a plan (you can pick a city instead).
• On-device storage: saved places and saved plans may be stored in browser localStorage / sessionStorage and are not automatically uploaded as an account profile.
• Business / admin accounts: email, password hash, name, role, and business profile fields you edit (hours, photos, contacts, etc.).
• Trip‑O reviews (if you submit one): display name, rating, text, and timestamp.
• Place catalogue data: public venue information (name, address, hours strings, aggregate ratings marked as public-source data). This is not your personal data.

We do not collect payment card data in V1. Consumer plan creation does not require registration.

3. Location use

Location permission is optional. When granted, it is used to show nearby places and distance. Plans can be built using a selected city without sharing GPS. Opening “Navigation” hands off to a third-party maps app (e.g. Google Maps) with the destination coordinates/address.

4. PostHog analytics

We use PostHog in the EU region (https://eu.i.posthog.com) to understand product usage. Events we intentionally send include:

• plan_started
• plan_completed
• alternative_viewed
• alternative_selected
• place_opened
• navigation_clicked
• plan_shared

Events are tied to an anonymous distinct id, not to a consumer login (unless you later create an account and we link identifiers — not required in V1 consumer flow).

5. Cookies / tracking

• Essential: session cookies for business/admin authentication (Auth.js / NextAuth).
• Analytics: PostHog capture requests + anonymous id in localStorage (see §4).
• Maps / tiles: third-party map tile providers may set their own technical cookies or logs when map tiles load.

We do not run advertising pixels in V1. If that changes, this policy will be updated and consent obtained where required.

6. Turso database

Application data (venues, business profiles, admin/manager users, Trip‑O reviews when present) is stored in a Turso / LibSQL database used by the production backend. Access is restricted by server credentials (not exposed to browsers).

7. Third-party services

• Vercel — hosting, CDN, serverless runtime
• Turso / LibSQL — database
• PostHog EU — product analytics
• Google Maps (or similar) — when you tap Navigation
• OpenStreetMap / Esri — map tiles

Those providers process data under their own terms and privacy policies.

8. Retention & deletion

Analytics events are kept as long as needed for product improvement (typically up to 12–24 months unless we configure a shorter PostHog retention). Account and review data is kept while the account/content exists. You can clear on-device localStorage yourself. To request deletion of account or Trip‑O review data, contact the privacy email in the TODO box above once published.

9. Your GDPR rights

If GDPR applies, you may have rights to access, rectify, erase, restrict processing, object to processing based on legitimate interests, data portability, and to lodge a complaint with a supervisory authority (in Lithuania: VDAI). Exercise rights via the privacy contact listed in the TODO section.

10. Children

The service is not directed at children under 16 without guardian consent. If you believe a child provided personal data, contact us (TODO email).

11. Changes

We may update this policy. The “Last updated” date will change when we do.