Privacy Policy

Effective date: September 16, 2026 · Last updated: November 4, 2026 · Version 1.3
Who this is from: Soltra LLC, a California limited liability company (“Soltra”, “we”, “us”)

Your data in one minute

Soltra holds your account and profile; your activities and the health data that came with them (routes, heart rate, calories, cadence, power, steps, elevation); your body weight if you allow it; photos you attach, each with a precise location; your subscription status; and product analytics. Most of it lives on our servers and is visible only to you. Usage events, crash and freeze reports, subscription records, notifications, and website data also reach the companies named in Section 9, and Section 10 says what each delete action removes and what limited records remain. Section 3 says exactly what each source gives us, Section 9 names every company that touches it, and Section 10 says how long each piece stays and how to delete it.

Two things belong at the top rather than buried further down:

• Everything Soltra shows you is private to you. There are no friends, followers, feeds, leaderboards, public profiles or shared heatmaps. No other Soltra user can see your routes, tiles, statistics, or photos and no one else’s data is shown to you.
• A stored calorie figure can reveal your body weight. Calories for an activity are computed from your weight, so anyone able to read that number and the model could estimate your weight to within a few kilograms. Only you and Soltra can read it, but we would rather say this plainly than let you assume the weight stays on your phone.

What Soltra doesn’t do

• We don’t sell or rent your personal data.
• We don’t show you advertising or let anyone use your data to advertise to you.
• We don’t use data from Apple Health or from your photo library for marketing, advertising, or any kind of data mining and we don’t allow anyone else to.
• We don’t train artificial-intelligence models on your data or give your data to anyone else to train theirs. The one exception is Mapbox, which draws the map. Its own policy lets it use de-identified data from map requests to improve its products, including its AI models, and Mapbox offers no setting to turn that off (Section 3.12).
• We don’t publish heatmaps, “popular routes”, or any other derivative of users’ routes, and we don’t build de-identified or aggregated datasets from your routes, photos or health data. The only aggregates we keep are the feature-usage counting and the daily totals described in Section 3.11.
• We don’t let another Soltra user see your data.
• We don’t store your health data in iCloud or sync anything through iCloud and the app’s local copy of your activities is kept out of your iPhone backups.
• We don’t let advertising companies or anyone else track your Soltra activity over time and across other apps or websites.
• We don’t read your Strava activities. If you connect Strava, data flows one way: from Soltra to your Strava account.
• We don’t write anything to Garmin Connect. If you connect your Garmin Connect account, data flows one way: from Garmin Connect to Soltra (Section 8.2).
• We don’t look in your Hidden album when suggesting photos and we don’t change or delete anything already in your photo library.

1. Who we are

The company responsible for your data is:

Soltra LLC
440 N Barranca Ave #5017
Covina, CA 91723
United States

For anything to do with privacy or with this policy, write to [email protected]. We have not appointed a data protection officer. The privacy address reaches the people who run Soltra.

Soltra is offered only through the United States App Store and is supported only in the United States. This policy is written for US law.

2. What the words in this policy mean

• Health data means anything about your body or its performance: heart rate, calories burned, cadence, power, step counts, your weight, and the workouts those numbers describe. Washington, Nevada, and Connecticut count this as “consumer health data”, along with the routes, places, and other details tied to your workouts, and require your consent before it is collected or shared. Our Consumer Health Data Privacy Policy lists everything we treat that way.
• Precise location means the GPS coordinates that make up a route, the coordinates attached to a photo, and any other position accurate to within a few metres.
• Our servers means the database, file storage, and server code we run on Supabase (Section 9). Soltra has no servers of its own.

3. What we collect and where it comes from

Soltra collects only what the map needs, and only from sources you turn on.

3.1 Your account and profile

Signing in with Apple gives us a stable identifier for your Apple Account, an email address, (the first time only) the name on it, and the credential Apple issues so that we can revoke the sign-in when you delete your account. If you chose Hide My Email, that address is a private relay that forwards to you and it is the only address we hold. We use it for messages about your account. For an account created on or after October 12, 2026, we also use it to send you news about Soltra, such as when it reaches the App Store. To stop the news, reply to any of those emails or write to [email protected]. Before you sign in, Soltra reads the country of your App Store account on your iPhone to check that Soltra is offered there. We don’t store that country. Your profile also holds what you set in the app: display name, profile photo, units, time zone, theme and map preferences, and your body weight if you allow Soltra to read it or type it in. Soltra also keeps a record of your agreement to our Terms of Service and this policy: which version of each you agreed to, when, how, and the app version you were using. There is no password sign-in and no guest mode and Soltra doesn’t ask your date of birth, sex, or gender.

3.2 Apple Health

Soltra reads from Apple Health only with your permission and you choose which types to allow. It asks to read: workouts; workout routes; heart rate; active energy burned; cycling cadence, distance, and power; running power; step count; walking and running distance; and body mass. It asks to write back only the activities you record in Soltra: workouts, routes, active energy burned, and walking, running, and cycling distance.

Soltra reads your most recent weight each time you open the app until you type one in Settings. After that Apple Health is not read for it again and Soltra doesn’t write weight to Health. With permission, iOS also wakes Soltra when a new workout lands, so your map stays current without you opening it.

Apple Health data does not stay on your phone. Soltra builds an activity record from each workout (Section 3.5) and sends it to our servers, where it is stored with your account.

The Health permission sheet iOS shows you is the authoritative list of what Soltra asks for. Change it at any time in the Health app › your profile › Apps (under Privacy) › Soltra. Health permissions are not shown under iOS Settings › Soltra.

3.3 Recording an activity on your iPhone

A recording uses your location, which Soltra keeps receiving with the phone locked during a recording and only then. iOS shows its blue indicator whenever it does. Soltra asks for “while using” access, not “always”, and doesn’t track you outside a recording. Motion & Fitness counts your steps and the phone’s raw motion sensors, which need no permission, pause and resume the recording automatically. Soltra can speak progress cues but doesn’t listen and has no microphone permission. The recording stays in a private database on your phone until it uploads, then is handled like any other activity (Section 3.5).

3.4 Files you import

You can import GPX, TCX, and FIT files and ZIP archives such as a Strava or Garmin export. The file picker is the consent: nothing is read until you choose files. From a ZIP, Soltra extracts only the route files and the activities list on your phone. Photos, comments, kudos, messages, and everything else are discarded and not uploaded. Route files hold health data: coordinates, heart rate, cadence, power, temperature, and altitude. They are parsed on our servers into an activity record (Section 3.5). Extracted route files are deleted as soon as they are processed. The archive goes once it is no longer needed to retry the import or answer a question about it. Your import history keeps each file’s original name and whether it succeeded. If you connect your Garmin Connect account, Garmin Connect sends Soltra the file of each new activity, which Soltra processes the same way (Section 8.2).

3.5 What an activity record contains

Whether it arrived from Apple Health, a Soltra recording, or a file, the record we store holds the full-resolution route, every coordinate and its timestamp, plus a simplified copy for drawing; a sample track carrying heart rate, cadence, power, temperature, and altitude along the route; totals (distance, elapsed, moving, and active time, elevation gain and loss, averages and maximums, step count, calories); the title, description, and type you gave it, whether you marked it a race, and any record time you corrected or removed; the device and app that recorded it and the time zone it took place in; and facts Soltra derives from the route: the tiles it filled, the city, region, and country it crossed, and records such as your longest, your fastest time over a set distance, or your first in a city.

For features we may add later, Soltra also keeps the activity type exactly as the source named it, such as “Trail Run” from Strava, a workout file’s sport and sub-sport, or Apple Health’s workout type. For an activity imported from a Strava export it keeps four more fields from the export’s activities list: the gear name, whether you marked it a commute, your perceived exertion, and the Strava activity ID. None of these is shown in the app today. Soltra doesn’t keep the list’s private notes, media and file names, flags, or weather.

Soltra also keeps the original each activity arrived as: the file you imported, the file Garmin Connect sent, or the data your phone uploaded for a Soltra recording or an Apple Health workout, including how accurate each GPS reading was. We keep it for three reasons: to recalculate the activity exactly when you change its type, to recalculate it if we correct how a number is worked out, and to give you a complete copy of your data when you ask for one. It is private to your account: no one else using Soltra can read it. Activities Soltra received before it began keeping originals have none.

The calorie figure is computed from your body weight, so that number can be used to estimate your weight.

Soltra has no privacy zones and no route trimming, because no one but you sees your routes.

3.6 Territory and places

Your filled tiles are computed on our servers from your routes on a fixed hexagonal grid and stored as tile identifiers against your account. Cities, regions, and countries are worked out inside our own database against public map data (Overture Maps, Natural Earth, OpenStreetMap contributors under the Open Database License, and GeoNames), which we host ourselves. Your coordinates aren’t sent to a geocoding service or any other third party.

3.7 Photos

Matching happens on your phone: Soltra looks for photos taken during an activity and shows them to you and works fully if you grant access to only a selection of your library. Nothing uploads until you confirm it and Soltra doesn’t upload a photo you haven’t confirmed. Soltra doesn’t look in your Hidden album and doesn’t suggest photos from iCloud Shared Albums, though you can hand-pick one. If you use an iCloud Shared Photo Library, iOS does not let Soltra tell those photos from your own, so a photo someone else took during your activity can appear as a suggestion. Only what you confirm is uploaded. Hiding a photo in Photos stops Soltra reading it, so an upload that has not happened yet will not happen, though one already uploaded stays attached until you remove it. Only a downsized display copy and a thumbnail are uploaded, not the original, and the stored copies carry no embedded metadata. Each photo is stored with its capture time and, when the activity has a usable position, a precise location: its own GPS position when that sits on or near your route, otherwise estimated from its timestamp along the route, or the activity’s starting point. A profile photo goes through the system picker, which needs no library permission. Soltra has no camera permission.

3.8 Sharing cards and replay videos

Share cards and replay videos are rendered entirely on your iPhone and handed to the iOS share sheet. Nothing is uploaded to Soltra. The temporary video file is kept out of device backups and deleted once the share sheet closes. What leaves your phone is what you chose to share, to the app or person you chose. If you save one to Photos and you haven’t already given Soltra access to your photo library, iOS asks whether Soltra may add to it. That add-only permission lets Soltra add to your library, not look through it.

3.9 Purchases

Apple sells Premium through the App Store. Soltra doesn’t see your card or bank details. RevenueCat (Section 9) receives the App Store transaction identifiers and links them to your Soltra account identifier. Our servers keep your subscription status, product, and trial and renewal dates.

3.10 Notifications

Soltra’s notifications cover your activities, places, personal records, imports, and subscription. There are also weekly, monthly, and yearly summaries and news about the app. All of them are on by default. If you bring no activities when you first set up Soltra, it turns on quiet notifications, which iOS allows without asking and shows only in Notification Center. iOS asks you before notifications can appear as banners or make a sound. Once notifications are allowed, iOS gives Soltra a push token, which we store against your account so our servers can send them. A notification can name a place where you filled in new tiles, a rounded figure, or the kind of activity. It doesn’t contain coordinates, a route, a health reading, an imported file’s name, or any text you typed. You can switch off each kind in Soltra’s Settings or all of them in iOS Settings › Soltra. The push token is deleted when you sign out.

3.11 Usage analytics, crash reports, and freeze reports

Soltra records which features you use and whether they worked, so we can fix what breaks. Usage events go to PostHog (Section 9), each naming the feature and an outcome, plus the standard context the analytics SDK attaches: app name, bundle identifier, version and build; device manufacturer, model, type, name, and screen size; OS name and version; locale, time zone, and network type; whether the build came from TestFlight or the App Store; and your subscription status. They are keyed to your account identifier, so they are pseudonymous rather than anonymous. They note when you record, import, or share an activity, including one that came from Apple Health, when Soltra matches photos to an activity, and whether each worked. They don’t carry GPS coordinates, route geometry, heart rate, calories or any other health value; the type of a workout or any other detail about it or about a photo; a count of your activities, photos or imported files; or free text you typed. PostHog receives the network address your phone connects from, as with any internet request. Soltra tells PostHog not to work out a location from it. PostHog is set to discard the address rather than store it. Session replay is switched off. Crash and freeze reports go to Firebase Crashlytics (Section 9) with your device model and iOS version, not linked to your account identifier. A crash report carries the app’s state at the moment it crashed. A freeze report shows which part of Soltra’s code was stuck and roughly how long the app froze; iOS hands it to Soltra on a later launch, so it carries the app’s state at that time.

Our server also sends our analytics provider (Section 9) a few daily totals across all accounts, such as how many activities and photos were added and how imports finished. They aren’t tied to any account, small counts are left out, and nothing from Apple Health is included.

Usage analytics and crash and freeze reports are on by default and can be turned off with Share usage analytics in Settings › Privacy. Turning it off also deletes the crash and freeze reports still waiting on your phone. Nothing collected afterwards leaves your device. The daily totals above are counted on our servers, not on your phone, so this setting doesn’t change them.

3.12 The map itself

The map is drawn by Mapbox software running inside Soltra, which requests map tiles from Mapbox’s servers. Like any internet request, those carry your IP address, the map content requested, and app and software versions, under Mapbox’s own privacy policy (mapbox.com/legal/privacy). That software can also send Mapbox de-identified location telemetry. Soltra switches it off and it stays off unless you turn it on yourself from the map’s ⓘ menu. Mapbox’s policy lets it use de-identified data from map requests, and from that telemetry if you turn it on, to improve its products, including training its AI models. Mapbox offers no setting that turns this off.

3.13 Age check at sign-in

Where the law requires it, Apple may show its own age-range prompt before you sign in. Apple tells Soltra only an age range, not a birthday, and Soltra keeps nothing from it: the answer decides whether sign-in continues, then is discarded. Elsewhere, no prompt appears.

3.14 Server logs and IP addresses

Our hosting provider, Supabase, logs each request with the IP address it came from, the time, the path, and the outcome. We use these only to keep the service running and secure and to investigate faults and they are kept only briefly, for a period that provider sets. Mapbox, PostHog, and Google’s push service also see your IP address when serving their requests, under their own policies.

Search text is sent to our servers to find matches and isn’t stored.

3.15 The joinsoltra.com website

This policy is published on joinsoltra.com. The site sets no cookies and runs no analytics in your browser. The site used to have a waitlist. If you joined it, your email address and sign-up time are stored with Cloudflare (Workers KV) until Soltra launches or you ask to be removed and are used only to tell you about availability. Each sign-up also sent PostHog (Section 9) a count from our server so we knew someone joined. It carried no email address and nothing about you or your browser. The form was protected by Cloudflare Turnstile, which checked technical signals from your browser to tell people from bots. Cloudflare keeps ordinary access logs as the site’s host.

3.16 What Soltra does not collect

Soltra has no permission for, and doesn’t access: your contacts, calendar, camera, microphone, Bluetooth devices, clipboard, or the advertising identifier. It does not ask for App Tracking Transparency, because it does not track you across other companies’ apps or websites. It does not use iCloud. There is no Apple Watch app. Watch workouts reach Soltra through Apple Health.

4. Why we use your data

Soltra uses what it collects only for these purposes:

• to create and secure your account and check that Soltra is offered in your country;
• for an account created on or after October 12, 2026, to email you news about Soltra, such as when it reaches the App Store (you can stop these at any time);
• to draw your map: your routes, tiles, territory, statistics, places, and photos;
• to estimate calories, from the weight you allow us to read or type in yourself;
• to save activities you record back to Apple Health, if you allow it;
• to send activities you record to Strava, if you connect it;
• to provide Premium and keep our record of your subscription;
• to send you notifications, which you can switch off;
• to find bugs and see what is worth improving;
• to keep a record that you agreed to our Terms of Service and this policy;
• to keep Soltra secure, prevent abuse, and meet our legal duties.

Your health data and your precise location are used only for the features above. You turn each source on yourself, on Soltra’s own screens and the iOS permission prompts that follow are how the phone lets Soltra read it. You can change your mind at any time: change a permission in iOS or the Health app, disconnect Strava, turn off analytics, or delete your data (Section 10). That does not undo what already happened, but it stops it going forward, and deleting your data removes what was collected.

What you must provide. Signing in with Apple is required to create an account. Without it there is no account. Everything else is optional, but Soltra can only draw a map from activities, so with no Apple Health permission, no recordings, and no imports the map stays empty.

Soltra makes no automated decisions about you. The only things it computes automatically are your own statistics, tiles, places, and achievements, shown to you alone.

5. How we handle Apple Health data

Because Soltra uses Apple’s HealthKit framework, here is how we handle Apple Health data, which also reflects Apple’s requirements for such apps:

• We use Apple Health data only to provide Soltra’s features to you: drawing routes, filling in tiles, computing statistics, and estimating calories.
• We don’t use it for advertising or marketing, don’t use it for data mining, and don’t disclose it to any third party for those purposes.
• We don’t sell it to advertising platforms, data brokers, or information resellers.
• We share it with a third party only at your instruction and only with a service that provides health or fitness features to you. Today that means Strava, and only if you connect it.
• We don’t store it in iCloud.
• You can revoke Soltra’s access in the Health app at any time and you can delete everything Soltra derived from it in Settings.

Deleting your data (Section 10) pauses Apple Health sync until you turn it back on in Soltra’s Settings, so deleted workouts are not immediately re-imported.

6. Location, routes, and territory

Your location is collected only while you are recording an activity or when you import or sync a route that already contains one (Sections 3.3 and 3.4). Soltra uses no geofencing of any kind, around healthcare facilities or anywhere else. Routes are stored at full resolution, including where you started and stopped and Soltra offers no privacy zones or trimming because routes aren’t shown to anyone but you.

7. Photos

Section 3.7 is the full account. Photos and their locations are visible only to you and you can delete every attached photo at once from Settings.

8. Connecting Strava and Garmin Connect

8.1 Strava

Connecting Strava is optional and connecting is your consent to the sharing it describes. If you connect it, Soltra sends each activity you record in Soltra that has a real GPS route to your Strava account, automatically, until you disconnect. Recordings made before you connected are only sent if you start the one-off catch-up in Settings and activities that came from Apple Health or an import aren’t sent, because they already exist elsewhere.

Strava receives a standard workout (FIT) file built from the stored sample track: the title, type, and start time, timestamps and coordinates, cumulative distance, altitude, elapsed and active time, and elevation gain. An iPhone recording carries no heart rate, cadence, power or temperature, so none is sent and Soltra doesn’t send your step count or calories.

Data flows one way. Strava attaches a basic read permission to every connection. Soltra doesn’t use it and doesn’t call Strava to read your activities, statistics, or profile. We store your Strava athlete identifier and the credentials Strava issues on our servers, readable only by our server code, not on your phone, and not shared.

Disconnecting in Settings stops further uploads, revokes Soltra’s access on Strava’s side and deletes the credentials. Deleting your account does the same and discards anything still queued. Strava’s interface gives us no way to delete activities already in your Strava account, so delete those in Strava if you wish. Once an activity reaches Strava it is Strava’s responsibility under its own privacy policy and your Strava settings decide who can see it.

8.2 Garmin Connect

Connecting your Garmin Connect account is optional. The feature is rolling out, so your app may not show it yet. You start in Soltra, sign in on Garmin Connect’s own page, and choose there what to share. By connecting, you consent to what this section describes.

What Soltra receives. Only activities. After you connect, each time an activity you record reaches Garmin Connect, Garmin Connect sends Soltra that activity’s file (FIT, TCX, or GPX) and the name of the device that recorded it. Activities recorded before you connected aren’t sent this way. You can import them as files instead (Section 3.4). Soltra doesn’t ask Garmin Connect for your sleep, stress, heart-rate history, body measurements, or any other data. If Garmin Connect sends any of that, Soltra doesn’t keep it. Soltra doesn’t read your Garmin Connect profile.

How Soltra uses Garmin Connect data. Only to show you your own activities. Our servers turn each file into an activity record (Section 3.5): the route, the totals, and a sample track that can include heart rate, cadence, power, temperature, and altitude. The file itself is kept as that activity’s original (Section 3.5). Soltra discards any file it can’t use, such as an indoor, multisport, manual, or unsupported activity. From the activities it keeps, Soltra builds your routes, territory, places, records, and statistics, shows your replays, and makes the share cards you ask for. Garmin Connect activities also count toward your weekly, monthly, and yearly summaries and your On This Day notifications. No other Soltra user can see this data. We don’t use Garmin Connect data for advertising, marketing, or research, and we don’t build aggregated or de-identified datasets from it. The daily totals in Section 3.11 count Garmin Connect activities and files imported from Garmin devices across all accounts. Those totals leave out any count under 10, and nothing in them is tied to a person.

What we store about the connection. Our servers keep the credentials Garmin Connect issues, your Garmin Connect user identifier, and the permissions you granted. Only our server code can read them. They aren’t sent to your phone, written to logs, or shared. For each activity Garmin Connect tells us about, we also keep its Garmin Connect activity number and whether we fetched it, so an activity you deleted isn’t fetched again.

Who receives Garmin Connect data. Garmin Connect sends the data to our servers, which Supabase runs for us (Section 9), and our servers send it to your phone. Google Firebase and Apple deliver any notification that draws on a Garmin Connect activity (Section 3.10). Such a notification can name a place, the activity type, the recording device, or a rounded figure. It doesn’t include the route or any health reading. If you ask us by email for a copy of your data, Google Workspace carries that email (Section 9). Usage events can note that you shared or opened something about a Garmin Connect activity but carry none of the activity’s data (Section 3.11). A share card or video you make goes wherever you send it (Section 3.8). On your phone, Mapbox’s map software draws the route. Mapbox receives requests for the map tiles that show the area on screen, including the tiles along a route when you play its replay. The pattern of those tiles shows roughly where the route went but not its points, times, or health values (Section 3.12). No other company receives Garmin Connect data. We don’t sell, rent, or trade Garmin Connect data and don’t share it with any third party for that party’s own use.

AI transparency statement. No AI system at Soltra, or at any company that processes data for us, processes your Garmin Connect data. We don’t use Garmin Connect data, or anything derived from it, to train, evaluate, or improve an AI model or give it to anyone else for that purpose. The one thing we can’t rule out is Mapbox’s own use of map requests: its policy lets it use de-identified map requests, which can include the tiles along a route you replay, to improve its products, including its AI models (Section 3.12). Because no AI processes Garmin Connect data, there is nothing to consent to today. If that changes, Soltra will ask for your explicit consent in the app before any AI processes your Garmin Connect data. You can withdraw that consent in Settings.

Data flows one way. Soltra doesn’t write anything to Garmin Connect. Activities that came from Garmin Connect aren’t sent on to Strava or saved to Apple Health (Section 12.3).

Disconnecting. When you disconnect in Soltra’s Settings, Soltra tells Garmin Connect to end the connection, stops new activities from arriving, deletes the credentials and your Garmin Connect user identifier, and drops any activity it hasn’t fetched yet. If Garmin Connect can’t be reached at that moment, we keep only the credentials needed to retry. We retry over about a day and then delete them whether or not Garmin Connect answers. Removing Soltra from your connected apps in Garmin Connect has the same effect as disconnecting. Turning off activity sharing for Soltra in Garmin Connect pauses new activities until you turn sharing back on. Activities Soltra already received stay in your account until you delete them. Delete your data removes those activities and their files but keeps the connection, so new activities keep arriving. Delete your account also ends the connection on Garmin Connect’s side (Section 10.2). Nothing Soltra does changes or deletes anything in your Garmin Connect account.

Seeing, correcting, exporting, or deleting your data. You can see your Garmin Connect activities in the app and edit each activity’s title, description, and type there. To get a copy of everything we hold, including the original Garmin Connect files, or to have us correct or delete something the app doesn’t let you change, write to us (Section 12.2).

9. Who processes your data on our behalf and who else receives it

We do not sell, rent or trade your personal data and we do not share it for anyone else’s advertising. The companies below are all based in the United States.

Processors handle your data only on our instructions, under contracts that require them to protect it at least as strongly as this policy states and to use it only to provide their service to us: Supabase runs our database, file storage, sign-in, and server code, which is everything this policy calls “our servers”, with the database and files hosted on Amazon Web Services in the United States; PostHog receives the usage events and daily totals in Section 3.11 and the waitlist sign-up count in Section 3.15; Google Firebase handles crash and freeze reporting and push delivery; Google Workspace sends and receives our email; RevenueCat tracks subscription status.

Independent recipients receive data under their own privacy policies: Apple for sign-in, Apple Health on your device, purchases, and push delivery; Mapbox for the map requests it serves (Section 3.12); Cloudflare for the joinsoltra.com website and waitlist (Section 3.15); Strava, only if you connect it (Section 8.1); and Garmin Connect, only if you connect it (Section 8.2). Garmin Connect sends your activities to us and receives from us only what keeps the connection working.

The public map data used to name cities and countries (Overture Maps, Natural Earth, OpenStreetMap contributors under the Open Database License, GeoNames) is downloaded and stored by us. Those projects receive nothing from us or from you.

No location is put into an analytics event. Soltra’s own analytics events don’t carry your location, your routes, or any health value. The Mapbox telemetry that could have sent location to Mapbox is switched off (Section 3.12). Soltra also tells our analytics provider not to work out a location from the network address your phone connects from (Section 3.11). Soltra’s App Store privacy label declares precise location as used only for app functionality. It declares approximate location for app functionality and for other purposes, which covers Mapbox’s own use of map requests (Section 3.12). It declares no tracking.

The few cases where we would disclose data to anyone else.

• If the law requires it: a subpoena, court order, or lawful request from a public authority. We tell you where we are permitted and able to and we disclose only what the request lawfully covers.
• To protect someone’s safety or to investigate fraud or abuse of Soltra.
• If Soltra is sold or merged, your data may transfer to the new owner under this same policy, and your deletion rights continue to apply.

10. How long we keep your data and how to delete it

10.1 Retention

Almost everything Soltra holds is kept until you delete it and goes when you do: your account and sign-in identity, the record of your agreement to our Terms and this policy, your display name, profile photo, and body weight, your activities, the originals they arrived as (Section 3.5), routes, sample tracks, tiles, places, and statistics (including duplicates Soltra detected and hid from you), your import history, your attached photos and their locations, your subscription records, your Strava connection and credentials, your Garmin Connect connection (its credentials and your Garmin Connect user identifier), the record of which Garmin Connect activities we fetched, and your push token and notification settings. Section 10.2 says which of the three delete actions clears which.

These are the exceptions:

10.2 Three ways to delete, all in Soltra’s Settings

Delete all photos. Removes every photo attached to your activities: the associations, the stored copies, and their locations. Your activities, routes, territory, statistics, profile, and account are untouched. This happens at once.

Delete your data. Permanently removes all your activity data from our servers: routes, sample tracks, tiles, territory, place attributions, statistics, achievements, import history and files, the originals your activities arrived as, photos, notification history, any queued Strava uploads, and the activities and files that came from Garmin Connect. If Garmin Connect had told us about an activity that Soltra hadn’t fetched yet, that activity still arrives after the deletion, like any new one. It also clears your display name, profile photo, and stored body weight and stops Soltra reading your weight from Apple Health again until you enter one yourself. What it deliberately leaves, so that you can keep using the app: your sign-in identity, the record of your agreement to our Terms and this policy, your subscription and its records, your notification settings and push token, and your Strava and Garmin Connect connections if you made them. You stay signed in and can start again with an empty map. Apple Health sync is paused until you turn it back on in Settings, so deleted workouts are not immediately re-imported.

Delete your account. Everything above, plus your sign-in identity, the record of your agreement to our Terms and this policy, your subscription records, your notification settings and push token, your Strava connection (which is also revoked on Strava’s side), and your Garmin Connect connection (which we also end on Garmin Connect’s side). If Garmin Connect can’t be reached, we retry over about a day and then delete the credentials whether or not Garmin Connect answers. We ask Apple to revoke the Sign in with Apple grant and ask RevenueCat to delete your subscriber record. You are signed out on every device. Deleting your account does not cancel an App Store subscription. Cancel that in your App Store settings, as the app reminds you.

Each request is accepted immediately and your data becomes inaccessible at once. The physical removal from our database and file storage runs in the background promptly and a scheduled process retries anything that fails and flags for us anything still outstanding. Copies in our hosting provider’s backups expire on that provider’s own schedule and in every case within six months, the limit state law sets, and aren’t used to restore data you deleted. When you delete your account we instruct the processors in Section 9 that hold data for us to delete it. When you delete only your data, your subscription and notification settings stay with those providers, because your account continues. Either way we delete the analytics profile and events PostHog holds under your account identifier. A request made by email is completed within the time the law allows. Both are irreversible. Keep a copy of anything you want first (Section 12.3). Either one cancels an import still running on our servers. If an import or a recording is running on your iPhone, finish or cancel it first.

If you cannot use the app, email [email protected] and we delete for you after verifying the request (Section 12).

11. How we protect your data

• Soltra uses TLS to encrypt traffic in transit between your phone, our servers, and the companies in Section 9.
• Every table holding personal data is restricted to its owner: the server is designed to refuse any query for another person’s rows and there is no feature that reads across users. The app is built to hold no key that can read another person’s data. The only keys it ships are the public ones Mapbox and RevenueCat issue for use inside an app.
• Photos and import files sit in private buckets no public URL reaches. The app fetches them with short-lived links that expire. Strava credentials and other secrets are readable only by our server code and aren’t logged.
• Our server code doesn’t put coordinates, email addresses or health values into logs.
• On your phone, staged imports, pending uploads, cached photos, your stored body weight, Soltra’s record of which Apple Health workouts it has read, your local copy of your activities, the map position you last viewed, and the live recording buffer are all excluded from device backups and protected by iOS file encryption, so an iCloud or computer backup does not carry your routes, health readings, or body weight out of the app. Soltra rebuilds that local copy from our servers when you sign in again. Preferences and a few sync bookmarks do go into backups (Section 10.1).
• Soltra doesn’t write to iCloud and doesn’t sync through it.

No system is perfect. If we learn that your health or location data has been acquired or disclosed without authorisation, we notify you as the Federal Trade Commission’s Health Breach Notification Rule requires, along with the FTC and any other regulator the law requires, saying what happened, what data was involved, and what we are doing about it.

12. Your choices and your rights

12.1 Controls inside the app and iOS

Apple Health access is in the Health app › your profile › Apps (under Privacy) › Soltra. Location, motion, photo, and notification access are in iOS Settings › Soltra. Everything else is in Soltra’s own Settings: usage analytics and crash reporting under Privacy, the Strava and Garmin Connect connections, individual notifications, and the three delete actions in Section 10.2. Mapbox telemetry is off unless you turned it on from the map’s ⓘ menu. Your name, photo, weight, and an activity’s details you edit in the app.

12.2 Rights you can exercise by writing to us

Wherever you live, you can ask us to:

• Tell you whether we hold personal data about you and give you a copy of it (access).
• Correct anything inaccurate.
• Delete your data or your account (also available in the app).
• Give you a copy in a usable format so you can take it elsewhere (portability).
• Ask us to stop or limit a particular use.
• Withdraw consent you gave earlier.
• Appeal if we decline a request. We explain why and how to escalate.

Write to [email protected]. We answer, and complete a deletion, within the time the law allows. We keep the correspondence only as long as we need it to show your request was honoured. We don’t charge for a request unless it is clearly repetitive or unfounded and we don’t treat you differently for exercising a right.

How we verify it is you. The only contact detail we hold is the email address Apple gave us, which may be a private relay address that forwards to you rather than your own. To act on an emailed request we reply to that address and act only on a confirmation that comes back from it. You can see which address it is under iOS Settings › your name › Sign in with Apple › Soltra. Making the change from inside the app, where being signed in is the proof, is the faster route. If you have turned off Sign in with Apple for Soltra in your Apple Account, the relay address no longer forwards to you and we may be unable to verify an emailed request. Signing in again restores it. An authorised agent can act for you with your written permission and the same verification.

12.3 Taking your activities elsewhere

There is no export inside the app. Two connections carry your activities out as data other apps can read. Both carry only the activities you record in Soltra:

• Apple Health. If you allow Soltra to write to Apple Health, it saves each activity you record there, with its workout, route, active energy burned, and distance where the activity has them (Section 3.2). Other apps you allow can read it from Apple Health.
• Strava. If you connect Strava, Soltra sends each activity you record from then on that has a GPS route to your Strava account as a standard workout file. Earlier recordings go only if you run the catch-up in Settings (Section 8.1).

Neither one carries activities that came into Soltra from Apple Health, from Garmin Connect, or from files you imported. Those already exist outside Soltra: in Apple Health, in Garmin Connect, and in the files you imported. Deleting them in Soltra doesn’t remove them there. Share cards and replay videos can be made for any activity. They are pictures and videos, not a copy of your data (Section 3.8).

For a complete copy of what we hold, including the original each activity arrived as, where we kept one (Section 3.5), write to us (Section 12.2). Deleting your data or your account can’t be undone (Section 10.2). Take what you want to keep first.

13. Outside the United States

Soltra is offered only through the United States App Store and its beta only to people whose App Store account is in the United States. It is not supported anywhere else, so this policy describes United States law.

14. If you are in the United States

Wherever you live in the US, the same practices apply: we do not sell your personal information and do not share it for cross-context behavioural or targeted advertising. We do not profile you to make decisions about you and we do not let advertising companies or anyone else track your Soltra activity across unrelated apps or websites. You have the rights in Section 12.

Your precise location and health data are sensitive information under California, Virginia, Colorado, Connecticut, Texas, Oregon, Maryland, and the other state privacy laws. We use them only to provide the features you asked for, not to infer characteristics about you, and only with your consent, given through the permissions and choices in Section 3.

California. The California Consumer Privacy Act applies only to businesses above certain size thresholds, which Soltra does not meet today. We make these commitments anyway. We collect the categories in Section 3: identifiers, health and fitness information, precise geolocation, photographs, subscription information, and how you use the app, for the purposes in Section 4, from you, your devices, and the companies in Section 9. Because we do not sell or share personal information, a Global Privacy Control signal changes nothing and we do not respond to “Do Not Track” because we do not track you across sites or apps. Under California’s “Shine the Light” law you may ask what personal information we disclosed for anyone’s direct marketing: the answer is none.

Appeals. If we decline a request you may appeal by replying to our answer. If the appeal is declined you may contact your state attorney general.

Washington, Nevada, and Connecticut consumer health data. Our separate Consumer Health Data Privacy Policy states, in the form those laws require, what consumer health data we collect, why, with whom we share it, and how to exercise your rights over it.

15. Washington, Nevada, and Connecticut consumer health data

Our Consumer Health Data Privacy Policy is a separate page. It sets out what consumer health data Soltra collects, where it comes from, why we use it, and who receives it. It also explains how to access or delete that data, withdraw your consent, or appeal a decision. It applies to residents of Washington, Nevada, and Connecticut and to anyone whose consumer health data is collected in Washington or Nevada.

16. Children and age

Soltra is not directed at children. You must be at least 13 to use it.

Apple’s age-range check may run before sign-in where the law requires it (Section 3.13). Soltra keeps nothing from it. If we learn that someone under the minimum age has created an account, we delete the account and its data. If you believe that has happened, write to [email protected].

If you are under 18, ask a parent or guardian to agree to our Terms of Service on your behalf. Because nothing in Soltra is shared with other users, a teenager’s routes aren’t exposed to anyone.

17. Changes to this policy

When we change this policy, we update the date at the top. For a change that affects how we use data we already hold about you or that reduces your rights, we tell you in the app before it takes effect and, where the law requires, ask for your consent again. Continuing to use Soltra after a change that needs no consent means the new policy applies.

18. Contact

Privacy questions and requests: [email protected]
Post: Soltra LLC, 440 N Barranca Ave #5017, Covina, CA 91723, United States