Footprints privacy policy
Effective 22 November 2026
Footprints lets you share where you are with people you choose, such as family. This policy explains what happens to your data when you use the Footprints apps for iPhone and Android. Footprints is run by Footprints Labs ("we", "us").
The short version
- We can't see your location. Your phone encrypts it before it leaves, and only the people you share with can decrypt it. The same goes for your name, the names of the people you share with, your places (such as "Home") and your battery level.
- There's no account. No email, phone number or password. The app makes a random key on your phone, and that key is how our server recognises your phone.
- No ads, no analytics, no tracking. The apps contain no advertising, analytics or crash-reporting code, and we don't sell or share data with anyone.
- Our server keeps very little, and not for long. Encrypted messages are deleted when they're delivered or after 7 days. A phone that hasn't connected for 90 days is deleted completely.
What stays on your phone
Your recent locations, the people you share with, their names, your places and your settings are stored only on your phone. The encryption keys are made on your phone, stay on it, and are left out of backups. If you delete the app or move to a new phone, these are gone, and your family will need to invite you again.
What our server (the "relay") stores
To deliver updates between phones that are often offline, the apps use a server we run, called the relay. It works like a locked mailbox. It holds encrypted messages it can't open, until the recipient's phone collects them.
The relay stores:
| What | Why | How long |
|---|---|---|
| Your phone's public key: a random number made by the app, not linked to your name, phone number or any account | So the relay can let your phone collect its own messages and no one else's | Until your phone hasn't connected for 90 days, then deleted |
| The day your phone last connected (the day only, not the time) | To know when to delete inactive phones | Same as above |
| A list of the mailboxes your phone collects from (random IDs, one per person sharing with you) | To deliver messages to the right phone | Until you remove that person, or 90 days of inactivity |
| Encrypted messages (your latest location, pause and stop notices, place alerts, key updates). Every one is the same size and can only be opened by its recipient | To deliver them | Deleted when the recipient's phone confirms it received them, when a newer location replaces an older one, or after 7 days, whichever comes first |
| Invites: an encrypted one-time exchange of keys when you add someone | To connect two phones | The contents are erased as soon as the invite is used. A record that the invite exists stays for up to 24 hours so a second tap on the link shows "already used" |
| A sign-in token (stored only as a one-way hash) | To keep your phone signed in | About 24 hours |
When delivered or expired messages are deleted, they are wiped from the database file, not just marked as deleted.
What the relay doesn't store: your location, your name, anyone else's name, your places, your battery level, the type of any message, or who sent it. Messages are written without saying who wrote them.
What the relay can see while it runs. Like any internet server, the relay sees the IP address of each connection and when it happens. It uses them in memory to limit abuse (rate limiting) and doesn't write them to disk. Our web server is set up with no access logs. In principle, someone with control of the server who watched these connections live could work out which phones share with each other, but not what they share. We plan to close this gap in a future version.
Notifications (push tokens)
The current apps don't send us a push-notification token. The Android app checks for updates by keeping a connection to the relay open while sharing is on, without using Google services. The relay software can store a push token if a future version of the app sends one. If it does, that token will be used only to wake your phone, any notification will contain no location or names, and we'll update this policy first.
Maps
Map images (tiles) are downloaded from our own map server. The request includes no identifier for you or your phone, and we keep no logs of it. Like any web request, it reveals your IP address and which map squares are being loaded, which can hint at the area you're looking at.
Place names from Apple or Google
To show a label such as a street or town next to someone on the map, the app asks your phone's built-in place-name service. On iPhone that's Apple's. On Android it's usually Google's, if your phone has Google services. It's sometimes absent, and then no label is shown. This sends a person's coordinates to Apple or Google, under their own privacy policies. It doesn't include names or anything that identifies you to us. If you tap Directions, the location is handed to your maps app.
Hosting
The relay and map server run on a rented server from OVHcloud, which processes the data described above on our behalf. They can't read the encrypted messages either. This privacy page itself is hosted by Vercel, which sees your IP address when you open it.
Deleting your data
Because there's no account, there's nothing for us to look up by name or email, and we can't tell which public key is yours. You're in control:
- Remove a person in the app: your phone stops collecting from that mailbox, and the relay deletes the mailbox and any messages waiting in it.
- Stop sharing or pause: your phone stops sending your location.
- Delete the app: the keys and everything stored on your phone are erased. What's left on the relay expires on its own: messages within 7 days, and your public key and mailbox list after 90 days.
Children
Footprints isn't directed at children under 13.
Changes to this policy
If we change what data the apps or the relay handle, we'll update this page and the date at the top before the change ships.
Contact
Questions about privacy: contact@footprints.here.
Security problems: please email the same address and say it's a security report.