Privacy

What Forklist stores about you, who can see it, and what happens to it when you leave.

Last updated 6 November 2026

The short version

• Nothing about you is sold or used for ads. No ad network or data broker gets anything from Forklist, and nobody pays for what it holds.
• There is no analytics of any kind. No Google Analytics, no pixel, no session recorder, no A/B tooling. Nothing in the app is watching how you use it.
• Your coordinates are used and never kept. Sorting by distance, delivery waits and the nudge near a saved place all happen on your device. Six screens send your coordinates to the server to answer you, and so do the widgets on an Android phone's home screen. Only a meet request keeps them, for two hours. A nudge keeps which place it was about and when, for 30 days. Here are the six.
• Your notes are private by default. A new pin is Just you until you change it. Explore shows the places people save. It shows a person's name or words only to someone who can already read their note.
• A friend can say you went somewhere together, and nothing shows until you say yes. Not me tells nobody.
• Two things can reach people who are not on Forklist. A guide you publish, which anyone with its link can read, and a crawl link somebody on a crawl turns on, which shows its stops and never its lines or who is going. Nobody sees a guide until you publish it. You can delete it at any time, and unpublish it while you have Forklist Plus.
• Deleting your account deletes your login and what you wrote. A line you wrote on someone else's crawl stays there without your name. Leaving lists that and everything else that stays.
• You can download a copy any time. Settings → Account → Download my data gives you everything below as one JSON file, except four things: reports other people filed about you, the team's log of what it took down, Google's details about a place, and what other people keep private about you, such as whether a friend you named has answered yet or a nickname a friend gave you.

What is stored, and why

This table lists everything Forklist keeps about you. "Who can read it" means who the server will show it to. One shared rule decides that for every query. Whoever runs Forklist sees more, listed under What the people who run Forklist can see.

In the EU and UK, each use on this page needs a legal basis. Running the app you signed up for is a contract with you, and that covers most rows. Handling reports, deciding who can use tables open to a city, and the team's log rely on keeping people safe, a legitimate interest you can object to. Taste match, taste twins and the For you sort rely on the same, and Settings turns them off. A nickname a friend gives you relies on the same, and you can object to it.

What is not stored

• Your password. Sign-in goes through Google or Apple, and Forklist never sees a password.
• Your location, everywhere but one screen. Coordinates are never written to the database, and the request log records the address you asked for without its query string. The exception is a meet request: the point you tap when somebody asks where you are is kept for two hours and then deleted. See the six screens that send them. A nudge is not a coordinate, but it says you were near a place; the nudge explains what is kept.
• A history of what you looked at. There is no record of which spots you opened, searched for or scrolled past. Tapping Fork it keeps only which friend a place came from, for at most 30 days.
• Your IP address. Held in memory for up to an hour to rate-limit abusive traffic, and never written to the database. There are two exceptions, both when you have no account. A message sent from the support page, or a report on a guide, is counted against a scrambled copy of your address, which cannot be turned back into it without a key the database does not hold, and that copy is deleted within ten minutes of the hour running out. A report on a guide also keeps a scrambled copy of your address joined to that guide, so a second report from you on the same guide replaces the first. It goes when the guide does.

Adding, upvoting and reporting need an account, and each upvote or report is kept with your account id, so each person counts once. The one exception is a report on a guide, which anyone can send; without an account it belongs to the scrambled copy described above. There is no anonymous voting.

Some screens are ordered from what you have saved: a For you sort, the cuisine tiles on the home screen, the stops a crawl suggests, and Pick one for me. A friend’s profile also shows a taste match: how much your two maps agree on places, kinds of food, dishes, price, stars and tags, counting only places of theirs you could already see. They read the places you pinned or marked, and nothing about what you opened or how long you stayed. In the taste match, kinds of food few people save count for more. To know which, it counts how many people saved each kind, private saves included, and keeps no names or places. Settings → Privacy → Using your saved places turns it off.

Taste twins look for the people whose saved places overlap with yours. It leans on the places hardly anyone has saved. Only people you can already reach turn up there: your friends, friends of your friends, and people in groups you are in. Like the taste match, it counts only places of theirs you could already see, and it never tells you how many people saved somewhere. The same switch turns it off, and off takes you out of other people’s twins as well as hiding theirs from you.

Year in Food is worked out from what you already saved and keeps nothing new. Its share card prints your first name, your number one with your note (even one only you can see), up to five of your places, and three counts: new places, kinds of food and new cities. If you have ranked none, the place you went last stands in for your number one. It prints nothing about a friend. It goes only where you send it. Forklist's servers keep no copy, and the apps delete their own working copy once you've shared it (on Android, the next time you share or open the app).

Who your marks reach

Been and want to try are yours, and nobody sees the list of them. Ten things do read them:

• Places you’ve both marked. When you and a friend both turn it on in Settings, each of you sees the places you have both marked. When three or more such friends want to try a place you want, a card in Friends and a notification name them.
• A friend’s taste match. It counts your marks on places they can see, so it can change when you mark one of them.
• How rare a kind of food is. The taste match counts how many people saved each kind of food, your marks included, and uses only the total.
• Taste twins. A twin’s row lists places they saved, marks included. So places you marked can show up for your friends, friends of your friends and people in groups you are in, when they can see the place.
• Whoever pinned a place is told when you mark it been, unless you turn that off in Settings.
• Your badges. Friends see them on your profile. Regular counts the places you have been, Curious the places you want to try, Roulette the times Pick one for me sent you somewhere you went, and Challenger the challenges for everyone you finished. Kindred counts the friends whose taste match with you is 89% or more, leaving out anyone who turned off Using your saved places.
• Where a place ranks. Once you have ranked five places you’ve been, anyone who can read your note on one of them sees its score out of 10, not its position, on the place and in their activity. That says you went there.
• Who you went with. Once you say yes, the place is on your Been list and people who can read your friend’s note may see you went together, and on which day.
• Want to go on a friend’s fork. That friend learns you want to go.
• Challenges. A challenge counts the places you marked Been inside its dates. The people in it with you see how many, and the day you finished, never which places.

Using your saved places, in Settings, turns the taste match and taste twins off.

What the people who run Forklist can see

The dashboard has roles, and a role decides which parts of it a person can open: a viewer sees accounts and totals, a moderator also sees reports and support messages, and can take down or clear what was reported and remove a nickname a friend asked about, and an admin can also see a whole email address, delete an account and read the log. When this page says the team, it means whoever holds a role. Together, the roles can see:

• Accounts. Each person’s name, when they joined and were last here, whether they have Forklist Plus, how many places, notes, friends and groups they have, and how many messages they have sent. The count of notes includes private ones.
• Your email address, mostly hidden. They see its first letter and the part after the @. The owner and admins can ask to see the whole address, and each time they do, whose address it was goes into a log.
• Totals. People, places, notes, marks, photos and messages, counted by day, and places counted by city and by kind. A place is named there only once somebody shares a note on it with friends or a group.
• Reports. What was reported and who reported it, and for a report about a person, the tables they have open and what other people can see of theirs: their name, line and city, the names of groups they named and lists they shared, their lines on crawl stops and their guide address. They can clear any of these. For a reported guide, what it says, even after its author unpublishes it, and they can take it down.
• Support messages, and the address you gave for a reply. On one asking about paused city tables, they also see whether yours are paused, how many people have open reports about you and how many reports are open, and the dates of the team's takedowns of yours.

The dashboard shows what a note says only when somebody reports it. It never shows your chats, which places you marked, or a list you have not shared, and it shows a shared list's name only when somebody reports you. Everything the team opens or changes there goes into a log, and so does giving someone a role there. When they take down something of yours, the log says whose it was, and for 90 days that pauses your tables open to a city.

Your location, and the six screens that send it

If you allow location access, your browser works out where you are. Most of what happens next stays on your device: the list sorts itself by distance, and a place's delivery waits are worked out against how far away you are. None of that is a request to us.

Fork near you lists the restaurants, cafés and bars around you. It asks Google for them straight from your browser, so your position goes to Google and never to Forklist. The list stays in the open page and is gone when you close it. Make it a night puts three or four of them in an order that walks, in the same page, and sends nothing anywhere. Saving that night as a crawl saves any stop that isn’t on your map yet to your map, as adding a place does, and opening the walk in Google Maps hands Google the stops, never where you are.

The picture on a city card is a small map of that city, fetched by Forklist from Google for a point near the middle of the places saved there, or the middle of the city where there are none, rounded to about a kilometre, with nothing about you attached. The pins on it are drawn in your browser.

Your position is read when you open the app and when you press Explore. You can also have it keep up as you walk: Settings, Privacy, Keeping up while you walk, which is off until you switch it on. Following reads the sensor while the app is open, and sends your position for the cuisine row below more often. Nothing new is stored.

The nudge near a place you saved is off until you switch it on in Settings, Notifications, When you're near somewhere you saved. With it on, your phone watches your position while the app is open and checks it against your own list. Until your phone finds a place on it within about 150 metres, the nudge sends us nothing. Then your phone sends which place it matched, never your coordinates, and the notification we write names that place. Switch the nudge off and the watching stops.

With the app closed, a Forklist Plus perk you turn on one phone at a time, the phone keeps watch itself, which needs your location set to Always and Precise. On an iPhone, Apple's location services do the watching. The Android app does not offer this yet. Forklist gives the phone a list of places to watch, each a place id and a pin with no name or note, and never asks where you are. The phone remembers where it was when it last picked which places to watch, and that stays on the phone. When you come within about 150 metres of one, the phone sends only the place it matched, never your location. The phone shows the nudge itself, in the words Forklist sends back, so it does not pass through Google's or Apple's push service.

With Places friends saved on as well, the list also holds places your friends saved: only a place you could already open on your map, unless they added it quietly, and never one you saved yourself. That nudge names the friend. Forklist asks all of this again when the phone reports a place, so a note made private since, an unfriend or a block means no nudge.

Forklist writes every nudge to your notifications, with the place and the time but never your position, so it knows not to nudge you about that place again for 30 days. That means Forklist knows you were near that place then. The row is deleted after 30 days.

Six screens do send your coordinates. The first five use them for that one answer and keep nothing:

• Exploring an area. Opening a city or a cuisine asks for the spots within a radius of you.
• The cuisines on your home screen. That row is ranked by how many places of each kind are near you. This one runs on its own when a location fix arrives, without you pressing anything. With following on, it runs again each time you move far enough.
• Pick one for me. A random pick needs to know which spots are close enough to suggest.
• Meet halfway. The midpoint is worked out from the starting points you enter, which can include where you are.
• Putting a crawl in order. Working out the order of an evening starts from where you are, when you have already allowed location. The order comes back; the position is not kept.
• Starting or answering a meet request. Asking a few people where they are sends your own position with the question, and tapping I'm here on somebody else's request sends yours back. This is the one screen that keeps what it sends. It is described below.

In the first five, the coordinates last for one request and are gone when it answers. Nothing writes them down. There is no column for them in any table listed above, no file and no log line. The server records the address a request asked for without its query string, and neither the CDN nor the load balancer keeps an access log. If request logging is ever turned on, this page will change with it.

The Forklist widgets on an Android phone send a position each time they look for something new: where you last opened the app, or, if you chose to have a widget follow you, where the phone is then. The server picks a place near it, and looks for a table, a crawl stop or a place you wanted to try within a mile of it. It is used for that one answer, and nothing keeps it.

Adding a place with no signal, in the phone app, keeps the name you typed, your note and where you were on your phone and nowhere else. When the signal comes back, your phone asks Google for a place by that name near where you were, and you pick the right one. Where you were stays on your phone until you pick the place, then it is deleted. It never reaches Forklist.

The one that is kept: answering a meet request

A meet request is the only thing in Forklist that stores a coordinate. Somebody asks a few people where they are, each person taps I'm here once, and the midpoint between whoever has answered decides what the app suggests. Your point is written when you tap and never before.

A request holds one point per person who answered. Those points are readable by the other people in that request and by nobody else. Every request is deleted two hours after it is made, and the coordinates go with it. Closing a request you started deletes it at once; leaving one somebody else started takes your own point out and leaves theirs alone. Your own points are in your data export while they exist, and deleting your account removes them.

What leaves the app

Google

Seven separate things, all from Google. Sign-in happens only if you choose Google, maps and fonts come with using the app, push only if you ask for it, your age range only in the Android app, and a Plus purchase only if you make one in the Android app.

• Sign-in, if you choose Google. Google gives Forklist your account id, name, email and avatar when you sign in, and nothing else. Google knows you signed in here.
• Maps and Places. The map, the search box, the walking route between a crawl's stops and a spot's photos and rating come from Google as you use them, so Google sees those requests. So does the city box in Edit profile, which sends Google what you type there. Home sends that city to Google too, to tell when you're away from it, and keeps the answer only while it's open. Fork near you sends Google your position to find the places around you. In the phone app, a place you added with no signal goes to Google once you are back online: its name, and where you were, so Google can find the place for you to pick. A crawl's route sends Google where its stops are, never where you are. When a guide, a crawl link or a crawl saved as a PDF includes a place only Google lists, Forklist asks Google Maps for that place's name, address and location at that moment, sending only Google's id for the place, and keeps none of what comes back. A guide or crawl link with such a place can also show Google's map, which your browser loads from Google: Google sees your IP address, your browser and the stops on the map, even a place no map lists, and that the page is on forklist.me, but not which guide or crawl link it is. Directions and Open in Maps open Google Maps with the place's address or name and Google's id for it. On a phone, when Forklist can match the place, your phone's own map app opens instead with where the place is and its name. On Android that is whichever map app you chose. Forklist sends none of them where you are. Photos, ratings and routes are never stored here.
• Fonts. Every page, and the app, loads its typefaces from Google Fonts. When a page opens, Google sees your IP address, your browser and that it was Forklist asking. Nothing about your account goes with it.
• Push notifications, if your phone allows them. Only in the phone app. It asks your phone once, after you first sign in, and your phone's own settings turn them off. A notification is the same line you would read in the app, so a friend's name, or the nickname you gave them, and a place's name go through Google's messaging service to your lock screen. A message shows who sent it, the group's name if it came in one, the phrase or emoji they picked and the name of any place they attached, so those go the same way. On Android, a notification about a place, or a message that attached one, can also show a photo someone added to that place that you can already see in the app, never one of Google's. It carries a Forklist address for the photo that stops working after ten minutes. A passport notification has no sender. It names a city you have saved places in when that city reaches a higher stamp, and the city's name goes the same way. If you also turn on the nudge near a place you saved, its notification names the place you are near, so Google's messaging service carries the fact that you are near it. The notification carries no coordinates: your phone does the matching and sends Forklist only the place it matched. A nudge your phone shows with the app closed does not go this way: the phone draws it.
• Your age range, in the Android app. The app asks Google Play on your phone for your age range and shows you nothing while it does. Google Play answers from what it already knows about your account or a parent's settings, or not at all. Forklist sends Google nothing about you to get it.
• Forklist Plus, if you buy it in the Android app. Google Play takes the payment, so Google knows you bought it. The purchase carries a code made from your Forklist account id, and Google keeps it with the purchase, even after you delete your Forklist account.
• Updates and ratings, in the Android app. The app asks Google Play whether a newer version is ready, so Google Play sees your device details and the app's version. Once, after you have marked five places as been, it can show Google Play's rating card. What you write there goes to Google Play. Forklist can't tell whether the card appeared or what you said.

Google's own privacy policy covers what Google does with that.

Apple

Sign-in, if you choose Apple. Apple gives Forklist your account id, your email or a forwarding address Apple makes, and your name the first time. Apple knows you signed in here. The sign-in page loads Apple's button from Apple, so Apple sees your IP address and your browser when that page opens, even if you choose Google.

Push notifications, only on an iPhone that allows them. Apple's push service carries the same one line that Google's does on Android. An iPhone takes push notifications only through Apple.

Your age range, on an iPhone where a law asks for it. The app asks Apple, and Apple may show you its own sheet first, where you can say no. Forklist sends Apple nothing about you to get it.

Forklist Plus, if you buy it on an iPhone. Apple takes the payment, so Apple knows you bought it. The purchase carries your Forklist account id, and Apple keeps it with the purchase, even after you delete your Forklist account. You can ask Apple for a copy of what it keeps at privacy.apple.com.

Directions, on an iPhone. When Forklist can match a place, Directions and Open in Maps open Apple Maps with where the place is, and Open in Maps adds its name. Forklist sends nothing about you.

One other thing reaches Apple, and only if you signed in with an Apple account: deleting your account tells Apple to cut the link between it and Forklist. Apple asks for that, and it is the only way the sign-in stops working from their side too. Nothing is sent but the token that names the link. That is the entire list of what goes to Apple.

RevenueCat, if you open Forklist Plus in the app

Forklist Plus is sold in the phone apps, through the App Store or Google Play. Apple or Google takes the payment, and Forklist never sees your card.

RevenueCat, a company that keeps track of app subscriptions, sits between the store and Forklist. The first time you open Forklist Plus on a phone, the app tells RevenueCat your Forklist account id, so a purchase belongs to your account and not to that phone. From then on RevenueCat gets your purchase history from the store: what you bought, when it renews or ends, and any refund. On the kind of phone you bought Plus with, opening Manage also asks RevenueCat whether your last renewal payment failed, so the app can tell you. That answer stays on the phone, and Forklist keeps none of it. Each time the app asks RevenueCat something, it also says the phone's make and model, its system version, Forklist's version, your language and your store's country. On an iPhone it also sends the code Apple gives Forklist for that phone, which no other company's apps share and which is not the advertising identifier. On an iPhone it also tells RevenueCat whether your phone lets Forklist ask to track you. Forklist never asks. RevenueCat sees the phone's IP address, as any server does. Forklist never turns on RevenueCat's advertising or attribution features, so RevenueCat never gets your phone's advertising identifier. Forklist asks RevenueCat about your account and keeps only the Forklist Plus row above. Until you open Forklist Plus on a phone, RevenueCat hears nothing from it, and the website never talks to RevenueCat.

When you delete your account, Forklist asks RevenueCat to delete everything it keeps under your account id, your purchase history included. Apple or Google keeps its own record of a purchase. The request carries that id and nothing else. Forklist sends that request for every account it deletes, because it can't tell who opened Plus. If you never did, RevenueCat has nothing under your id to delete. Deleting it does not cancel a subscription; Apple or Google keeps charging until you do.

RevenueCat handles this for Forklist under a data processing agreement. It hears nothing about your places, notes or friends, and it shows Forklist subscription totals, never how anyone uses the app.

Hosting

The app runs on Amazon Web Services in the United States. AWS holds the database and serves the traffic, so standard web server logs exist there.

Nobody else

That is the entire list, and each is there to make something you asked for work. No third party gets your data for analytics, advertising, personalisation or crash reporting.

Amazon Web Services, which hosts Forklist, and RevenueCat work for Forklist under data processing terms. They may use your data only for the job this page describes, and must protect it at least as well as this page does. Google and Apple get only what this page lists, and they handle it under their own privacy policies.

Your rights, and the two buttons for them

Wherever you live, you have these rights over the rows above, and in the EU and UK the General Data Protection Regulation backs them. Two of them are buttons in the app.

None of this costs anything or needs a reason. The two buttons work at once. For anything else, ask.

Cookies, and what sits in your browser

Two cookies on the website and three in the apps, all strictly necessary. One keeps you signed in, and one protects your sign-in while you are away at Google or Apple. The third is set only in the Android and iPhone apps, and only tells Forklist to show the app's own sign-in. Your settings, such as theme, units and text size, are not cookies. Signed out, they stay in your browser. Signed in, most of them are saved to your account, so they follow you to every device you sign in on. There is no analytics cookie, no advertising cookie and no third party setting anything through this app. That is why the notice has nothing to ask you.

The Android and iPhone apps also keep a copy of your map, your profile and your settings on the phone, so a screen opens at once and your profile and settings are there with no signal. It holds the nicknames you gave friends, the places on your map, the notes you can read with their scores, your own marks and where you ranked them, with Overture's name, address, pin, phone and website for a place where Overture lists it. Nothing Google gives Forklist is kept there but a place's id, and a pin Google gave for at most 30 days. A free account's copy holds up to 1,000 places, without photos. With Forklist Plus it holds every place on your map, up to 1,000 of the photos you added yourself, your lists and the lists shared with you, and the crawls you are on: each stop, the line on it and who wrote it, the times and the addresses. When Plus ends, what is on the phone stays: up to 1,000 places keep updating, the lists, crawls and photos already there keep up, and no new ones are added. With nudges on with the app closed, the phone also keeps its list of places to watch. When a note stops being yours to read, because of a block, an unfriend, leaving a group or its writer narrowing who sees it, it leaves the phone the next time the app reaches Forklist, and so does a crawl you leave, a list a friend stops sharing or a photo you remove. Signing out, signing out everywhere, deleting your account or signing in as someone else empties it; a sign-out made on another device empties it the next time the app reaches Forklist. Everything in it is on the server too, except a place you added with no signal, which waits there until you send it, and a change to how the app looks made with no signal, until the signal comes back.

The cookies page names each cookie, how long it lasts, which settings follow your account, and what stays on the device.

Leaving

Settings → Account. You type DELETE instead of tapping a button, because this cannot be undone.

Deleted as soon as you confirm:

• Your account, and its link to the Google or Apple account you signed in with. The Google or Apple account itself stays as it is.
• Every note you wrote, your ratings and your upvotes.
• Every guide you wrote, published or not. Its link stops working at once.
• Your saves and upvotes on other people's guides.
• Your profile photo, your banner and every photo you added to a place or a guide, files included.
• Your lists, your Been and Want to try, the places you took off the table, and your passport.
• How you ranked the places you've been.
• The asks you sent naming friends who went with you, and the asks sent to you. A place a friend said yes to stays on their list.
• Your reactions to friends' forks, and which friend's fork or message you forked a place from.
• Your place in every challenge, and any challenge you said Not now to. A challenge you started with friends carries on for the others, without your name.
• An ask you sent into a challenge stays with that friend, without your name.
• Your friendships, any requests still pending in either direction, the requests you declined and anyone's decline of yours.
• The nicknames you gave friends and any nickname a friend gave you, with any record that the team removed one.
• Your group memberships, your conversations and your notifications.
• Every crawl you started, your place on anybody else's, and the record of who you took off a crawl and who took you off theirs.
• The polls you started and your votes in others, and every table you opened and every seat you asked for.
• The people you blocked and anyone's block of you, the point you sent to any meet request that has not expired yet, and your answer to the age question.
• Any support message you sent.
• Every session, so every browser and every phone is signed out.
• Your age record, and where it came from.
• The team's record of anything it took down of yours.
• Every report you filed, open or closed.
• The push token for each phone where you turned on notifications, so they stop arriving, the key your phone's widgets and nudges use, and the pick Fork me remembers.

• Also deleted: any place left with no notes on it at all, and any group where you were the only member.
• Also done: if you signed in with an Apple account, Forklist tells Apple to cut the link. Apple asks for that, and it stops the sign-in working from their side too.
• Also done: Forklist asks RevenueCat to delete everything it keeps under your account id.
• Not done: Forklist Plus is not cancelled. Apple or Google keeps charging until you cancel. Cancel first: on an iPhone in Settings, your name, Subscriptions; on Android in Google Play's Subscriptions; or from Manage or cancel in the app.
• Kept: places other people have also written about. Your leaving does not remove a restaurant from their map. A stop you added to someone else's crawl stays on it, and so does any line you wrote there, without your name. A group that still has people in it keeps the name you gave it, without your name.
• Kept by the team: reports other people filed about you or something you added. Each keeps the kind of thing it was about, the reason, when it was filed, who filed it, whether the team has closed it, and the words of whoever filed it, which may name you. There is no set end yet. When there is one, this page will say it. These reports share one random code, so the team sees them together. Nothing in a report leads back to your account.
• In backups: a backup of the database is kept for seven days, so a copy may exist for up to seven days after you leave.
• Kept without a name: the team's log of what it opened or changed keeps your account id, which no longer leads to anyone.
• Free at once: your guide address, forklist.me/guide/ and the name you picked. Anyone can take it.
• Out of Forklist's reach: a crawl someone on it saved as a PDF keeps any line you wrote there, with your first name.
• Asked first: if you lead a group with other people in it, you choose who takes it over before the deletion runs.

Before you confirm, the app shows you exactly what will go. You can also ask, and Forklist deletes it and writes back when it is done. You don't need to give a reason either way. This is your right to erasure under GDPR Article 17.

The deletion page covers the same steps on its own.

Children

Forklist is for people 13 and over. If Apple or Google tells us an account belongs to someone under 13, or you tell us, we delete the account and everything in it.

If you are 13 to 17, everything on this page applies to you as it does to anyone. Tables are for people 18 and over. Ask a parent or guardian before you buy Forklist Plus. Apple and Google may ask them to approve it, and where a parent's settings say no, the store will not sell it.

Changes, and asking

If this page changes what is collected or who can see it, the date at the top changes and a dated entry below says what changed.

Forklist is run by Aditya Prasad, a sole proprietor in Virginia, USA, who is responsible for your data here. Write to socials@forklist.me, or use Support.

2 October 2026: signing in with Apple, what RevenueCat does, that deleting your account does not cancel Forklist Plus, and a line for teenagers. Later the same day: deleting your account also deletes what RevenueCat keeps about your purchases, a profile shows your Plus rank but no longer the date you joined it, a crawl stop's line carries the name of whoever wrote it, a crawl can have a link that opens without signing in, and a guide you publish can be read by anyone with its link and reported without an account.

3 October 2026: a nudge keeps which place it was about and when, for 30 days, and is then deleted; what the phone keeps for nudges with the app closed; and six screens send your coordinates, not five. Later the same day: a guide's count of your cities leaves out notes only you can see, and you can keep six photos on a place with Forklist Plus.

4 October 2026: the Android app, and the iPhone app where a law asks for it, ask Google Play or Apple for your age range. Forklist keeps whether you are 18 or older, uses it for tables, and deletes an account they say belongs to someone under 13. At a table, people who are not friends see each other's initial. The people seated see each other's pictures once the table is full or three hours before it meets. Later the same day: tables open to a city are for accounts two weeks old, with five friends and ten saved places, and pause while two people's reports about you are open or for 90 days after the team takes something of yours down. The team's log of a takedown now says whose it was. Later still: a note on Tables says why your city tables are paused and lets you ask a person to look again, who answers within two weeks; automated decisions have their own row; and the page says the legal basis for each use. Download my data names the three things it leaves out and gives a place only Google lists by its Google id and a Maps link; the answer to a support message you send signed in arrives in the app; and the reports row says only reports from people signed in to Forklist count. Also that day: a crawl link joins a guide as what can reach people who are not on Forklist; what a guide or a crawl link shows about a place you pinned; a crawl you can save as a PDF; your guide address is free once you delete your account; the phone keeps up to 1,000 of your photos; fonts from Google and Apple's sign-in button; and deleting any account asks RevenueCat to forget it. Later the same day: a stop you added to someone else's crawl, and any line you wrote there, stays when you leave; and a guide, a crawl link or a crawl saved as a PDF asks Google Maps for a place only Google lists, keeps none of the answer, and can show Google's map. Later still: a notification's photo is one someone added to the place, never one of Google's, so a photo you add can appear in a notification to anyone who can see your note there.

8 October 2026: the Android app does not offer nudges with the app closed yet.

11 October 2026: the Support messages row says what a message sent from inside the app carries besides your words: whether the app loaded, the last error it hit, and your window size. The line is not new: messages sent from the app carried it before this page named it.

12 October 2026: the Android and iPhone apps set a third cookie, which only tells Forklist to show the app's own sign-in. It holds the number 1 and nothing else. Later the same day: the RevenueCat section names what the app tells RevenueCat with each request, and no longer lists what RevenueCat deletes, because Forklist asks RevenueCat to delete everything it keeps under your account id. The row on whether you are 18 or older says the app asks each time you open it until Forklist has a reply, then once a year, and that Forklist keeps when Apple or Google last replied. The Google and Apple sections name a Plus purchase, which carries your Forklist account id, or on Android a code made from it, to the store that takes the payment, and the delete-account page says Forklist asks RevenueCat to delete everything it keeps under your account.

13 October 2026: the Apple section and the delete-account page now say where to ask Apple for a copy of what it keeps.

17 October 2026: the Leaving list now also names the people you blocked and anyone's block of you, the reports you filed and the reports about you or something you added, and the team's record of anything it took down of yours. Deleting your account deleted these before the list said so. It also says the team's log keeps your account id, which no longer leads to anyone. Deleting your account now also deletes the notifications you caused in other people's bells, which used to keep your name. Later the same day: a request you decline is kept for 30 days, so another request from the same person in that time does not reach you, and leaving deletes it.

18 October 2026: the Leaving list puts one thing on each line, in the order the deletion page uses, and says your Google or Apple account itself stays as it is. Settings and the help and support pages now say what this page says about a nudge: your location is never sent to us, and Forklist keeps which place and when, for 30 days.

19 October 2026: this page said a few people run Forklist and that each has a role. It now describes the dashboard's roles and what each can open, and does not say how many people hold one.

19 October 2026: when a crawl's owner takes someone off it, Forklist keeps who and when, so an older link, the crawl in a chat or anyone else on the crawl cannot put them back. The owner's Download my data includes it, and leaving deletes it.

19 October 2026: when somebody reports you, the team also sees what other people can see of yours: your name, line and city, the names of groups you named and lists you shared, your lines on crawl stops and your guide address. They can clear any of these. Clearing one is a takedown: Forklist tells you which rule it broke, and for 90 days it pauses your tables open to a city.

19 October 2026: a report somebody else filed about you, or about something you added, stays with the team after you delete your account. It keeps the kind of thing it was about, the reason, when it was filed, who filed it, whether the team has closed it, and the words of whoever filed it, and nothing that leads back to your account. Before, it was deleted with your account. Every report you filed is still deleted, open or closed.

20 October 2026: Leaving says a report kept after you delete your account also keeps who filed it and whether the team has closed it, and that there is no set end for keeping it yet. A report on a guide sent without an account no longer keeps the scrambled copy of the address once the guide is gone. The roles now say a moderator can take down or clear what was reported. The row on reports you file now says, as Leaving does, that the words in a report kept after the person it is about deletes their account may name them.

21 October 2026: the row on tables you open said a table's group and chat stay until the people in it leave. When a host called a table off, they were already deleted with it. Now they are also deleted when the Forklist team removes a table, unless someone reported a poll in that group. Notes shared with a group deleted this way become visible only to whoever wrote them.

21 October 2026: the reports kept after you delete your account now share one random code, so the team sees them together. The code does not lead back to your account.

23 October 2026: on the kind of phone you bought Forklist Plus with, opening Manage also asks RevenueCat whether your last renewal payment failed, so the app can tell you. The answer stays on the phone.

24 October 2026: after you mark a place Been, the app can ask which of two places you liked more and keep the order. Once you have ranked five places, a ranked place shows a score out of 10 instead of your stars, to you and to anyone who can see your note there. The ranking is in Download my data, and leaving deletes it.

25 October 2026: the settings row says it also holds choices you make outside Settings, such as how you sort each list. The rows on pins and notes and on your ranking say what you and others see before you have ranked five. Later the same day: a new row says who sees your profile's line, go-to and city. The short version says your notes, not everything you write, are private by default, and both deletion summaries say a line you wrote on someone else's crawl stays. The cookies page says what clearing your site data loses. Leaving says a group keeps the name you gave it. The row on the pick Fork me remembers says it is kept for the Fork me widget. The address to write to is now socials@forklist.me. The short version and the row on places said Explore never shows who saved a place or what they wrote. That was wrong. Explore shows a person's name or words to someone who can already read their note, and to nobody else.

26 October 2026: a new row, Who you went with: a friend can name you on a place they marked Been, you are asked first, and only your yes adds it to your Been list. Download my data carries the friends you named who said yes and every ask you were sent, and leaving deletes both. Later the same day: two more rows, reactions to a friend's fork and where you forked a place from; an upvote tells the note's author someone agreed, never who; and when three or more friends who share their marks want to try a place you want, a card and a notification name them. Download my data carries your reactions and where you forked from, and leaving deletes both. Later still: a new row, Challenges. The people in a challenge with you see how many places you have counted and the day you finished, never which places, and the Challenger badge joins your badges. Download my data carries your challenges, and leaving deletes your place in them. Who your marks reach now lists ten ways, and a paragraph says what Year in Food's share card prints. Download my data leaves out a fourth thing, whether a friend you named has answered yet, so that Not me stays private. Later again: the Messages row says a reply sent from a friend's fork keeps which fork it answers, shown to each of you only while you can still see the fork. Download my data carries it on each message.

27 October 2026: the Challenges row says an ask a block or an unfriend takes away is kept as Not now keeps one, so you are not asked into that challenge again.

31 October 2026: Your badges says what Kindred counts: friends whose taste match with you is 89% or more, leaving out anyone who turned off Using your saved places. The Messages row says you can react to a message with emoji, that everyone in the chat sees who reacted and with which, and that everyone in a group reads its chat. The Lists row says a list published as a Plus guide can be read by anyone with its link.

4 November 2026: a new Google item, Updates and ratings, in the Android app. The app asks Google Play whether a newer version is ready, and once, after you have marked five places as been, it can show Google Play's rating card.

4 November 2026: some sentences say the same things in plainer words, and three things changed. Leaving says backups of the database are kept for seven days. Google's and Apple's sections say what Directions and Open in Maps give a map app. The Nobody else section used to say every company named here is bound to protect your data as well as this page does. That was not true of Google or Apple, which handle what they get under their own privacy policies, and it now says so.

6 November 2026: a new row, Nicknames for friends: a name you give a friend, which only you see. Your friend is never told. Download my data has the ones you gave. Unfriending, blocking or deleting either account deletes every nickname between the two of you. If your friend asks, the team can remove the one you gave them. Leaving and the deletion page now say so. A notification can carry it through Google's or Apple's push service to your lock screen. If the team removes one, you are told and can't give that friend a new one while you stay friends, and Download my data shows that. The section on what the people who run Forklist can see now says a moderator can remove one. Download my data now names what other people keep private about you as one of the four things it leaves out. A nickname a friend gives you relies on a legitimate interest you can object to, and the phone apps' copy now holds the nicknames you gave.