Syncspot
Draft pending review

Privacy policy

Last updated: Thursday, 15-Oct-2026

This policy is a draft for review before the beta and waitlist launch. The operator’s legal identity, processing grounds and retention schedule still need sign-off.

Who operates Syncspot

Syncspot is a group travel planning service at syncspot.space. Contact hello@syncspot.space about your personal data. The operator’s legal name and address will be confirmed before public launch.

What we collect

Accounts contain a name, email address, password hash and optional profile photo. Sessions contain an internal account identifier, expiry, and technical information such as IP address and browser details. Trips contain membership, per-trip names, origins, flights, shared plans, links and files. Password reset links and beta invitation credentials are used to control account access.

Waitlist and invitation permission

Joining the waitlist records your normalized email address, the time and version of your explicit permission, subscription state, invitation history and technical token hashes. It does not create an account. We use this permission only to send a beta invitation; we do not send newsletters or a signup confirmation. You can withdraw through the confirmation link in an invitation, or contact hello@syncspot.space for withdrawal, correction or erasure. Withdrawing does not delete an existing account. We remove unconverted waitlist records after 180 days from signup and converted records after 30 days from registration, through a daily background job. Invitation records and stored recipient jobs are removed with the waitlist record; independent accounts remain.

Protecting the waitlist

Cloudflare Turnstile verifies waitlist submissions and processes technical browser information and the request IP address to prevent abuse. Dedicated rate limits use a keyed, rotating hash of the IP address and time window; the counters do not store raw IP addresses or email addresses and expire within a day. Functional verification may use Cloudflare’s technical cookies. A successful new signup records an anonymous analytics event without an email address, invitation token or subscriber identifier.

How trip information is shared

Trip content is available to the trip’s members. Your name and avatar help other travellers identify you. Avatar images are served through a public media domain. A trip invitation does not grant beta account access. Only invited users can create accounts during the beta.

Services that process data

Vercel hosts the application in Frankfurt. Neon stores application and queue data in Frankfurt. Cloudflare supplies DNS, EU object storage and email forwarding. Resend processes queued transactional emails in its configured Ireland region. PostHog EU receives pageview, page-exit and explicit product analytics events. Account events use an internal account identifier. Sentry EU processes scrubbed error reports and may retain approximate city-level geography. Each provider may retain operational records under its own terms.

Cookies and analytics

Functional cookies maintain your account session and a short-lived beta registration context. The registration context is removed after successful signup or expiry. On our production website, PostHog analytics use cookieless measurement without cookies or browser storage. PostHog temporarily processes the IP address, browser user agent, site hostname and day to derive a rotating anonymous visitor identifier; raw IP addresses and raw user agents are removed from cookieless events. This estimates daily visitors, rather than recognizing people across days. We record pageviews and page exits, including timing and scroll measurements, with the site hostname and a limited set of page paths. Unknown paths are grouped together. Query strings, URL fragments and referrers are removed. Automatic click and form tracking, session replay and analytics cookies are disabled. We do not include email addresses, invitation tokens or password reset tokens in analytics events.

Retention and account deletion

You can request deletion in Account settings or contact us. Account deletion is blocked while a trip you administer still has other joined travellers, regardless of its dates. After deletion, your memberships and flights are removed. Shared content in surviving trips remains without personal attribution. External file and analytics erasure run through a durable background queue. Processor logs and backups may follow separate retention periods, which will be confirmed before launch.

Questions and data rights

Contact hello@syncspot.space to request access, correction or erasure of your personal data, or to raise a privacy concern. Applicable data protection rights and complaint information will be finalized with the operator’s legal details before launch.