Memory
Privacy

Privacy policy

Memory, the Android trip app · updated

Stays on your phone

Trips, plans, notes and to-dos
Expenses and who owes whom
Photos and memories
Documents, encrypted, never sent
Activity routes you record

Reaches our serveronly if you use it

Sign-in: Google id, email, name
Shared trips: encrypted, we can't read them
Trip pages you choose to publish
Ideas: a rounded destination point
Live flight: number, date and airports
Map routes: the start and end of ground legs
NEVER ADSTRACKINGSELLING DATAAI ON YOUR DATA

In short: what you put into Memory stays on your phone. There are no ads, no analytics and no tracking, and nothing is sold. A few lookups need the internet; this page lists every one of them, what is sent, and why.

01What stays on your phone

Your trips, plans, events, activities, expenses, notes, to-dos, people you add by name, photos, goals, boarding passes and your profile are stored only in Memory's own storage on your phone. Memory has no copy of them.

  • Android backup is turned off for Memory, so none of this goes to a cloud backup or to a new phone by itself. You can make your own export file (a .memory file, PDF, calendar or CSV) and decide where it goes. A full backup is a file locked with a password only you know; it includes your Documents unless you switch that off in Backup, and nobody (including us) can open it without the password.
  • Documents (passports, IDs, cards, insurance, medical details) are encrypted on the phone with a key kept in the phone's secure key store, are hidden from screenshots, and never leave the phone unless you yourself share a copy (for example, a watermarked copy you send to a trip member).
  • Location: Memory uses your phone's GPS only while you are recording an activity (a run, walk, hike or ride) that you started, and the route is stored on the phone. Memory does not track you in the background. To pick sensible defaults (country, currency, units), it reads your phone's region and network country on the phone; this is not sent anywhere.
  • Health Connect: if you allow it, Memory reads exercise sessions, distances and exercise routes from Health Connect to show them as activities. They are stored on the phone and not sent anywhere.
  • Camera and photos: used only when you scan a boarding pass or document, take a profile picture, or pick photos. Text and barcode reading (ML Kit) runs on the phone.
  • Notifications (document expiry reminders, "On this day", a followed flight) are made on the phone.
  • Plan with AI (only when you use it): on phones that have their own AI (Gemini Nano, part of Android), your request is processed on the phone and Memory sends it nowhere. On other phones, Memory writes the request for you and you choose to copy or send it to an AI app you use (ChatGPT, Claude, Gemini or another); that app then sees what you send it, under its own privacy policy. The request holds only the trip's place, dates, number of people, what you typed, and the times and places of stays and flights already booked: never names, documents, expenses, prices or booking references. Nothing is added to your plan until you review it.

02What goes to Memory's own server, and why

Memory has a small server, run by the app's developer on a rented server at memory.istemlab.com.np. It never stores your trips in readable form. It is contacted only for these features:

FeatureWhat is sentWhat is kept
Every server callA random install id made by the app (not linked to your name, phone number or Google account), so the server can limit how often one phone calls it.Counters in memory for about an hour. The server does not record IP addresses. Its web server keeps a short technical log (time, page address with private codes and search words removed, result), and only the newest few megabytes of it.
Ideas for a destinationThe destination's position (rounded to about 1 km by the phone and about 10 km by the server) and its country code. Nothing else about your trip.The ideas pack for that area, shared by everyone (public information from Wikivoyage, Wikidata and OpenStreetMap).
Following a flight liveThe flight number, its date, and its two airports and timetable times (so the server can find the plane when its radio call sign isn't the flight number). Nothing else about your trip.The public flight position for under a minute, then deleted. Which plane flies that flight (public information), until a few hours after it lands.
Map routes (so ground legs follow real roads and rail lines)The start and end of a ground leg (car, bus, taxi, train), rounded to about 50 m, and how you travel it. Nothing else about your trip. Our server asks OpenStreetMap-based routers (OSRM on FOSSGIS's servers, openrouteservice, Overpass) for the route, so they see only those two points, coming from our server.The route line for those two points, shared by everyone who asks for the same leg, for up to 180 days.
Publishing a trip as a link (only if you choose to)The plan you chose to publish (places and days; never expenses, people, bookings or documents), the first name you chose to show, and the photos you picked, with their location and camera data removed.The page, until you remove it in the app or it expires (at most one year). Pages are hidden from search engines.
Signing in with Google (only when you share a trip, sync or move phones)Google's sign-in token.Your Google account id, email and name, until you delete your account.
Sharing a trip with its membersChanges to the shared trip, encrypted on your phone with a key only trip members have. The server cannot read them. An invite link can also show the trip's name and your first name, if you choose to.The encrypted data until every member's phone has collected it, or 30 days at most. Invite codes (and the name shown on the invite page) until they expire (at most 30 days).
Plan with AI: checking the suggested places on the mapEach suggested place name (and its town), roughly where your trip is (rounded to about 1 km), and your phone's language. Nothing else about your trip. Our server asks Photon (OpenStreetMap data) for it, so Photon sees only that search, coming from our server.The search result, shared by everyone who asks the same, for up to 7 days.
Push wake-upsA push token for your phone (Firebase Cloud Messaging), so a member's change can wake your phone. The message has no content.The token, until you delete your account.

All traffic to the server is encrypted (HTTPS). The server makes a backup every night; backups are kept for 14 days, so anything deleted from the server is gone from its backups within 14 days.

03Services your phone contacts directly

Some lookups go from your phone straight to a public service. Like any website, these services see your phone's IP address and what was asked. Memory sends them no name, account or trip details beyond the request itself.

ServiceUsed forWhat it sees
Photon (komoot), OpenStreetMap dataPlace search; and, when you publish a trip page, naming the town near a private stay ("Stay near Ubud")What you typed, and roughly where your trip is (to rank nearby results first). When you publish: one point near each private stay, rounded to about 1 km, asked once and kept on the phone
Wikipedia, Wikidata and Wikimedia CommonsPictures and names of placesThe place's name or position; picture downloads
OpenFreeMap, NASA GIBS, EOXMap and satellite tiles on the maps and globe (and on published trip pages)Which map area you are looking at
FrankfurterExchange rates for expensesTwo currency codes and a date
Open-MeteoWeather for trip daysA trip place's position and dates
Google (ML Kit and Google Play services)Reading barcodes and text, the document scanner, and Plan with AI on phones with their own AI (Gemini Nano), all on the phoneThe images and your Plan with AI request are processed on the phone. ML Kit itself sends Google diagnostics and usage information: device details (maker, model, Android version), the app's name and version, per-installation identifiers, performance (such as how long a feature took), which feature ran, error codes and the size of its input and output. For Plan with AI (ML Kit's GenAI APIs) it also sends user, device or other identifiers and the phone's configured languages. Google says it does not pass this to third parties; see Google's ML Kit data disclosure.
Google sign-in (when you sign in)Proving who you areThat you signed in to Memory, under Google's own privacy policy
Apps you share to (Instagram, WhatsApp, email…)Only when you tap ShareWhat you chose to share

04What Memory never does

  • No ads, no advertising id, no analytics or tracking tools, no crash-reporting service.
  • Your data is never sold, rented or shared for marketing.
  • No cloud AI. The only AI feature, Plan with AI, uses your phone's own AI on the phone, or an AI app you choose to send the request to yourself.

05Deleting your data

  • In the app: Profile › Preferences › Privacy › Delete my account and data. This deletes everything on the phone (trips, Documents, photos, settings and keys) and asks the server to delete everything it holds for you: published pages, and, if you signed in, your account, devices, invites and encrypted sharing data.
  • Without the app: see how to delete your account.
  • Uninstalling the app deletes everything on the phone. Data other trip members already have on their own phones stays with them.

06Children

Memory is not made for children under 13 and does not knowingly collect information from them.

07Changes and contact

If this policy changes, the new version will be posted here with a new date. Questions or requests:

bikesbade@gmail.com