Privacy notice
This notice covers the WayToGo! beta app and this public information website.
1. Who is responsible?
The controller is Davide Mauri, an individual, bul. Tsar Boris III, 165, apt. 43, Sofia, 1612, Bulgaria. Privacy requests and support: info.waytogo2026@gmail.com. WayToGo! is currently operated by an individual, not a company. This notice will be updated if the operator changes.
2. Information we use
- Account: email address, authentication identifiers, display name, email confirmation status and the dated declaration that you are at least 18. Email/password authentication is managed by Supabase Auth; we do not provide a way to retrieve your existing password. Google sign-in supplies account information through Google and Supabase.
- Profile: optional photo, biography, spoken languages, date of birth, gender and preferences you provide. Date of birth and gender are subject to restricted access. The age declaration is not an identity-document check.
- Vehicles and journeys: saved vehicle details, model, colour and registration plate; planned cities, meeting points, addresses, coordinates, departure times, prices, seats and travel preferences.
- Activity: booking requests, confirmations, cancellations, conversations, message text, reviews, saved journeys and route alerts.
- Support and safety: support messages, reports about users or content, relevant snapshots and moderation decisions. For technical feedback you may include the app version/build, web build, platform, operating system, browser version, language and an optional device model you enter. These details are shown before sending and can be excluded; the automatic collection does not include passwords, tokens, conversation text, precise location or device identifiers.
- Delivery and operation: push device tokens, language, notification preferences, delivery states and technical request information processed by our hosting and delivery providers.
Meeting-point coordinates describe places selected for a journey; they do not constitute continuous device-location tracking. Do not include unnecessary sensitive information in public notes, messages or support requests.
3. Purposes and legal grounds
We process necessary account, journey, booking and messaging information to provide the service you request (GDPR Article 6(1)(b)). Security, abuse prevention, moderation, proportionate technical records and handling disputes rely on our legitimate interests in a safe and reliable service (Article 6(1)(f)), balanced against users’ rights. Applicable legal obligations may require specific processing (Article 6(1)(c)).
Optional communications and device permissions are managed through the available settings and, where consent is required, on that basis (Article 6(1)(a)); you can withdraw such consent. Essential authentication and service emails are different from marketing. We do not currently operate a marketing mailing list. Reading this notice does not give blanket consent to unrelated uses.
You must provide the information needed for an account and the action you request. Optional profile information can be omitted, although some features, such as eligibility for women-only journeys, depend on relevant profile details. Without the 18+ declaration, new journeys, bookings and messages are restricted.
4. Visibility and recipients
Profile information intended for other participants is available to signed-in users according to the app’s permissions. Journey information is shown to people browsing journeys. Messages are available to the conversation participants and may be accessed by authorised staff when needed to investigate reports. Saved vehicles are private; registration plate access is restricted by journey and booking permissions. Support requests, report evidence and moderation records are restricted to authorised people.
Providers involved in the service include:
- Supabase: authentication, database and photo storage.
- Cloudflare: application and website hosting, server functions and scheduled delivery/cleanup tasks.
- Google Places: place searches and selected meeting points. Search text and relevant search areas are sent to this service.
- Google Cloud Translation: journey notes when translation is requested; translations are cached.
- Firebase Cloud Messaging: device tokens and push notifications. Push text uses general event descriptions rather than the full conversation message.
- Resend: authentication, service and support email delivery.
- Google/Gmail: the support mailbox and, when chosen, Google sign-in.
The application database is hosted in the Supabase project’s eu-west-1 region. This does not mean that every provider or operation is restricted to the EEA: delivery, hosting infrastructure and provider support may involve other countries, including the United States. Relevant provider arrangements include the Supabase DPA, Cloudflare DPA, Resend’s data protection and transfer information and Firebase data processing terms. Depending on the service and transfer, these arrangements provide safeguards such as standard contractual clauses. Contact us for information about the safeguards relevant to your data. Google sign-in, Gmail and Google Maps/Places also operate under their applicable service terms and Google’s privacy policy; they are not all covered by the same processor arrangement. Place searches also involve the Google Maps Platform terms.
5. Retention and account deletion
| Records | Normal cleanup criteria |
|---|---|
| Profile, saved vehicles and preferences | While your account is active; ordinary personal details are removed through account deletion, subject to report evidence and necessary technical references. |
| Closed journeys, bookings and conversation history | 12 months after closure and relevant later activity. Active journeys, pending/confirmed bookings, unresolved booking problems, recent messages or reviews, and preserved evidence can delay cleanup. |
| Closed support requests in the app database | 6 months after recorded closure. |
| Closed reports and moderation actions | 12 months after final handling, except open cases or documented preservation holds. |
| In-app notifications | 90 days from creation. |
| Finished delivery records | 30 days for eligible email logs; 7 days for completed push logs. |
Cleanup runs periodically in batches. Existing journeys already closed when the policy was installed start from that installation date where a reliable closure timestamp was not recorded. A preservation hold requires a reason and periodic review; its review date does not automatically authorise destruction.
Account deletion removes ordinary personal details and your own message text sooner. Some technical identifiers and shared records remain to preserve other participants’ history and handle safety cases. Photos retained as evidence are queued for removal once no longer needed by an open case or preservation hold and not used by a profile. See account deletion for the available request methods.
Database cleanup does not itself erase messages already delivered to a mailbox or provider backup copies. Support mailbox conversations are reviewed manually for deletion after six months from case closure, except unresolved disputes or documented preservation needs; this includes relevant sent mail and attachments. Gmail’s trash may retain deleted messages for a further 30 days. This mailbox procedure is separate from the automatic database cleanup.
Provider copies and technical identifiers
On the current Free plans, Supabase lists one day of API/database logs, and Cloudflare Workers Logs lists three days. These are the product log windows, not a promise that every provider security or account record has the same lifespan. Resend states that email and log data are kept for 30 days and backups for seven days. Supabase Free does not include the daily backup history offered on paid plans; we do not currently maintain our own manual database exports. Provider infrastructure copies remain subject to the applicable provider terms.
Firebase installation identifiers have a separate lifecycle: Firebase states that, after an API request to delete an identifier, deletion from its live and backup systems occurs within 180 days. Removing a WayToGo! account or its push-token association does not by itself establish that such an installation-deletion request has been made. In our database, device associations are disabled on sign-out and removed on account deletion; a device inactive for more than 30 days is excluded from push delivery, which is not the same as automatic deletion of its record.
A minimal disabled Auth record and technical account-deletion marker, including identifiers and processing dates, currently remain to preserve shared-record dependencies and reject access by deleted accounts. These markers are not automatically erased by the 12-month journey cleanup and are not described as anonymous. Their continued necessity must be reviewed when the associated records are removed or a privacy request is handled. You can ask us for information or erasure where applicable. Current provider details are available from Supabase, Cloudflare, Resend and Firebase.
6. Your rights
Depending on the applicable conditions, you may request access, correction, erasure, restriction, portability, or object to processing based on legitimate interests. You may withdraw consent where processing relies on it. Contact info.waytogo2026@gmail.com; we may need proportionate information to verify your identity. Requests are normally handled within one month, subject to the GDPR’s permitted extensions.
You may complain to the Bulgarian Commission for Personal Data Protection (CPDP), or another competent supervisory authority where applicable.
7. This website and changes
This public website does not include advertising trackers, third-party fonts or an analytics script in its source. Hosting providers still process technical requests needed to deliver it. The app stores authentication sessions and local preferences required for its functions; native notification permission is controlled through the device and app settings.
We will revise this notice when the service, operator or data practices change. Material changes will be communicated through an appropriate service channel.