Draft for review — not yet in effect. Not legal advice, and not reviewed by counsel (drafted 2026-11-13 from BioLog's published policy and ViaTrail's code). Highlighted notes mark facts to confirm before publishing.
ViaTrail — Privacy Policy
Published by Terrastation SBC, a Minnesota specific benefit corporation · Last updated: [REVIEW: publication date] · Version 1.0
This Privacy Policy explains how Terrastation SBC (“Terrastation,” “we,” “us”), a Minnesota specific benefit corporation, collects, uses, shares, and protects personal information in connection with the ViaTrail mobile application and related websites (the “Service”). Protecting privacy — especially the privacy of younger users — is central to our public-benefit mission. We aim to collect only what the Service needs, and we do not sell your personal information.
ViaTrail is a private walking journal. It has no social features: nothing you record is shown to other ViaTrail users. The only people who ever receive information about your outings are the emergency contacts you choose, as described in section 2.
We apply a high global standard, drawing on the EU/UK General Data Protection Regulation (GDPR) and U.S. state privacy laws, to all users regardless of where they live.
1. Ages we serve and children's privacy
ViaTrail is intended for users who are at least 13 years old. Before an account can be created, the app asks for the age range your Apple Account shares. If it shows you are under 13, the sign-up screen is not shown, no account is created, and no information is collected. If you decline to share an age range, or the check cannot be completed, you may create an account, and by doing so you confirm that you are at least 13. [REVIEW: deliberately unlike BioLog, a decline does not block sign-up (ViaTrail D34). The “you confirm” sentence is new and is mirrored in Terms §1.]
If you are between 13 and the age of majority where you live, you may use the Service only with the permission and supervision of a parent or legal guardian, who agrees to our Terms on your behalf. We do not permit accounts for children under 13 and do not knowingly collect their personal information. If we learn that a child under 13 has created an account, we will delete the account and its data. A parent or guardian may contact us at the address below with any question about a child's use of the Service.
2. Information we collect
Account information
When you create an account we collect your email address and, if you give one, a display name. Your display name is not shown to other users; it is the name your emergency contacts see in the messages we send them. Authentication is handled by our identity provider (Supabase Auth), which also records when you signed up and last signed in. [REVIEW: Supabase Auth's own audit log can also hold the IP address of sign-in events — confirm on the prod project, and add it here if so.]
Age eligibility
The app uses the age range your Apple Account shares on your device, to decide whether an account may be created and whether AI species identification is available. We do not collect or store your date of birth or age range. We store only whether your account may use AI species identification, as derived from that age range.
Outings and the path you walk
When you start an outing, the app records the path you walk: a series of GPS positions, each with its time, its accuracy and, where available, its altitude. Recording continues while the outing is running — including with the screen off or the app in the background — and stops when you end it. We also store the outing's title (named automatically from the place and time it started, which you can change), its start and end times, and your phone's time zone. When an outing is ended at the point your walk actually finished, any positions recorded after that point are deleted.
To notice when a walk is over — for example, when you stop for a while or start driving — the app uses your iPhone's motion and activity data. That data is processed on your iPhone and is never sent to us.
Sightings and photos
When you log a sighting during an outing we store its photo, the names, category, and notes you add, where it was made (GPS coordinates, and where available elevation and accuracy), and when. If you choose a photo from your device's library, we read the date and location recorded in that photo, if it has them, to fill in the sighting. Photos are re-encoded on your device and stripped of embedded metadata on our servers before they are stored. You may also search for a named place to set where a sighting was made.
AI species identification
If you use AI species identification, the app first asks for your permission, and you can withdraw it at any time in Account. We then send the photograph together with an approximate location for the sighting (rounded to about 1 kilometer), its elevation rounded to the nearest 50 meters, the month and year it was observed, and the category and names you entered, to our AI provider, Anthropic, PBC, which returns identification suggestions. Anthropic generally deletes the inputs and outputs of this processing within 30 days. Content that Anthropic's systems flag for policy review may be retained for up to two years, and related safety-classification scores for up to seven years. Anthropic is contractually prohibited from using this content to train its models.
If you accept a suggestion, the app saves two things it suggested with the sighting: the species' classification (kingdom, phylum, class, order, family, and genus, where the AI is confident of them) and a short description of the species' typical habitat. Like the rest of your journal, both are shown only to you.
Safety backup and emergency contacts
Safety backup is optional and is off unless you turn it on for an outing. To use it, you add up to five emergency contacts: a name you choose for each one and their email address. This is personal information about people who may not use ViaTrail, so please add only people who would expect to hear from you.
The first time you add someone, we email them one invitation. Nothing else is sent to them unless they accept. A person can decline, and can ask never to be added as anyone's emergency contact again. We keep a record of each invitation sent and of each such choice, linked to their email address, so that removing and re-adding a contact cannot resend an invitation or undo their answer.
For an outing with safety backup on, we also store which contacts are watching it, your planned finish time, how long a silence or a delay should last before your contacts are told, and when our servers last heard from your phone. While the outing runs, your phone sends its path to us whenever it has signal, and a scheduled job on our servers checks whether your phone has gone quiet or you are overdue.
What your contacts receive. We email your accepted contacts when an outing with safety backup starts, if your phone goes quiet, if you are overdue, when you push back your finish time, if you ask for help, and when the outing ends. Depending on the message, it includes your display name and email address, the outing's title, its start time and planned finish, your starting position, the last position your phone reported with its time, accuracy, and altitude, the distance walked so far, and links that show those positions on OpenStreetMap. Each message lets the contact stop receiving messages about you.
“I need help”
The “I need help” screen shows your position on your device. Calling an emergency number or texting the people you choose happens through your iPhone's own Phone and Messages apps; we do not receive those calls or messages. If safety backup is on and you choose to alert your contacts, we send them the help message described above, with your position.
Diagnostic and crash data
Our servers use error logging (Sentry) to capture errors so we can fix them, retained for up to 90 days. These reports do not include IP addresses, email addresses, names, the contents of requests, or locations; they may include an internal account identifier. The ViaTrail app does not send crash reports to us. Reporting is disabled entirely in our development environment. [REVIEW: 90 days is BioLog's Sentry retention; confirm ViaTrail's prod project uses the same.]
Network data
When the app connects to our servers, the IP address it connects from reaches our API host (Render). We use it to limit repeated sign-in and verification attempts; the limiter holds it in memory only. Render's request logs also record it, for the period stated in section 8.
Cookies and browser storage
The ViaTrail app and our website at viatrail.live do not use cookies or browser storage for advertising or analytics. The website sets no cookies at all. [REVIEW: the contact invitation and “stop messages” pages are served by our API, not this site; confirm they set no cookies either.]
Information we do not collect
We do not serve advertising and do not collect advertising identifiers. We do not read your device's address book, and we do not receive your motion data. We do not sell or “share” (as defined under U.S. state privacy laws) your personal information for cross-context behavioral advertising.
3. How we use your information
- Provide the Service: record and store your outings, paths, sightings, and photos, and sync them to your account.
- Provide AI species identification when you request it.
- Operate safety backup when you turn it on: send invitations and messages to your emergency contacts, and notice when your phone has gone quiet or you are overdue.
- Communicate with you: transactional email such as verification codes.
- Keep the Service safe: prevent abuse of the invitation feature (for example, by limiting how many invitations can be sent), and enforce our Terms.
- Maintain reliability, protect the Service, and comply with law.
4. Legal bases for processing
- Performance of a contract — to provide your account and the core features you request, including safety backup.
- Consent — for device permissions (camera, location, and motion) and for AI identification; you may withdraw consent at any time. An emergency contact's acceptance is their consent to receive messages about your outings.
- Legitimate interests — to secure the Service, prevent abuse, and improve reliability; and to send a contact the single invitation that asks for their consent, and keep their answer.
- Legal obligation — to comply with applicable law, including child-safety reporting.
5. How your information is shared
We do not sell your personal information. Your outings, paths, sightings, photos, and notes are not visible to other ViaTrail users. We share information only as follows:
- With your emergency contacts, at your direction — only for outings with safety backup on, only to contacts who have accepted, and only as described in section 2.
- With service providers under contract — Supabase (database, storage, authentication), Render (API hosting and the scheduled job that checks safety-backup outings), Resend (delivery of email, including verification codes, invitations, and messages to your contacts), Sentry (error reporting), Anthropic, PBC (AI species identification, which receives the photograph and the approximate location, elevation, and month and year of the sighting), Netlify (hosting for viatrail.live, which receives visitors' IP addresses), and Apple (App Store / TestFlight, the age range, and maps and place search, which receive the text you search for, the map area shown, and an outing's starting position so the app can name the place). Each processes data on our behalf under data-processing terms. [REVIEW: confirm data-processing terms are in place with each provider for ViaTrail, Netlify included.]
- With OpenStreetMap — when a contact opens a map link in one of our messages, OpenStreetMap receives the contact's IP address and the position shown, under its own terms.
- For legal and safety reasons — to comply with law and lawful requests, enforce our Terms, and protect users and the public, including reporting apparent child sexual abuse material as described below.
- In a business transfer — in a merger, acquisition, or asset sale, subject to this policy.
6. Child-safety reporting
If we become aware of apparent child sexual abuse material, we will preserve it as required and report it to the National Center for Missing & Exploited Children (NCMEC) and, as appropriate, to law enforcement, consistent with applicable law. [REVIEW: BioLog's §6 says it “may scan content, including public photos”. ViaTrail has no public content and no photo scanning, so that sentence was dropped; confirm.]
7. Location data
ViaTrail records precise location only while an outing is running — continuously, including in the background, so that your path is complete — and when you log a sighting. It asks for permission first, and you can revoke it at any time in your device settings; without it, the app cannot record a path. Your path and sightings are visible only to you. Your emergency contacts receive positions only from outings with safety backup on, as described in section 2. When you use AI identification, an approximate location is sent to our AI provider, and when an outing starts its starting position is sent to Apple to name the place, as described above.
8. Data retention
When you delete your account through the in-app deletion option, we immediately and permanently delete your live data — your account, outings and their paths, sightings, stored photos, emergency contacts and the records of invitations you sent, and your authentication identity — with no soft-delete or deactivation delay. When you delete an outing, its path, sightings, and photos are deleted at once; if your contacts were told about that outing, its title, times, and planned finish are kept for up to 24 hours, only to tell them it has finished. Residual copies age out of backups as follows:
- Database backups (application and identity data) — retained for 7 days on a rolling basis, as nightly backups.
- Photo storage backups — retained for 30 days under an immutable object lock that prevents early deletion (including by a compromised key).
- Error and diagnostic data (no IP addresses, email addresses, or names) — retained for up to 90 days.
- API request logs, which include the IP address a request came from — kept by Render for [REVIEW: Render's log retention for the plan ViaTrail's prod service will run on].
[REVIEW: backups are BioLog's arrangement, which you chose for ViaTrail — they must exist on the prod project before this is published.]
Two records are kept after an account is deleted. If someone asked never to be added as an emergency contact, we keep their email address so that no account can invite them again; this is their instruction, not the deleted account's data. And if we suspend an account for violating our Terms, we keep its email address and the reason, to enforce the suspension. [REVIEW: state how long the suspension record is kept — e.g. “for as long as the suspension lasts” or “indefinitely”. Nothing in the code expires it today.]
[REVIEW: Resend keeps its own log of emails sent, including recipient addresses — state its retention here once confirmed for the account ViaTrail uses.]
9. Your privacy rights and choices
You can rename or delete your outings and sightings, turn AI identification sharing off in Account, add or remove emergency contacts, and delete your entire account at any time in the app. To change the display name you gave at sign-up, contact us. [REVIEW: the app has no way to edit a display name after sign-up (no API route). Either build one, or keep this “contact us” line.]
If you are someone's emergency contact, you can decline an invitation, ask never to be added again, or stop messages using the link in any message we send you, and you may contact us to exercise the rights below.
Subject to applicable law, you may have rights to access, rectify, erase, restrict, or object to processing; to data portability; to withdraw consent; and to lodge a complaint with a supervisory authority. U.S. state residents may have rights to know, access, correct, delete, and obtain a portable copy of personal information, and to opt out of sale or targeted-advertising “sharing” (which we do not do). We will not discriminate against you for exercising these rights and, where required, will provide an appeal. To make a request, contact support@terrastation.io.
10. International data transfers
Our providers, including our AI provider, may process data in the United States and other countries. Where we transfer personal information out of the EEA, the UK, or Switzerland, we rely on an appropriate mechanism such as the Standard Contractual Clauses and the UK Addendum, with supplementary measures where needed.
11. Security
Your sign-in token is stored in the iPhone keychain, on that device only, and API traffic uses HTTPS. Photos are kept in private storage and shown through links that expire after an hour; the link our AI provider receives expires sooner. Invitation and “stop messages” links are stored only as a one-way hash, so a copy of our database cannot be used to answer for a contact. Photo backups are held under an immutable object lock. [REVIEW: true only once the section 8 backups exist on prod — confirm both together.] We take reasonable measures to protect your information however no system is perfectly secure.
12. Changes and contact
We may update this policy; material changes will be posted here with a new “last updated” date and, where appropriate, additional in-app notice.
Terrastation SBCEmail: support@terrastation.io