How FARON handles your data
FARON is a private place for your trips. Overnight stays, stops, notes and photos are private by default, and you decide what enters the archive.
Where is my data stored?
Core data — your account, trips and photos — is processed in Lovable Cloud, with Supabase as the underlying infrastructure, in Supabase's Ireland region (eu-west-1) within the EU. Some providers may process data outside the EU/EEA; see the privacy policy for roles, recipients and transfer safeguards.
What is stored?
- Account details (email address and user ID)
- Logged overnight stays, stops and trips
- Notes, tags, structured place interests and private review status you add
- Coordinates you choose to save
- Photos you upload
- The feedback category and comment you submit in the app
How are place interests used?
Interests you confirm on places in Want to visit can be used to rank and explain place suggestions in Premium planning. FARON does not automatically classify old tags, place names or notes, and it does not change profile interests without your choice.
Website and blog analytics
If you actively consent on the device, FARON collects limited usage and blog statistics. Basic Consent Mode is used: the Google tag is not created and no cookieless ping is sent before opt-in. A profile value never enables analytics on a new device, and withdrawal stops future hits and clears analytics storage where the browser permits.
Manual logging, not automatic tracking
FARON does not record your movement in the background. Location data is saved only when you choose to log an overnight stay, stop or trip.
For the practical limits, read No background GPS tracking.
For the technical detail on hosting, photos, signed links and deletion, open Data and security in FARON.
Local and cloud storage
The device may store the authentication session, language, theme, app choices, consent, drafts, first-night data, offline queue, offline maps and route cache, search history, sharing choices, Premium and checkout status, push installation and analytics data. Necessary storage supports function, security and your choices; analytics storage requires consent. The cookie page lists purpose and deletion criteria.
Who has access?
The account and private trips are private by default. Co-travellers can see the trip they were given access to, and content you actively publish through a public link is available to anyone with the link without granting account access.
Technical administrative access is available to the people responsible for FARON's operations, security, support and troubleshooting when needed.
Product feedback appears in a read-only admin view and may trigger an internal push notification or administrator email. FARON retains it for 12 months; trip data and diagnostics are never attached automatically.
Sharing and invitations
Trips are private by default. Curated sharing displays only the content you select. Full sharing includes every stop and overnight stay with notes, reviews, ratings, weather, tags, accommodation type, places and all photos. The link does not grant account access.
- Shared-link views are counted in aggregate without IP addresses, cookies or device information.
- Photos use time-limited URLs that normally expire after one hour.
- You can disable sharing and make the trip private again.
- Invitations may store an email address, user IDs, status, timestamps and a single-use token. Favourites and recent co-traveller addresses, reusable group links, connection requests and push notifications have their own lifecycles.
- No automatic invitation email is sent; you share the link yourself. Data is removed when no longer needed for the invitation, group, security or a dispute.
Service providers
FARON's verified product integrations include:
- Lovable Cloud, with Supabase as the underlying infrastructure, for accounts, database, storage and server functions
- Stripe for subscription and gift payments
- Lovable Emails for authentication and transactional email, and Brevo for marketing email after opt-in
- Google for user-initiated sign-in, Analytics after consent and Fonts as an external resource
- Esri for geocoding and maps, Geoapify/OpenStreetMap for secondary place search, and Open-Meteo for weather data
- BRouter and OSRM for routes
- OpenFreeMap/OpenStreetMap, Thunderforest and CARTO for map and place data
- the browser's push provider when push is enabled
Roles differ between processor, subprocessor, external data source and user-initiated external link. Core data is processed in Supabase's Ireland region (eu-west-1). Some providers and subprocessors may process data outside the EU/EEA under their applicable transfer safeguards. FARON does not sell data for third-party marketing.
Can I delete my data?
Yes. You can permanently delete the account from the profile page. Your own archive and the account link are removed from the active service. Content you added as a co-traveller to someone else's trip remains with the trip owner, while technical author fields are transferred to the owner. Remove that content first or contact FARON with a rights request.
Before deleting the account, you can download your data.