Guest and account data
Guests keep plans, demo points and settings in the browser. With an account, Supabase Auth processes identity data and GemGo synchronises saved trips and collections to its EU database.
This notice describes the current GemGo beta. The legal controller identity and privacy contact still have to be confirmed before public production launch.
Beta notice · 13 August 2026Guests keep plans, demo points and settings in the browser. With an account, Supabase Auth processes identity data and GemGo synchronises saved trips and collections to its EU database.
Precise location is requested only after an explicit action for routing or a check-in; GemGo does not keep continuous movement history. A gem proposal uploads the chosen photo to a private moderation bucket.
Account and sync data are processed to provide the requested service. Optional location and photo submission follow your action and consent. Security, moderation and anti-fraud records support GemGo’s legitimate interest in protecting the service.
Supabase (EU West) provides Auth, database and private Storage; Vercel hosts the app. Google processes OAuth if you choose it. OpenStreetMap, Open-Meteo and Wikimedia Commons may receive network data when maps, forecasts or photos load.
Browser data remains until you remove it. Account data currently remains until account deletion. Contribution and moderation retention, automated rejected-photo cleanup and the final legal schedule must be approved before public production.
You may export local and account records below. Access, correction, erasure, restriction, portability and objection requests require a published controller contact; that is an open launch blocker.
Delete only GemGo data stored in this browser, or export a portable copy of local and signed-in account data.