ChimpTrip AI · Privacy draft

Privacy Policy

Draft, not finalThis is a working draft for owner review. It is not legal advice, has not been reviewed by a lawyer and is not launch-ready.

Effective date: Owner decision: not set. Operator: Owner decision: legal entity not named. Contact: Owner decision: no contact address published. Governing jurisdiction: Owner decision: not chosen.

Travel data

Guests: questionnaire answers and results stay in your browser storage.
Account holders: travel profiles, drafts, initial recommendations and saved favorites are stored on our server and tied to your verified account.
Notifications: simulated only; nothing is actually sent.
Deleting your travel profile clears profile, draft and initial results, not saved vacations or your Clerk identity.

Service providers

Clerk provides authentication. Replit provides hosting and the database. Infrastructure and authentication providers may process connection metadata (such as IP addresses) independently under their own terms; we make no guarantee about their retention.

Automatic anonymous traffic counts

We automatically count approved public pages using first-party daily counters, without analytics cookies, browser storage, visitor IDs or cross-visit tracking. We do not estimate unique people or sessions.
The count request sends the public page path without account credentials. Only after a separate location opt-in may it also carry a short-lived in-memory location permission; that permission is never stored with analytics. We exclude account, questionnaire, notification, admin and sign-in pages, full URLs, query strings, travel answers and account identities.
Each stored counter groups a UTC day, environment, public page and approximate country/region. We do not retain a separate event, event time, IP address or browser identifier for each page view.
Collection is currently enabled only in the development environment and is off in production by default.
Reports cover the last 90 UTC days. Older aggregate buckets are removed on analytics requests, not on a schedule; idle periods can delay removal. Previous consent-based records are retained separately, are not used for new visitor tracking and are not combined with these counters. Owner decision: legacy-record retention, scheduled deletion and backup/log retention
We do not retain raw IP addresses or precise coordinates.
Location lookup requires explicit opt-in, a verified trusted proxy chain and an approved licensed local database. Only approximate country and province/state are recorded, never location inferred from travel answers or currency. No external IP lookup service is called. Until activation prerequisites are approved, location remains Unknown.
Do Not Track and Global Privacy Control signals prevent counting. JavaScript-disabled visits, blocked or failed requests are not counted; reloads and bots can inflate counts. Totals are approximate.
Network addresses are processed transiently for local approximate lookup and bounded in-memory abuse prevention, not inserted into analytics tables. Infrastructure providers may independently process connection logs under their own policies.

The footer offers separate location consent when available. You can withdraw it there immediately, without reloading; future location requests stop, while general anonymous counting remains unchanged. Permission is kept only in memory for this loaded tab, expires after at most 15 minutes and is cleared by reload or server restart. Withdrawal is also broadcast to other open tabs where supported. Previously recorded anonymous aggregates cannot identify your individual contributions. Before enabling production collection, the operator must review applicable notice, consent and privacy requirements. Owner decision: production privacy review

Retention and rights

Account data and server log retention periods: Owner decision: not yet set. Access and correction request process: Owner decision: not yet set.