Foothold privacy policy
Last updated 6 November 2026.
Foothold is a visual planner for time blindness. It is made by Maciek Mostowski (calmneuroprints@gmail.com).
Your tasks never leave your phone, except what you ask the assistant, a trip you share, and Android’s encrypted backup to your own Google account. Habits, timers, templates and completion marks stay on your phone, and in Android’s backup when it is on (see Backups below). There is no account, no analytics and no crash reporter. The only parts of Foothold that talk to a server of ours are the assistant, only when you ask it something — see Assistant below; a trip you share — see Sharing a trip below; the check of how much AI you have left, which sends only a random number — see Your AI allowance below; and a tester code, if you type one — see Tester code below. The free plan shows ads after its first week — see Ads below; on the paid plans (No ads, Plus) there are none, and no advertising identifier is read.
Reminders use Android’s local notification system. They are scheduled on the device and are not sent through any server.
The homescreen widget reads the same on-device list so it can show what is next. It does not send that list anywhere.
Recipes: when you ask Foothold to read a recipe — with Foothold’s button in the browser while you look one up, or by sharing a recipe page’s link to Foothold — the app downloads that one page directly from its website, as a browser would, to read its list of ingredients. Nothing about you or your tasks is sent with it, and it does not pass through any server of ours. The search itself is Google’s, in your browser.
Prescriptions: a prescription you scan with Foothold, share to it or paste a link to is read on your phone — the picture and the text read from it do not leave your phone unless you tap Read it with AI (see below; only the text goes, never the picture), and a link is downloaded directly from its website, as a browser would. The scanner and the text reading are Google’s (ML Kit, working on the phone); they may send Google statistics about the phone and how they ran, such as its model, the app’s version and how long the reading took, under Google’s own terms.
Contacts: when you add a person to a meeting with the Contacts button, Android asks whether Foothold may read your contacts. If you allow it, Foothold reads only the person you pick — their name, phone number and email address — and keeps them with that meeting on your phone, so Call, Message and Email can reach them. Those buttons open your own dialer, messaging app or mail app, filled in; you press Call or Send there, and Foothold sends nothing itself. It never reads the rest of your contacts and never sends any of it anywhere. If you say no, Android lets you pick just a phone number or an email instead, and nothing else is read.
Meetings and your calendar: when you open From Google Calendar or switch on Add to Google Calendar, Foothold asks Android for Calendar access, then reads and writes the calendars on your phone — the meetings it lists, adds or changes, with their times, links and the email addresses of the people in them. This happens on your phone. Your calendar’s own sync (Google Calendar’s) carries what Foothold writes to your account, as it would a meeting you added in Google Calendar yourself; nothing goes to any server of ours. You can take the access away in Android’s settings.
A meeting’s map: a meeting with a place shows it on a small map. The streets are drawn from OpenStreetMap’s map pictures, downloaded as a browser would — OpenStreetMap sees which part of the map is shown, not the meeting. An address is turned into a point on the map by your phone’s own location service (Android’s, Google’s on most phones). Your location is used only when you tap Show me on that map: Android asks the first time whether Foothold may use it; Foothold then puts you on the map and says how far each place is, while the screen is open. It keeps your location nowhere and never sends it anywhere. You can take the access away in Android’s settings.
Backups: Save now, under Backup in Settings, writes one file with everything Foothold keeps — your tasks, what you ticked, your templates and settings — to the place you pick on your phone: its Downloads, or a place like Google Drive that you choose in Android’s own file picker. Foothold itself sends it nowhere; a place like Drive keeps it under its own terms. Restore reads only the file you pick.
Android’s own backup: when backup is on in your phone’s settings and the phone has a screen lock, Android copies what Foothold keeps on the phone — your tasks, what you ticked, your templates and settings, not recordings — to your Google account, about once a night, and gives it back when Foothold is installed on a new phone signed in to the same account. The copy is encrypted on the phone with your screen lock, so neither Google nor we can read it; Foothold never receives it, and Google keeps it under its own terms. With no screen lock, nothing is copied. Moving to a new phone by cable or Wi-Fi carries the same, from phone to phone. You can turn the backup off in your phone’s settings.
Your calendar on Today: when you switch on Google Calendar events on Today in Settings › Calendar, Foothold asks Android for Calendar access, then reads the appointments in the calendars on your phone — their names, times and places — to show them among your tasks, on the widget and in a reminder to get ready. It only reads them, on your phone: it does not change them, does not keep a copy, and sends nothing anywhere. Switch it off in Settings, or take the access away in Android’s settings.
Measurements: the numbers you note with Measure — blood pressure, heart rate, weight and the like — with their times and notes, stay on your phone with your tasks. Show the doctor makes a page of them that Android’s print service prints or saves as a PDF; where that page goes is up to you. Foothold sends it nowhere.
Assistant: when you ask the assistant something — by speaking or by typing, on Today, Add a task or Start now, or in a task’s form — Foothold sends the assistant’s server (ours, run on Cloudflare) what you asked, as text; your phone’s date, time and time zone; the app’s language; and, in a form, which kind of task it is. Asked on Today, Add a task or Start now, it also sends the names of your shopping lists and, so that it can move, rename, tick or delete a task you name, a list of your tasks from yesterday to two weeks ahead: their names, kinds, days and times, whether they repeat and whether they are ticked, each under a number made up for that one question. Notes, steps, places, people and everything else stay on your phone. Our server passes this to Anthropic’s Claude, which works out the answer; Anthropic processes it on our behalf and does not use it to train its models. Our server keeps none of what you asked, of your tasks or of the answer. It keeps only a random number made on your phone, with how many questions it asked this month and its AI allowance (see Your AI allowance below); and, on the free plan, a scrambled form of your internet address with that day’s count, deleted after a day. What the assistant proposes changes nothing until you confirm it.
Speaking to the assistant: your words are turned into text by Android’s speech recognition — on the phone where it can, otherwise by the phone’s speech service (Google’s on most phones) under its own terms. Foothold keeps no recording and sends none anywhere. So that your task names are heard as written, Foothold gives them to the speech recognition as words to expect. Android asks the first time whether Foothold may use the microphone. Names you say are looked up in your contacts on your phone, only if you have allowed Contacts; your contacts never go to our server or to Anthropic. The assistant does not use your location.
The assistant's suggestions: when you tap a “Suggest” button, Foothold sends the assistant only what that suggestion needs — a task's name (and its notes, or a meeting's place, or an event's day), a dish and how many servings, a sentence about a workout, the visible text of a recipe page Foothold could not read, today's open tasks (their names, times and lengths) for “What should I start now?”, or the week's counts of done and planned for each task for “The week in words”. When you add a task whose name Foothold has no picture for, its name alone is sent to pick one; on the free plan our server refuses it, and no model sees it. As with the assistant, nothing is kept on our server and the model does not train on it.
Asking about your stats: when you ask the assistant a question on Stats, Foothold sends it what you asked and, worked out on your phone from the last eight weeks, each task’s name with its counts — how often it was planned and ticked, in the last seven days, this month and on each day of the week, how many times in a row it is ticked now and its best run — and the days it was missed. Notes, steps, measurements and everything else stay on your phone. As with the assistant, our server keeps only how many questions were asked this month, and the model does not train on it.
Planning a trip: when you tap Plan the trip (or Find a place to eat, or Plan a bar crawl), Foothold sends the assistant what you filled in — what it is for (sightseeing, a meal or bars), where, how long, the day and the start time, how you get around, what you like, the budget, a meal’s cuisine, the pace, the line you added and how many plans you want to choose from — with your phone’s time zone; for a change, the plan so far and the change you asked for. The place you typed is first turned into a point on the map by your phone’s own location service, and that point goes with it — the area you named, never where you are. Our server then asks OpenStreetMap for the restaurants, bars or sights around that point, with their addresses and opening hours (its Overpass service, and its Nominatim service for the point when your phone could not find it); OpenStreetMap is asked by our server, not by your phone, and learns only that area and what kind of places were looked for. When you open a plan, each of its places is checked on the web through Anthropic’s web search — whether it still runs there, its hours that day and its price: your phone sends our server a ticket our server made for that place (its name, address and kind as OpenStreetMap has them, and the area you named), with the day and the time the trip gets there; the pages used, and OpenStreetMap, are shown with the plan. Your phone’s own location service then checks each place’s address, on the phone, as it finds a meeting’s place. Your location is never sent. A stop not found on OpenStreetMap is turned into a point on the map by your phone’s own location service, as a meeting’s place is, and the trip is kept on your phone with your tasks, with the stops you tick as visited. On a trip’s own screen, once you have allowed Location (Show me asks the first time), the map shows where you are while the screen is open; as on a meeting’s map, your location is kept nowhere and never sent anywhere. Tapping a stop opens the routes there in your map app, which finds where you are itself. As with the assistant, our server keeps only how many trips were planned this month and how many places were checked today, and the model does not train on it.
Sharing a trip: only when you tap Share this trip, and after Foothold has said what is sent and asked for the name the others will see, that one trip goes to our server, which gives you a link. What goes is the trip’s name, day and start time; what the plan says and what it was planned from — the area, how long, how you get around, what you like, the pace, the budget, the cost and the pages used; each stop with its name, address, point on the map, times, what it offers and what it costs; and, as the trip goes on, when it started and which stops were visited or skipped. Your other tasks, this task’s notes, the line you added when asking for the trip and where you are never go. Anyone with the link can see the trip, as a web page even without Foothold, and anyone who joins in Foothold, up to eight people, can change it and sees the others’ names and what they changed. While Foothold is open, each phone in the trip exchanges changes with our server; when it is closed, it does not. Our server keeps the trip, those names, the random number above of each phone in it, never shown to the others, and for two days how many trips that number shared. None of it goes to Anthropic or to any other AI. It is all deleted when the person who shared the trip stops sharing or deletes it, or after 60 days in which nobody opened it. Leave takes only your phone off the trip; what you changed stays in it until sharing ends. Everyone who joined keeps their own copy on their phone.
Recording a meeting: when you tap Record, Foothold records sound with the microphone until you stop it — also with the screen off, with a notification showing that it records. The recording is a file kept in Foothold’s own storage on your phone; it is not sent to our server or anyone else. It leaves the phone only if you share it yourself, to the app you choose. Deleting it in Foothold deletes the file. Please tell the people you record that you are recording.
Summing up a recording (Streść, Foothold Plus): only when you tap it, the recording is sent to our server, which passes it to a speech-to-text service (ElevenLabs, under its own privacy policy) to be written out with times and speakers, and the text to our AI model provider to write the summary or answer your question. Our server does not keep the recording or what was said. ElevenLabs and Anthropic may keep them under their own terms. Anthropic does not train its models on them. Our server keeps only how many minutes and questions were used. The transcript, the summary and the answers are kept on your phone beside the recording and are deleted with it. The names you give the speakers stay on your phone; the lines of speakers you untick are not sent at all. A PDF of the notes is made on your phone and leaves it only when you share it, to the app you choose.
Asking the help (Pomoc, Ask, every plan): only when you tap it, your question and the help's own pages are sent to our server, which passes them to our AI model provider to write the answer. Our server does not keep the question. Anthropic may keep it for up to 30 days under its own terms, and does not train its models on it. Our server keeps only how many questions were asked that day. Searching the help happens on your phone and sends nothing.
Read it with AI: when Foothold’s own reading of a photo or a page finds no clear lines for a list — a shopping list, things to take, steps, or a prescription’s medicines — it offers this button and says what it does. Only when you tap it, the text your phone read off that page is sent to our server, which passes it to Anthropic’s Claude to pick out the lines. The picture is never sent. The text goes as it was read, so it can hold whatever is printed on the page: on a prescription, the medicines and any names on it. Anthropic processes it on our behalf and does not use it to train its models. Our server keeps none of the text, only how many were read that day. It uses a little of your AI, about one question. The lines come back to your phone for you to check and tick.
Your AI allowance: every plan comes with some AI each month (the free plan a few queries, counted whichever feature asks), and Top up AI adds more. To count it, our server keeps, under the random number above, which plan that number is on and when its month ends, how much of the month’s AI and of its top-ups is left, how many ads it has watched this month for a little more, and each top-up’s purchase number, so that it counts once. These are amounts only, nothing of what you asked or of the answers, and they have no end date, because a top-up never expires. Delete my AI data in Settings › Plans deletes them and the counts of questions and minutes; any top-up credit is lost with them, and while Plus runs it asks you to cancel first. A new record with nothing used starts the next time your phone asks. When you open Settings or the assistant, or watch an ad for more AI, your phone asks our server how much is left, so that it can tell you. That question sends only the random number above, and our server keeps no record of it. To answer, our server may ask RevenueCat which plan that number is on.
Foothold Plus: the subscription is bought through Google Play, which takes the payment — we never see your card. RevenueCat, the service we use for subscriptions, receives from Google Play what was bought and when it renews, under the random number above, with technical details such as the app’s version, under its own privacy policy; it tells our server whether that number is on Plus. Foothold gives neither RevenueCat nor our server your name or email address.
No ads and Top up AI are bought the same way as Plus, through Google Play and RevenueCat, and each is paid once. RevenueCat tells your phone that it has No ads, and tells our server about each top-up, so that our server can add it to that random number’s AI, or take it back after a refund. Restore purchases on a new phone moves what is left to that phone’s random number.
Tester code: if you are testing Foothold and type a tester code in Settings › Plans, your phone sends it to our server with the random number above. If it is right, our server keeps that this number has a tester code, with no end date, and asks RevenueCat to give that number No ads; nothing is paid, and neither gets your name or email address. A code that is not right is not kept: our server only counts such tries by a scrambled form of your internet address, deleted after a day. Delete my AI data in Settings › Plans deletes the mark that this number has a code; RevenueCat keeps its record of No ads.
Ads (the free plan only): for the first week after you install or update Foothold there are none. Then Foothold says on its Today screen that ads begin, and only after you answer does it start Google AdMob, Google’s ad library. In the European Economic Area and the United Kingdom, Google’s consent form first asks what you allow; you can change your answer any time in Settings › Assistant › Ad privacy choices. To show and measure ads, AdMob collects what any ad needs — the phone’s advertising ID (where you allow it), its model and language, an approximate location from the IP address, and how ads were seen and tapped — under Google’s own privacy policy (policies.google.com/privacy). Foothold never gives AdMob a task, a list, a recording or anything you wrote. When you watch an ad for a little more AI, AdMob tells our server, signed, the random number above and that the ad was watched; the server adds a little to that number’s AI and keeps only how many such ads it has watched this month, and each ad’s number for 40 days, so that it counts once. On the paid plans AdMob is never started.
Signing up on our website: if you leave your email address on Foothold’s website, to hear when Foothold is on Google Play or on iPhone, or to test it, we use it for that and for nothing else, because you asked us to. It reaches us, with what you asked for and that you agreed, through the service that receives the website’s form on our behalf, or as an ordinary email if your email app opens instead. We never sell it or pass it on to anyone for their own use. If you volunteer to test, we also add it to the testers’ list in Google Play, so that Google lets that account install the test. We keep your address until that email has gone out or the test has ended, or until we know it never will, and then delete it. To change your mind sooner, write to the address below: we take you off and delete it.
This website: it is served by Cloudflare, which handles your internet address to deliver the pages, as any web host does, under its own privacy policy. The website sets no cookies, has no analytics and loads nothing from other companies; even its fonts are its own files.
If you otherwise contact us by email, that email is ordinary correspondence. We do not add you to a list.
Google Play may collect install and crash statistics under Google’s own terms. That is Google’s data, not ours. We do not get a copy of your habits from Play.
Questions: calmneuroprints@gmail.com