Privacy Policy
Last updated: November 19, 2026
AtlasCam is designed to put useful context - maps, speed, altitude, weather, ride telemetry, and more - on your camera view. This policy describes what information AtlasCam may access on your device, how it is used, and the specific features that send information off your device.
Summary
- Core camera and ride-library features do not require an account. Community is optional and uses an account or a private-by-default guest profile.
- AtlasCam does not sell your personal information, and does not integrate advertising SDKs.
- Photos, videos, routes, and telemetry you capture stay on your device unless you export them, save them elsewhere, choose to share them with Community, or turn on one of the broadcasting features described below.
- Three optional features send information off your device while they are switched on: live streaming and watch links, the AI voice copilot, and the local network HUD overlay. All three are off by default.
- Heart rate and other health data stay on your device unless you choose to share them. Watch links hide heart rate unless you turn that off.
- When you use weather, map, Health Connect, or subscription features, Apple and Google platform services may process related data under their own policies.
Information AtlasCam accesses
Depending on the features you use, AtlasCam may request access to camera, microphone, location, photos or local files, Bluetooth, workout and heart-rate data, device motion, depth sensors on supported devices, and folders you select. If you connect them, AtlasCam also reads telemetry from your board, bike controller, or a Tesla vehicle over Bluetooth, and what is playing in Spotify or Apple Music.
How information is used
- Camera and microphone: used to preview and record photos, videos, and audio.
- Location: used for speed, altitude, heading, coordinates, route maps, and weather context. If you allow Always access, AtlasCam can keep logging a telemetry ride, and keep a broadcast running, after you leave the app. Your device shows its own indicator whenever this is happening.
- Photos and files: used only when you choose media to edit, export, save, or manage.
- Ride telemetry: used to show and save ride stats, overlays, maps, and exports.
- Health and Bluetooth metrics: used to include workout context such as heart rate, calories, distance, and board or vehicle telemetry when you choose those features.
- Camera detection: if you turn on viewport detection, AtlasCam labels what the camera sees, such as people, vehicles, animals, and signs, on your device. It finds faces only as boxes to label; it does not recognize who anyone is or build face templates.
Health data
AtlasCam reads heart rate, active calories, workout distance, and workout time from Apple Health, Health Connect, a paired watch, or a Bluetooth heart-rate sensor, only after you grant permission. It uses them to show workout context in your overlays, ride stats, and exports. Apart from videos you export or stream with a heart-rate widget showing, health data leaves your device only in these three cases, each of which you choose:
- Watch links. Heart rate, calories, and workout distance are hidden from watch links and the OBS overlay by default. If you turn off Hide heart rate in the streaming privacy settings, they are sent to the AtlasCam Live relay and shown to anyone with your link while you broadcast.
- Community posts. If you select heart rate or calories when sharing a ride, those values are stored with the post and shown to its audience.
- The voice copilot. While the copilot is on, your current heart rate is part of the ride readouts sent to OpenAI so it can answer questions about your ride.
AtlasCam never uses health data for advertising, never sells it, and never shares it with data brokers. You can revoke health permissions at any time in your device settings, and delete a Community post to remove the health values stored with it.
Live streaming and watch links
AtlasCam Live is off until you turn it on. It has two independent parts, and each sends different information to a different place.
Watch links
A watch link lets someone follow your ride in a browser. While a broadcast is running, your phone sends ride telemetry - which can include your live position, speed, altitude, heading, route, and board metrics, and your heart rate, calories, and workout distance only if you turn off Hide heart rate - to a relay operated by AtlasCam and hosted on Cloudflare Workers, which forwards it to whoever has the link.
- Telemetry only. No video, audio, or camera imagery is sent to the relay. The viewer's browser draws its own map.
- Anything you hide is never sent. Fields you switch off in AtlasCam's streaming privacy settings are removed before the data leaves your phone, so they cannot be recovered from the feed by the relay or by a viewer.
- Anyone with the link can watch. There is no sign-in and no viewer list. Treat a watch link as public, and share it only with people you want following your location.
- What the relay keeps, and for how long. While a broadcast is live the relay holds your most recent readings and a simplified version of your route, so someone opening the link partway through sees the ride already in progress. Both are deleted when the broadcast ends, and the link stops working - it cannot be reopened.
- Starting away from where you are. An optional setting withholds your position until you are a distance you choose from where the broadcast began, so a link does not draw a line to your front door. It is off by default; you turn it on in the streaming settings.
- The viewer's browser. The watch page loads map tiles from OpenFreeMap and its map library from unpkg. Those services receive the viewer's IP address, as any website's would; they receive nothing about you beyond the telemetry drawn on the page.
Broadcasting to your own channel
If you stream to Twitch, YouTube, or another RTMP destination, you supply the address and stream key, and AtlasCam sends video and audio directly to that service. Your video does not pass through AtlasCam. Because the HUD is drawn into the video, anything on screen - including your location, speed, and route - is part of what you publish there. What that service then does with your broadcast is governed by its own privacy policy. Your stream key is stored in your device's Keychain and is not sent anywhere except to the destination you entered. When you use Twitch, AtlasCam asks Twitch for its list of ingest servers to pick a nearby one.
If you paste your channel's public watch page into AtlasCam, that address is forwarded to your watch-link viewers so their browser can embed your stream. It is the only thing about your channel the relay receives.
AI voice copilot
The voice copilot is off by default and does not work until you paste your own OpenAI API key into Settings. While it is switched on, your microphone audio is streamed in real time to OpenAI, along with context needed to answer you: your ride readouts (speed, time, altitude, weather, heart rate, and board battery), your location as coordinates or nearby place and street names, and, if viewport detection is on, short text labels for what the camera detects, such as people or vehicles. No camera images are sent. Usage is billed to your own OpenAI account, and OpenAI processes that data under its own terms. Your API key is stored in your device's Keychain, on that device only, and is sent to no one but OpenAI.
Turning the copilot off in Settings stops the audio stream. Removing your API key disables the feature entirely.
Local network HUD overlay
The OBS overlay serves your live HUD readings as a web page to your Wi-Fi network, so streaming software on a computer can display them. While it is on, any device on the same network can open that page - there is no password. It is off by default, is reachable only from your local network, and never leaves it. The same privacy settings that redact watch-link fields apply here.
Community
Community is optional and requires you to sign in. You can create an account with email and password or a supported identity provider, or choose Continue as guest to use Firebase anonymous authentication without providing an email address. Guest access still creates a private-by-default rider account so Community can enforce account-specific privacy, blocking, and reporting controls. You can later link a sign-in provider from your profile.
When you use Community, AtlasCam processes your account identifier and the profile information you choose to provide, such as display name, username, bio, privacy setting, and avatar. If you choose to share a ride, AtlasCam sends the ride details you select, which may include a title, caption, route, distance, duration, speed or elevation statistics, and optional video, image, or telemetry files. Community also processes your likes, comments, follows, blocks, reports, and moderation actions. Your chosen audience controls who can see each shared post; private profiles and posts are limited as described in the app.
Firebase Authentication verifies your sign-in. Community account and interaction records are handled by AtlasCam's API on Cloudflare Workers and stored in Cloudflare D1; profile images, ride videos, and related files are stored in Cloudflare R2 when those services are configured. The API uses your sign-in token to authorize requests. AtlasCam does not receive your password from Firebase. Community media and data are sent only when you use Community or choose to share them.
If you enable Community notifications, AtlasCam and Firebase Cloud Messaging process a device push token so the app can deliver Community notifications. You can turn notifications off in Android settings. You can delete your Community profile from its profile editor; this removes the account's Community posts, relationships, reports, and uploaded Community files. Firebase sign-in identity deletion is handled separately by the app when you confirm account deletion. A minimal identity tombstone may be retained to prevent a deleted account from being recreated with an existing valid sign-in token.
If you sign up with email, Firebase sends account emails such as address verification and password resets on AtlasCam's behalf. AtlasCam does not send marketing email.
Safety and legal holds. When a moderator removes a post, or a post is reported for child safety, the post disappears from Community but its media is kept privately for up to one year, even if the post or account is later deleted. No one can view it through AtlasCam during that time. This lets AtlasCam report child sexual abuse material to the National Center for Missing & Exploited Children and preserve it as federal law requires, and respond to other legal requests. The media is deleted when the hold ends.
Third parties
AtlasCam uses platform services such as Apple Maps, WeatherKit, Photos, HealthKit, StoreKit, Google Maps, Google Play Billing, Health Connect, and system file or backup features where enabled by your device settings. Those services are governed by the applicable provider's privacy terms.
The Android app also sends the coordinates a feature needs to these map and data services. They receive your location for that request, not your identity:
- Mapbox - map tiles and styles for maps and exports, and directions when you ask the copilot for a route. The Mapbox SDK also collects anonymous map and location usage to improve its maps; you can opt out in Settings > Privacy.
- OpenStreetMap's Overpass API - to find landmarks near you for viewport detection.
- Open-Meteo - weather for your current location.
- U.S. Geological Survey - elevation for your current location.
Beyond those, AtlasCam contacts the following, each only when the relevant feature is in use:
- OpenAI - microphone audio and ride context, when the voice copilot is on. See above.
- The AtlasCam Live relay (operated by AtlasCam on Cloudflare Workers) - ride telemetry, while a watch link is broadcasting. See above.
- Firebase Authentication - sign-in verification for Community accounts, including anonymous guest sessions. See above.
- Cloudflare - Community API traffic and, when you choose Community features, account, profile, interaction, and uploaded media data. See above.
- Firebase Cloud Messaging - device push tokens and notification delivery, when Community notifications are enabled.
- Spotify - if you connect Spotify for the Now Playing widget, AtlasCam signs in to your Spotify account to read, and let you control, what is playing. Your Spotify sign-in token is stored on your device.
- Twitch - if you connect Twitch chat, AtlasCam signs in to your Twitch account to read and send chat messages for your channel. Your Twitch sign-in token is stored on your device.
- The streaming service you choose (Twitch, YouTube, or another RTMP destination) - your video and audio, while you are streaming. See above.
- MLB Stats API and ESPN - public schedules and scores for the sports scoreboard overlay. AtlasCam asks only for a league and a date; your location is not sent, and the nearest venue is worked out on your device.
- atlascam.app - the catalog of downloadable HUD looks and overlay packs. No personal information is sent.
- PostHog - optional anonymous usage analytics, crash reports, and basic app and voice-copilot performance diagnostics (such as latency, token counts, and error codes - never audio, prompts, GPS coordinates, routes, filenames, or board names) on iOS, off by default and sent only if you switched them on during setup or in Settings. They are not linked to your identity and are never used for tracking or advertising.
- TelemetryDeck - optional anonymous usage analytics, off by default and sent only if you switched them on during setup or in Settings. They are not linked to your identity and are never used for tracking or advertising.
As with any internet request, these services can see your device's IP address. AtlasCam does not integrate advertising SDKs and does not share your data with advertisers or data brokers.
Subscriptions
AtlasCam Pro is purchased and managed through the store provided by your platform. Apple or Google processes your payment, and AtlasCam never receives your payment details. If you sign in to an AtlasCam account, AtlasCam's API verifies your purchase with Apple or Google so Pro follows your sign-in to your other devices: it stores the store, product, a purchase identifier, its status, and its expiry date, linked to that sign-in.
How long information is kept
- On your device: rides, media, and settings stay until you delete them or the app.
- Watch links: the relay deletes what it holds when the broadcast ends.
- Community: your profile, posts, and interactions are kept until you delete them or your account. Deleted records can remain in Cloudflare's database recovery history for up to 30 days. Media under a safety or legal hold is kept for up to one year, as described above.
- Pro purchase records: kept while they are needed to provide Pro to your sign-in. Email privacy@atlascam.app to have them deleted.
- Optional analytics: anonymous PostHog and TelemetryDeck analytics and diagnostic records are kept under each provider's retention policy.
Children
AtlasCam is not directed to children under 13, and Community requires you to be at least 13. AtlasCam does not knowingly collect personal information from children under 13. If you believe a child under 13 has created a Community account or shared information with AtlasCam, email privacy@atlascam.app and it will be deleted.
Your rights
Wherever you live, you can ask for a copy of the personal information AtlasCam holds about you, ask for it to be corrected, or ask for it to be deleted, by emailing privacy@atlascam.app. In practice this is your Community account data and any Pro purchase record linked to it; everything else stays on your device. AtlasCam responds within 45 days and will not treat you differently for making a request.
Our website
atlascam.app does not use cookies, analytics, or advertising scripts, and serves its own fonts. Like any website, its hosting provider receives visitors' IP addresses in order to deliver the pages.
Do Not Track
AtlasCam does not track you across other websites or apps, and does not let third parties do so through AtlasCam, so it treats every visitor and user the same whether or not a Do Not Track signal is sent.
Changes to this policy
When this policy changes, the updated version is posted here with a new date at the top. If a change affects how your information is shared, AtlasCam also notes it in the app's release notes before it takes effect.
Your choices
- Revoke camera, microphone, location, photos or files, Bluetooth, and health permissions at any time in your device settings.
- End a broadcast at any time. Ending it retires the watch link and deletes what the relay was holding.
- Choose what a watch link and the OBS overlay may show, in AtlasCam's streaming privacy settings - hidden fields are never transmitted. Heart rate is hidden by default.
- Turn the voice copilot off, or delete your API key, in Settings.
- Turn optional analytics on or off in Settings, and on Android, opt out of Mapbox map usage collection in Settings > Privacy.
- Manage or cancel subscriptions in your Apple Account or Google Play subscription settings.
- Delete your Community account or request removal of Community data at atlascam.app/delete-account/.
Contact
Email: privacy@atlascam.app