Privacy Policy
Last updated 6 September 2026
The short version
My Burrito Finder has no accounts, no cookies, no analytics, no advertising and no tracking of any kind. That is true of the website and of both apps. There is no server-side code and no database anywhere in the project, so there is nowhere for it to keep anything about you.
A couple of small things are saved, and they are saved on your own device rather than sent anywhere: the last area you searched, so you do not have to retype it, and whether you have already been asked about location. Your location is only ever used if you grant permission, and only while you are using it.
Finding places does mean asking other organisations for maps and data, and those requests necessarily reveal your IP address and what you searched for. Every one of them is listed below, for each of the three.
What this policy covers
Three things, which do the same job in three different places:
- The website at myburritofinder.com.
- The Android app,
com.humanelycoded.myburritofinder, on Google Play. - The iPhone and iPad app,
com.hugheswd.MyBurritoFinder, on the App Store.
They behave the same way and hold the same things about you, which is to say almost nothing. Where the plumbing genuinely differs — which services each one talks to, and how you take a permission back — that is spelled out separately below rather than glossed over.
Who runs this
My Burrito Finder is a personal, non-commercial project operated by Andrew Hughes in Oregon, United States. It is not currently a business, sells nothing, and earns no revenue. If that ever changes, it will be operated by Humanely Coded, and this policy will be updated to say so before any commercial activity begins.
Questions about this policy, or about privacy in any of the three, can go to privacy@humanelycoded.com.
What is stored on your device
Nothing is stored anywhere else, because there is nowhere else. None of the values below is transmitted to this project or to anyone else, and none of them identifies you.
On the website
One value, in your browser's localStorage:
| Name | What it holds | Why | How long |
|---|---|---|---|
mbf.area |
The last area you typed, such as “Portland, OR” | So the search box is already filled in next time | Until you clear it |
You can remove it at any time by clearing site data for myburritofinder.com in your browser settings, and the site will work exactly as before.
No cookies are set by this site, for any purpose, including analytics and advertising. There is no session storage and no other browser storage in use.
In the Android app
Three values, in the app's own private storage:
| Name | What it holds | Why | How long |
|---|---|---|---|
last_area |
The last area you typed | So the search box is already filled in next time | Until you clear the app's data or uninstall it |
location_asked |
Whether you have been asked about location, either way | So you are not asked again on every launch | Until you clear the app's data or uninstall it |
location_system_prompted |
Whether Android's own permission dialog has ever been shown | So a “not now” is not mistaken for a permanent refusal | Until you clear the app's data or uninstall it |
You can remove all three at any time under Settings → Apps → My Burrito Finder → Storage → Clear data, or by uninstalling the app.
In the iPhone and iPad app
Three values, in the app's own preferences:
| Name | What it holds | Why | How long |
|---|---|---|---|
mbf.area |
The last area you typed | So the search box is already filled in next time | Until you delete the app |
mbf.locationAsked |
Whether you have been asked about location, either way | So you are not asked again on every launch | Until you delete the app |
mbf.seenWelcome |
Whether you have dismissed the welcome card | So it does not come back after you have closed it | Until you delete the app |
Deleting the app removes all three. The apps ask for no other permissions and read nothing else from your device — no contacts, no photos, no calendar, no files, no device identifiers.
Device backups
Both apps keep the values above in the ordinary place an app keeps its settings, which means they are included in your own device backup if you use one — Google's Android Backup, or Apple's iCloud or computer backup. That backup belongs to you and is governed by Google's or Apple's policy, not by this one. Nothing else the apps hold is backed up: the Android app's map tile cache is explicitly excluded, since it is large, disposable, and has no business in anyone's cloud.
Your location
Location is optional in all three, and refusing costs you nothing: you can type an area instead and everything else works normally. What you lose by refusing is the “you are here” marker, the opening search, and routes.
If you do grant permission, your coordinates are used to:
- centre the map on you and mark where you are;
- search for burrito places near you;
- draw a driving route from you to a place you choose;
- bias search suggestions toward places near you.
Your coordinates are held in memory only, and are discarded the moment you close the tab or leave the app. They are never written to storage and never sent to this project — there is no server here to send them to. They are sent to the services listed in the next section, because finding somewhere near you necessarily means telling something where you are.
On the website
The page asks your browser for your location using the standard Geolocation API, and your browser asks your permission first. You can withdraw it at any time in your browser's site settings for myburritofinder.com.
In the Android app
The app explains what it wants and why before Android's own permission dialog appears, with a “Not now” that costs nothing, and it remembers your answer so the question is asked once rather than on every launch. It requests foreground location only: there is no background location, and the app asks for a single position rather than subscribing to updates. Approximate location is enough for everything it does. You can withdraw permission under Settings → Apps → My Burrito Finder → Permissions.
In the iPhone and iPad app
The app explains what it wants and why before iOS shows its own prompt, which iOS offers only once. It asks for While Using the App only — never Always, never in the background — and asks for one position at a time rather than tracking you. If you turn Precise Location off, the app works normally and does not ask you to turn it back on; an eight-kilometre search does not need the last hundred metres. When your position is used only to bias search suggestions toward your part of the world, it is rounded to about a kilometre first. You can withdraw permission under Settings → Privacy & Security → Location Services → My Burrito Finder.
What is sent to other services
Each of the three is assembled from several independent services, contacted directly from your browser or your phone. Each service can see your IP address, the approximate time of your request, and whatever that service is being asked for. None of them receive a name, an email address, or an account, because nothing here ever asks you for one. No identifier of this project's own is sent to any of them, and nothing about you comes back.
These services are used to deliver the maps and the listings, not to profile you. What each one does with the request is governed by its own policy, linked below.
From the website
| Service | Operated by | Receives | Their policy |
|---|---|---|---|
| Map tiles | OpenStreetMap Foundation | Your IP address and which map squares you view, which reveals roughly where you are looking | Policy |
| Area lookup (Nominatim) | OpenStreetMap Foundation | Your IP address and the area you typed, when you run a search | Policy |
| Place search (Overpass) | Overpass API community servers | Your IP address and the coordinates you are searching around | Site |
| Search suggestions (Photon) | komoot GmbH | Your IP address and what you type in the search box, as you type it | Policy |
| Driving routes (OSRM) | FOSSGIS e.V. | Your IP address, and the start and end coordinates of a route — only when you ask for one | Policy |
| Map software (Leaflet) | unpkg, served by Cloudflare | Your IP address, when the map library file is downloaded | Policy |
| Web font | Your IP address, when the font file is downloaded | Policy | |
| Web hosting | HostGator | Standard server log entries: IP address, time, page requested, browser version | Policy |
From the Android app
| Service | Operated by | Receives | Their policy |
|---|---|---|---|
| Map tiles | OpenStreetMap Foundation | Your IP address and which map squares you view | Policy |
| Area lookup (Nominatim) | OpenStreetMap Foundation | Your IP address and the area you typed, when you run a search | Policy |
| Place search (Overpass) | Overpass API community servers | Your IP address and the coordinates you are searching around | Site |
| Search suggestions (Photon) | komoot GmbH | Your IP address and what you type in the search box, as you type it | Policy |
| Driving routes (OSRM) | FOSSGIS e.V. | Your IP address, and the start and end coordinates of a route — only when you ask for one | Policy |
| Working out where you are | Google (Play services location) | Whatever Android's own location service needs to produce a position, only when you have granted permission and only while the app is open | Policy |
From the iPhone and iPad app
The iPhone app draws Apple's map and gets its routes from Apple rather than from the OpenStreetMap tile servers and the OSRM routing server the other two use. That is a deliberate choice, and one of the reasons for it is this table: it removes two organisations from the list of those that see where you are. The listings still come from OpenStreetMap, which is why the credit appears on the map and under the results.
| Service | Operated by | Receives | Their policy |
|---|---|---|---|
| The map, driving routes, and working out where you are | Apple (MapKit, Core Location) | Map and directions requests, and your position when you have granted permission | Policy |
| Area lookup (Nominatim) | OpenStreetMap Foundation | Your IP address and the area you typed, when you run a search | Policy |
| Place search (Overpass) | Overpass API community servers | Your IP address and the coordinates you are searching around | Site |
| Search suggestions (Photon) | komoot GmbH | Your IP address, what you type in the search box as you type it, and your position rounded to about a kilometre | Policy |
The app stores themselves
Downloading either app is a transaction with Google Play or the App Store, and those companies keep their own records of it under their own policies.
Neither app contains an analytics, advertising, attribution or crash-reporting SDK of any kind, so nothing is collected by this project or sent anywhere by it. Separately from that, if you have opted in to sending diagnostics to Google or Apple, your device may send them crash reports and usage statistics about the app, and Google and Apple then make some of that available to us — as aggregate crash and install counts in the Play Console and App Store Connect. It arrives with no identity attached, we cannot tie any of it to a person, and it is used only to find and fix crashes. Whether your device sends it at all is a setting on your device, in Google's or Apple's hands and yours, not ours.
Ratings and photos
All three can optionally show ratings, price tiers and storefront photos from Foursquare, which OpenStreetMap has no field for. That is switched off in all three today, so nothing is sent to Foursquare and no Foursquare content is loaded. If it is ever switched on, this policy will say so before it is.
What none of these do
- They do not create accounts or ask for a name, email address or phone number.
- They do not set cookies, and the apps contain no advertising, analytics, attribution or crash-reporting SDK.
- They do not read any device identifier — no advertising ID, no IDFA, no device fingerprint — and the iPhone app never shows a tracking permission prompt because it has nothing to track you with.
- They do not build a profile of you or track you between visits, between sessions, or across other sites and apps.
- They do not sell or share personal data. There is no personal data to sell, and none ever will be sold.
- They do not use your data to train machine learning models.
- They do not keep server-side records of searches, because there is no server-side code anywhere in the project.
- They do not request background location, notifications, contacts, photos, the microphone, the camera, or access to your files.
Your privacy rights
Laws including the Oregon Consumer Privacy Act, the California Consumer Privacy Act, and the UK and EU General Data Protection Regulation give people rights over personal data held about them — typically to know what is held, to get a copy, to correct it, to have it deleted, and to opt out of its sale or of profiling.
Nothing here holds personal data about you. There is no database, no server-side code and no accounts, and the handful of values saved stay on your own device under your control. So there is no file to send you, nothing to correct, and nothing to delete on request — you can delete everything yourself by clearing site data for myburritofinder.com, clearing the Android app's data, or deleting the iPhone app. There is no sale of personal data to opt out of, and no profiling or targeted advertising takes place.
Because there are no accounts, there is nothing to close and no account deletion to request.
If you would like to exercise a right, ask what is held about you, or raise a concern, write to privacy@humanelycoded.com and you will get a reply within 30 days. Requests are free. If you are in the EU or UK you also have the right to complain to your national data protection authority; if you are in Oregon you may contact the Oregon Department of Justice.
Data about your visit does reach the third-party services listed above, and rights over that data are exercised with those organisations directly, using the links in those tables.
Do Not Track and Global Privacy Control
Nothing here tracks anyone, so a Do Not Track header or a Global Privacy Control signal changes nothing about how the website behaves. There is no tracking to switch off and no sale or sharing of data to opt out of. The apps have no equivalent signal because they have nothing for one to turn off.
Children
None of these are directed at children, none knowingly collects information from anyone, and none has any means of collecting information from a child, since they ask for nothing and store nothing about the people who use them.
Security
Everything is served over HTTPS, in the browser and in both apps, and neither app ships an API key or any other secret. There is no personal data held anywhere, so there is no store of it to be breached. The website additionally restricts itself with a Content Security Policy, which limits it to the services listed above and blocks anything else from loading or being contacted.
Changes to this policy
If this policy changes, the date at the top of this page changes with it. If any of the three ever starts collecting something it does not collect today, or the project begins operating commercially as Humanely Coded, that will be stated here before the change takes effect.
Contact
Andrew Hughes, Oregon, United States
privacy@humanelycoded.com