Privacy
KiND Social · Last updated 3 October 2026
Who we are
Saucer is operated by KiND Social, a sole proprietorship in Sevier County, Tennessee, United States. Questions about anything on this page go to 13rt.com@gmail.com.
What we collect
Your account
You sign in with Google, or with a link sent to your email address. We store the email address on the account and the profile picture your sign-in provider gives us. We never see or store a password. Google's sign-in and our email links are handled by Firebase Authentication, and your sign-in record there may carry the name on your Google account — we do not copy it into Saucer and nothing on Saucer shows it.
Your profile
The handle you pick, a short bio if you write one, and the answers you choose to fill in — a favourite dish, and so on. Each of those has its own switch, and nothing is shown that you did not turn on.
What you post
Photographs, the caption you write, the restaurant, the dish, and the kind of food. Plates are public. Anyone can see them, signed in or not, signed with your handle and nothing else. That is the point of the site — it is a place to show what you ate, not a private album.
Posting is only possible from inside the restaurant, so your device's position is checked at that moment. Your coordinates are not stored. What a plate records is the restaurant it was posted at, and how far from that restaurant's map pin you were when you posted — a single distance in metres, kept so we can tell that a place's customers sit ninety metres from its pin and widen that restaurant's posting radius. It cannot be turned back into where you were: it is a distance from a fixed point, not a direction, and the point is the restaurant you already named.
What you do
Likes, comments, the plates you keep in collections, the plates you send to other people, who you follow, and who you block. Likes and comments are public. Collections are private unless you make one public. Blocks are never shown to anybody.
If you report a plate, nobody can read your report — not the person who posted it, not other users. Only we can, and only to decide whether the plate stays.
Payments, for restaurants
If you claim a restaurant page, payment is taken by Stripe. Card details go to Stripe and never reach us or our servers. We store the customer and subscription identifiers Stripe gives us, and when the year runs out.
On your device
Saucer keeps a few things in your browser's own storage: your feed filters, plates you have hidden from your own feed, an unfinished post, and whether you have been here before. These never leave your device and we cannot read them. There is no advertising or analytics tracking on Saucer, and no third-party advertising cookies.
How your photographs are checked
Every photograph is analysed by Google Cloud Vision before it posts, to confirm it is food and to refuse anything unsafe. The image is sent to that service for that check. We keep the labels it returns, so a decision can be explained later.
Who else handles your information
- Google Cloud and Firebase — hosting, sign-in, the database, photo storage, and the code that runs the site. Data is stored in the United States.
- Google Cloud Vision — the food check described above.
- OpenStreetMap (Nominatim) — turning a set of coordinates into the name of a town. This is how a restaurant gets its city and country, and it is also how your kitchen gets its town, so the position of your kitchen is sent to them at the moment you place it. It is sent once, nothing is stored there by us, and only the town name comes back.
- Stripe — payments, for restaurants only.
We do not sell your information, and we do not share it for advertising.
What restaurants can see
A restaurant that has claimed its page sees the plates posted there, with the handle on each one, exactly as everybody else does. It can take a plate down from its own page if the plate has no likes, and it can sponsor one. A restaurant is never told who claimed a discount beyond the code at the till, and never gets a list of its diners.
Where your kitchen is
Saucer Home is for food you cooked at home, and a dish can only be posted from the kitchen it came out of — the same rule that means a plate can only be posted from inside the restaurant. To check that, we need to know where your kitchen is, so we ask once, the first time you post a dish, and store that position.
It is never shown. Not to other cooks, not on a map, not as an address, and there is no way to get directions to a kitchen. It is not in anything the app sends to anybody's phone, it is kept out of our records of who did what, and it is not written to our diagnostic logs. The only thing published from it is the name of your town, worked out from the position and never finer than a town.
It is used for three things: checking you are at home when you post, deciding which kitchens appear in Browse for somebody nearby, and deciding which dishes appear in the Local feed for somebody nearby. The last two answer at the scale of a county, deliberately, so that nobody can use them to work out where you live.
You can move it whenever you like, and deleting your account deletes it. If you never use Saucer Home, it never exists.
Leaving
You can delete your account from the Saucer menu, under your handle.
What goes: your sign-in, the email address on it, your profile picture, your bio and answers, your collections, who you follow and who follows you, anyone you blocked, your inbox, any discount codes you were holding, where your kitchen is, the dishes you posted from it and the recipes you wrote. You will not be able to sign in again.
What stays: your plates with their captions, your comments, your likes — and your handle. Restaurants build their menus out of those photographs and may be paying to run one, so they are not withdrawn. Your handle stays yours rather than being recycled, so nobody else is ever credited with your photographs. The dialog says all of this before you confirm.
A restaurant page that has been claimed cannot have its account deleted, because the page carries money, a menu and discount codes attributed to it. A restaurant that is finished simply stops using the page.
Deleted data can persist for up to seven days in our encrypted backups before it ages out. We keep an internal record that an account was deleted, and when.
How long we keep things
Plates, comments and likes are kept for as long as Saucer runs — they are the site. Account and profile information is kept until you delete your account. Our own operational log of actions taken on the site is kept for as long as it is useful for moderation and for answering disputes. Backups are kept for seven days.
Children
Saucer is not for anyone under 13. If we learn that an account belongs to a child under 13, we delete it.
Your rights
Wherever you live, you can ask us what we hold about you, ask for it to be corrected, or ask us to delete your account — the last of which you can simply do yourself. If you are in the EU, the UK, or California, you have further rights under your own law, including the right to a copy of your data and the right to object to how it is handled. Write to 13rt.com@gmail.com and we will answer within 30 days. We do not sell personal information, so there is nothing to opt out of.
Changes
If this page changes in a way that matters, the date at the top changes and we say so in the app. Continuing to use Saucer after that means the new version applies.