Privacy Policy for Movetain

Updated: October 21, 2026 · Version 2026-10-21

Movetain is provided by an individual developer. This notice covers the Android app, web portal and Relay service. Contact: [email protected]. Local recording and online features handle data differently; not all data stays on your phone.

1. Data and purposes

• Recording on your device: GPS coordinates, timestamps, speed, altitude, waypoints and route statistics; photographs, audio notes and sensor or heart-rate measurements when you use those features. Location recording can continue while the screen is locked through an Android foreground service.
• Google sign-in: Firebase account identifier, name, email and profile image provided through Google authentication. These identify your account and control access to cloud routes and rooms. Movetain does not receive your Google password.
• Cloud routes: planned routes and recordings you save to the cloud, including coordinates, names, statistics and associated photographs. A recording may contain sensor or heart-rate information. Review its contents before uploading or sharing.
• Rooms and phone synchronization: messages, participants, device identifiers, positions, telemetry, waypoints and routes transmitted by connected phones, browsers and radio gateways. Room participants can receive data according to their access role. Phone synchronization can send history and photographs to your signed-in portal.
• Operation and security: connection times, IP addresses, browser/app/device details, account and room identifiers, errors and activity records. Route activity records can include route titles, upload/delete actions, file counts and sizes, but not the full route geometry.
• Terms and account requests: the accepted document version, server timestamp and whether acceptance occurred in the app or portal. Existing tester accounts may be exempt from the initial acceptance prompt; that exemption is not recorded as acceptance.

2. Where information is stored and processed

• Your device: local recordings and media remain in app storage unless you use an online transfer, export or sharing feature.
• Google Firebase: Authentication manages sign-in; Realtime Database stores cloud route data, account-related records and service controls; Cloud Storage stores uploaded media. Route coordinates are database content, not photograph files.
• Relay hosting: the server runs on Amazon Web Services and stores room history and administrative/connection journals. Persisted room and journal data is encrypted on the server; this is not a claim of end-to-end encryption or exclusion of administrator access.
• Other service providers: Cloudflare handles web traffic; MapTiler and other map sources supply maps and terrain; weather requests use weather providers such as Open-Meteo. Requests can reveal IP addresses, the viewed map area or requested coordinates. Online map requests may occur even when a recording is stored locally.

Service providers process data on infrastructure that may be outside your country. Their processing is also described in their own notices: Google, AWS, Cloudflare, MapTiler and Open-Meteo.

3. Access and sharing

Cloud records are associated with your account. Room access keys and invitations grant access to others; protect them and distribute them carefully. Storage currently permits signed-in users to read media through the SDK, and download URLs containing access tokens can be used by anyone who has the URL. Do not treat an uploaded photo or its link as a private vault. Recipients may keep copies after you remove the original.

The service operator can access data where needed to operate, support and secure the service. Hosting and infrastructure providers process it for the functions described above. Information may also be disclosed when legally required. This policy does not promise that cloud data is available only to you.

4. Retention

• Local recordings remain until removed from app storage. Cloud routes and media have a separate lifecycle; deleting a local recording does not delete its cloud copy.
• Room messages and time-series history normally use a 90-day retention window, subject to account settings and storage quotas. Saved routes, waypoints and room settings are not all governed by that same time-series expiry.
• Connection history is limited to 30 days and the latest 100 entries per account.
• Route activity and administrative journals have configurable retention and size/count limits; their default retention is 90 days. Shorter size limits can remove older entries sooner. Contact support for the settings applicable to your data.
• Infrastructure logs and provider backup lifecycles are separate from the visible application records. Deletion from a live view does not guarantee immediate removal from every provider backup or a recipient's copy.

5. Your choices and deletion requests

Account & Data shows account quotas and the available deletion methods. When automatic deletion is available, it requires a fresh Google confirmation and explicit acknowledgement. It disables access, clears associated live cloud and Relay records and removes the Movetain sign-in account. Your Google account and local phone recordings, photographs, maps and settings are not deleted. Export anything you need before confirming.

Cleanup waits at least 65 minutes for old sign-in tokens to expire. A final sweep after eight days removes files that could arrive from an upload started before the request. Failed stages are retried; the status page does not report completion while cleanup is unfinished. Signing in again does not cancel deletion or restore data. New registration becomes available after the old account and its primary data have been successfully removed; the final upload sweep applies only to the old UID and does not affect a new account. The old UID remains in encrypted processing state until completion; a hashed request receipt and hashed UID remain for 30 days afterwards. Device-only cooldown timestamps without an account association, infrastructure logs, provider backups and recipients' copies have separate lifecycles. Contact support about these exceptions or an incomplete request.

You can manage Android permissions in device settings, stop recording, sign out, and choose whether to upload a recording. Optional permissions should be granted only for features you want to use. Withdrawing a permission can prevent that feature from working.

Delete local recordings in History. Use the portal's explicit cloud-delete action to remove a cloud route and its linked photographs. If photograph cleanup fails, the route record is kept for retry. Clearing cache or uninstalling the app is not a request to delete cloud data.

Account and personal-data requests: email [email protected] with the subject “Movetain account and data deletion” from the account email if possible. Specify whether you want account deletion, cloud-data deletion, access or correction. We may verify ownership; never send a password, authentication token or identity document unless a lawful, necessary verification method has been agreed. We will explain any data that must be retained and the reason. Applicable rights and response periods depend on the law that applies to your request.

6. Notices, permissions and changes

This notice explains processing; it is not a blanket consent to every use of data. Where additional disclosure or consent is required, it must be provided in connection with the relevant feature. Android permissions and Google authorization do not replace every such requirement.

We will update this page when practices change and provide additional notice or request renewed acceptance where required. Questions or concerns: [email protected].