Privacy Policy
Built on security & local trust.
1. Local-First Processing
Unlike traditional video creators that upload your assets to a cloud server, mapFlyover uses WebAssembly (FFmpeg.wasm) to render your videos locally on your own machine. Frames are rendered in your browser. Saved project configurations, uploaded soundtracks, generated narration and exported videos are stored in Firebase.
2. Data Collection
We store account information, project configurations, media, usage counts and support conversations. Narration text is sent to Google Gemini to create audio, and audio sent for captions is processed by Groq, in both cases with your own API key; place names are sent to the location service. We do not track your precise location or sell your production data to advertising networks.
3. Map Provider Usage
Our map animated video creator fetches data from satellite providers (ESRI, Mapbox). Usage is subject to their respective privacy terms. If you provide your own Mapbox token, you retain full control over that data layer.
4. Security
We use Firebase Authentication and secure Firestore rules to ensure that account owners can access their projects and authorized administrators can manage support and accounts. Firebase media download URLs contain access tokens; anyone given a download URL can access that file.
5. Your API keys and connected agents
Narration and captions use the Gemini and Groq API keys you add in Settings. A key is checked with its provider when you save it, stored encrypted on our server, never shown back to you in full, and used only for your own requests. You can remove a key at any time. If you connect an AI agent with an access token, that agent can read and change your projects with your permissions, and its provider handles what it reads under its own terms. You can revoke a token in Settings at any time.