Wassaaa Privacy Policy
Wassaaa is provided by Sigmaton LLC ("Sigmaton", "we"), a company registered in Sharjah Media City, Sharjah, United Arab Emirates. This policy explains what data may be processed when you use Wassaaa, including checking in at a place, its menu and your orders, Rewards, your conversation with its team, voice notes, and, if you choose to meet people, your selfie, chats, filters and stickers; nearby locating and notifications.
1. Information We Process
- Anonymous Firebase session identifiers and, if you choose to keep your account (Keeping your account on a new phone, below), your phone number, or your Apple or Google sign-in and its address, and your account identifier. An account that already had an email address and a password keeps them until it chooses one of these ways.
- Recent location fixes used to show nearby venues and validate an active visit to a place. A fresh latitude, longitude, accuracy, and timestamp may be sent to Firebase for that admission or lease check, then are not stored in the record of who is at the place or turned into a route history. With it the app sends whether your phone reports the location as simulated and, on iPhone, whether it came from a connected GPS accessory. If the place has added its own Wi-Fi, the server compares the internet address your request comes from with that network, and keeps nothing about your address. When you come into a place, our server compares it with the place it last counted you in and when (records it already keeps to count you in one place at a time, and, once a visit there has ended, a note of that place and the last time your phone showed it was inside, kept for 24 hours and then deleted, at once when you erase your account; no phone and no place's team can read it), and refuses an arrival you could only have made faster than a plane; nothing more is kept for it. Location checks for a visit stop when the visit ends; your exact coordinates are never shared with the other people at the place. To show the places around you, your phone works out for itself which squares of the map to load (each about 150 metres across) and asks for those, the way a map app asks for map tiles; your coordinates are not sent for this, and which squares you load is not stored.
- Your phone's motion sensor, on your phone only: during a visit, Wassaaa notices when the phone is lying still so it can pause location updates and save battery. The same stillness lets the phone check in with our server less often during a visit: with each check-in the phone tells our server only whether it is lying still, and that is not kept. The readings themselves are never uploaded or stored.
- On iPhone, for the few things described in Nearby Interaction locating, a short-lived Nearby Interaction discovery token is exchanged with the other phone. The token is a pairing value, not your name or a public profile.
- Content you send in chat, including text, stickers, photos, and voice messages. A voice message you send a place's team (or they send you) is compressed audio stored only until your visit ends, when it is deleted with the conversation; the team and the Wassaaa operators can play it during the visit. Voice messages are not offered in Campus buildings or classes. Words you write to a place's team (a message, or the note on an order) are checked by our server against the content policy, with the rules that hold on Everyone here: words aimed at a person are refused, and a swear word is masked ("f**k") before the team sees it; our server keeps only the masked words. To stop misuse, your phone writes beside each message you send in a private chat how much of its allowance for a burst of messages is left, with the time of that message and which message it was, and our database refuses a message past the limit; that count is kept with the chat and deleted with it. (A phone on an older version of the app hands its messages to our server, which counts the messages you send in a private chat each minute, with the time of the last one; that count is deleted when your visit ends.)
- Which team member answered. In your conversation with a place's team, each reply from a team member, and the record of who has taken your conversation, carry a code that stands for that team member at that one place. Our server makes it with a key only our servers hold, so it cannot be turned back into their account and it is not the same at another place; your phone uses it only to tell two team members apart. Until older versions of the app are retired, your phone is also still given the identifier of that team member's account beside the code, as it has always been; the app shows neither of them, and a phone on an older version of the app reads only the identifier. Your language. When you start a conversation with a place's team or write in it, the app or the place's page tells our server the language it is in; our server keeps it with its own note of whose the conversation is, where neither you nor the place's team can read it, only so that a team member's "On my way" reaches you in that language, and it is deleted with the conversation.
- What you see of a place's team: whether it is here, and where your message has got to. In a place's bar the app (and the place's page in a browser) shows one line: "The team is here", with "Usually answers in about 3 min" once the place has had five first answers in two weeks, or "The team is away right now". Our server works it out from the place's team: the team is here while someone has started a shift and a screen of that shift has been heard from in the last two hours (A team member's shift, below). The line says nothing about who, how many, or where anyone is. Above the box you write in, one quiet line says how far your message to the team has got: "Sent"; "Delivered to the team", when an alert for it was accepted for the phone of someone on shift (or, while nobody is on shift, of one of the place's owners or managers, who are alerted instead), or one of their screens was open; "Seen", when a team member opened it; and "{name} has it", when a team member took it. The name is the one that team member shows on their replies (the name they, or the owner who added them, gave; never an email address); when they show none, it reads "The team has it". Our server keeps these as times and a name on your conversation with the team, with the number of minutes the place has set for answering (two to start): when an alert for your message was accepted, when the team opened it, when a team member took it and who, and when you were last told that nobody had. If a team member's shift ends while they have your conversation, it goes back to the team and keeps that person's name and the time until someone takes it again, so that the next team member can see it was left open; your phone can read that name, and never their account. All of this goes with the conversation (section 6). One notification: if nobody has taken your message after twice the number of minutes the place has set, you are sent one notification, "Nobody has picked up your message yet. If it's urgent, ask at the counter." (at a hotel, "at the front desk"), whatever your notification settings say: like the steps of an open order, neither "From the place you're at" nor "Pause notifications" holds it (an older version of the app, open on screen at that moment, may still hold it by them). It is sent once for each wait, and never while someone has your conversation, after your visit has ended, or to a guest using a place from a browser, whose page shows the same line instead. It carries only the place's name, those words and what the app needs to open the conversation. To send it on time, our server checks the conversations that are waiting when your phone or a team screen is open and, with every screen closed, every 15 minutes, so it can come up to 15 minutes late.
- A place's messages to everyone inside, on your phone. When a place's team sends a short message to everyone inside (fresh bread out, last call), your phone shows it in Chats, under the place's name, for the rest of your visit, and counts it as unread until you open it. For that it keeps, in the app's ordinary storage, the messages of your current visit with their times, the identifiers of the place and of the visit, when it first saw that visit and how far you have read: the place's own words, and nothing about you. They are replaced when your next visit begins, and go when you erase your data. Our servers keep only the place's latest message, on the place's own record, where any phone can read it.
- In a private chat, from this version of the app, your phone puts each message, sealed, into the conversation on our servers itself, and our database accepts it only from one of the two people in that chat, while that person is inside the place among the faces. Our server then gives each message a number in the conversation's order, so that both phones can tell when one has not reached them and count exactly what is new; the number says nothing of what the message says, and it is deleted with the conversation. (A phone on an older version of the app hands each message to our server, which puts it there and numbers it the same way.)
- In a private chat, receipts: when your phone has received the other person's messages, and when you have read them, so their phone can show "delivered" and "seen". They are times only, kept with the conversation and deleted with it. "Read receipts", a switch in the app's Settings, is on unless you turn it off; with it off, your phone sends no "seen", and you see no "seen" from anyone either, while "delivered" is still sent. It is for chats between guests: a place's team still sees when you have read its reply. "Message info" on a message of yours shows when it was sent, delivered and seen, as your phone saw those times (a time it did not see is not shown); it asks our servers for nothing, and nothing more is kept for it.
- If you delete one of your own messages for everyone in a private chat ("Delete for everyone"; versions of the app before this one call it "Unsend"): it is deleted from the conversation on our servers at once. So that both phones can show "This message was deleted" where it stood, a mark is kept with the conversation: whose message it was, when it had been sent, its number in the conversation's order and when it was deleted, and nothing it said; any reactions to it are deleted in the same step. The mark is deleted with the conversation. A note naming only the message is also kept for the other person's phone, so it can remove its copy (including the read-only copy described below) the next time the app is open. The note is deleted when that phone has used it, and within two days at most. (A phone on an older version of the app does not show the mark: there the message simply goes.) If you delete a message from your own phone only ("Delete for me"), nothing is sent to our servers or to the other person, who keeps the message; what your phone remembers so that it stays deleted is described further down, with what is kept on your own phone.
- A reaction you leave on a message in a private chat is sealed on your phone like a message, and kept on our servers beside that message, with the time you left it: one for each person in the chat, until you change or remove it, the message is deleted, or the conversation ends. Our server cannot read it. It does tell the other person's phone that you reacted, with a notification that has your name for the visit, the place's name and, as a message's does, the address of your small photo, and says you reacted, once for each message from each person: changing a reaction, adding it again or taking it back tells nobody, and a chat the other person muted tells them nothing. To tell it once, our server keeps, under the chat and only until the chat ends, who reacted to which message, and never the emoji. While their phone shows message text (Words on your lock screen), the emoji goes too, sealed in a small envelope of its own that only their phone opens. They can turn these notifications off with "Reactions" in Settings › Notifications, and Pause holds them. While the other person's app is open, their own phone may tell them of it. (To a phone on an older version of the app, your phone sends a reaction the earlier way, as a sealed message of its own that is not one to notify about, described with screenshots in section 2.)
- You can edit the words of a message of yours for 15 minutes after you sent it, when the other person's phone has this version of the app. The new words are sealed on your phone like the first and take their place on our servers, with when the message was last edited and how many times, and the message is shown as "edited". The earlier words are not kept on our servers and are not shown again, except in two places: a read-only copy that the other person's phone made before the edit (section 6) still holds them until that copy is deleted; and a reply written before the edit carries, sealed like the rest of it, the start of the words it answered, which a phone shows only where the edited message is no longer in the conversation on that phone (where it is, the reply shows the new words).
- A photo you send in a private chat as "View once" (offered when the other person's phone has this version of the app) is sealed like any photo; beside it our servers keep a mark that it is view-once and where its sealed file is, so that our server can delete the file. It can be opened once, and only inside the place: the other person's phone shows it from its memory, without keeping it as a file, and tells our server that it was opened, which deletes the photo from our storage and from the conversation at once, with any reactions to it; when they close it, it is gone from their phone too. You cannot open it again yourself. Both phones then show "Opened" where it stood, and a mark is kept with the conversation: whose photo it was, when it was sent, its number in the conversation's order and when it was opened, and nothing of the photo. A view-once photo that is never opened goes with the conversation. Screenshots of it are treated as in the rest of a private chat (section 2); nothing stops someone from photographing the screen with another device.
- If you choose "Mute for this visit" in a private chat, your phone writes that choice into the chat on our servers, where the other person cannot read it, and they are not told. While it stands, neither our server nor your phone notifies you of that chat's messages or its "Keep in touch" taps (or, on a phone on an older version of the app, of its games: an invitation, a yes to yours, "Your turn"); a match, a place's question and the place's team are not muted by it. It lasts until you unmute the chat or the chat ends, and is deleted with the chat.
- A safety tip about money. In a private chat, your phone looks for requests for money or codes (a payment app, a gift card, "send me the code") and, if it finds one, shows you a safety tip once. It reads what you are sent and what you write, and also the line the other person has for their visit, which a new chat shows on its card. This runs only on your phone; nothing about it is sent to us or kept.
- People you have met, on your phone only: when you and another guest have both written to each other in a private chat, your phone remembers it, so that if the two of you are in a place together on a later visit, their face can say "You met at Jebena". What it keeps is a list on your phone: a one-way mark of the other person's account (made with a random secret that never leaves your phone, so the mark cannot be turned back into the account), the place's name, and when. The list is encrypted on your phone and never uploaded: our servers do not know who has met whom, and the other person sees the same line only if their own phone remembers too. Each meeting is deleted 180 days after it happened. You can clear the list at any time by turning off "Remember people I've met" in Settings, which also stops it. Blocking someone removes them from the list, and unblocking does not put them back. "Erase everything about me" and deleting your account clear it. This works because your phone's anonymous account stays the same from one visit to the next, even though your handle and selfie do not: that account is what your phone's list recognises. Nothing is remembered in a Campus class.
- People you block: when you block someone, Wassaaa keeps with your account who you blocked, the handle they had, when, and the name of the place you were in. Your phone uses it to keep them hidden from you, our server uses it so that the two of you can never be matched and they cannot write to you (in versions of the app before this one, so that they cannot say hello to you either), and Settings shows it to you under "Blocked people" as where and when ("Blocked at Jebena · Oct 3"; an older version of the app lists the people without where and when). Nobody else can read your list, and the other person is not told. So that you are no longer shown to them either, our server keeps the same block the other way round (that they were blocked by you), where no phone can read it, and, while you are on a place's list and they have a visit there, writes one line that their phone alone can read: it says to leave you out of the people it shows them, and nothing else. All they can notice is that your face is no longer there. The line is there only while you are on the place's list: it is deleted when either visit ends, when you unblock them, and when you leave the list, and it is written again if you come back onto it. (A phone on an older version of the app does not read that line, and goes on showing you.) Your list holds 200 people at most: when it is full, our server notes that it is (a number, with your account, where no phone can read it), and you can block someone new once you have unblocked someone; the note is deleted when your list is shorter, and with your account. All of it is deleted when you unblock them, erase your data or delete your account. A block made with an older version of the app has no place's name. If someone blocks you, their list holds the same about you: the handle you had on that visit, when, and the place. It stays in their list until they unblock you, erase their data or delete their account, also after your visit has ended and after you erase your own data, and only they can read it. While you have a visit in a place and they are on its list, your phone is given the line described above, so that it leaves them out of the people it shows you; the line holds their account's random identifier and nothing more, the app shows it to you nowhere, and it goes when either visit ends, when they unblock you, and when they leave the list.
- Keep in touch. In a private chat you can tap "Keep in touch" if you would like to swap a way to reach each other. It is your choice, and nothing is shared until both of you have tapped it: one tap alone tells the other person nothing, not who tapped and not that anyone did. Our server keeps only that a tap happened, where no phone can read it, until the chat ends (a chat ends when your visit or the other person's does; section 6 says when that is); when both of you have tapped it forgets who tapped first, and it keeps no record of who swapped details with whom. Your own phone remembers that you tapped (and that the chat has already offered it once), so the chat can say so, and forgets it when the chat ends or your visit does, and within ten hours in any case. If the other person taps after you, a notification tells you that you both want to keep in touch; it says nothing more, because nothing has been shared yet. Then each of you chooses what to share (a name, a phone number, or a handle on an app, in which case you also choose which app it is on: Instagram, Snapchat, TikTok, X or Other) and types it fresh each time: the app does not remember what you typed or which app you chose, or fill them in for you. What you share, and which app a handle is on, travels inside the encrypted chat as a message like any other, so we cannot read it. On the phone that receives it, a handle on Instagram, Snapchat, TikTok or X has a button that opens it in that app, and a phone number has Text and Call buttons that open that phone's own Messages and Phone apps. For a handle, the other person's phone first shows where it goes, as for any link (section 5), and only if they then choose Open does it leave Wassaaa; nothing is sent to us when any of these buttons is tapped. It stays in the chat on both phones, and in the read-only copy each phone keeps for a day, and you can delete it for everyone like any message. If you report a card someone sent you, what it says is sent with the report, like any reported message. Blocking or reporting someone cancels a tap that was waiting. Keep in touch is never offered in a class.
- "You met". When two guests who are finding each other in a private chat see that they have, either phone can say so: by the arrow's own "found", or by a tap on "We found each other" on Light up (section 4). Our server then keeps, under the chat and where only its two phones can read it, only that you found each other and when; both phones read it and write one quiet line in the chat, "You met · 9:22 pm". The line is not a message: nobody sends it, nobody can reply to it, and no notification is ever sent for it. Each phone keeps the time of the line, and whether the chat has made its one offer of "Keep in touch" after meeting, on that phone only, and forgets them when the chat ends or your visit does, and within ten hours in any case. Our server's mark goes with the chat, or sooner, when the two of you start to find each other again. It says that one of the two phones said you met, while both were finding each other; it does not mean that anyone checked.
- If you join a class in a college building: your full name as your instructor's roster expects it, your attendance, and your answers and score on a class quiz. See Campus Classroom, which describes that mode in full.
- If you choose to leave it, as you end a visit or when Wassaaa asks you once afterwards (below), at a restaurant, bar or cafe: a rating of one to five stars and an optional comment of up to 50 words. It is stored without your name, photo, handle or account, keyed only so the same visit cannot rate twice. The comment is read by the Wassaaa team only; the place's own team never sees it, and is never told who rated. The place's team does see the stars of each rating as it arrives, with no name, photo or handle; at a quiet place it may still be able to guess whose it was. The stars count toward the place's public stars ("★ 4.6 · 42 verified visits") when you were inside the place for ten minutes or more of that visit: what other guests see is the place's average and how many ratings count, never yours alone, and only once five different people have rated. A rating counts toward a place's public stars only if your account is at least seven days old or the team handed you an order during that visit (one given on the place's Wi-Fi counts too, but you are never asked to join it), and never if you are on the team of a place within 100 meters. After three ratings from accounts under 30 days old count at a place in 24 hours, the next ones are held for review and do not count, high or low alike; for that we keep the time of each such rating for 24 hours (deleted within two days), filed under the rating, not under you. It makes no difference whether you took a selfie: a visit in which you are here to order can leave a rating in the same way, and its stars count by the same ten minutes inside. To count one rating per person per place in any 30 days, we keep a one-way code made from your account and the place, with the stars you gave and the day; it cannot be turned back into your account and is different at every place. How the stars are worked out is at How stars work. (Older versions of the app offered a thumbs up or down, or said only the Wassaaa team sees a rating; those go to the Wassaaa team only and never count toward stars.) Stars after a visit. Some while after your phone was last seen inside a restaurant, bar or cafe, about 30 to 45 minutes, while your visit is still kept, Wassaaa may ask you once, with a quiet notification, how the place was. It makes no sound and does not light the screen. Nothing is offered for an answer and none is needed; stars you give count toward the place's public stars with no name attached, as at End visit. It is not asked if you are back inside, in the last 15 minutes of your visit, for a hotel itself or in Campus, if you were there under ten minutes, if you have rated that visit already, or if you reported someone there or were removed. To ask only once, our server marks the visit with the time it asked, and that mark goes with the visit. So that a visit you have already sent your stars for is not asked about again, from this notification or at End visit, even after the app has been closed and opened again, your phone keeps a random identifier of that visit and the moment it ends, on this phone only: until that moment, which is never more than ten hours after you sent them, and until you sign out, change account or erase your data, whichever comes first. It does not keep your stars or your comment, and it is never uploaded. The notification holds the place's name and, so that a tap opens the right place, the random identifiers of the place and of the visit; it never holds your account. Turn it off with "After a visit" in Settings › Notifications; a pause holds it, and a phone on an older version of the app is not asked. After one or two stars the app also offers "Tell us what went wrong", which opens an email to support@sigmaton.com in your own mail app, with the place's name in its subject and, as Settings › Help › Report a problem does, the app's version and build, your phone's model and its system version already written in it. You see all of it before you send it, Wassaaa adds nothing else, and nothing is sent unless you send it.
- The store's rating sheet. To choose a good moment for your phone's app store to ask you to rate Wassaaa, the app keeps a few counts and times on this phone only: how many visits began, in how many conversations you both wrote and how many orders were picked up; when it last asked; when something last went wrong (a refusal, an error, a report, a block, a removal or an order not collected); and when it was last told that an order of yours had to be confirmed at the counter first, which holds the sheet back for 30 days. So that nothing is counted twice, it also keeps, for two days, a random identifier for each visit, conversation and order it counted, and nothing else about them. The rest stays until you sign out, change account or erase your data, and none of it is ever sent anywhere. The store decides whether to show its sheet, and Wassaaa never learns what you chose. Wassaaa never asks in answer to a tap, in a first visit or in Campus, never right after stars or any other rating of ours, and waits a day after anything that went wrong. "Rate Wassaaa" in Settings opens the store's own page for the app (section 5).
- If you report someone: what you saw, sent with the report so a person can act on it. That is the message you reported and the last few things that person sent you in that conversation. When the report is about a post on Everyone here or at a table, our server files beside it the words of that post as it keeps them (as written, before any strong word was masked) and the handle it was posted under, so that the person who reviews the report reads what was really posted; they are kept with the report's line in our safety team's queue, 180 days at most. Your own messages are not sent, the person reported is not told who reported them, and the place you are in never sees the contents of a report. So that one person counts once, our server also notes, where no phone can read it, that your account reported that person in that place; the note is deleted when that person is removed from the place because of the reports, when the place's day ends (the next 6 am there), or when the last visit in that place ends, whichever comes first. When a report of yours alerts our safety team, the server also keeps the time of that alert, under a one-way code, for ten minutes, so that several reports in a row alert them once; every report still reaches them. So that one person's reports cannot outweigh everyone else's, our server also counts the reports you make in each visit to a place, under a one-way code (a number and when your visit began): only your first twenty in a visit count toward taking a post down or toward the record of the person you report, and a report about someone who was never in that place counts toward neither. Every report still reaches our safety team.
- If you are reported, or a place's team removes you: a safety record about your account, so the person who reviews reports can see whether it has happened before. It holds how many reports you have received, from how many different people and at how many places (the people are kept only as one-way codes, never their names or accounts), what was done and when. It is deleted 180 days after the last report or action. If you erase your account within 30 days of a report about you, or of a removal or a pause, that record is kept for 180 days after the erase, with your account's id and the name you went by on the reports our safety team can still see, so that the person reviewing reports can still act on them: never the reporters' own words beyond what each report already keeps, and nothing else of your account. Beside it our server notes when the account was erased, until when the record is kept and the places it is about; no phone can read either. After the 180 days both are deleted. While you are in a place, the server also notes which places your current visits are in, so that a suspension can end them; that note goes when the visit ends. In each place our server also keeps a count of how many different guests there have reported you, where no phone can read it. A report counts toward removing someone automatically only when the person reporting has been at the place for at least 10 minutes and their account is at least a day old; our server reads when their visit began and when their account was made, and keeps nothing new. Every report still reaches our safety team. When it reaches three, the phones of the guests in that place are told that, and only that, never the count. You are removed from the place until the end of its day only when three of the people who reported you there had a tie to you: a chat between you, a yes of yours to them, or a post of yours that their report names (on Everyone here or at your table). Our server reads each tie when the report is counted and notes beside the count only that one was found, never which; nobody is shown it. When you are removed the count starts again from nothing. Otherwise the count and its notes are deleted when the place's day ends (the next 6 am there), or sooner if the last visit in that place ends before then. A decision to keep you out of one place, or to pause your access everywhere, is kept until it ends and then deleted.
- If your access is paused: so that deleting the app or erasing your data does not lift it, the app keeps a random code on your phone, in its secure storage, that tells our server a paused account used this phone; and on an iPhone, our server asks Apple to remember the same about your phone using Apple's DeviceCheck, two yes-or-no values Apple keeps for each app on each iPhone. We receive no identifier of your phone from either. Our server asks for that DeviceCheck answer for every new account on the iPhone app; it knows a request comes from the iPhone app from the check that it comes from a genuine copy of the app, whatever the app itself says. If Apple turns an answer down, or an iPhone sends none, our server writes one line in its security log, under a one-way mark of the account, at most once an hour. When the pause ends or is lifted, the code is forgotten and Apple's values are cleared the next time the app checks in. So that an iPhone asks Apple once for an account and not at every visit, the app keeps in the phone's secure storage a one-way mark of the account it has already asked for; the mark cannot be turned back into the account, is sent to nobody, and goes when you erase your data.
- So that a place's removal, a block, or a stop on paying after a dispute cannot be undone by erasing your data and coming back as a new guest: since November 19, 2026 the app keeps one random code for your phone (the same code as for a pause, above), in its secure storage, and sends it when you enter a place or come in to order. Our server hands the code to your phone the first time, and keeps which code your account last came with, under your account, until your account is erased. It is not an identifier of your phone, and nothing else is learned from it. A removal: if you are removed from a place (by its team, by our safety team or by three reports), our server keeps that removal under the code, with your account, until the removal ends (it runs out or is lifted). Until then a new account on the same phone is kept out of that place, and only that place, in the same words. A block: if someone blocks you, our server keeps that block under the code, with your account and theirs, for as long as the block stands. A new account on the same phone is blocked by that person too, as if they had blocked it, once their own app is a version from November 19, 2026 or later (an older one would show them a second line), and they are told nothing; it ends when they unblock you or erase their account, and erasing yours leaves it. An erased account: if your account is erased while it keeps a safety record (the point above), the record keeps a one-way code made from the phone's code, never the code itself, for its 180 days, so that our safety team sees "same phone" when a new account on that phone is reported. Erasing your data leaves the code on your phone; on an iPhone it also stays when you delete the app, and on Android deleting the app takes it. A version of the app before November 19, 2026 is given no code. A dispute: if you dispute a payment you made on this phone (paying for an order in the app, below), the stop on paying in the app is also kept under a one-way code made from the phone's code, never the code itself, and every account on the same phone is stopped, in the same words, until the stop on your account would end (the place wins the dispute or our support lifts it), and at most 180 days after the dispute's newest word; erasing your account leaves it. A payment made on a version of the app that is given no code carries none: its dispute stops your account only. A prize draw: where a phone is held to one entry, when you answer a question with a prize our server keeps a one-way code made from the phone's code and the question, never the code itself, with your account, until your visit ends, the question is cleared, or your account is erased. A second account on the same phone is told that this phone is already in the draw; its answer still counts. If the first has left, the entry passes to the second, and the first account's card says so. The code is used for nothing else.
- Keeping your account on a new phone. Entering a place never needs an account: the app makes one for you, with no name, email or phone number. A restore key: once you have something to keep (a stamp, a match or a paid order), your phone makes a random key and keeps it in your own password store (iCloud Keychain on an iPhone, Google's Block Store on an Android phone) and on the phone. We keep only a one-way code of it, under your account. When the app is put back on the phone, or on a new phone of the same kind, it finds the key and asks "Carry on as you?". Move to a new phone: the old phone shows a code for five minutes; the new phone scans it and becomes your account. We keep only a one-way code of it, until it is used or runs out. Keep my account: if you choose to, you can add your phone number, or sign in with Apple or Google, so that your account comes back even if you lose your phone. Firebase Authentication (Google) keeps the number or the address as your sign-in; with a phone number, Google texts you a code. We use them to sign you in and for nothing else, and never show them to anyone or to a place. We keep which of these ways your account has, never the number itself. If you signed in with Apple, deleting your account also tells Apple to end Wassaaa's sign-in. Your points: once you choose one of these ways, we also keep, under your account, a one-way fingerprint of the loyalty card on your phone (never its number), so that when you sign in on another phone your points move to the card there. One phone at a time: when your account comes back on another phone, the phone it was on is signed out and a visit open there ends. We keep the time, under your account, so that phone can sign itself out. A pause follows a phone number: if an account with a phone number is paused, we keep a scrambled code of the number (made with a key only our server holds; never the number) while the pause lasts, and for at most a year, so that erasing the account and signing in again with the same number does not end it. Erasing your account removes the key's code, the ways, the card's fingerprint and the time; a pause's code stays until the pause ends, as the pause does.
- Venue activity counts — how many visits, how long visits lasted, private chats that began between guests (and, from versions of the app before this one, hellos sent and accepted), staff conversations, instant answers opened, order-ready alerts, visits during a place's deal, how many selfies wore the place's own frame, how many wore the place's own lens or the lens of one of its events (a number for each lens), how many guests an announcement reached, how many guests used the place from a browser page, and how quickly staff first replied (and, from the same conversations, how many were taken within the place's own target and how many later, the slowest first reply, how many guests tried to reach the team or order while it was away and in which hour of the place's day, how many were told that nobody had picked up, wall posts and orders counted for Regulars) — kept per day and per hour as numbers only, never tied to a person. The place's own team sees these numbers as they are, even when they are small: on a quiet afternoon a count of one is one visit, with how long it lasted, and the team is not told whose. How long a visit lasted means time inside the place: when your phone comes back into a visit after being quiet for longer than the 30 minutes described in section 6, our server notes how long it was away and takes that off. The note is a number, kept with the visit where no phone and no place's team can read it, and deleted when the visit ends. So that a guest who tries again is counted once in a day as having asked while the team was away, our server keeps a one-way code of the visit with the place's day, where no phone and no place's team can read it, and deletes it two days on. To tell a place how many of its guests are new and how many came back, the server keeps a one-way hash of your account together with that place, and the day you last came. It is not your account, name or a visit history, it cannot be matched between places, it is never kept for a college building, and it is deleted 60 days after your last visit there, or at once if you erase your data. So that a place can be told how many of its guests came back often, that mark also holds the dates of your last three visits there (dates only, in the place’s own time), and they go with the mark. When a visit ends, our server adds one to a few small counts of the place for that month: how long the visit lasted (in bands, such as under 15 minutes or over 90) against whether an order was counted in it; how quickly the team first replied (within the place’s target, up to twice it, or later) against the stars given; and how long visits lasted during one of the place’s events or not. They are counts in a table of cells, never a visit, a guest or an account. Our server also notes which hours of a place’s day something of the place’s was running (a moment, a deal, its question, a pick or an announcement), and when a hosted moment ended, so that Insights can show what an event did.
- Where a place runs Rewards, its loyalty program (open to every place on a paid plan, never in Campus; it was Regulars, and before that a stamp card): you earn points for every dollar you pay there, before tax and tip. The place picks how many points a dollar gives; your points are a balance, and the place's rewards are items from its menu at a points price (never alcohol), which you spend with a tap on "Use". Wi-Fi, location, a visit, a selfie and "Meet people" play no part in earning or using a card, nothing is earned for a rating, a post or a share, and there is no limit to how many purchases earn in a day. What waits for the team's OK (since November 19, 2026): a card's till receipts at a place past about three in an hour or eight in a day, and a scan by the team above $100 or three times what that place usually scans, wait for an OK from the place's owner or a manager on shift, never the one who scanned; your card shows those points as waiting, outside your balance. If nobody says OK within 24 hours, or one says no, they are not added, and your card says so for 7 days, with how many and the day. For this our server keeps, for each place, your card's receipts there counted for the day (three days at most) and the points waiting or lapsed, under your card's one-way mark; and, for the place, the amounts and times of its last scans (to know what it usually scans) and its day's largest scans with the first name of the team member who scanned, for 35 days: never whose card. How a purchase earns. Where the place's Square or Clover till is linked to Wassaaa (Square, Clover), a screen on the counter shows a one-time QR for each sale as the till rings it up, good for two minutes; you scan it in Wassaaa and the points land. An order you placed in the app earns when the team taps Picked up. Where no till is linked, the team scans your card and gives a set number of points. If you scan the counter's QR with your phone's camera and do not have the app, a page keeps that sale's points for you until the same time the next day, so that you can get Wassaaa and tap Collect; after that they are gone. What your phone keeps. The number of your card, a random number, and a copy of each of your cards. That number alone is also kept in your own iCloud Keychain or Google Block Store, so that your cards come with you to a new phone (see the paragraph on backups, below). What our server keeps. A SHA-256 of the card number (a one-way fingerprint, so that the number itself is not held) and a random holder number; and, for each place where you have a card, a one-way mark of your card and that place with your balance, the day of your last purchase and a reward you are holding. For each sale that earned points: the amount that earned them, its time, the register it was rung on and whether the points were collected, for 30 days, so that a refund in the till can take its points back. Never a card number, a name, what was bought, or a list of your visits. Who can match what. No place can match you with another place, or recognise you from one purchase to the next: the QR is sealed for our server, and each place's card is filed under its own one-way mark. Our server can link your cards to each other, because Rewards lists them; it shows a place nothing about another place. Rewards. When you tap "Use now" on a reward in Rewards, its points are held for you for 15 minutes and are spent when the place rings the "Wassaaa reward" discount in its till; if none is rung, they come back by themselves. If you cancel it, they come back once the till's next sales show no reward rung for it, or after about three minutes; until then the hold keeps when you cancelled and when the points come back, and it goes with the hold. A reward's end date, if it has one, is shown in capitals. How long. Points are kept for 12 months after your last purchase at that place, and for 30 days after the place leaves Wassaaa; what you earned stays if the place changes or pauses its card. "Leave" on a card ends your card at that place, and "Erase everything about me" ends all of them, at once. "Move my cards" brings your cards to a new phone with the card number. When your phone finds a different card number from the one it last used (for example one that iCloud Keychain on an iPhone, or Google's Block Store on an Android phone, brings from your other device), the app moves the old number's points onto it, and the old number is forgotten; our server keeps, for 30 days, only a link from the old card at each place to the new one, so that a refund in the till can still take its points back. For this alone, the phone keeps the number it last used, on that phone only, and puts it back if iCloud Keychain or Block Store loses it. The place sees how many guests hold points and how many rewards it gave; never who, and it sees nothing of your other places. The notice of a financial incentive is the next paragraph.
- Notice of financial incentive (California). What the program is: a place's Rewards program gives you points and rewards in return for the purchase data described above (the amount of a purchase, its time and its register, kept as described). Its terms: points are earned as the place sets (a number for every dollar, before tax and tip), rewards are items from its menu at a points price, points are kept for 12 months after your last purchase there, and a refund takes its points back; the rules are shown behind "How it works" on every card. How to join: the first-time screen of Rewards, which shows this notice before any card is made; joining is a choice and nothing else in Wassaaa depends on it. How to leave: "Leave" on a card, or "Erase everything about me", at any time and with no charge; points you have not used are then lost. Why we value it as we do: Wassaaa sells nothing about a guest and pays nothing for it. The place gives the reward, and Wassaaa only keeps the card; we place no price on the data beyond the points the place chooses to give for a purchase.
- While you are at a place, that place may send one short announcement to everyone there, among the faces or here to order alike — at most one every two hours — as a notification that shows its words. It goes to everyone the place counts as there, as its own question does (until 30 minutes after a phone last showed it was inside), and to any phone that showed it was inside within the last ten minutes at most; never to a visit that is only kept, and you can switch it off with "From the place you're at" in the app's notification settings. When the place asks its own question, everyone it counts as there is told of it once, and that does not use up its announcement (see a place's own question, below, which also says what a phone on an older version of the app is told); the same switch turns it off.
- If you order in the app at a restaurant or cafe, reserve something at a shop, or ask for something at a hotel: what you ordered, reserved or asked for (for an item that has choices, the ones you made, such as a size or a milk), the total, your table if you give one (at a hotel, your room number instead, if you give it, and always when you ask for an order to be brought to your room), and an optional note, sent to that place's team in your conversation with them. You pay in the app when you send it, through the place's own payment company (Paying for an order in the app); at a place that takes no payments in the app yet, you pay at the counter, and a request at a hotel is free. A reservation at a shop is not a sale: the shop sets the things aside for you, and you pay for them in the app when you reserve, the money being held then and taken when the shop sets them aside, and let go if it can't (at a shop that takes no payments in the app yet, you pay the shop's own price at its counter when you collect them). If the shop keeps a count of what it has, a reservation takes what you reserved off that count while it is open, and the count goes back up if the reservation ends without a sale: you cancel it, the shop declines it, its time runs out, or the shop's team closes it as not collected (if the team undoes that, it is taken off again). Collecting it is a sale and leaves the count as it is. The count is the shop's own number about its things, never about you. A guest is shown it only when it is five or fewer ("Only 3 left") or none ("Out of stock"), or when a reservation asks for more than there are: the quantity is then lowered to what is left, and the app says how many that is. While you are at the shop, your phone or browser is sent the exact number without showing it, so that the reservation you are building can stop at it; before you enter, what anyone can read carries a number only when it is five or fewer. So that exactly what was taken goes back, our server keeps a note of it, with the reservation's identifier and its conversation's and no name or account, until the reservation ends (two hours at most), and for six hours more if it ended by running out of time or as not collected, so that an undo can take it off again (section 6). Before you reserve, the app tells you how long the shop keeps it for you: the time the shop set, two hours at most (two hours until the shop sets one); on the reservation it says until when. You can cancel it until you have collected it, also once the shop has started getting it ready. If nobody has collected it when its time is up, it ends by itself: our server closes it at your phone's next check-in, or within 15 minutes at the latest (once you have told the team you are at the counter, it waits for them until two hours after you reserved, then ends the same way); you are sent one notification that it has ended, as for the other steps of an order, the shop's team is shown that its time ran out (on its list, and as one quiet line in your conversation with it: when, and how many items, never which; nobody is alerted), and it no longer keeps your visit (section 6). A reservation that ends this way is not counted against you as not collected (the point after next). The place keeps its own record of each order for its books — items (with the choices made on each), prices, total, table (at a hotel, or for an order brought to a room, the room number), times and how it ended — with no name, photo, note or account attached. How it ended can be: picked up (also when you said you had it as you ended your visit), declined, cancelled, closed by the team as not collected, ended by itself when a reservation's time ran out, or not closed by anyone.
- At a place that sends its orders to its own Clover till. At a place whose till is Clover and that has turned on "Send orders to Clover", the order you place there (in the app, at a table with its code or anywhere inside; at a hotel, a request from your browser too) is also sent to that place's own Clover account, so that its team has it on its own till: what you ordered, the choices on each item (a size or a milk, for example), your note, the first name you use for that visit (such as "Sam" or "Guest 427"), your table or "Counter", and a number for the day (for example "Wassaaa 12 · Sam · Table 4"); nothing else about you is sent. We send no account, photo, phone number, email address or location, and no customer record is made in Clover. An order marked "Confirm at the counter first" is sent only when the team starts making it. Clover is the place's own service, chosen by the place: what its Clover account keeps of your order is under the place's care and Clover's own terms and privacy policy, not ours. If the team declines your order while it is still open and unpaid in Clover, our server deletes it there. You pay for it in the app, as for any order (above); it reaches Clover marked as paid in Wassaaa, with its amount, so that the team does not take payment for it again, and Wassaaa never takes, sees or refunds a payment through Clover. What we keep of an order sent to Clover, and for how long, is in section 6.
- Paying for an order in the app. Every order you send in the app, and every reservation at a shop, is paid in the app when you send it, with Apple Pay, Google Pay (with the cards in your Google Wallet) or a card; there is no paying at the counter for it. A place that takes no payments in the app yet shows its menu, and its orders are taken at the counter; a request at a hotel is free; a page in a browser shows the menu and points you to the app. Who you pay: the place, which is the seller, on its own account with its payment company, Stripe or, where the place chose "Square, your till", Square; the payment company is the place's, Wassaaa receives no money and takes no fee. The Stripe platform used for the places' payments is run by Sigmaton's sole proprietorship in Alameda, California (the owner's US business), for the places' payments only; Sigmaton LLC remains the "we" of this policy for everything else. At a place that chose Square: you pay in Square's own sheet, a card typed into Square's own field or Apple Pay or Google Pay through Square, and the money goes to the place's own Square account. Our server sends Square the order (the items and their prices, the tax, the tip you chose, the first name you use for this visit, the table and your note) and the payment's amount, with a single-use token that Square's sheet gives; Square keeps its fee if the place gives money back. Your card: you give it to Stripe (or to Square, at a place that chose Square), in its own sheet or through Apple's or Google's wallet, under its privacy policy and, for a wallet, Apple's or Google's; Wassaaa never receives or keeps your card number, its last four digits, its expiry date, the name on it or an email, and keeps no card for next time. The place sees the payment in its own Stripe or Square account, as that company shows a seller. What our server does: when you send the order it asks the payment company to hold the total it works out itself (the menu's prices, the place's tax, the tip you chose), and the order goes to the team only once the company says that amount is held; it asks it to take the money when the team starts your order (or marks it ready or picked up), to let the hold go if the team can't make it, you cancel, or the order is never started, and, at the place's call, to give some or all of it back. Since November 19, 2026, if someone on the team who is not an owner or a manager says they can't make your order after it was started, your refund waits for an owner's or a manager's OK, and your order says so; the payment's record keeps who asked and who answered, as one-way codes of their accounts, for as long as the record. What we keep: with your order, and in the place's books (which never name you), how it was paid (Apple Pay, Google Pay or card; cash for an order taken at the counter), the amount, the tax and the tip, whether the money is held, taken, let go or refunded, and the payment company's identifier for the payment, for 90 days as the books are; a payment held for an order that was never sent is let go within 30 minutes and its record kept as long. Declined cards: if a card is declined while you pay in the app, we count the declined cards for one hour under a one-way code made from your account (never the card or your account itself), to stop stolen cards being tried; at the third in an hour, every payment of yours still open is let go, and the app takes no new payment from you until the hour has passed. The count is used for an hour and deleted within 25 hours of the first card declined in that hour, and at once when you erase your account. While a payment is open (up to 30 minutes), its record carries that code; it is removed when the order is sent or the payment is let go. Disputes: if you dispute a payment for an order with your bank (a chargeback), the place's payment company tells us, and the app stops taking payments from your account, at every place, until the place wins the dispute or our support lifts the stop; any payment of yours still open is let go. When you try to pay, the app says so and gives the address to write to if you think it is a mistake. The place's owners are told that a payment was disputed, its amount and what was ordered, never who you are. To do this, each payment's record keeps a second one-way code made from your account (never the account itself) for as long as the record is kept (90 days), and a dispute writes a line under that code: for each dispute, whether it is open, lost, won or lifted, when we heard of it, the place and the payment company, never your card, the bank's reason or the amount; and a note from the dispute's own identifier to that code, so that a dispute decided after the payment's record has gone can still lift the stop, kept as long as the dispute is on the line. A dispute won goes from the line a week after; one our support lifted, 180 days after; one that is open or lost stays until then; the whole line is erased at once when you erase your account. A payment made before November 19, 2026 carries no such code: its dispute is told to the place's owners and stops nothing. When you erase your account, our server keeps only that its code was erased, and until when, for 100 days (longer than a payment's record keeps the code), so that a dispute's later word writes nothing under it; the code cannot be turned back into an account, and no account will ever have it again. If the payment was made on a phone that keeps the app's random code (the phone's code, above), its record also keeps a one-way code made from the phone's code, as long as the record, and the dispute writes the same line under that code too: every account on the phone is stopped until the dispute is won or our support lifts the stop (lifting it for an account on the phone lifts it for the phone), and at most 180 days after the dispute's newest word; erasing your account leaves the phone's line, and the note from the dispute keeps the phone's code and forgets your account's. Your bank's check: when you pay by card, typed in or in a wallet, the payment company may ask your bank to check that it is you (3-D Secure), in its own sheet; the check is between you, your bank and the payment company, and we keep only that it was asked. To stop card testing, we count how many payments a place starts in an hour. Each order is counted once, by a one-way code of the order, never your account; the count is deleted within about two hours. Your phone keeps on its receipt how you paid and the amount. Where the place runs Rewards, a paid order's points land when the money is taken, and a refund takes them back. A tip goes to the place in full.
- If your visit ends with an order open. If an order of yours is still open when your visit ends (you press End visit, the place's team or Wassaaa removes you, your visit reaches its end, or, in a browser, you clear the conversation), the order does not vanish from the team's screens. Our server keeps a card of it where only that place's team can read it: what you ordered, the total, the note you wrote on it, the table or the counter it was for (or, at a hotel or for an order brought to a room, the room number), the name you went by for the visit, how far the order had got, how the visit ended and when, and when your phone was last seen inside. For a reservation at a shop it also says until when it was kept for you; for a request at a hotel, or an order brought to a room, it says nothing about your phone, not even when it was last seen. Your conversation with the team, your messages and your photo still go with the visit, and nothing on the card lets the team write to you. The card stays until someone on the team closes it (as picked up, or as not collected), and for up to four hours after your visit ended; one the team closed as not collected while you were still there stays for up to four hours after it closed it. An order you cancel, or say you have collected, as you end the visit leaves the same card, marked so, for the same time. Beside the card, where no phone and no place's team can read it, our server keeps which account it was for, for three things only: to count it if the team closes it as not collected (the next point), to show the team that you are back inside if you walk straight back in, and to reach the card if you erase everything about you. It goes with the card. What the team is told while an order of yours is open: when your phone was last seen inside the place, as a time, and never where you are; when you press End visit with an order that is already being made or is ready, the team's phones and its staff console are alerted that you ended your visit; and when your phone is seen outside the place, they are alerted too, and the order says that you are back inside if you return. At a hotel, for a request, the front desk is told none of this about your phone: not when it was last seen, not that it was seen outside and not that you are back inside; it is alerted only when you press End visit with a request it is already on or that is ready. The same is true of an order you asked to have brought to your room from a place inside a hotel: that place's team is told none of this about your phone, and is alerted only when you press End visit with that order already being made or ready. Your phone counts as seen outside only when there is no doubt: the app steps out by itself as you walk away with it open, a check of your location finds you clearly beyond the place's edge (one check near the edge is never enough), two checks in a row find you outside, or you are let into another place (the team is not told which). The team is never told where you are or went, how far away or in which direction: "outside" is the only word it is given about where you are. A phone that is locked in a pocket is not checked, because the app does not read your location in the background: the team then sees only the time your phone was last seen, and nothing calls that leaving. So that it can tell the team these things, our server keeps a note of an open order of yours under your account at that place (which order, which visit and conversation, and when and how often a check found you outside), where no phone and no team can read it; it goes when the order is closed or the visit ends. Before you end a visit with an order open, this version of the app says what will happen to the order: one that has not been started yet can be cancelled in the same step, and for one that is ready the app asks whether you got it, and a yes closes it as picked up, on your word, with no alert. An erase (section 13) takes your name and your note off such a card at once, and the account beside it; the card's items stay until it is closed or its hours run out.
- An order the team closes as not collected. If a place's team closes an order of yours as not collected (it was made, and nobody came for it), you are sent one notification that says so, whatever your notification settings say: like the steps of an open order, neither "From the place you're at" nor "Pause notifications" holds it (an older version of the app, open on screen at that moment, may still hold it by them); if the team undoes it, nothing more is sent. For a request at a hotel, and for an order brought to a room, the team's step reads "Couldn't hand it over" (nobody answered at the room, for example): it is the same step, and it is counted in the same way. So that ordering and walking away cannot become a habit, Wassaaa keeps a count of the orders that teams have closed that way for your account: a line for each, holding the time and nothing else (not the place and not the order), kept for 30 days. Only a "Not collected" that someone on a team tapped, and did not undo, is counted, and, since November 19, 2026, a reservation at a shop whose time ran out before you collected it (it is told to you by the reservation's own notice, with no second one; never one made from a browser, or one whose time ran out after you told the shop you were at its counter): never a phone that stopped being seen, a phone seen outside, an order you cancelled or said you had collected, an order the place declined, or one that nobody closed. While two or more lines are younger than 30 days, your next orders, at any place, arrive marked for the team to confirm at the counter first: the team is asked to start such an order once you are at the counter or once it has checked with you at your table; a request at a hotel, or an order to be brought to your room, so marked asks the team to check with you before bringing it. The app tells you so before you order, and on the order. The mark never refuses an order, and it goes by itself once fewer than two lines are younger than 30 days; you cannot clear it, and no team can set it or clear it. No team is ever shown the count, how many orders there were, when or where, or which team closed them: a team that receives a marked order sees the mark and nothing more. The count is erased with your account (section 13). Its limits: it belongs to the account, so erasing everything about you, reinstalling the app or starting again as a new guest leaves it behind; an order from a browser is never counted; and an order from a version of the app that cannot tell you about the mark is never marked.
- When an order asks you to confirm at the counter first, without that count. An order is food made for you, and a phone's location can say "inside" for the flat upstairs or the house next door. So an order also arrives marked for the team to confirm at the counter first, in the same way, when your phone is not on the place's own Wi-Fi and one of these is true: your account is new (younger than seven days, or no order of yours has yet been handed over by a team); the location this version of the app sends with the order puts you at the place's edge rather than well inside it (inside the place itself with an accuracy of 30 metres or better), even though you were let in; the place says it is upstairs or on a rooftop, where no phone's location can tell its floor from the street below; or you ordered from a browser. The place's Wi-Fi is checked at the moment you order, as it is when you enter. A place may, for a while, ask accounts new to Wassaaa that are not on its Wi-Fi to order at the counter; it also does so while several such orders are waiting. The location sent with an order is checked and dropped, never stored. So that it can tell whether your account is new, our server keeps, where no phone and no team can read it, how many of your orders a team has handed over and when the last was (a count, never where or what), and a scrambled code of the visit it was handed over in (it names no place or time and only lets a rating from that same visit count; the next handover replaces it), until you erase your data or delete your account. A place's team sees only the mark on the order, never why. A place may also draw its real shape instead of a circle; your location is then judged against that shape.
- Where in a place you can order. A place may draw, inside its circle, the part of it where its team takes orders in the app (the room itself, say, and not the plaza outside). The same location sent with an order, or when its menu opens, then also tells whether your phone is clearly outside that part, judged against how sure the reading is: if it is, the app does not take the order and says so (with a version of the app from before November 2026, the order asks you to confirm at the counter first instead). A table code you scanned at the place, or the place's own Wi-Fi, counts as being inside. Nothing more is kept: the location is checked and dropped, as above. While your phone lies still, the app may combine its last few readings into one for this, on your phone. If you have turned off precise location, a place cannot tell that you are inside it, so the app may ask you once, when you open a place, to share your precise location while you use the app.
- If a place brings orders to tables and you ask for yours to be brought to you ("Bring it to me"): the app offers it only once your order names a table (scanned from the table's code, or typed), and the order is brought to that table. No selfie is used to find you, and the staff member bringing it is shown none. (If your phone has an older version of the app, the staff member bringing such an order is still shown your selfie beside it, so they can find you, and beside no other order.) To your room: at a place inside a hotel that has switched on "Bring orders to guests' rooms", you can instead ask for your order to be brought to your room ("Bring it to my room"), with your room number, which is sent in the table's place. The team brings it to that room. Nothing is charged to the room: you pay the place, as for any order, and Wassaaa takes no payment. Such an order says nothing about where your phone is (If your visit ends with an order open, above). On iPhone, the order card on your lock screen uses a push token from Apple, stored until the order ends.
- If you ask for Wassaaa at a place ("Bring Wassaaa here"): the place's name and city, whether it is your place or you are a regular there, and your email only if you give one. It is read by the Wassaaa team and deleted after 180 days. If you said the place is yours and gave your email, we may send you one email inviting you to sign it up, with a link that stops us ever emailing you again.
- The language your phone is set to, when it is one Wassaaa speaks (English, Spanish or Arabic). The app sends it with each request so that our server can answer in your language, and keeps it beside your push token so that a notification reaches you in it. It is used for nothing else, and it goes when the push token does.
- A push token for your device and your notification switches, used only to send the notifications you allow. Your phone keeps its own copy of those switches, so the app follows them from the moment it opens, and a switch you change with no connection is sent to us when there is one. (A phone on an older version of the app keeps no copy.) With the token, your phone also says whether it answers from a notification and whether it opens a message's words now (Words on your lock screen). Pause notifications: "Pause notifications" in Settings › Notifications silences your notifications for an hour, or until 8:00 am: matches, messages, reactions, the question after a visit, what the place you're at tells you (a class's alerts too), City moments, the places you follow or asked about, and the reminders you asked for. An order you're waiting on still comes (its steps, and the team's messages in the conversation that holds it), and so does anything about your safety. While a pause runs, Wassaaa keeps the time it ends with your notification choices and sends none of those notifications before it; your phone keeps the same time, and stops following the places you follow, the reminders you asked for and your city's moments until the pause has passed: it follows them again the next time Wassaaa is open after it. "Resume" ends the pause at once. The time stops counting when it has passed, but it stays in your notification choices on our servers, where our server ignores it, until you pause again, press "Resume", or erase your data or delete your account. If you ask to be told when a place is lively, that follow is kept on your phone as a subscription with Google's messaging service, not in our database, and ends after the one alert. No such alert is ever sent for a hotel itself (At a hotel, below). A reminder you ask for on a moment that a place has planned is described under "Remind me", below.
- A face on a notification. When you and someone in a place where you have a visit have both said yes to each other (the notification goes to whichever of you said yes first; the other is sent one too only if their phone is down when the chat opens), or when someone there sends you a message (a wave in a chat that has opened is one: a waving-hand sticker), reacts to a message of yours, asks to find you there, or taps Keep in touch after you did (in versions of the app before this one, also when someone invites you to a game, waves at you, says hello or says yes to your hello), while the app is closed, the push we send through Apple's or Google's notification service carries their handle for the visit, the place's name and one more thing: the address of their small tile photo, the same picture the guests among the faces in that place already see on its list of people. Your phone fetches the picture from our storage with that address and shows it on the notification. A push never carries where anyone is, and never words that anyone but your phone can read ("Words on your lock screen", below). Besides the handle and this address, it holds only what the app needs to open the right place and chat: the random identifiers of the place, the chat and, for a hello, the sender's account (hellos are in versions of the app before this one). A phone on a version of the app that can answer from a notification or show a message's words is also told which kind of notification it is, so that it offers the right buttons (Replies from a notification, below). The notification for a match carries nobody's account: it has the other person's name for the visit, the place's name, the address of their tile photo, and which chat to open. The address works only while that person's visit lasts: when the visit ends the picture is deleted, so an address that arrives later opens nothing, and the notification shows the app's own mark instead. The picture stays on the notification until you clear it or open that chat, and the app clears its notifications when a visit ends while it is open. So that it does not fetch them again, the app keeps the small photos of the people in the place on your phone, left out of backups and sealed with a key that stays on this phone, until your visit ends and never for more than eight hours. It deletes them then, when you end the visit, when you block that person, when you sign out and when you erase your data. The larger photo you open by tapping a face is kept only while the app stays open. The app does not add the sender to your phone's contacts, suggestions or lists of conversations. A phone on an older version of the app is not sent the address. In the same way, when the other person is sent the notification that you both said yes, or when you write to someone, react to their message, ask to find them, or tap Keep in touch after they did (in versions of the app before this one, also when you invite someone to a game, wave at someone, say hello or say yes to their hello), the address of your own tile photo is sent to their phone. "Faces in notifications" in Settings › Notifications (on unless you turn it off) decides whether this phone shows a person's photo beside their name on a match, a message or a reaction. It belongs to this phone: it is kept with this phone's registration for notifications, and on the phone itself only once you have turned it off. Off, Wassaaa sends this phone the notification without the photo's address, and the notification shows the app's own mark instead.
- Words on your lock screen. A push never carries words that anyone but your phone can read. For a message in a private chat, it may carry the message still sealed, exactly as it is on our servers: your phone opens it with that chat's key, which it keeps on this phone only until the chat ends, and shows the words on the notification. Apple and Google pass on bytes they cannot read. While the app lock is on, or if you turn "Show message text" off, your phone keeps no such key where the notification can use it, and shows only that a message came; so does a long message, and one your phone cannot open. Turning the app lock on, or "Show message text" off, also takes the words off notifications already showing: on an iPhone it removes the notification of a message or of a reaction that holds them, and on Android it shows the notification again without them (and, with the app lock on, without Reply). Who is sent it: only a phone whose app said, in the same registration that says whether it shows faces, that it opens sealed words, and only while "Show message text" in Settings (on unless you turn it off) is on and the app lock is off; every other phone is sent what it was sent before. What the push holds is the message's random identifier, a number and a tag that your phone needs to open it, and the sealed words: never the sender's key or account, never the sealed message of a photo you can view only once, and nothing at all for a chat you muted. A photo, a voice message or a GIF shows as that word alone: its picture is never in the push. A wave shows as "Waved at you.": your phone works that out from the sealed message, and the push says nothing of it. Where the key is kept: for each chat that is going on, the chat's own key, which opens that chat's messages and nothing else, with the chat's place, the moment it ends, the other person's account and whether a reply may be typed in it and, so that the notification offers the right buttons, whether you are inside a place now (among the faces, or here to order). On an iPhone it is one entry in the phone's secure storage that only Wassaaa and its notification extension can read (a small part of the app that your iPhone runs to prepare a notification); it can be read while the phone is locked, once it has been unlocked since it started, and it stays on this phone and is not restored to another. On Android it is in Wassaaa's own secure storage. It is removed when the chat ends, which is when the visit does, and when you sign out, change account or erase your data; none is kept while the app lock is on, and turning "Show message text" off removes every key at once. On Android, to show a chat's last few lines together, the app keeps up to six of them, with their words, in its own secure storage on your phone, only where a key may be used, until you open the chat or the visit ends (swiping the notification away does not remove them). When a message is deleted or edited, your phone takes its words off the notification quietly, and nothing new appears. For this our server sends the phone a quiet message that names only the chat and the message, with no words and nothing to show. A phone with no signal, or an iPhone on which Wassaaa was swiped away, keeps the words until Wassaaa is next opened. Then the words of a deleted message go, and so do those of an edited one, except the first words of a message edited in a chat you can only read from outside (after you have left the place): those stay on the notification until you open that chat or it ends. Your phone's own setting for previews on the lock screen still decides whether anything is shown while it is locked.
- Replies from a notification. On a phone with a version of the app that handles it, the notification of a message, of the reply of a place's team and of a new chat can offer a button: "Reply" (type your answer in the notification itself) or, on a new chat, "Say hi" (opens the chat with the keyboard up) or "Open chat". Nothing done from a notification says yes, takes a yes back, answers a place's question, claims a prize, closes an order or says you are at the counter, and nothing done from one reads your location, renews your visit or changes whether you are shown as seen outside. A reply you type is sealed on your phone as a message in the app is (when it is to a person) and goes in the same write the app makes, without opening Wassaaa; to a place's team it goes as the team message the app sends. On an iPhone "Reply" first asks for Face ID, Touch ID or your passcode, so that someone holding your locked phone cannot answer as you. On Android Wassaaa does not ask yet: your phone's own settings decide whether a reply can be typed before you unlock it, so someone holding your locked phone may be able to answer as you. A notification that comes while the app lock is on offers no Reply and shows no words. If one was already showing when you turned the app lock on, it loses its Reply on Android, and on an iPhone a reply typed on it is not sent: your phone says "Not sent. Open Wassaaa to reply." When it is sent: at once, while the place still counts you as there, which is while your visit's check is running or, if your phone went dark inside the place, up to 30 minutes after it was last seen inside; otherwise the reply waits, kept on your phone, and a quiet notification says "Not sent yet" and where to open Wassaaa, and it goes the next time you open Wassaaa inside the place. If the chat has ended, or one of you has blocked the other, it is not sent and is kept nowhere. What your phone keeps meanwhile: the reply, sealed in the phone's own file with any message of yours that waits (section 6), left out of backups, until it is sent or refused or the visit ends; on an iPhone, the words you typed also wait in a file in the app's private storage until the app has taken them up, protected until the phone is first unlocked and left out of backups, and forgotten after twelve hours at most; and a random identifier for the reply, with no words, for thirteen hours, so that a reply handed over twice is sent once.
- Your visit on an iPhone's lock screen. While you are among the faces of a place that shows its people, an iPhone can keep one card on its lock screen and in the Dynamic Island (a Live Activity): "Your visit at Jebena Cafe" over "until 5:00 am", the moment your visit ends by itself, written as the app writes any time. The card is made and updated by the app on your phone alone: it uses no push token, nothing is sent to our servers or to Apple's push service for it, and we keep no record that it was shown. It holds the place's name and that time, never a face, a handle, a count of people or a match. Anyone who can see your lock screen can read it, so while the app lock is on the card says only "Your visit" and the time, with no place's name, and the name is not stored in the card at all. The card for an order you place follows the same rule: if the app lock is on when you place the order, its card on the lock screen and in the Dynamic Island says "Your order" and names no place; switching the lock on while an order is open applies from your next order (on Android, where an order shows as a notification, a lock turned on or off applies at the order's next step). It is not shown for a place you came into only to order, for a class or for a hotel itself, and Android shows none. It goes when you end the visit (End visit or End all), leave the people there ("Exit meet"; on an older version of the app, turning off "Meet people"), are removed, sign out or erase your data, and when your visit ends by itself. If the app cannot take it down at that moment, because your phone is asleep or Wassaaa is closed (your visit ends by itself, or a place removes you), the card stays: at your visit's own end it reads "Visit ended", and either way it is there until you next open Wassaaa, which takes it down, or iOS removes it (iOS ends a card eight hours after it began, and may leave it up to four hours more). You can stop it in your iPhone's Settings › Wassaaa › Live Activities; that changes nothing else about your visit.
- If you ask to be told when someone arrives at a place: the same kind of subscription, on your phone, ending after the one alert; the place itself is marked with the time someone asked, never who. The alert names the place, never the person who arrived, and none is sent for a guest who comes in to order, or for a hotel itself.
- City moments (Wassaaa Hour): while the switch is on in Settings › Notifications and no pause is running, your phone works out by itself which of our launch cities it is in and subscribes to that city's announcements with Google's messaging service. Your location is not sent to us for this, and we keep no list of who is in which city. At most one such notification a week per city.
- "Remind me", on a moment a place has planned. On a place's card, a guest who is not inside that place can tap "Remind me" under a moment the place has planned (a quiz night, live music). Your phone then signs itself up, with Google's messaging service, to one notification topic named by the place, the moment and the start of that day's occurrence, in the language your phone is set to. Nothing about who asked is written to our servers: no list, no count and no time, and the place is never told that anyone asked, or how many. The notification is sent once, by our 15-minute check, in the quarter hour before the moment starts, after the check has looked again at the place's plan and at whether the place may show the moment (a check that runs long can send it a few minutes after the start). For that reason "Remind me" can be asked until 15 minutes before the moment starts and not in the last quarter hour, and a reminder you asked for before then stands until the start. It carries the place's name and a line such as "Quiz night starts at 8:00 pm.", and only the identifiers the app needs to open the place: no person and no position. It is never shown to a guest who is inside the place: your phone stops waiting, and leaves the topic, when you come into that place, when the reminder has come, 30 minutes after the moment's start, when you tap Undo or turn that reminder off, and when you erase your data; if the place moves the time, your phone moves its ask to the new time, and if the place calls the moment off, the ask ends without a word. On your phone only (section 6), Wassaaa keeps each reminder you asked for until one of those things happens (the place's identifier and name, the moment's identifier and name, its start and when you asked), and your choice "Reminders you asked for" in Settings › Notifications, which is kept only while it is off: off ends every reminder and hides "Remind me". Neither is uploaded. If your phone leaves a reminder's topic, for any of the reasons above, and cannot tell that it has (for lack of a connection), it also keeps that reminder's name on the phone: the place, the moment and its start, never a person, with the time after which nothing is sent to it. It keeps that until it has left the topic or until 30 minutes after the moment's start, whichever comes first, and tries again each time Wassaaa starts and each time you come back to it; it is not uploaded. Erasing your data removes it, though an erase made with no connection can leave your phone still owing a topic, and keeping its name again, until 30 minutes after the moment's start. "Pause notifications" holds reminders as it holds the places you follow: your phone leaves their topics and joins them again after the pause. The sign-up with Google's messaging service stays until your phone leaves the topic. All that our server keeps of a reminder is a note, with no person in it, that it was sent for that moment and start, for two days, so that it is not sent twice (section 6).
- Tonight near you, and a moment on the map. A place that has planned a moment shows its name and its times as public words, like its opening hours: on its pin on the map from the middle zoom in (a small mark, and a few words with the time when you are close in), on its card on Home, at the top of its tab inside, and on the page a door code opens (section 10). "Tonight near you" on Home lists the moments that are on now or start before 4 am, at places within about 5 km of you (or of the middle of the map when your phone has no position), by start time and then distance, never by a place's plan or by how many people are there. All of it is made on your phone from the place cards the phone already holds: how far a place is is worked out there, nothing about where you are is sent for it, and no new request is made. In the evening (6 pm to 3 am by your phone's clock), when a place with people in it is within a walk, Home chooses "Live now" for you and says so once; if you clear it, your phone remembers that in one word of its own, never uploaded, and does not choose it for you again until you choose "Live now" yourself. "One more visit fills your card at…" is read from your phone's own list of cards (Regulars). Across a whole city, the map's badge says "Something's on tonight" from the times of its places' moments alone: never which place, what is on, or how many. None of this is shown for a hotel itself (a place inside a hotel may show its own), in Campus, for a place that has not joined, that is hidden from the map or asks for a code at its door, during a private event, or once the place's plan has lapsed; and a moment says nothing of who is there: no count, no names, no faces and nothing of matching.
- If you add a tagline under your name for your visit: up to 40 characters. Outside a Campus class you type the words yourself; the place suggests none. In a Campus class you pick one from a short list ("Up for a chat", "With friends", "First time here"…). Typed words are checked before anyone sees them. Our server checks them against the content policy, with the same rules as the posts on Everyone here (below), and your phone checks them first so that it can tell you at once. A phone number, a link or a social media handle is refused, and so is anything else the content policy refuses. A swear word is shown masked ("f**k") to everyone, and our servers keep it masked. Your tagline is stored with your visit, as plain text that is not end-to-end encrypted (the Wassaaa team can read it), and shown under your name to the people in the place, and it goes when the visit ends, or sooner if you leave the faces with "Exit meet" (on an older version of the app, by turning "Meet people" off). You can change it or have none. On an older version of the app, a tagline you typed is not shown. In a Campus class you can only pick a tagline from the list; you cannot type one. On your phone only: your phone remembers the last tagline you used, typed or picked, so that the box starts with it on your next visit. That copy is kept on this phone alone and is never uploaded; it is cleared when you sign out, start as a new guest or erase your data, and it goes if you delete the app.
- At a big place that has split its list into sections (a festival's stages, a conference's halls): which part of the place you are in, from the short list the organiser set. Your visit starts in the first one and you move yourself with one tap; we do not work it out from your location. It is stored with your visit, it decides whose list you are on and whose you see, so the people in that part of the place can see you are there, and it goes when the visit ends, or sooner if you leave the faces with "Exit meet" (on an older version of the app, by turning "Meet people" off). The place's team sees none of it.
- Meeting people, or here to order. Coming in is one tap: at every place but a Campus class, Enter lets you in with no camera and no selfie. You then have every tab of the place; Meet shows you only how many are here and a button, "Take a selfie", which opens the camera, and "Everyone here", where the place has it, shows you only what the place itself puts there (its question, its deal, what is on, and the posts its team writes there as the place, with the one it pinned) above the same button. (At a hotel itself there is no selfie and no Meet tab: At a hotel, below.) If you take the selfie you are among the faces: the other guests there who took one see your photo and your name for the visit, and you see theirs. What this policy says about the people in a place, the place's list, saying yes, private chats, the shared wall and a table's conversation is about the guests among the faces; a place's own question is for everyone inside, with a selfie or without. On an older version of the app the selfie is still asked for as you enter: "Meet people" is a switch in its Settings, on unless you turn it off and the same at every place; with it on, the app asks you for a selfie as you enter a place, and the camera has a button, "Not this time" (so have the page that first asks you to agree to the selfie check and your pass when it first appears); with it off, or after "Not this time", you are here to order, as described next. The oldest versions have neither the switch nor "Not this time": every visit they make begins with a selfie. With no selfie, you are here to order. No name is asked. You are shown to no other guest and you see none: you are on no list; Meet and "Everyone here" show you none of the people there and none of the guests' posts on the wall, only the place's own (an older version of the app, where Meet is called People, gives you no People tab at all); and you have no table's conversation and no chat with another guest. That is not only what the screen leaves out: our server gives your phone none of it. What you have is the place's menu and ordering, your conversation with its team, its information, its own question when there is one, what its team posts on "Everyone here", your card (Regulars) and its stars. (On its screens the app calls this "with no selfie", and speaks of ordering only where it knows that the place takes orders in the app; at a shop it speaks of shopping and reserving instead, as in "Just shopping this time", and at a hotel of asking for something.) There is nothing to turn down in advance: Meet and "Everyone here" offer the selfie on every visit. In a few cases the camera still opens on the way in (when "Back in as …" finds that your earlier selfie can no longer be used, say), and it then has "Not this time" too. When your visit's eight hours are up while you are still inside, no camera opens: you enter again for a new visit, with no selfie. "Not this time" is for that one entry, and nothing of the tap is kept beyond the visit (on an older version of the app, the next time you tap Enter at a place it asks again, at the same place too, where a selfie then joins the faces in the visit you already have there). Until a visit with no selfie ends, our servers keep it as a visit to order, and your phone's pass for that place says the same (section 6). (That it was tapped is one of the steps counted without identity, described below.) How you are checked: the same either way. Your phone's location must show that you are inside the place when you come in, and again while the app is open there: about every four minutes when you are here to order, about once a minute in a visit with a selfie, or about every three minutes in one while your phone lies still (our server sets that pace, between one and ten minutes; a Campus class stays at once a minute); the second point of this section says what is sent for that, and what is not kept. Counted: either way you are one of the number of people the place shows ("12 here"): a number, never who (a hotel itself shows that number to nobody but its own team: At a hotel, below). You are counted from when you come in until 30 minutes after your phone last showed it was inside, in one place at a time. You stop being counted at once when you end the visit, when your phone is found outside, and when it shows you inside another place; otherwise the place's number is put right within about 15 minutes after those 30. So that a script cannot run a place's number up, our server counts, under your account, how many new visits you begin in an hour, with a selfie or without (20 at most; one more is refused until that hour is over) and how many times in an hour you change the place you are counted in, with a selfie or without (twelve at most; past that, entering another place, or coming back into one you had left for another, is refused until that hour is over, or until you end your visit at the place you are counted in; stepping out of a place and back into it is not a change). An hour is an hour by the clock (from 9:00 to 10:00, say); both counts are deleted once their hour has ended, within a day at most. To keep you counted in one place at a time, and among the faces of one place at a time, our server also keeps two notes under your account: the place you are counted in, and the place whose list of faces you are on, each with the visit and the time your phone's check put you there. No phone and no place's team can read them; each goes when that visit ends, when you erase your data, and when the last visit in that place ends, and the second also when you leave the faces. So that two requests from your account that change what you are at a place (coming in, joining or leaving the faces, ending a visit) are answered one after the other (one that would have to wait more than a few seconds is refused, having changed nothing, and is sent again by your phone or by your next tap), our server keeps one more note under your account while such a request, or its own clean-up of a visit of yours, is at work: a random identifier of that work and the moment it stops counting, thirty seconds on at most, and nothing about you or the place. No phone and no place's team can read it; it is deleted as soon as the work is done, and one left by work that was cut short goes the next time such work is done for your account, with our clean-up once a minute has passed since it stopped counting (the clean-up runs every 15 minutes), or when you erase your data. With a visit among the faces (from this version of the app) our server also keeps the random identifier of the entry that put it there, so that the same entry sent again after its answer was lost is answered as it was the first time; it goes when the visit ends. And so that a request of yours that arrives late does not undo what you did after it, each request that changes what you are at a place (from this version of the app) carries the moment it was asked for, by your phone's own clock, and our server keeps, under your account and for each place, the latest such moment it has acted on there and when it did: two moments, and nothing of what the request was. A request that carries an earlier moment than that changes nothing. No phone and no place's team can read them; they are kept while your visit at that place lasts and, where no visit of yours stands there, for 20 minutes after they were written, then deleted by the next clean-up, and they go when you erase your data. Your phone, for its part, keeps the moment it gave its last such request (one number, in the app's ordinary storage: signing out or signing in to another account leaves it as it is, and erasing your data clears it), so that a new request never carries an earlier moment than the one before it, even if the phone's clock has been set back. What is kept when you are here to order: a visit with no photo. Our server keeps, under your account's random identifier, a random identifier for the visit; an automatic name, such as "Guest 427", which is the name the place's team reads on a conversation or an order of yours; your table, if a table's code or link brought you in or you named one; that your phone's location was checked; your conversation with the place's team and an order in it; your answer to a place's question, if you give one (below); and times: when you came in, when your phone last showed it was inside, and when the visit ends. It is a visit like any other, on the same clock: it ends eight hours after you came in at the latest, and sooner when you press End visit (section 6 says the rest), and everything this policy says of a visit is true of it except what needs a selfie. Changing during a visit: if you are here to order, you can join the faces at any time in the same visit with "Take a selfie" in Meet or "Everyone here", which opens the camera (on an older version of the app, with "Meet people" on, from the line "Want to meet people here? Take a selfie" on the place's own screen). The visit goes on with the same end, and the name on your pass (the automatic one unless you type another) is your name for the visit from then on. While you are among the faces you can change that name on your card ("Your card here": the pencil on your bar at the foot of the place), up to ten times in one visit: the new name takes the old one's place at once wherever the people there see you (on Meet, on your card, on your posts on the shared wall, at your table, in hellos you sent that are still waiting and at the top of your private chats), as a new photo does, and nobody is told. It is checked as a name on a pass is, and it goes with the visit like the first. A conversation with the place's team keeps the name it began with (below). In a Campus class, or on an older version of the app, the name stays as it was given at the door. If you are among the faces and tap "Exit meet", at the end of your own bar at the foot of Meet, and then "Exit", you leave the faces of that place at once (on an older version of the app, "Leave the people here", under the faces, and then "Leave"; on a still older one, turning "Meet people" off does this): you come off the place's list; your selfie and its smaller copy are deleted from our servers, and the app takes back the copy it had uploaded (section 2 says how); your posts on the shared wall, your seat at a table with what you wrote there are deleted; and every yes you said that had not been matched is taken back. Your answers to the place's questions, and an entry in a draw, stay: you have still answered, and each question is answered once. Your phone does its part at once: from that moment it treats you as here to order at that place, and Meet and "Everyone here" offer the selfie again (on an older version of the app the switch is off at once, and the app never turns it back on by itself). Our servers are told at once when your phone can reach them. When it cannot, the app keeps a note (described below), says so ("Your selfie at Jebena will be deleted as soon as this phone is online."), and asks again by itself until they have answered: when its connection is back, when it is opened or comes back to the front, at least every five minutes while it is open, and before you enter a place or sign out. Until our servers have been told, nothing of the above has happened there for that place: that selfie stays with them, and the other guests in that place can still be shown you as they are shown someone whose phone has gone quiet (section 6); all of it goes when that visit ends at the latest. A copy of your small photo that another guest's phone had already fetched stays on that phone, as "A face on a notification" describes. You are here to order from then on, under the same name: you stay counted, and your conversation with the place's team and any order in it go on as they were. Your private chats stay until the visit ends, to read: you can no longer write in them, you can still open a photo or a voice note in them (a view-once photo excepted), and the other person can still write, which reaches you as a notification. What our servers still keep of that visit so that those chats can be read no longer says your name, your tagline for the visit or your section: the name stays in the chats you already have, and with your conversation with the place's team. The other places of the same night: "Exit meet" is for that place only. A visit of yours with a selfie still kept at another place (section 6 says what a kept visit is) keeps its selfie until that visit ends. On an older version of the app, turning the switch off does the same at every other place where a visit of yours with a selfie is still kept: that selfie is deleted too, and you stop being among the faces there, in the same way: at once where your phone can reach our servers for that place, and otherwise as just described, with that selfie on our servers until they have been told, and at the latest until that visit ends. The same is asked of a place your phone had asked to let you in among the faces and had not heard back from (its note is described below). One case keeps a selfie while you are here to order: if you go back into a place where a visit of yours with a selfie is kept and, on its card, tap "Order only this time" in place of "Back in as …" (the button reads "No selfie this time" where the app does not know that the place takes orders), you leave the faces there as described above except for two things, which stay with that visit: the selfie, with your name, your tagline and your section, shown to nobody, so that one tap ("Meet people here again", in Meet or "Everyone here"; on an older version of the app, on the place's screen) puts you back among the faces with it; and every yes you had said, which is not taken back: it waits, as a yes waits for someone who has dropped off the place's list (the next point), and can become a match only once you are back among the faces. Both go when the visit ends (on an older version of the app, also when you turn the switch off). On an older version, turning the switch on again changes nothing by itself, and cancels nothing: a selfie that was still to be deleted is deleted all the same, and the app goes on saying so until it is. What your phone keeps: no choice about meeting people, since there is no switch to keep; a choice of "Meet people" off that an older version of the app kept is forgotten the next time this version starts (an older version keeps that one choice, and only while it is off; it is cleared when you sign out, start as a new guest, or erase your data). While our servers have still to be told that you left the faces at a place, it also keeps a note of that, one for each such place: the place's identifier and name; the visit's identifier, where your phone has it, and its end; which account asked; and when you asked, by your phone's own clock, which is sent with the request so that it takes nothing off a visit you put back among the faces after that moment. The note goes when they have answered, when that visit's end has passed, and when you sign out, sign in to another account or erase your data. It is written before the place is asked: when you leave the faces there with "Exit meet", when you tap "Not this time" at a place where our servers may still have you among the faces, and, on an older version of the app, for each place when you turn the switch off. Before you sign out or sign in to another account, the app tries once more, for a few seconds, to tell our servers what it still owes them (this, and an End visit they have not heard of: section 6); what cannot be told by then is forgotten with the account, and that selfie stays on our servers until its visit ends. Your phone also keeps a note of each entry among the faces, one for each place, from the moment it asks a place to let you in (or, where it no longer had that note, from the moment our servers tell it that such an entry went through) until our servers have said what your visit there is: the place's identifier and name; a random identifier of the entry itself, so that trying again sends the same entry, which our servers answer with the visit it began, while that visit lasts, and not with a second one; your account's identifier; when it was asked for, which is the moment the request carries, and when it was sent, both by your phone's own clock; the name it asked with and where the copy of its selfie your phone uploaded is, so that trying again sends the same name and selfie (neither is kept for an entry that carries a kept visit on, and both go from the note when you end your visit there); the end of your visit there, where your phone already knew one; and whether you have ended your visit there since, and when. It is there so that an entry whose answer never reached your phone (the app was closed, the connection went) does not leave you among the faces, with a selfie on our servers, with nothing on your phone to undo it: the app asks our servers nothing only to find out, and what you do next settles it, by the place alone and whatever visit stands there. "Not this time" at that place (or, on an older version of the app, turning "Meet people" off) asks that place to take you off its faces; End visit there asks it to end any visit of yours it has; and if you were already in that place with no selfie, your phone's next check of your visit there tells it that the entry went through (you are then among the faces, and "Exit meet" takes you off them; on an older version, with the switch off, you are taken off them). That note goes when our servers have answered the entry or one of those requests (an answer that is only about your phone, such as where it is, settles nothing for a note that was already there; a refusal does remove the note of the very entry it refuses, which began nothing), when that visit's end has passed, ten hours after it was sent at the latest, and when you sign out, sign in to another account or erase your data. One limit: when the answer to an entry among the faces is lost and you were not already in that place, the visit it began is not shown on your phone, though the other guests there can be shown you as they are shown someone whose phone has gone quiet (section 6), until you tap Enter there again (which carries that visit on), the visit ends, with its selfie, at its own end, or, on an older version of the app, you turn the switch off; and an entry that reaches our servers only after they have answered one of those requests is not undone by that answer, and stays until you next come into that place or the visit ends. Not in a class: a Campus class always asks for your name and a selfie at the door, and has no "Not this time" and no "Exit meet" (on an older version of the app, the switch does nothing there).
- First-visit tips. In your first visit among the faces of a place, the app can show up to three short tips, each once: on the place's own tab, on "Everyone here" and over your visit bar. A tip goes when you tap "Got it" or do the thing it names, and nothing times one out. To show each only once, your phone keeps, on the phone only, which of the three you have put away and the identifier of the visit they began in; it is not tied to your account and not sent to us. A tip you did not meet in that visit is not shown in a later one: as soon as your phone is in another visit, even one entered while the first is kept, it marks all three as put away and drops the identifier, and keeps only which of the three are put away. Signing out leaves the list as it is; "Erase everything about me" removes it, and the app then shows the tips again in your next first visit. Settings › Your data › What Wassaaa has about you lists it, as "First-visit tips", while your phone keeps anything.
- At a hotel. At a hotel, Wassaaa shows nobody and counts nobody in public: no number, no word like "Busy", no glow on the map, no alert that it is lively. The hotel's own team sees its own counts, never who. The bars, restaurants and other places inside a hotel are places of their own and show theirs. At the hotel itself there is nothing of the faces: no selfie, as you come in or later (a phone on an older version of the app may still take one as you come in: below); no list of the people there and no Meet tab; no shared wall, no table's conversation, no matching and no place's own question; and nobody is told when someone arrives there. It plans and shows no moment (Tonight near you, above), and no screen for a TV is made for it. You come in as here to order (the point above): you can message the front desk, ask for something and read the hotel's Guide, and you are counted for the hotel's own team and shown to no other guest. Your visit lasts as at any place: eight hours at most from when you came in (section 6). A place inside a hotel (a bar or a restaurant in it, say) is linked to the hotel only when both places have agreed (section 8), never because of an address or open data. Its card says "Inside" with the hotel's name; the hotel's card lists it under "Inside", with its own word for how lively it is; and on the map it can be folded under the hotel's pin, which then shows a small dot while a place inside is lit up, never a number. While you have a visit at a place inside a hotel, you can message the hotel's front desk and ask it for something without leaving: you stay counted at the place you are in, and our server keeps a visit of yours at the hotel beside it, on the same clock as any visit; with it you are shown to no other guest, and you are counted at the hotel only for its own team, never who: as one more of its guests "here now" for up to ten minutes each time you open its front desk from there (an announcement the hotel sends to its guests here now reaches you in those minutes), and as one more visit in its figures for the day. Moving between a hotel and a place inside it is never one of the twelve changes of place in an hour (the point above). A phone on an older version of the app may still open the camera as you come into a hotel, until Wassaaa stops letting that version in; from this version on, no selfie is asked there. With the oldest versions you go in with the selfie, but you are put on no list of the people there and the app shows you to nobody there, and the selfie goes when the visit ends, as any does (until Wassaaa stops letting the very oldest version in, a phone on it that is there at the same time may still show you, as it may anyone else who came in with an older version). With a later one, the app says that guests aren't shown to each other at this hotel, and "Not this time" lets you in without the selfie. That selfie begins no visit at the hotel, and our server leaves it where only you can read it: if you then go into a place inside the hotel, the app may use it there, and otherwise it goes as section 2 says of a selfie the door did not let you in with, within eight hours at the latest. Such a phone may also show a hotel as "Quiet": a word it draws by itself, not one our server sends.
- Saying yes, and a match. Two guests can chat with each other only after both have said yes to each other; nobody can ask anyone to chat. A yes: when you tap Yes on someone, or swipe their card to the right, your phone tells our server that your visit said yes to theirs and when, and sends a promise of the key your phone will use in the chat that would open with that person (section 6 says what that is), a number that says which sealed messages your phone can open, and which visit of theirs your phone was shown: our server only compares that with the visit they have, and if it is not the same, treats the yes as one said to someone who has left the place (below). Your phone does not send a yes to someone whose visit it has not been shown; it asks you to try again. The record names the two visits, not your accounts. It is kept on our servers where no other phone can read it, and it is shown to nobody else: not to the other person, and not to the place's team. Your own phone can ask our server for one thing: the list of the people your visit has said yes to and not taken back (those who were on the place's list when you said yes to them, or are on it now; never someone who has left the faces since with "Exit meet" or, on an older version of the app, by turning "Meet people" off, who is shown to nobody), with the name each goes by for the visit, so that after the app was closed it still shows "You said yes" and lets you take it back. The list says nothing about anyone's answer. If the other person says yes to you too, our server finds the two together, opens a private chat between you and deletes both: that is a match. Nobody is ever told of a yes that was not returned, and nothing is sent for one. When both have said yes, the one who said yes first is sent a notification ("You and Maya both said yes. Say hi."); the one whose yes was second is looking at the app at that moment and sees it there. One case is different. A yes said to someone in the moment their phone was dropping off the place's list (section 6 says when that happens) waits, and if they had said yes too, the chat opens when they are back on the list. Then the one who said yes first is sent the notification as always, and if the phone of the one whose yes waited is down by then, they are sent the same notification too, from the other person, with that person's name for the visit and their face; if their app is open they see it there and are sent nothing. So each of you is sent at most one notification for a match, only when both of you said yes, and never for a yes that was not returned. You can take a yes back at any time until the other person has said yes too: it is deleted, and a yes that was taken back can never become a match (the limits, below, say what our server notes for that). Once both of you have said yes the chat is open, and leaving a chat is a separate step. A yes you said that has not been matched is deleted when your visit or the other person's ends, when either of you blocks or reports the other, and when you leave the faces with "Exit meet" or, on an older version of the app, by turning "Meet people" off (the point above says how; "Order only this time" takes no yes back). A yes someone else said to you is not deleted when you leave the faces: it stays with their visit like any yes nobody answered, it cannot match while you are not among the faces, it matches if you join them again in the same visit and say yes to that person (or had said yes to them before "Order only this time", which takes none back), and it is deleted when either visit ends, on a block or a report, or when they leave the faces with "Exit meet" (or turn "Meet people" off). A pass (a no) never leaves your phone: the app remembers it only so that it does not show you the same person again until you ask (at the end of "One at a time" it offers the people you passed on once more, and their card on Faces still offers Yes), sends it to nobody, and forgets it when your visit ends at the latest. Who can be matched: the guests among the faces, and nobody else. Our server keeps with your visit that it can be matched, and that goes when you tap "Exit meet" (on an older version of the app, turn "Meet people" off) or the visit ends. Only while you are on the place's list, the phones of the other guests there who can be matched too are told that you can be, so that they can show you one at a time and offer Yes and Pass on your card. When you leave the list your tagline goes (at once when your phone is found outside, when you enter another place or when you leave the faces; within about 15 minutes when your listing runs out or your phone goes quiet without saying so), and it comes back if you return. A guest who is here to order is shown to nobody, one at a time or otherwise, and can never be matched; they can still write to the place's team. What a card shows is what your face on the place's list already shows: your photo and name for the visit, your tagline, and whether you are here now. There is no profile, and nothing asks for your gender or your sexual orientation: we do not ask for either, and we do not work either out, from who you say yes to or from anything else. Limits, and your own list: a visit has no limit of yeses. So that a script cannot say yes to a whole place in a moment, our server counts your yeses in each minute, at most 10. Since November 19, 2026 it also keeps one number for your visit, how many yeses it has said: there is no limit to it, but when it passes 60 our server puts one line in our safety team's own list, so that a person can look at an account saying yes to everyone, and that is all it is used for. The line names your account and the name you went by for the visit, the place and the time, never whom your yeses went to and never the number; it is kept as a report is (section 1). Neither you nor the place nor any other guest is shown the number or the line, and the number goes with your visit. It keeps, for your visit, the list of the people you said yes to and have not taken back, each with when, which visit of theirs it was said to and the number your phone gave that tap, and whether they were on the place's list at that moment: that is how any of them can be taken back at any time, and how your phone can show them again after the app was closed. A yes you said to someone who was not on the place's list at that moment (their face was going as you tapped, or they had already left the place) has a line in your list that your phone is not shown: the next time your phone asks for its list, either the list shows it, because they are on the place's list again on the same visit, or the yes is taken back. Our server keeps at most 200 such lines for a visit; a newer one pushes the oldest out, which takes that yes back too. A yes said to someone who had already left the place is kept only as such a line (who it was said to, when and the number of the tap), and nowhere else. When your phone asks for the list, our server also keeps the number your phone gave at that moment, until your visit ends or a higher number takes its place (the notes, below, say when): a yes or a take-back sent before it that had not arrived by then is void, so the list your phone was given stays the truth. It counts how many times you have joined or left the faces in your visit: after 20, you can no longer join them in that visit, and leaving them is never refused for that count; a joining that was refused is not counted. When a yes of yours is taken back (by you; by tapping "Exit meet" or, on an older version of the app, turning "Meet people" off, which takes back every yes your visit gave; or by our server: when your phone asks for its list and the list cannot show it, when newer lines push it out, or when it finds a yes that your list no longer holds) our server notes that one was taken back from that person, until you say yes to them again or your visit ends (it keeps at most 200 such notes for a visit; beyond that the oldest go, and with them any yes or take-back your phone sent before them that has not arrived is void: the number of the last note to go takes the place of the number kept when your phone asked for its list, if it is higher), and it notes which match is being finished, until its chat is open, so that a yes that was taken back can never become a match even if a copy of it reaches our server late. Only your own phone can ask for your list; no phone can read the rest; and all of it is deleted when your visit ends. Never counted for anyone, never measured: nobody is shown how many people said yes to them. A place's team is never shown a yes or a pass, who said yes to whom or who matched, and no count of yeses is kept for a place. A place's team never sees your face. Its tools have no Meet tab: no list of the guests who are there, and none of their faces; and nothing its tools show, and nothing a team member's account can read or is sent, carries your photo or the address of it. What a team does see is the name you go by for the visit: the automatic one, such as "Guest 427", when you came in to order; the one on your pass, automatic or chosen, once you have taken a selfie in that visit, or the one you have since changed it to on your card, also after you leave the faces. It reads that name on a conversation or an order you start with the team, with your table if you gave one, on your posts on the shared wall, and beside a prize you won. At a shop, where an order is a reservation, the shop's team reads that name with the things you reserved and your note: never your account and never your face. If your visit ends with an order of yours still open, the team also reads that name on the order's card, for up to four hours after (see If your visit ends with an order open, above). A conversation keeps the name you had when it began: if you came in to order as "Guest 818" and later took a selfie as "Ana", the conversation you had begun still reads "Guest 818", a later one reads "Ana", and a team that has both can tell that they are one visit. The same holds when you change your name on your card. The limit of that promise: it is about the team's tools and accounts. A member of a place's team who is also in the place as a guest among the faces sees those faces as any guest does, and may know the name on an order from one of them. If your phone has an older version of the app, two things are still as they were, until that visit ends: a team's tools show your photo in one case, beside an order you asked to have brought to you; and our server keeps the address of your photo on the record of each conversation you start with the team, and nowhere else, where no other screen of theirs shows it but a team member's account could read it. Nothing about a yes, a pass or a match is part of the usage measurement described below. What a place's daily numbers do include, as before, is how many private chats began there (each match begins one): a number, never who. A place can switch matching off for its guests; it is never offered in a Campus class or building, or at a hotel itself; and your conversation with a place's team never needs a match. A wave in a chat: from the version of the app that has Light up, a guest can wave at the person they matched with inside the chat. It is a waving-hand sticker, a message like any other, sealed like the rest (see A face on a notification and Words on your lock screen). Versions of the app before this one have waves and hellos instead. When you wave at someone or say hello: the wave, or the words you write (up to 160 characters), with your handle and photo, sent to that person only. Words you write are checked by our server against the content policy before they are sent. A hello is deleted when it is answered, when either visit ends, or after 15 minutes; the notification it brings never shows your words. So that nobody can send hello after hello, our server counts the hellos you send one person in a minute, at most five, and notes who has said hello to whom in the place; no other guest's phone can read either. The count and the notes are deleted when your visit or the other person's ends, and anything left of them when the last visit in that place ends. A hello from an older version is not delivered to a phone on this version: the sender is told to update the app, and the other person is told nothing.
- If you post on Everyone here, a place's shared wall: your words (up to 140 characters, no links), with your handle and photo for that visit. Posts are seen by the guests among the faces in the place and by the place's team, and by nobody outside it; a guest who is here to order sees none of them and cannot post. The place's team can post on the wall too, as the place: those posts, and the one it pins, are seen by every guest inside, with a selfie or without, and carry no guest's name, photo or account. Unlike private chats, posts are not end-to-end encrypted: they are checked automatically by our server against the content policy before they go up, and the Wassaaa team can read them. A post is deleted four hours after you wrote it, or when your visit ends if that comes first, and you can take it back yourself at any time. Your posts also go at once if you leave the faces during the visit. Walking out does not end a visit (section 6 says what does), so a post can stay up for the rest of its four hours after you have walked out. A reaction you leave on a post is kept on the post as a number; that it was yours is kept only with your visit and goes with it. Replies and mentions (since October 30, 2026): a post can answer another post, and then carries the name and the first words of the post it answers, which go from it the moment that post goes; and a post can name up to three people in the place with "@", and then carries who it names, by their account's random identifier, with the name each goes by for that visit (the place's team is never given either). Nobody can name someone they blocked or who blocked them. The person a post names, and the author of the post it answers, get a notification with the post's words, its author's handle and photo for the visit and the place's name, under the "Messages" switch and held by Pause; nothing else on the wall brings a notification. Swear words in a post are shown masked to everyone ("f**k"), on the wall, at tables and in those notifications; the words as written are kept on the post beside them, for the post's life, so that a guest who turned "Hide strong language" off in the app's Settings sees them. That setting is kept only on your phone, never on our servers. If someone reports a post, the report carries its words, like any report, and if three different people report it, it is taken down. If a place's team takes a post down, its words, the reason and your account are kept in the record of what the team did, for 180 days, so we can check that teams use this fairly. Tags and menu items. The tags in a post (words that begin with “#”) and the menu items it names are counted for the place: how many posts, how many replies, how many different guests and in which hours of the day, never who. A tag stays in the place’s counts only when 3 or more different guests used it that day; otherwise it is deleted, with its counts, when the place’s day ends. Until then our server keeps a one-way code of your visit, so that you count once; no phone and no place’s team can read it. A tag that stays is kept with the place’s other counts (400 days) and is seen by the place’s team, in its Insights and in the brief and email described in Insights, and the Monday email, and by Wassaaa’s own operators, as a crowd’s word and never with who wrote it; the place’s team can hide a tag from its Insights. A post you take back, or that is taken down, is taken off the counts. The posts of a place’s team add no tags. A place may switch its wall off, and there is no shared wall in Campus or at a hotel itself.
- If you join Your table, the conversation for the people at one table: joining is your choice (scanning a table's code only offers it), and you can leave it with one tap. We keep your seat at that table with your visit, and the words you write there (up to 140 characters, no links) with your handle. They are seen by the people who joined the same table, up to twelve, who also see each other's handles; not by other tables, the rest of the place or the place's team. Like the shared wall, a table's conversation is not end-to-end encrypted: every line is checked automatically by our server against the content policy, and the Wassaaa team can read it. What you wrote is deleted when your visit ends or when you leave the table's conversation, and the conversation itself goes with the last person in it. Walking out of the place does not end a visit (section 6 says what does): your seat and your lines stay until one of those two. Leaving the faces takes you out of the table's conversation too. Nobody is seated with someone they blocked. If someone at the table reports a line, the report carries its words, like any report, and if two different people report it, it is taken down. It never brings a notification. Swear words are shown masked, as on the shared wall, with the words as written kept on the line for those who turned "Hide strong language" off. There are no tables in Campus or at a hotel itself.
- If you answer a place's own question, one its team asks everyone inside (two to four answers; sometimes a right answer, a closing time or a prize): you can answer from the app with a selfie or without, with one tap, and once. Our server keeps your answer with your visit where only your own phone can read it, so that your phone shows what you picked; it goes when your visit ends, or with the question if that is sooner. So that each person answers once, our server also notes that your account answered, never which answer, where no phone and no place's team can read it, until the question is taken off or cleared (below), or you erase your data: ending your visit and coming back in, or joining or leaving the faces, does not let you answer it again. Everyone, the place's team included, sees numbers only: how the answers split and how many people answered; nobody is shown who answered what. If the place marked a right answer, everyone is shown it when the question closes, never before. When the place asks its question, everyone it counts as there (as described above), among the faces or here to order, is sent one notification with the question, and the prize if there is one, once for each question (for a phone on an older version of the app, see the end of this point); it is not the place's announcement, and "From the place you're at" in the app's notification settings turns it off. With a prize: answering is your entry in the draw, which is free and tied to nothing: no purchase, no order, no rating, no share. Our server keeps your entry with your visit, where no phone can read it; it goes when your visit ends, so ending your visit takes you out of the draw, and coming back in does not put you back in, since your account has answered. When the question closes, our server picks one winner at random from those who answered and are still counted in the place at that moment, other than the place's own team and Sigmaton's own people. So that Sigmaton's own people are never drawn in a place's prize draw, we keep a note of each account that has signed in to our operators' portal, with a one-way code of its email address (never the address); it goes within a day of someone no longer being an operator, and with the account if it is erased. The winner is told on their own phone; the place's team is given only the name the winner goes by for the visit, so that it can hand over the prize, and our server keeps the winner's account and that name with the question. Every draw is sponsored by us, Sigmaton LLC, and the place provides the prize, with its stated value, which is kept with the question; the official rules say the rest. If the winner does not come forward, the team can draw again once the winner has left, or fifteen minutes after the draw (a winner the team removed from the place counts as still there until then), five draws at most; a new draw takes the win off the earlier winner's phone. If nobody answered, there is no draw; if nobody who answered is still there, nobody wins. The question itself, with its numbers and the winner's name, is cleared by our clean-up once 30 minutes have passed since it closed, or since its last draw if that is later, or three hours since it was last touched, and at once when the place takes it off; one with no closing time is closed by our clean-up once it has run three hours. The place learns how many questions it asked and how many guests answered, never who. A phone on an older version of the app shows a place's own question as a poll on Everyone here, and only where the place has its shared wall on, with no prize, no closing time and no right answer: its answer counts in the numbers and is not in the draw, and our server keeps it with the visit so that the card shows it. Its notification of the question never names the prize; where the place's shared wall is off, it shows no place's own question and is sent no notification of it. Questions are answered in the app, not from a browser page, and there are none in Campus or at a hotel itself.
- If you tell us something is wrong with a place that has not joined (a wrong name, closed, not a public place): the reason and any note you add. It does not carry your name or account; your account is used only to count five such notes a day, as a one-way code deleted when the day ends. The note is read by the Wassaaa team and deleted 180 days after it is handled.
- If you are a place's owner or manager and add its Wi-Fi in the staff console: that network's public internet address, until you remove it, or 120 days after it was last added or last used to let a guest in.
- If you are on a place's team: how you sign in, and how someone is added. An emailed code. Once Wassaaa switches its email on, "Email me a code", in staff mode or in Wassaaa Team, makes our server send the address you typed one email with a 6-digit code, but only if that address is on a place's team, has an invitation waiting, or was told by a join code that is still live to sign in first (below); it answers every address the same, so it tells nobody who is on a team. The email is an account message, not marketing, and it is delivered by Resend, our email delivery service (section 5). The code works once, for ten minutes, and five wrong tries end it; a new code replaces the old one. We keep it only as a salted one-way digest, filed under a one-way code of the address, with when it was made, when it runs out, its wrong tries and whether Wassaaa Team or staff mode asked for it. If the email cannot be sent, we send the sign-in link below instead. Typing the right code proves that you hold the inbox, as opening a link does, and we keep the same proof for 30 days, for the same single purpose; a person removed from the team is refused. Until Wassaaa switches its email on, Wassaaa Team and staff mode sign you in by the emailed link. An emailed link. "Email me a sign-in link", in the staff console, in staff mode or in Wassaaa Team, makes our server send the address you typed one sign-in email, but only if that address is on a place's team, has an invitation waiting, or was told by a join code that is still live to sign in first (below); it answers every address the same, so it tells nobody who is on a team. Once Wassaaa switches its email on, the email is in our own words and in your language, and it is delivered by Resend, our email delivery service (section 5); until then, or if ours cannot be sent, it is Firebase's own, and Google sends it. Either way it is an account message, not marketing. The link carries a one-time secret that only that inbox sees. We keep the secret only as a one-way code, with the address the link was sent to, what it is for and the place and page it opens (and, if that address's account was never confirmed, the identifier of that account), until it runs out (one hour; an invitation's, 30 days). A sign-in link works once, and once it is opened we also note which account opened it. Opening it proves that you hold the inbox: we keep that proof, your account's identifier, the address and the time, for 30 days. It is what lets an invitation sent to that address join you to a team: an invitation is joined only that way, with that address's own Google sign-in, or by signing in to an account that we made for that address ourselves, never with a password alone on an account someone else made. If someone else had registered that address first and it was never confirmed, their password and any other sign-in on it end the moment the real owner of the inbox proves it with a link or a code that can join them to a team: an invitation's own link, or any sign-in link or emailed code while an invitation for that address is waiting. A link or a code that can join nothing ends nothing: the account of someone already on a team, a guest's own account and an account a join code made keep their password and their phones when the address's owner opens a sign-in link of their own or types an emailed code. That is never done to an account that we, or the Wassaaa team in the Admin Portal, made for the address (an invitation's, or one set up with a password handed over): its holder keeps their password and their phones. It is done to an account that a join code made, for as long as its address is unconfirmed (below). In person. An owner or a manager can show a code of eight characters, with its QR, on their own screen for ten minutes. The new team member types it or scans it on their own phone, gives their first name and their email address, and joins at once; those two are kept on their new team account and team row, with the role. Because the address is only what they typed, we also keep a note that the code made the account (the address, the time and the place); while that address is unconfirmed, the first time its real owner opens a link or types a code for it that can join them to a team (an invitation's link, or any sign-in link or emailed code while an invitation for that address is waiting), the sessions the code made end, and that person signs in again with a new link or code. No email is sent and no password is made. The code works once, five wrong tries end it, and we keep it only as a one-way code, with the place, the role and the account that made it, and, as short one-way codes, up to three different addresses typed at it by people who were not signed in: a fourth ends the code. The screen that shows it listens for it, and shows who joined (their first name, their email address and their role, with the identifier of their account so that it can offer to remove them) for ten minutes, to the place's owners and managers only. A person whose address already has a Wassaaa sign-in signs in first and then types the code; until the code ends, that address may be sent a sign-in link even though it is not on a team (we keep a one-way code of the address and the time, nothing else), so that the person has a way to sign in first. If they sign in with that link, the browser where they typed the code keeps the code and the address, for ten minutes at most, so that the page the link opens can use the code for them; it is not sent to us. An address that is used as a guest in the Wassaaa app becomes a team account this way, and the app then signs it out as a guest, so the page suggests another email for the team. On your other phone. A signed-in team member can ask for a code that signs their own account in on another phone: it works once, within ten minutes, and we keep it only as a one-way code with the account it is for. Signing out on the screen that shows it ends it; closing the code only hides it, so that the phone can still use it (Staff on an iPhone's Home Screen needs it after Safari), and it stops working at its ten minutes. It also stops working if that account's sessions are ended after it was made (a password change, or the shut-out above) or the account is disabled. To stop abuse, we count the links and the emailed codes asked for by each address and by each network address, the codes each place and each account made today, the wrong codes tried from each network address and account, and the wrong emailed codes tried for each address today (the addresses and the account only as one-way codes), as the table in section 6 says. Two-step sign-in. A place's owners and managers, and a college's admins in Teach, must turn on two-step sign-in; anyone else on a team may. Firebase Authentication (Google, section 5) keeps your authenticator app's secret key and asks for the app's 6-digit code when you sign in on a new device; Wassaaa never sees the key. Before you set it up, we email your address a sign-in link, so that only the inbox's holder can. Our server keeps which authenticator apps were set up through those steps (Firebase's identifier for each, and when) and eight backup codes, as one-way digests only: we never keep a code itself, and you see them once. A code you type is checked against those digests; a right one turns two-step off and ends every session of the account, and you sign in again and set it up anew. We count backup codes tried for each address and from each network address, as one-way codes, for a day. When you turn it on or off, move it to a new app, make new backup codes, use one, sign out everywhere, or another owner of your place or the Wassaaa team resets it, the place's audit log says who did it and when (and, for the Wassaaa team, why).
- If you are on a place's team: your shift, and when we last heard from your screens. A shift. "Start shift", in the staff console, in staff mode or in Wassaaa Team, makes our server note that you are on shift at that place. It keeps your name as you gave it (never an email address), when the shift started and when it is due to end, whether its test alert reached your phone, whether one of your screens is open now, the last time one of them was heard from, and whether it was started by an older version's "On shift" switch. A shift is due to end at the place's closing time plus half an hour (eight hours when the place has no hours that day, and never more than twelve hours after it started), or at the end time picked in Wassaaa Team when it starts (at least half an hour ahead, and never more than twelve hours after it started); "Keep going" adds two hours, never past 16 hours after the start. It ends sooner at "End my shift" and when you sign out, and our server then removes it. The place's active team can read these, so that "On shift now" and "phone seen 8:02 pm" can be shown; nobody else can. While nobody at the place is on shift, its alerts go to its owners and managers instead, to every device of theirs with alerts on; and its owners and managers see in the console's Team list whether someone who has not started a shift has the app on a phone (yes or no, never which phone). Your test alert. To send it we also note which of your devices you started the shift on (the key of its alert registration, and whether it is a browser, an iPhone or an Android phone); only our server can read that, and it goes with the shift. The alert is one notification to that device, "Test alert from {place}. If you can read this, your phone will ring for guests."; if it reached you and you answer Yes, we keep, for that place, the time and the kind of phone ("the last test alert you passed here"), so that the place's "Before you open" list can show that a teammate's phone rings; it is removed when you leave the team. When we last heard from you. When the staff console, staff mode or Wassaaa Team opens a connection to our servers, it writes one marker for that browser tab or that start of the app (a random key, the time, and whether it is a browser or the app) and, when the connection ends, the time it ended; it writes nothing while the connection stays open and nothing on a timer, and only our server reads it. A marker is kept for 24 hours after the connection ended and deleted within 31 hours of it; one that never closed (a lost connection) is deleted two days after it was made. Our server also notes the time (at most once a minute) when you do something on a conversation: send, take, read, close, complete an order or confirm a reward. From these the guest's line reads "The team is here" while a shift is open and a screen of it was heard from in the last two hours (What a guest sees of the team, above), and a team member's phone is called quiet after five minutes with no connection and no action, so that a teammate can take over. We keep no position and nothing about where your phone is. Points you give. Where your place runs Rewards and you give points to a guest (by scanning a card where no till is linked), our server counts the points given by each team member each day, and the place sees that count with your name as you gave it, as it sees the rest of its team. Your browser. The console keeps a random key for each browser tab, for as long as the tab is open, and, on this browser only, that it has shown you a place's "ready" moment; neither is sent to us except the key, which is the name of the marker. When your shift ends with conversations in your hands, they go back to the team with your name and the time until someone takes them (What a guest sees of the team, above). A place that has not started a shift keeps the "On shift" switch as before, except that while every switch at the place is off, the owners' and managers' own included, its alerts go to its owners and managers.
- Technical diagnostics and security logs needed to operate, monitor, and protect the service.
- Usage measurement, without identity. So we can see where guests stop and what to improve, the app counts which steps a phone reaches and sends them to Google Analytics for Firebase with the random identifier it gives each app install. The steps are: the first time the app is opened; the welcome finished; your first answer about location; the first map; a place chosen on the map or in the list; a place's menu opened from its card before entering (the first look at each place, not every one); entering a place, and whether you came in among the faces or here to order; a selfie started and finished, or declined with "Not this time"; your first message; a card or a place's link handed to your phone's share sheet or to Instagram, and the link from "Know the team here? Tell them" handed to the share sheet (each counted when it is handed over, whatever you then do with it, with the kind of place and whether it has joined: never which place, and never which app it went to (the app neither keeps nor sends it)); the visit ending; and coming back on a later day. Nothing is counted about a yes, a pass or a match: no step is sent when you say yes, pass, take a yes back or are matched. Beside these the app counts details of the same kind: each time the app is started; each welcome screen, and the age screen shown and agreed to; the location screen and each answer about location; the selfie check shown and agreed to, and a selfie screen left without a photo; a selfie used to go in, or as a visit's new photo, with the lens and the look it wore, each as one word from the app's own list (never with a place, a person or the photo, and not in a class); a tap on Enter, and an entry that failed, with the code of the reason; going back to the map during a visit; a change of your tagline for the visit (which tagline of the short fixed list, if you picked one; never the words you typed) or of your section; an alert for a place turned on or off; a place's link or printed code opened (for a place, a table or the counter, or as an invitation when the link came from a card or link someone shared; never for a class); a place's "Website" or "Shop online" opened (the kind of place and whether it has joined, and nothing else: never which place or the address); a request for a place to join Wassaaa; a visit to a place that unlocks premium chat for its guests; and how long the app waited for our server at a step of a visit (going in, the menu, an order, a message, a message to the place's team), as one of five bands from under 300 milliseconds to over 10 seconds, never the exact time: going in each time, the others once in a visit. (A phone on a version of the app before this one, which has waves and hellos, also counts: the first wave or hello of a visit; the first one accepted; each wave, each hello, and each hello you accept; with going back to the map, how many chats were open; and, in place of the list just given, how long the app waited for our server at a step of a visit (going in, the menu, an order, a wave or hello, a hello you accept, a message, a message to the place's team), as one of five bands from under 300 milliseconds to over 10 seconds, never the exact time: going in each time, the others once in a visit.) A step carries at most the kind of place and whether it has joined Wassaaa, a number of days or another small count, or one word from a short fixed list, such as "allowed" or "not now" (a selfie's lens and look are two such words); never which place, a name, handle, photo, message, account, age, who you met, or where you are. Nothing is counted in a class. Nothing is sent before you agree on the age screen: measurement stays switched off in the app until then; the steps you take before it wait on your phone and are sent only if you go on; and if you answer "I'm under 18" they are deleted and nothing is sent. You can turn measurement off at any time: "Help improve Wassaaa" in the app's Settings stops these steps and crash reports together, at once, and a crash that happens before you agree on the age screen, or while that switch is off, is not reported. A phone on an older version of the app has no such switch; there Google Analytics starts when the app is first opened, and a step also carries the place's own id. Google Analytics also records by itself what it records for any app that uses it, such as that the app was first opened, updated or brought to the front and for how long, with the app's version, your phone's model, its system version and language, and the country or region of your internet address. So that each step is counted once, the app keeps on your phone the day it was first and last opened and, for your last few visits, which of their steps were counted, the kind of place each was at (never which place), when it was last renewed and when it ends; "Erase everything about me" clears both. Wassaaa turns off Google's advertising identifier and ad personalisation for these events and never uses them for advertising.
- Paid placements. A brand may pay Wassaaa to offer a sponsor’s selfie frame at some places, and a place may pay to show one card marked Sponsored (Boost); both are labelled, and neither changes a place’s stars or its place in the list. If you choose a sponsor’s selfie frame, our server counts that one more guest chose it at that place: a number, with nothing about you. The frame’s picture is fetched from our own storage, not from the sponsor. Boost. A place that has joined Wassaaa may pay to show one card, marked Sponsored, in “Tonight near you” on Home, for an event, a deal or its night. It never changes a place’s stars or the order of places, it never sends a notification, and it is never shown on Campus. Your phone keeps, on the phone only, the boosted cards it showed you, for 24 hours. Once a day the app tells our server that a card was shown, and our server adds one to a count. If you enter that place within a day, the app adds “came from a boost” to that visit’s own check-in, and our server adds one to a count; it keeps nothing that joins you to the card. One phone in ten, chosen by a code made on the phone, is not shown a given boost, so the place can see how many came because of it; that phone still keeps the card it would have shown, tells our server once a day that it would have been shown, and adds the same “came from a boost” to a visit, counted apart. Featured was replaced by Boost on the day Boost went live: an older version of the app may still ask our server to note that a Featured place was opened, and nothing is noted, because no place is Featured. The sponsor and the place are told the numbers and nothing else: never who, never a photo, never anything you wrote.
- Signals that a request comes from a genuine copy of the app or website: Apple App Attest and DeviceCheck on iPhone, Google Play Integrity on Android, and Google reCAPTCHA Enterprise on the web. App Attest, DeviceCheck and Play Integrity check the app and device, and never tell us who you are. reCAPTCHA Enterprise reads more. On the pages where it runs (section 10 lists them; it runs on no other), it looks at how the page is being used (for example clicks, pointer movement and the rhythm of typing), at your browser and device, and at your internet address, and it sets and reads a cookie of Google's own (
_GRECAPTCHA) or a similar identifier in your browser. These go to Google, which works out whether the request comes from a person's browser or from an automated program; our server learns only whether the check passed. Google does this on our behalf, under Google Cloud's data processing terms: it uses what reCAPTCHA collects only to provide the check and to keep it working against new abuse, for security and to prevent fraud. Google says more in its questions and answers about reCAPTCHA. At a place's door (entering, coming in to order, a class code, paying, and answering a question that has a prize), and when you spend a reward, the app signs what the call says (the place, your location and a one-time number from our server) with a key your iPhone makes for Wassaaa (App Attest), or has Google Play Integrity vouch for it on Android, so that a location changed on its way is refused; our server keeps the key's public half, which can only check those signatures, until you erase your account, and reads Google's answer, which also says whether this copy of the app came from Google Play for the Google account on the phone. It keeps none of that about you, only a count for each day, across all phones, of how many door checks got each kind of answer. A phone that cannot be confirmed may be left out of a prize draw, and its reward may wait for a manager's OK. It loses nothing: the answer still counts and the points stay. While a reward waits, our server keeps that it waits, with a one-way code of your account, for its 15 minutes, in the list the place's owners and managers answer from, which never says why; then it goes. Nothing else about the check is kept on your account, and nobody, the place's team included, is told why. A failed check at a place's door leaves one line in our server's log, saying which kind of phone and which door, with no account or place, and a reward that could not be confirmed adds one to the day's count. While an iPhone has a proxy set, the app sends no location at the door.
2. Camera, Photos, and Microphone
- Your selfie and the face check. When one is asked: only to meet people. You come into a place with one tap and no camera (where a visit of yours with a selfie is still kept there, the place's card offers "Back in as …", one tap with that selfie), and the app asks for a selfie only when you tap "Take a selfie" in Meet or "Everyone here". In a few cases the camera still opens on the way in (when "Back in as …" finds that your earlier selfie can no longer be used, say), with "Not this time". An older version of the app asks for a selfie as you enter a place, with "Meet people" on in its Settings, and you can tap "Not this time" (section 1). At a hotel itself none is asked (section 1). Until you take one, or after "Not this time", none is kept (a photo already taken for that pass is deleted: below); section 1 says what you are then: here to order. A Campus class always asks for one. Before your first selfie the app asks you once to agree to the check, and keeps the date you agreed on your phone. Purpose: to show the other guests among the faces in a place a real, current photo of you, and to keep out pictures of nobody, of several people, or not taken just now. What is checked: that the photo shows one live face, taken with the camera at that moment. Where: on your phone. Nothing about the shape of your face is stored, sent to us or to anyone else, or used to recognise you. How long: the photo lasts for one visit, and its smaller copy goes with it. A visit lasts eight hours at most from when you came in (up to two hours more while an order of yours is still open), and ends sooner when you end it; section 6 says how. The photo never outlasts its visit. It goes sooner if you tap "Exit meet" during the visit: both copies are deleted from our servers as soon as your phone can tell them (at once when it is connected), at that place only (on an older version of the app, turning "Meet people" off does this, and deletes the selfie of every other visit of yours that is still kept too; section 1 says how, what happens until they have been told, and what another guest's phone may already hold); the app takes back the copy it uploaded, as it does when you end a visit (below). You can have a selfie and a visit at each of several places at once, each until its own end; section 6 says how. (A phone on an older version of the app: its visit can run out sooner, two hours after the phone was last there, and the same photo can then start a visit again at that place until eight hours after it was first used there.) A new photo during a visit: while you are among the faces of a place you can take a new photo whenever you like, up to ten times in one visit, with the camera only (never from your photos). When you tap "Use this photo", it is sent to our storage like the first one, and it takes the old photo's place for everyone at once: on Meet, on your card, on your posts on Everyone here, at your table, in hellos you sent that are still waiting (on an older version of the app) and at the top of your private chats. Nobody is told that you changed it. The old photo and its smaller copy are deleted from our servers as soon as the new one is in place; if that step is cut short, they go with the visit at the latest (section 6 says how a clean-up finds what is left), and the app takes back the old upload it holds, as it does for the first photo. A message you already sent in a private chat keeps the address of the old photo, which then shows nothing. The new photo is checked like a selfie (the next item), and it gets a note that it was used, like the first (below). A Campus class keeps the photo taken at the door, which is its record of who was there, and takes no new photo. When it is sent: a photo you took with the button is sent to our storage, where only you can read it, when your pass appears, so that going in does not wait for it; a photo the camera took by itself after you blinked stays on your phone until your first tap on the pass that uses it (Enter, "Edit pass" or a change of its look). Nobody is shown either until you go in. You can stop a blink from taking the photo with "Blink to take your selfie" in Settings: a blink then only unlocks the button, and you tap it to take the photo. That choice is kept on your phone only, and only while it is off; signing out or signing in to another account leaves it as it is, and erasing your data clears it. Leaving the camera takes no photo, and the camera's own file of a picture is deleted from your phone as soon as the photo for your pass has been made from it. If you go back, retake it, change its look or tap "Not this time" instead, and when you end a visit, the app takes that copy back: at once when your phone can reach our storage, and otherwise as soon as it next can. It is deleted or, where that is refused, replaced by a blank picture, which is cleared within eight hours (sixteen for a class). Until it has done so the app keeps a note on your phone of which copy to take back; a copy the app never gets to take back is deleted by our server within the same eight or sixteen hours. If you pressed Enter and the door did not let you in (you were outside the place, say), the photo is kept, where only you can read it, for "Try again" on that pass, for up to eight hours; it is taken back when you leave the camera or that pass by any road, tap "Not this time", turn "Meet people" off on an older version of the app, or sign out, and, if the app was closed with that pass open, the next time it starts; if you sign in to another account, your phone forgets it and our server deletes it within those eight hours. A note that it was used: so that one selfie cannot start a visit at a second place, or after its eight hours, our server keeps a note for each selfie you have gone in with: which upload it was, at which place and when. No phone can read it. It is used for those eight hours at most and deleted within 16 hours of the selfie's first use (a class selfie's: used for the class day, and deleted within a day), and at once if you erase your data or delete your account. Never sold: your selfie is never sold, never used for advertising, and never used to train anything.
- A check of photos for nudity, on your phone. A selfie is shown to the other guests among the faces in a place, so the app also asks your phone to look at the whole picture. A selfie your phone flags as possibly showing nudity is not accepted: you are asked to take another, and nothing about the attempt is kept or sent. A new photo you take during a visit is checked in the same way. In a private chat the same check looks at a photo you are about to send (if it is flagged the app asks "Send this?" once, and the choice is yours) and at a photo you have chosen to open (if it is flagged it stays covered until you tap again, with Block and Report beside it). Where: on your phone only. No picture is sent anywhere to be checked, and nothing about an answer leaves your phone: no picture, no score and no count, to us, to the place or to anyone else. What it looks at: the picture, not the shape of a face. It does not recognise or identify anyone. On iPhone: the check is Apple's own, on iOS 17 and later, and it answers only while you have Sensitive Content Warning turned on in the phone's Settings under Privacy & Security (or Communication Safety is on in Screen Time), and have not switched it off for Wassaaa. With it off there is no check, and the app works as it did before. From iOS 27 Apple's check can also flag other sensitive content, such as graphic violence; a chat photo flagged for that is covered and asked about in the same way, and a selfie is not refused for it. What Settings shows: on an iPhone, Settings says whether your phone's Sensitive Content Warning is on; that is read on your phone, shown to you, and not sent or counted. On Android: there is no such check yet. Not a guarantee: the check can miss a picture and can be wrong about one. That is why every photo in a chat arrives covered, and why you can always report and block.
- Camera is used to capture a selfie and optional filter preview when you choose to do so. Face detection is used to confirm that the image contains one face; Wassaaa does not claim that this is government identity verification or full liveness detection. Face detection, face tracking for lenses, and the checks on the picture all run on your phone: the shape of your face is never uploaded or stored, and it is not used to recognise you. The face tracking that places a lens also reads your expression, such as an open mouth, raised eyebrows or a smile, on your phone only, to make the lens on screen react; it is never sent, kept or counted.
- Your selfie is used as your temporary profile image at the place. The other guests among the faces there see it, with your handle, while you have the app open there; a guest who is here to order does not see it, and neither does the place's team; in a class, classmates see it with your first name. A smaller copy is made for lists of faces. Our server also saves a lighter copy of each of the two (the same picture, in a file that loads faster), and with each person's small photo the list carries a tiny blurred copy of it (a sketch of its colours that the app shows while the photo loads), made by our server. These extra copies are kept and deleted with the photo: wherever this policy says that your selfie and its smaller copy, or both copies, are deleted, they go too. All of them are deleted when your visit ends, or sooner if you leave the faces with "Exit meet" (on an older version of the app, by turning "Meet people" off): at a place, the visit ends eight hours after you came in at the latest, or up to two hours later while an order of yours is still open (a class selfie follows the class rules below). If you take a new photo during the visit, it takes the old one's place, and the old one is deleted at once. It is not a permanent profile.
- If you turn on the app lock in Settings, your phone checks it is you (Face ID, Touch ID, a fingerprint or your passcode) when Wassaaa opens: every time, unless you choose a longer time under "Lock after" (1 minute or 15 minutes), and then only when the app has been out of sight for that long, and always when the app starts afresh. The check happens on your phone; Wassaaa is only told yes or no and never receives your face, fingerprint or passcode. Whether the lock is on and your "Lock after" choice are kept only on your phone.
- Screenshots: on Android, the system does not allow screenshots or screen recordings of a private chat (a view-once photo included) or of the people in a place. On iPhone, which cannot block them, a screenshot of a private chat, or of a view-once photo while it is open, is noted in that chat for both of you ("Maya took a screenshot"), as an encrypted message like any other; nothing about the picture itself is read or sent. Your phone says beside the sealed line that it is a screenshot line, so that our server can tell the other person's phone of it with a notification ("Took a screenshot of the chat."), under their "Messages" switch and not for a chat they muted; it cannot read the line itself. A reaction, or a reaction taken back, that your phone sends to a phone on an older version of the app is marked in the same place as one not to notify about, and the server cannot read which of those it is. The server keeps these marks with the sealed message until the chat ends.
- Microphone is used for voice messages only while you hold (or have locked) the record button. Nothing is recorded otherwise, and a recording you discard never leaves your phone. On Android the app also asks for the microphone permission before it turns a voice message into text (next point), because Android's speech recognition does not work without that permission, even though nothing is recorded then; while it works, Android may show that the microphone is in use.
- Wassaaa Team, the separate app for a place's team (section 6), asks for no location, asks for the camera only when you tap "Scan rewards" to read a guest's Rewards code (read on your phone; the picture never leaves it), and never shows a team member a guest's photo or anything of who has said yes to whom. It asks for the microphone only when you first hold the record button to answer a guest with a voice message, and records only while you hold it; a recording you discard never leaves your phone, and one you send is kept as any voice message in a conversation with a team is kept (section 6).
- Voice to text: tap "Show text" under a voice message in a chat, and your phone turns it into words with its own speech recognition, which the app asks for only in the form that works on the phone itself: the recording and its words are not sent to Wassaaa, Apple, Google or anyone else for it. The words are kept in the app's memory only, for you; they are not sent to the other person or written to your phone. Where a phone cannot do this by itself in the app's language (on Android, before Android 13), the app does not offer it. On iPhone the system asks your permission for speech recognition the first time; on Android, for the microphone, as above.
- Photo library access is used only when you choose to attach media, or to save your pass's photo (section 5): on an iPhone the app is only allowed to add a photo, never to read your library; on Android the photo is saved in Pictures/Wassaaa, with no permission.
- A place may offer a frame for your selfie, like a sticker around the edge of the picture. It is yours to choose: nothing is applied unless you pick it, and the place is told only how many guests wore it on a given day, never who.
- A place may also offer its own lens: a shape from Wassaaa's gallery in the place's colour, such as a crown or a halo, named for the place. An event at the place may offer one for its hours, and Wassaaa may offer a lens for a night, at some places or at all of them, or a new lens for everyone. Each is yours to choose: none is on unless you pick it, it is drawn on your phone, and never in a class. When you go in wearing one, our server is told which lens it was, by a code, and counts it: a number for each lens, at each place, on each day, with nothing about you. The place's team sees the numbers for its own lens and its events' as they are; Wassaaa sees the numbers for its own lenses; nobody else sees a number under five. The picture of a lens Wassaaa adds is fetched once from our own storage.
3. How We Use Data
- Deliver core app features, including social interactions and messaging at a place.
- Use a recent, bounded location fix only to display nearby venues and confirm that an active visit remains inside the place's configured area. While an order of yours is open, checks that find your phone outside the place beyond doubt also tell the place's team that it was seen outside, and never where (section 1 says when). Ending a visit ends the location checks for it and any Nearby Interaction locating; Wassaaa does not continue UWB or any tracking at the venue after that visit.
- Apply automated safety checks to some text and use reports, blocks, and support review to prevent abuse.
- Improve reliability, safety, abuse prevention, and troubleshooting.
- Meet legal and security obligations.
4. Nearby Interaction locating
On iPhones that support it, Nearby Interaction lets two phones in the same place find each other: distance and, where available, direction, calculated on the two phones themselves. Wassaaa uses it only for these:
- A place's team member finding a guest who has asked them for help.
- A team member bringing an order to a guest who asked for it to be brought to them, where that guest's phone has an older version of the app: an order from this version is brought to the table it names, and no phone is looked for.
- Picking up an order at the counter, where the counter's phone recognises a guest's phone held close to it.
- Two guests who have both agreed, in their private chat, to find each other: for five minutes at most, and it stops when they meet or either of them stops it.
It is not used to admit you to a place, identify you, or track everyone in a place, and it is not offered to a guest who is here to order (section 1). The team's side runs in the staff mode of the Wassaaa app and in Wassaaa Team. Distances, directions, coordinates, routes and raw ranging measurements are never uploaded to Wassaaa and are never shown to anyone but the two people it is for.
- The server stores only the opaque pairing tokens (a phone that cannot show the arrow gives none), with start and expiry times and, from the version of the app that has Light up (below), one yes-or-no value for each phone: whether that phone can show the arrow at all. Each token can be used for five minutes at a time, renewed while in use, and is deleted when the conversation, order or request it belongs to ends. It does not store a distance history.
- It stops when the help request or order ends, when either guest stops finding the other, when your visit ends, when the operating system denies permission, or when the token expires. While the app is in the background the operating system pauses it; coming back resumes it only while the same visit and request are still going.
- Apple may show its own one-time Nearby Interaction permission prompt. Wassaaa cannot bypass it; without it, everything works as before: the team finds you by your table, and two guests find each other from the place's list and their selfies.
- Availability depends on the phone's hardware, operating-system support, permission and indoor conditions. Android phones and iPhones older than the 11 cannot show the arrow; they use Light up (below), or the place's list and their selfies.
- Light up. Where the arrow cannot run (an Android phone, or an iPhone older than the 11, on either side), two guests who have both agreed, in their private chat, to find each other see the same colour instead: both screens fill with one colour for 30 seconds, with the other person's name, and each looks up for the other. Either of you can stop it, or tap "We found each other", at any time, and it stops by itself after 30 seconds. While it shows, your phone turns its screen up to full brightness and keeps it from going dark, then puts both back; neither needs a permission. Light up measures nothing about where anyone is: no coordinates, distance or direction are taken, sent or kept. Each phone tells our server only whether it can show the arrow (yes or no), with its request to find each other, and which version of the chat its app has (a number, kept with the visit). Our server picks one of five colours that no other pair in the same place is using (if more than five pairs are finding each other at once, the one used longest ago), holds it for the pair for 30 seconds, and sends it to the two phones in the chat, which are the only ones that can read it. The chat keeps its own record of that light (the colour and when it starts and ends, nothing else), and only the two phones in the chat can read it. It is removed when a phone ends Light up and, if neither does, when the two of you start to find each other again or the chat ends. The place's list of colours names no chat and no person: for each colour it keeps only when it was last given and when it ends, so there is nothing to forget. The colour is let go when the 30 seconds are up, even if neither phone could tell our server so, and at once when either of you stops Light up or taps "We found each other". If a chat ends while Light up is showing, the colour stays set aside, for no chat and no person, until its 30 seconds are up. All that stays against the five colours is when each was last used in that place, so that two pairs near each other are not given the same one, and that goes when the last visit in the place ends. It is offered only when both phones have the version of the app that has Light up; if either has an older one, you get what you had before (the arrow, where both can show it).
5. Data Sharing
We do not sell personal information. Data may be shared with Firebase/Google infrastructure, Apple or Google payment services, notification providers, and other service providers strictly for hosting, storage, billing, notifications, safety, and service operation.
For people who run a place: the emails we send you about your place, such as an approval, a decline or an invitation (described in If you run a place), are delivered by Resend, an email delivery service acting for us, which receives your address and the message. The same goes for the sign-in code that a place's team asks for, and, once Wassaaa switches its email on, for the sign-in links and invitations sent to a place's team and to a college's instructors and admins (described in how you sign in). Nothing about a guest is sent to it. Stripe is our payment processor for a place's plan: invoices are sent and paid through Stripe, and a place that pays by card does so on Stripe's own pages. You give your payment details to Stripe, under its privacy policy, and Wassaaa never receives them. What we send to Stripe and what it tells us is in If you run a place. A guest never pays Wassaaa: where a place takes cards in the app, a guest pays the place, which is the seller, on the place's own Stripe account, and nothing about the guest but the payment is sent to Stripe (Paying for an order in the app). Where a place chose Square, the guest pays on the place's own Square account in the same way, and the order goes into the place's Square too (If you run a place). Where the owner has not allowed orders and payments, nothing about a guest is sent to Square. A place can also connect its own Square till so that its menu, what is sold out and its hours come from it; we only receive from Square, and nothing about a guest is sent to it, unless the owner also allows orders and payments, as described just before (If you run a place). A place can also connect its own Clover till, so that its menu, what is sold out and its hours come from it and, if the place turns it on, the orders its guests place are sent to the place's own Clover account (what they ordered, their note, the first name they use for that visit and the table or counter, and nothing else about them) (If you run a place).
Other services your phone contacts
Almost everything the app does goes through Wassaaa's own server, which runs on Google's Firebase. For the few things below, your phone talks to another company's service directly. Each of them sees your phone's internet address, as any service a phone contacts does.
- Paying for an order: Stripe, and Apple's or Google's wallet. Only where a place takes cards in the app and you choose Apple Pay, Google Pay or Card: your phone opens Stripe's own sheet or card field for the place's Stripe account, and Apple Pay, or Google Pay from the cards in your Google Wallet, hands Stripe the card you pick. What reaches Stripe is the payment (the amount, the place's account) and the card details you give it, under Stripe's privacy policy; it is never given your Wassaaa account, your handle, your selfie or anything you said in the app. The Stripe platform for the places' payments is run by Sigmaton's sole proprietorship in Alameda, California, for the places' payments only. What our server does with the payment is in Paying for an order in the app.
- Paying for an order at a place that chose Square: Square. Only where a place chose "Square, your till" for its payments: your phone opens Square's own sheet, where you type a card into Square's own field or use Apple Pay or Google Pay through Square. What reaches Square is the payment (the amount, the place's Square account) and the card details you give it, under Square's privacy policy; our server also sends Square the order, as If you run a place says. Square is never given your Wassaaa account, your handle or your selfie.
- GIFs: KLIPY. In a private chat you can search for a GIF, in versions of the app that have the GIF button. When you open the picker your phone asks KLIPY for the GIFs: what reaches KLIPY is the words you search for, a random number made on your phone for this purpose only, and your internet address. The random number is not your account and is used for nothing else; it stays on your phone until you erase your data or delete the app. KLIPY is never given your Wassaaa account, your handle, your selfie or the place you are in. A GIF travels in a chat as a link, and the phone that receives it fetches the picture from KLIPY's servers, so KLIPY sees that phone's internet address too, whether or not that phone ever searched. The app fetches a GIF only from the servers of KLIPY, or of GIPHY (a second GIF library the app can show a GIF from; no current version searches it), and from nowhere else: a link to any other server is not loaded. Photos and voice notes are never links: they come from Wassaaa's own storage.
- Maps: Apple on iPhone, Google on Android. Your phone asks Apple Maps or Google Maps for the part of the map you are looking at, under their own privacy policies. If that map cannot be shown (an iPhone on which Apple Maps fails to appear, or a copy of the Android app made without Google Maps), the app draws the map itself from the map tile servers of OpenStreetMap, run by the OpenStreetMap Foundation; they see your internet address, the squares of map on your screen and the app's name. The places on the map come from our own server. If you tap Directions on a place's card, the app opens Apple Maps (iPhone) or Google Maps (Android) with that place's position and name and nothing else; what the maps app does with them is under its own policy. None of these map services is given your Wassaaa account or told which place you enter.
- Fonts: nobody, from build 69 of the app on: its typefaces are inside the app and nothing is fetched. Builds up to 68 fetch them from Google Fonts the first time they are needed, which shows Google your internet address and which typeface is asked for. (The build number is in brackets after the version, on the app's About screen.)
- Crash reports: Google's Firebase Crashlytics. If the app fails while it is being measured (after you agree on the age screen, and unless you have turned off "Help improve Wassaaa" in the app's Settings), a report goes to Crashlytics: the error and where in the app's code it happened, your phone's model and system version, and Crashlytics' own random identifier for the app install. The app does not attach your account, handle, messages, photos or location to it; an error's own text can name the record the app was working on, such as a place's identifier. Wassaaa Team, the app for a place's team, sends the same kind of report only while a team member is signed in to it, and unless "Help improve Wassaaa Team" is off in its settings (the gear); it is on until it is turned off, and turning it off, or signing out, also deletes the reports not yet sent. This is part of the technical diagnostics in section 1.
- The face check and code scanning: Google's ML Kit and Apple's reader. Checking that a selfie shows one face is done on your phone by Google's ML Kit. A QR code is read on your phone too: on an iPhone by Apple's own reader, which is part of the phone itself and for which the app sends nothing to anyone, and on Android by Google's ML Kit, whose code reader comes inside the app. The picture never leaves your phone for this. ML Kit itself reports to Google how it is working: your phone's model and system version, the app's name and version, how long a check took and whether it failed, and ML Kit's own random identifier for the app install. Nothing in that report is a picture, your face or your Wassaaa account. The in-app scanner opens only Wassaaa's own codes; any other code is read on your phone, not opened, and not kept.
- A place's own website or online store ("Website", or "Shop online" at a shop). Where a place has given Wassaaa the address of its own website, or a shop of its own online store, the app shows a globe on the place's card on the app's first screen, a line on its page ("Website", or "Shop online" at a shop) and on the list you can read before entering, and the page its door code opens shows it too. Tapping it leaves Wassaaa: the address opens in your phone's own browser exactly as the place gave it, and from there you are on the place's site, under its own terms and privacy policy, not ours. Nothing about you goes with it: no account, no name or handle, no visit and nothing that says where you came from; the page a door code opens asks your browser not to tell the place's site which page you came from. The place's site sees what any website sees, such as your internet address. That you tapped it is counted without identity, as section 1 says.
- A link in a message. A web address in a private chat, or in your conversation with a place's team, is shown as a link. Nothing is fetched to preview it: no phone contacts that site until someone chooses to open it. Tapping it first shows where it goes, the site's name with the whole address under it; only if you then choose Open does your phone open it, in its own browser or in the app that owns that address, outside Wassaaa. That site then sees your phone's internet address, as any site does, and you are under its own terms and privacy policy, not ours.
- Rating the app: the store's rating sheet. The App Store on an iPhone and Google Play on Android can show their own sheet asking you to rate Wassaaa. It is the store's, under its own privacy policy: Wassaaa sends it nothing about you, is not told whether it was shown or what you chose, and cannot fill it in for you. What the app counts to pick a moment stays on your phone (section 1).
- Checks that the app is genuine (Apple App Attest and DeviceCheck, Google Play Integrity, and Google reCAPTCHA Enterprise on the website) are described in section 1, and the app store's age signal in section 11.
- Notifications reach an iPhone through Apple's push service and an Android phone through Google's Firebase Cloud Messaging, using the push token described in section 1.
- Usage measurement goes to Google Analytics for Firebase, as described in section 1.
- When the law requires it. We also share information when the law requires us to. One case is set out in the community rules: child sexual abuse material, with the account it came from, is reported to the CyberTipline of the National Center for Missing & Exploited Children (NCMEC), as United States law requires of us.
6. Data Retention
Your in-place identity (handle and selfie), chats and shared media are removed when your visit ends, with bounded technical cleanup as a fallback. A visit starts when you come into a place and ends eight hours later at the latest. It ends sooner when you press End visit: on the place's screen while you are inside, and, for a visit you have walked out of, from anywhere: in the app's Settings, on that visit's card (an older version: on its pass under "Your visits" on the first screen), or in one of its chats read from outside. End visit ends the visit at once on your phone, and on our servers at once when your phone is connected, otherwise as soon as it next is (described below). A visit also ends sooner when you erase everything about you or delete your account (section 13), or when the place's team or Wassaaa removes you. One more thing can end a visit with a selfie: taking a selfie at a seventh place, when the app ends the oldest of your visits with a selfie that no open order is keeping (described below). Nothing else ends a visit, and nothing makes it longer: not walking out, not locking your phone or closing the app, not coming back, not a message. One exception: an order of yours that is still open when the eight hours are up keeps the visit until the order is done, at most two hours more (described below). Everything in the visit goes at that same moment: your handle and both copies of your selfie, your chats with their photos and voice notes, the yeses you said, your conversation with the place's team, your seat and your lines at a table, and your own answers to a place's questions, with any entry in a draw. One thing can outlast the visit: if an order of yours is still open when it ends, the place's team keeps that order's card (what you ordered, your note, the table or the counter, or the room number at a hotel or for an order brought to a room, and the name you went by) until someone on the team closes it, and for up to four hours after the visit ended (section 1); your conversation with the team still goes. And so that each person answers a place's question once, the note that your account answered it, never which answer, stays after the visit until that question is over: until the place's own question is cleared, and with it the name a prize's winner went by (section 1). If a deletion ever fails at that moment, a clean-up finds what it left: within about 15 minutes, a chat or a conversation with a place's team whose visit has gone; ten hours after it started, any chat or conversation that is still there; in the six-hourly clean-up, a visit's photos and a chat's photos and voice notes once those files are ten hours old; and after one day our storage itself deletes any such file.
If we report child sexual abuse material as the law requires (section 5), we keep what that report holds for as long as the law asks of a provider that reports, one year in the United States, and then delete it.
If you walk out without ending your visit, it is kept until eight hours after you came in, so that your conversations are still there if you come back. Until then our servers keep your handle, your selfie, your chats and what was shared in them, and the rest of what is listed above. Beyond the 30 minutes described below, you are not on the place's list for that time. The other person in a chat can still write to you, and you are sent a notification for it (unless you muted that chat); as always, it does not carry their words. From outside, the app shows you those chats to read: their words as they are on our servers, the other person's new messages included. You cannot reply from there (from this version of the app, our servers accept no message, reaction, edit, game move or "Keep in touch" tap from outside the place). You can open a photo or a voice note from there until the visit ends: for each one, our server gives your phone a link to the sealed file that works for half a minute at most, and never past the end of your visit or the other person's, and only your phone can open what it fetches. A view-once photo opens only inside the place: from outside, our server gives no link to it. Reading a chat from outside sends nothing: no "delivered" or "seen", no reaction, and nothing else that tells the other person you opened it. Opening a photo or a voice note there asks our server only for its link, and the other person is not told. (Builds of the app up to 69 show no chat from outside, and build 70 shows them without opening their photos and voice notes.) Every version also has the read-only copy on your phone described below. If you walk back in before the visit ends, it is the same visit: the same handle, the same selfie and the same chats, with no new selfie. Going into another place ends nothing. You can have a visit kept at each of several places at once, and a selfie with each visit in which you are among the faces, each until its own end. Your phone keeps what it needs for each of them (a pass for each place), so that until a visit's end you can go back into its place with one tap and no new selfie, and read its chats from outside. You are among the faces of one place at a time, and counted in one place at a time: when you enter another place you come off the first one's list, and out of its number, at once. Your phone keeps passes with a selfie for at most six places; if you take a selfie at one more, the app ends the oldest of those visits that no open order of yours is keeping, on our servers too, and says so once on its first screen ("Your visit at Jebena has ended: this phone keeps up to six visits with a selfie."; a line the app was closed before it could show is not shown later). If an open order is keeping every one of the six, none is ended: the app does not let you into a seventh place with a selfie until one of them has ended ("You have six visits kept. End one in Settings to come in here with a selfie."), and you can still come in there to order. A visit with no selfie is not one of the six. One limit: if you sign out or sign in to another account, your phone forgets the visits it kept: each stays on our servers until its end, its chats can no longer be opened on your phone, and Settings no longer offers to end it. You can end it sooner from anywhere: in the app's Settings, which shows each visit that is still kept, with End visit under each (an older version also offers it on that visit's pass on its first screen); in one of its chats read from outside; or by erasing everything about you (Settings, "Erase everything about me"; for a linked account, "Delete account"). Any of these ends it at once when your phone can reach our servers. If the app cannot reach them when you confirm End visit, inside a place or from outside, it still ends the visit on your phone at once, and sends the request again when it is next opened, comes back to the front or gets its connection back, and before you enter a place, sign out or sign in to another account. Until the request gets through, the visit stays on our servers, and at the latest until its own end; and if you walk straight back into the same place and our servers still have that visit, the app ends it first and then lets you in afresh. If you are still inside when the eight hours are up, the visit ends all the same and its chats go with it; coming in again starts a new visit. A phone on an older version of the app (one that has waves and hellos) could not open its chats again after that long, so it keeps what it had: a visit it walks out of is kept for two hours after the phone was last there, never beyond the eight hours, and a chat between two such phones is removed at the latest four hours after it starts.
For the first 30 minutes after your phone last confirmed you were inside, other guests in the place still see you, dimmed, as "here a few minutes ago", and can say yes to you; nothing reaches you unless you had said yes to them too, and then the match reaches you as a notification, wherever your phone is by then: tapping it opens that chat to read, and you can write in it once you are back inside, before your visit ends. When you open the app it checks again that you are inside. (In versions of the app before this one they can say hello, and the hello reaches you as a notification.) That means someone who has walked out with their phone locked may be shown that way for up to 30 minutes; if you open the app outside, you are taken off the list as soon as your phone is found outside, and if you enter another place you are taken off the first one's list at once (the visit itself is still kept, as described above). You can turn this off in Settings, under Meeting people, with "Stay visible when you put your phone away" (it is on unless you turn it off; versions of the app before this one call it "Stay listed, phone down" or "Seen with your phone down", and show it on the entry pass too): then you are shown only while the app is open. Ending a visit in the app removes you from the list at once when your phone is connected, and otherwise as soon as it next is. After those 30 minutes, and until your visit ends (or soon after your phone goes down, if you turned this off), you are not on the place's list: nobody is shown your face or your card, so nobody can choose to say yes to you (or, in a version of the app before this one, send you a new hello). A yes someone said in the moment your face was going is kept with their visit like any yes; it becomes a match only if you come back onto the list and have said yes to them too, and it is deleted when either visit ends. A yes you said earlier stays until your visit ends. This never applies in a Campus class. Posts on a place's shared wall are deleted when their author's visit ends, or four hours after they were written, whichever comes first. A private chat has no clock of its own: it is removed when your visit or the other person's ends, whichever comes first, and its photos and voice notes are removed in the same step. A conversation with a place's team lasts as long as your visit, unless the team closes it: a closed conversation is deleted 30 minutes after it is closed, and writing to the team again within those 30 minutes opens it again. A "Keep in touch" tap is deleted when its chat ends. A yes you said to someone is deleted when the two of you match, when it is taken back, when your visit or theirs ends, when either of you blocks or reports the other, and when you leave the faces with "Exit meet" or, on an older version of the app, by turning "Meet people" off (not when they leave them: then it stays with your visit, and can still match if they join the faces again in the same visit and say yes to you); a pass was never sent to us. A safety report, with the messages sent in it, is kept until it is closed and for 12 months after that; it is then deleted, and only the number of reports deleted at that place is kept. Its line in the safety team's queue is deleted 180 days after the report was made. Limited operational logs may be retained longer for abuse prevention, support, and legal compliance.
The one-way mark a place keeps of your visits (whether you had been before) is deleted 60 days after your last visit there, and at once if you erase your data or delete your account. Visit ratings and their comments are deleted 30 days after they are left; the daily star (and older thumbs) counts remain as numbers only. The one-way code that keeps a rating in a place's public stars, with its stars and day, is kept for 180 days (the window the stars cover), then deleted; it is deleted at once if you erase your data or delete your account, and the place's stars are worked out again without it. Voice messages are deleted when the conversation they belong to ends with your visit, and in any case within a day. A place's order records are deleted 90 days after the order. While an order you placed is still open, your visit is kept until the order is done, even past its eight hours: for at most two hours after you placed the order, so never more than two hours past the moment the visit would have ended. A reservation at a shop is an order with a time of its own: it is kept for you for the time the shop set, two hours at most, and then it ends by itself (our server closes it at your phone's next check-in, or within 15 minutes at the latest; once you have said you are at the counter, two hours after you reserved), and from then on it no longer keeps your visit. The visit is kept whole for that time, your selfie with it if it has one, so the team can finish the order and tell you it is ready. If you have walked out, you are not shown to other guests or counted meanwhile; if you come back in, it is the same visit, with no new selfie, and you are shown and counted again only once your phone has proved it is inside. If you are still inside with the app open, you stay on the list and are counted as before. A new selfie is asked for only once the order is done or its two hours are up, when the visit ends. On your own phone only, Wassaaa keeps a read-only copy of each of your chats that has something written in it, made each time your phone leaves the place (when you end the visit, and also when you walk out without ending it) and kept for 24 hours from the last time it left, and receipts of your orders for 90 days. The chat copies are encrypted on the device; neither is ever uploaded, and both are deleted on that schedule; the server's copy of a chat is still removed when the visit ends. So that a visit you walked out of can be carried on, read from outside or ended from outside, your phone also keeps one entry in its secure storage, with a line for each place where you have a visit (the pass for that place): the place's identifier and name; the visit's identifier; whether you are among the faces there or here to order, and whether our servers hold a selfie for that visit; the name you have there; your table there, once you have given one (from a table's code, or as your last order named it), so that your next order there starts from it; whether the place takes orders in the app, once your phone has learned it, so that the app's words for that visit are right when it cannot ask; where an order of yours there was open when your phone last heard of it, the time until which it may still be open (two hours from when you placed it), so that the limit of six described above never ends a visit with an order waiting in it; for a visit with a selfie, the address of your photo and where the copy your phone uploaded is, so that ending the visit from outside can take it back; the secret that opens that visit's chats, from which your phone makes each chat's own keys (a visit that never had a selfie has no chats and no secret); a fingerprint of the key the other person promised in each of its chats, as your phone first saw it, so that a key or a promise that changes is noticed even after the app was closed (described below); which account the visit belongs to, so that a pass is never shown or used under another account on this phone (one found there is removed); when you last came in there, by your phone's own clock, which only puts the passes in order; and what tells the phone how long to keep them (the time the visit ends, the later time an open order may keep it until, and whether the place's door has since refused the visit). It stays on this phone only: it is never uploaded, and it is not restored to another phone. Each line is kept until its visit's end as your phone last heard it, and removed sooner when that visit is ended (by End visit, by a removal or by an erase), when you sign out or change account, or when it is the oldest of more than six kept visits with a selfie that no open order is keeping, and the app ends that visit to make room. In two cases a line can outlast its visit, and in that time the app does not say the visit is kept: when your phone went down with an order open whose own two hours end later than the visit does, until the end of those two hours (so at most two hours past the visit's end), because that order may be keeping the visit and your phone, while it is down, cannot hear when the order is done; the extra time is taken back as soon as your phone hears that the order is done, or is told the visit's end with no order keeping it; and when the place's door has refused the visit, until your next entry there is answered, or until the end your phone had been told if that comes first. If your phone has no connection when the app is opened, the app cannot check our servers' clock. It then removes what it kept for a visit (this entry, the note described next, and what goes with them) only once the phone's own clock shows more than 24 hours past the visit's end; anything nearer than that is removed as soon as the app is next connected. When you end a visit, the app also keeps a note that the visit has yet to be ended on our servers, written before the request is sent and removed when they have answered it (so for a moment at every End visit, and for longer only when they cannot be reached, as above): the place's identifier, the visit's identifier, the time the visit would end by itself, whether it was a visit to order (the request that ends one is another), when it was ended, by your phone's own clock (the request carries that moment, so that it ends no visit you came back into after it), where an order of yours was open as you ended the visit, which order it was and what you chose for it (to cancel it, that you had it, or to leave it as it was), which the request carries too, and which account ended it, so that the request is only ever sent by that account; and nothing else. The note is kept in your phone's secure storage, on this phone only and in no backup, and is sent nowhere except as that request. It is deleted only when our servers have answered the request, when the visit's own end has passed (ten hours at most), and when you sign out, sign in to another account or erase everything; a request that fails is sent again. On an iPhone these two entries stay if you delete the app: each is void once its time has passed, and is removed the first time the app runs again and is connected, or once a day has passed by the phone's own clock. So that your conversation with a place's team can be found again after the app was closed, the app also keeps, in its ordinary storage on your phone, for each of the last ten visits in which you wrote to a place's team: the visit's identifier, the place's identifier and the conversation's identifier, and nothing of what was written. A line is removed when your phone learns that its visit is over, and every line when you sign out or change account; one whose end your phone never hears of stays until ten newer visits push it out, and "Erase everything about me" clears them all. During a visit the words of your chats are kept in the app's memory and are not written to your phone, with one exception: a message you have written that has not been sent yet (your phone had no signal, or had been asleep) is kept on your phone, encrypted, so that it is not lost if the phone closes the app. It is deleted as soon as it is sent or refused, when you end the visit, sign out or change account, and at the latest when the visit ends: your phone goes by the end our server gave it and, where it has none, by the longest a visit can last (eight hours, and two more for an open order), counted from when you wrote the message. Your phone also keeps one short list for the visit: which messages you deleted from your own phone ("Delete for me"), and which you deleted before they were sent. It names the messages and holds none of their words; it is encrypted on your phone, left out of your phone's backup, and deleted when you end the visit, sign out or change account, and at the latest when the visit ends, worked out the same way, counted from when the list last changed. (A message you delete before it is sent is not sent. A phone cannot always know, though: if an earlier try had already reached our servers, your phone deletes that copy for everyone when it finds it, which leaves the mark described above.) To count what is new in each chat, the app also keeps in its ordinary storage on your phone, for each chat, the number in the conversation's order of the latest message of the other person's that you have seen there, and nothing of what was written; a chat's number is kept until the visit it belongs to ends at the latest, and all of them go when you sign out, change account or erase your data. If you turn "Read receipts" off, the app keeps that choice in its ordinary storage too, only while it is off; signing out or signing in to another account leaves it as it is, and erasing your data clears it. A photo or a voice note that you send or open during a visit, one waiting to be sent included, is kept as a file in the app's temporary folder and deleted when your phone leaves the place, whether you ended the visit or walked out (if the app was closed before that, the next time it leaves one). One you open from a chat read from outside is kept the same way, and deleted when the app hears that its visit has ended, or the next time your phone leaves a place, whichever comes first. A view-once photo is never kept as a file on the phone that opens it. (A phone on an older version of the app keeps no such message, and instead keeps the open conversation in an encrypted file during the visit, deleted the next time the app starts.) Also on your own phone only, encrypted and never uploaded: the list of people you have met, each meeting for 180 days, or until you turn it off in Settings, block the person, or erase your data. The chat copies, a message waiting to be sent and the list of people you have met are left out of your phone's own backup (to iCloud, Google or a computer), and the key that opens them is kept for this phone only, so they cannot be opened on any other phone. On an iPhone, your order receipts, your settings (whether a blink takes your selfie among them, and, on an older version of the app, your choice of "Meet people"), the notes of a place that has still to be told that you left the faces and of an entry a place has not answered yet, the moment your phone gave its last request that changes what you are at a place, the lines just described that say which conversation with a place's team belongs to which visit, and a block that has not reached us yet are kept the ordinary way: like most things an app keeps on a phone, they can be part of that backup, if you have one switched on; that backup is yours, and Wassaaa cannot read it. On an Android phone, Wassaaa tells Android to leave everything it keeps out of the phone's backup and out of a copy made to a new phone, so if you reinstall the app or move to a new phone, Wassaaa starts fresh there. Android's own backup stays off and nothing else is kept in a backup or a transfer; the single exception is the random number of your Rewards card, which your own iCloud Keychain or Google Block Store keeps. The key to each chat for a notification is kept for this phone only, so it cannot be opened on any other phone, and a reply waiting to be sent is left out of the backup too; your choice of "Show message text", the counts for the store's rating sheet, the random identifiers of the visits you have sent your stars for (until each ends) and the random identifiers of replies you typed in a notification (thirteen hours, never their words) are kept the ordinary way on an iPhone, like your other settings, so a backup of the phone, if you have one switched on, can hold them. (A phone on an older version of the app keeps the chat copies and that list the ordinary way too, and an Android phone on an older version keeps its receipts and settings that way as well.) So that an accident can be undone (a place's menu or a course deleted by mistake), a safety copy of our database is made once a day and each copy is deleted after 30 days. A copy holds what the database held on that day, so something that has since been removed, your visit and its chats included, can remain inside a copy for up to 30 days. A copy is not read for any other purpose; visits and chats are never put back from one; and if a copy is ever used, whatever was erased or deleted after it was made is removed again. Photos, voice notes and the pictures on a menu's items are files, not database records, and are not in the copy; a menu put back from a copy may point at a picture that has since been deleted, and the place adds it again. If you are venue staff and turn on phone alerts in the staff console, that browser's push token is stored under your staff account until you sign out there or turn alerts off. If you sign in to staff mode in the Wassaaa app, that phone's push token is stored under your staff account as well, with the language the phone is set to, so a guest's message or a new order can alert the phone while it is locked, in that language. It is the same token the app keeps for your own notifications, it is used only to send those alerts, and it is removed from your staff account when you sign out of staff mode or when that account is deleted. The same record carries yes-or-no marks, which the app and the console write: whether it shows a number on its icon, and, written only by the versions of the app from October 24, 2026 until this one, whether this phone plays the team's own alert sound (this version gives the team's alerts the phone's own notification sound, writes only the number mark, and leaves the sound mark out the next time it writes the record; a browser's record carries only the first). None of them says anything about you. With the number mark on, each alert also carries the number to show, how many guests are waiting for a reply and how many orders are waiting to be closed at the place the alert is about, and no name; when that count cannot be read, the alert carries no number and leaves the icon as it is. A phone or browser on a version from before October 24, 2026 writes neither mark and is sent alerts as before. For as long as staff mode is part of the Wassaaa app, a phone that is both a guest's and a team member's therefore holds one push token, stored under both accounts: your own as a guest, and your staff account. No guest and no place's team can read either copy, but on our servers the two accounts can be seen to share a phone. Erasing your data as a guest, or deleting your guest account, takes the token off your guest account only: your staff sign-in and its alerts stay until you sign out of staff mode.
If you use Wassaaa Team. A team member's phone may run a separate app, Wassaaa Team, instead of staff mode in the Wassaaa app or as well as it. If you sign in to Wassaaa Team, that phone's push token is stored under your team account, with the language the phone is set to, so that a guest's message, request or order can alert the phone while it is locked, in that language. It is Wassaaa Team's own token, not the Wassaaa app's, and Wassaaa Team never signs in as a guest, so using it joins your team account to no guest account. The token is used only to send those alerts, your shift's alerts and the count below, and it is removed from your team account when you sign out of Wassaaa Team or when that account is deleted. The same record carries the yes-or-no marks that a phone in staff mode carries (whether it shows a number on its icon, and, from an older version of Wassaaa Team only, whether it plays the team's own alert sound) and one more that says the token is Wassaaa Team's, so that our server sends it the form of alert that app shows. None of them says anything about you. When your team account has a phone with Wassaaa Team, our server sends the account's team alerts to that phone and not to its other phones that have only staff mode, so that you are alerted once, except the phone you started your shift on at that place, which is always alerted (the device noted for your test alert, A team member's shift); a browser that has alerts on is alerted as before. For as long as staff mode is part of the Wassaaa app, what is said above about it stays true of it. What an alert carries. A title and a line in our own words, such as the number of items, the total and the table or room of an order, and, for Regulars, the reward as the place wrote it; and, first, the name the guest goes by for this visit. It never carries a guest's own words, what was ordered, a guest's account, a face, or anyone's position. It reaches the phone through Apple's or Google's notification service, as the alerts of staff mode do. Buttons on an alert. An alert on a locked phone can offer "Take it" and "On my way", and, when your shift is about to end, "Keep going". On an iPhone each first asks for Face ID, Touch ID or your passcode, so that someone holding your locked phone cannot act as you; on Android the phone's own unlock comes first, and Wassaaa Team opens to finish the step. "Take it" takes the request as the button in the app does, and "Keep going" adds two hours to your shift, as it does in the app. "On my way" takes the request and also sends the guest the words "On my way." as your reply, which they see with the name you show on your replies; to send it in their language, our server uses the language the guest's own page or app said when they began that conversation or last wrote in it (kept with the conversation, where neither the guest nor the team can read it), or else the language kept beside the guest's own push token, as for every notification to that guest, or else English. If a teammate has already taken the request, nothing is sent; nor is it when the team has already answered the guest's last message, and pressing it again while the guest waits for the same reply sends nothing more. No button closes an order or says that a guest is at the counter. On an iPhone, a button you press is kept until it is carried out, in one file in the app's private storage: the place, the conversation and the button, never words, protected until the phone is first unlocked and left out of backups. It is forgotten when you sign out, and after twelve hours at most. The count on your lock screen. While you are on shift, Wassaaa Team can keep one line on an iPhone's lock screen (a Live Activity, which the Dynamic Island also shows) and, on Android, one quiet ongoing notification: how many guests still here are waiting for a reply, how long the oldest has waited for one, and how many orders are waiting to be closed. A guest who leaves stops counting within 15 minutes of the place no longer counting them as here. Each update to an iPhone also carries the time your shift ends, after which a line that is no longer updated is dimmed. To keep it up to date, our server keeps for you at that place, where only our server can read it: the kind of phone, the key of this phone's alert registration, the Live Activity's own token (an iPhone's only), when it registered, when it last sent an update, and the last numbers it sent. Numbers only: never a name, a table, a guest's account, a photo, or anyone's position. They reach the phone through Apple's or Google's notification service. The registration is deleted when your shift ends (A team member's shift), or sooner when the phone's token stops working, and with the place if it leaves Wassaaa. Crash reports. If Wassaaa Team fails while you are signed in to it, it sends a crash report as the Wassaaa app does (Crash reports): the error and where in the app's code it happened, the phone's model and system version, and Crashlytics' own random identifier for the install; never your account, a guest's words or anyone's position. "Help improve Wassaaa Team" in its settings (the gear) is on until you turn it off; off, it sends none and deletes the ones not yet sent. On your phone. Wassaaa Team keeps on your phone: the sign-in; the places you are on, the place you chose and the places' names (so that an alert can name its place and, on Android, so that the count can be drawn while the app is closed); on Android, for each place, the time of the last update of the count and the time its shift ended (so that an older update cannot bring the count back); the guests' voice messages you play, as temporary files that are deleted when you close the conversation, when your shift ends, when you sign out and when you delete your account, and a voice reply of yours until it is sent or discarded; and, on an iPhone, a button you pressed until it is carried out (above). Two choices belong to the phone and not to your account: on Android, whether Wassaaa Team has already asked the phone's question about alerts, and your choice of "Help improve Wassaaa Team", kept only while it is off. Signing out removes everything else listed here. On Android none of it is in the phone's backup; on an iPhone the file of a pressed button is left out of backups and the rest is kept the ordinary way, so a backup of the phone, if you have one switched on, can hold it. The table in section 6 says how long each lasts.
Nearby Interaction pairing tokens are short-lived operational data. Access is revoked immediately when the request, order or visit ends, and any token left by a lost connection becomes unusable after its five-minute expiry. We do not retain continuous UWB coordinates or movement history. The colour that Light up gives a pair is held for 30 seconds and then let go, even if neither phone could tell our server so, with no chat or person left against it in the place's list of colours; the chat keeps its own record of the light (the colour and its two times, readable by the two of you only) until a phone ends Light up or, if none does, until you start to find each other again or the chat ends.
“Anonymous” means your temporary handle at a place is not a public account profile. It does not mean that activity is invisible to Wassaaa: authenticated service records, device signals, abuse reports, and operational logs may be processed as described here. Private chats between two guests are end-to-end encrypted: the words of a message are sealed on your phone before they are sent, and only the other person's phone can open them. Photos and voice notes are sealed the same way, each with a key of its own that travels inside the encrypted message; Wassaaa stores and relays bytes it cannot read, and checks only their size and how long they are kept. If the other person's phone has an older version of the app, which cannot open sealed files, the app does not send a photo or a voice note at all, and tells you so. (A phone that is itself on an older version still sends its own the earlier way whenever it, or the phone it is sending to, cannot seal them: encrypted in transit and stored by Wassaaa, which could read them, until the chat ends. When the other person's phone is one that cannot seal, the chat's lock tells you that what they send you is not sealed.) Each chat has keys of its own: your phone makes them from one secret it keeps for the visit and from the chat's identifier, so a chat always gets the same keys and no other chat gets them, and nothing more is kept for them. When you say yes to someone, your phone sends with it a promise of the key it will use in the chat that would open with that person: a one-way code made from the key, not the key itself. When a match opens a chat, the two promises are kept with the chat and deleted with it. The phone of whoever said yes second publishes its key first; the other publishes its own only after it has read that key and checked it against the promise. From the first time your phone sees the chat, it holds to the other person's promise as it found it, and keeps it in the pass for that visit (described above): it seals your messages only to a key that keeps that promise, and does not show a message sealed with any other. If the other person's key or promise ever changes, the chat says so where it happened ("Their security code changed"), its lock shows a warning, and your messages stay sealed to the key your phone first saw. (In versions of the app before this one a hello carries the same kind of promise.) Each chat shows four symbols made from both phones' keys for that chat; two people who are together can compare them. Because each phone promised its key before it saw the other's, and the chat says so if a key changes, matching symbols are a strong check that the two phones hold each other's keys. It is not a proof: it would not stop someone who controlled our servers and set out to fool it. Anyone who got that one secret from your phone during the visit could read all of that visit's chats, earlier messages included. A phone on an older version of the app uses one key for the whole of a visit, in every chat of that visit, and a new one for the next visit; in a chat with such a phone, the symbols are a quick check, not a guarantee. Conversations with a place's team are not end-to-end encrypted: the place's staff and the Wassaaa operators can read them, so do not send sensitive information there.
What is kept and for how long
This table gathers the periods stated through this policy; the sections say what each thing is and who sees it. "Erase everything about me" and deleting your account remove what is tied to you sooner, as described in section 13. In the app, Settings › Your data › What Wassaaa has about you shows, in plain words, what Wassaaa keeps about you right now, where, and until when, each line opening the control that changes it; it never shows a number of people, chats or yeses, or of orders closed as not collected.
Each period is when a thing stops being used and can no longer be seen. Its record is deleted by the next clean-up after that, and the clean-up runs on a clock: every 15 minutes for whatever lasts minutes or hours, so such a record can stay up to 15 minutes past its time; and once a day, counting whole calendar days, for whatever lasts days or longer, so such a record can stay up to two days past. What is kept only on your phone is deleted by the app itself, the next time it is opened after the period ends.
| What | Kept for |
|---|---|
| As a guest, on our servers | |
| Your visit, and everything in it: your handle and selfie, with the selfie's smaller copy, a lighter copy of each of the two, and a tiny blurred copy of the smaller one; your private chats, with their photos, voice notes, receipts and the marks that a message was deleted, the reactions in them, the marks that a view-once photo was opened, whether you muted one, and the count of your messages your phone writes beside them; your conversation with a place's team, and an order in it, and the language your app or page said there (which only our server reads); the note our server keeps while an order of yours is open, so that it can tell the place's team (which order, and when a check found you outside); your tagline for the visit and your section; which version of the chat your app has (a number); the random identifier of the entry that put the visit among the faces; the count that limits your private chat messages in a minute; and, where your phone was away from the visit for a stretch and came back, how long it was away (a number). A visit you came into to order is the same, with an automatic name and no selfie | Until your visit ends: eight hours after you came in at the latest, and sooner when you press End visit, erase everything about you, or are removed. Walking out, locking your phone or closing the app neither ends it nor makes it longer. If an order of yours is still open when the eight hours are up, all of it is kept until the order is done, at most two hours more. A reservation at a shop is kept for you for the time the shop set, two hours at most, and then it ends by itself, within 15 minutes of its time at the latest (or of two hours after you reserved, once you have said you are at the counter); the conversation it was in stays with the visit. Some of it can go sooner than the visit: a private chat ends when the other person's visit ends; a conversation that the place's team closed is deleted 30 minutes after it is closed; and a voice message goes within a day in any case. A phone on an older version of the app: a visit it walks out of is kept for two hours after the phone was last there, and a chat between two such phones is removed at the latest four hours after it starts. If an order of yours is still open when the visit ends, its card stays with the place's team: see the row for it below. |
| Your place on the list of people there | While you are there with the app open; and for the first 30 minutes after your phone last confirmed you were inside you are still shown, dimmed (you can turn this off). End visit removes you at once when your phone is connected, and otherwise as soon as it next is. Entering another place removes you at once too, and leaving the faces as End visit does: at once when your phone is connected, and otherwise as soon as it next is. If you are here to order you are on no list, and you are counted in the place's number for the same 30 minutes at most. |
| What goes when you leave the faces during a visit (you tap "Exit meet"; on an older version of the app, you turn "Meet people" off): your selfie and its smaller copy, your place on the list, your tagline for the visit and your section, your name in what our servers keep of the visit for your chats, your posts on "Everyone here", your seat at "Your table" and what you wrote there, and each yes you said that had not been matched | Deleted as soon as your phone can tell our servers, at the place you are in (and, when an older version of the app turns "Meet people" off, at every other place where a visit of yours with a selfie is kept): at once when it is connected, otherwise when it next is, and that selfie stays until then, at the latest until that visit ends. The rest of the visit stays until the visit ends: your private chats, to read, and your conversation with the place's team with any order in it. Your answers to the place's questions, with any entry in a draw, stay too. If you tap "Order only this time" on a kept pass instead, the same goes except your selfie, your name, line and section, and each yes you said: these stay with that visit until it ends (or, on an older version of the app, until you turn "Meet people" off). |
| A photo you replaced with a new one during a visit: the old photo and its smaller copy | Deleted from our servers as soon as the new photo is in place. If that step is cut short, they go when the visit ends at the latest (the clean-up in section 6 finds anything left). |
| The counts that stop a script from running a place's number up: how many new visits your account began in the hour, with a selfie or without, and how many times in the hour you changed the place you are counted in; and, so that copies of your data cannot be asked for without limit, how many copies of your data you asked for in the hour | Until their hour has ended, within a day at most. |
| The notes of the one place you are counted in and of the one place whose list of faces you are on (each: the place, the visit, and when your phone's check put you there) | Until that visit ends, or you erase your data; anything left goes when the last visit in that place ends. The note of the list you are on also goes when you leave the faces. No phone and no place's team can read either. |
| The note that a request of yours which changes what you are at a place, or our clean-up of a visit of yours, is at work, so that two such requests are answered one after the other (a random identifier of that work, and the moment it stops counting) | While that work is done: deleted as soon as it is. One left by work that was cut short stops counting after thirty seconds at most, and is removed the next time such work is done for your account, by our clean-up once a minute has passed since it stopped counting, or when you erase your data. No phone and no place's team can read it. |
| The note of your latest request at a place that changes what you are there (coming in, joining or leaving the faces, ending a visit), so that one that arrives late does not undo what you did after it: the moment it was asked for, by your phone's own clock, and when our server acted on it (two moments for each place, from this version of the app, and nothing of what the request was) | While your visit at that place lasts; where no visit of yours stands there, 20 minutes after it was written. Or until you erase your data. No phone and no place's team can read it. |
| The note that a selfie was used to go into a place (which upload, which place, when) | Used for eight hours at most, and deleted within 16 hours. A class selfie's: used for the class day, and deleted within a day. |
| The note that you deleted a message for everyone | Until the other phone has used it, and within two days at most. |
| A "Keep in touch" tap | Until its chat ends. |
| A yes you said to someone | Until the two of you match (both yeses are then deleted and a chat opens), until it is taken back, until your visit or theirs ends, until either of you blocks or reports the other, or until you leave the faces ("Exit meet"; on an older version of the app, "Meet people" turned off), whichever comes first. |
| Whether your visit can be matched, and what our server keeps with your yeses: how many you said in a minute, how many times you joined or left the faces, your own list of the people you said yes to, the number your phone gave when it last asked for that list (or the number of a note that had to go, if that is higher), and the notes of a yes that was taken back and of a match being finished | Until your visit ends. A line of your list goes sooner: when you take that yes back, when the two of you match, when you block or report them or they block you, when they erase their data while they have a visit in the place, and when you leave the faces ("Exit meet"; on an older version of the app, "Meet people" turned off). A line your phone has been shown also goes within about 15 minutes after their visit ends, and sooner if your phone asks for the list first and the list can no longer show it. A line it has not been shown stays until your phone next asks for the list, which either shows it or takes that yes back, or until 200 newer such lines push it out. A note that a yes of yours was taken back goes sooner only when you say yes to that person again, when that person erases their data while they have a visit in the place, or when more than 200 notes are kept and it is among the oldest. The note of a match being finished goes when its chat is open. Your tagline among the guests who can be matched is there only while you are on the place's list. |
| A wave or a hello (versions of the app before this one) | Until it is answered, until either visit ends, or 15 minutes, whichever comes first. |
| The count that limits your hellos to one person, and the notes of who said hello to whom (versions of the app before this one) | Until your visit or the other person's ends. Anything left is deleted when the last visit in that place ends. |
| The place's own record of an order (no name, photo, note or account) | 90 days after the order. |
| An order's card that a place's team keeps after your visit ended with the order still open: what you ordered, the total, your note, the table or the counter (at a hotel, or for an order brought to a room, the room number), the name you went by for the visit, how far it had got, how the visit ended and when, and when your phone was last seen (for a reservation, also until when it was kept; for a hotel's request or an order brought to a room, nothing about your phone) | Until someone on the team closes it, and for up to four hours after your visit ended (after the team closed it, if it closed the order as not collected while you were still there). An erase takes your name and your note off it at once. |
| Which account an order's card was for, kept by our server beside the card, where no phone and no place's team can read it | As long as its card: it goes with it. An erase removes it at once. |
| What a reservation at a shop that keeps a count took off the count, so that exactly that can be put back: the reservation's identifier and its conversation's, the items and how many, and the time (never a name or an account) | Until the reservation ends, and no longer than two hours from when it was made (two hours from the moment the team undoes a close, when it does). One let go because the reservation ran out of time or was closed as not collected is kept six hours more, so that the team can undo that, and is then removed by our next clean-up. Only our server can read it. |
| How a visit ended, when someone ended it (End visit, a removal, a conversation cleared in a browser), noted by our server so that an order's card can say so | Until the visit's records are gone and any card is made, and an hour at most. No phone and no place's team can read it. |
| The count of the orders that places' teams closed as not collected for your account, and of reservations whose time ran out before you collected them: a time for each, and nothing else | 30 days for each, or until you erase your data or delete your account. No place's team can read it, and your phone reads it only in a copy of your data that you ask for. |
| The last place you were counted in, and the last time your phone showed it was inside, once that visit has ended (for the check that no one arrives faster than a plane) | 24 hours, and deleted within 15 minutes after; at once when you erase your account. No phone and no place's team can read it. |
| A one-time number our server gives for your next call at a place's door (entering, coming in to order, a class code, paying, a prize question's answer, spending a reward), so that the call's proof can be used once | Five minutes, and deleted within 15 minutes after; at once when you erase your account. No phone and no place's team can read it. |
| A reward waiting for a manager's OK: which reward, its points, and a one-way code of the account that asked | 15 minutes, and deleted within 15 minutes after. No guest can read it; the place's owners and managers see the reward and the time, never why it waits. |
| The public half of the key your iPhone makes for Wassaaa's checks at a place's door (App Attest), with the key's id, the app and the kind of build Apple named, the counts of its last signatures, and when it was made and last used | Until you erase your account. It can only check the app's own signatures, and says nothing about you. No phone and no place's team can read it. |
| A count for each day, across all phones, of how many Android door checks got each kind of Google Play Integrity answer, with no account, place or time of day | At most 60 days. It names nobody, and no phone and no place's team can read it. |
| Cards declined while you paid in the app: a count for the last hour, under a one-way code made from your account (never the card or the account) | Used for an hour, and deleted within 25 hours of the first card declined in that hour; at once when you erase your account. No phone and no place's team can read it. |
| A payment you disputed with your bank: a line under a one-way code made from your account (never the card or the account), each dispute's state, when we heard of it, the place and the payment company, with a note from each dispute to the code; and the code itself on each payment's record; for a payment made on a phone that keeps the app's random code, the same line under a one-way code made from the phone's code, and that code on the payment's record | The code, as long as the payment's record (90 days). A dispute's line: until the place wins it, and a week after; until our support lifts it, and 180 days after; at once when you erase your account. The phone's line: the same, except that erasing your account leaves it, and a dispute on it goes at most 180 days after its newest word. That your account's code was erased: 100 days. No phone and no place's team can read any of it. |
| How many of your orders a team has handed over, and when the last was (a count, never where or what), and a scrambled code of the visit it was handed over in (it names no place or time; the next handover replaces it) | Until you erase your data or delete your account. Only our server can read it. |
| A team member's weekly counts at a place: rewards confirmed, orders declined after starting and orders closed as not collected, under a code that stands for them at that place, never their account | Three weeks. Only our server can read them. |
| A post on "Everyone here" | Four hours after you wrote it, or until your visit ends if that comes first. |
| A post a place's team took down (its words, the reason, your account) | 180 days. |
| Your seat at "Your table", and what you wrote there | Until your visit ends, or you leave the table's conversation. |
| Your answer to a place's own question, your entry in its draw, the one-way code that keeps one entry for each phone, and the note that your account answered it | Your answer, your entry and that code: until your visit ends, or until the question is cleared. The note that your account answered (never which answer), and the question itself with its numbers and its winner's name for the visit: until the place takes the question off, or until 30 minutes after it closes or after its last draw, whichever is later, and at the latest three hours after it was last touched, with our next clean-up. |
| The mark that your visit is not shown a place's card at the top of its Menu tab (the hold-back) | For that day of the place only, readable by your account alone, and then deleted. Nothing else about you is kept for it. |
| A place's counts of orders by item and part of the day, and of items added from its card by kind | Kept, only as numbers for the place and the day, never tied to a person. |
| A star rating and its comment | 30 days after you leave it. The place's daily star counts stay, as numbers only. |
| The one-way code that keeps your rating in a place's public stars | 180 days. |
| The time of each rating from an account under 30 days old that counted at a place, so that a rush is held for review (filed under the rating, never under you) | Used for 24 hours, and deleted within two days. Only our server can read it. |
| The one-way mark a place keeps of your visits (new or returning, counted orders, and the night of your last counted order: a date) | 60 days after your last visit there. |
| A place's activity counts, per day and per hour, and the hours of its day in which something of the place's was running (a kind and an hour, no guest) | 400 days, as numbers only, never tied to a person. |
| A place's counts of its visits by month: how long a visit lasted against whether an order was counted, how quickly the team first replied against the stars given, and how long visits lasted during an event (a count in each cell, never a visit, a guest or an account) | 13 months, counted from the month the visits began, then deleted by our daily clean-up. |
| The dates of your last three visits to a place, inside the one-way mark above (dates only) | With the mark: 60 days after your last visit there. |
| The tags and menu items in posts on "Everyone here", counted for a place: how many posts, replies and different guests, and in which hours (never who) | A tag used by 3 or more different guests that day: 400 days, with the place's activity counts. A tag used by fewer is deleted with its counts when the place's day ends. Seen by the place's team and by Wassaaa's own operators. |
| The one-way code of your visit that lets a tag count you once | Until the place's day ends at midnight there, then deleted shortly after (within about ten minutes). No phone and no place's team can read it. |
| A note that an account was erased, so that its last visit is not counted in a place's visit facts (the account's identifier and the time) | A day, then deleted by our daily clean-up. Only our server can read it. |
| Where your message to a place's team has got to: when an alert for it was accepted, when the team opened it, which team member took it (the name that person shows on their replies) and when, the number of minutes the place has set for answering, when you were last told that nobody had picked it up, and, if a shift ended with it in hand, that person's name and the time | As long as your conversation with the team (the first row): until your visit ends, or until 30 minutes after the team closes it. |
| That your visit has already been counted as asking while the team was away today: a one-way code of the visit, the place's day and the time | Two days at most, and deleted within seven hours after. It is used only so that one visit is counted once in a day, and no phone or place's team can read it. |
| The safety record about you, if you were reported or removed | 180 days after the last report or action; if you erase your account within 30 days of a report, a removal or a pause, 180 days after the erase, with your account's id on the reports still open to our safety team and a note of the erase. |
| The count of guests who reported you in a place, the note of who they were, and whether each had a tie to you | Until you are removed from that place at three reports, until the place's day ends (the next 6 am there), or until the last visit in that place ends, whichever comes first. |
| When a report of yours last alerted our safety team (a time, under a one-way code) | Used for ten minutes, and deleted within seven hours. |
| How many reports your visit to a place has made (a number and when your visit began, under a one-way code) | Used for ten hours after your last report there, and deleted within sixteen hours. |
| A decision to keep you out of a place, or to pause your access | Until it ends: the place's day, 7 or 30 days for a place; 7, 30 or 90 days, or until lifted, for a pause everywhere. |
| Your phone's random code (on your phone), which code your account last came with, and a removal, a block or a dispute's stop on paying kept under the code (a dispute's under a one-way code made from it; on our server) | On your phone: until you delete the app on Android; erasing your data leaves it, and on an iPhone so does deleting the app. Which code your account last came with: until your account is erased. A removal under it: until the removal ends. A block under it: until the person who blocked unblocks or erases their account. A dispute's stop under it: until the dispute is won or our support lifts it, and at most 180 days after its newest word. Its one-way code on an erased account's safety record: as long as that record, 180 days after the erase. |
| A report, with the messages sent in it | Until it is closed, and for 12 months after that. It is then deleted, and only the number of reports deleted at that place is kept. Its line in the safety team's queue: 180 days after the report was made. |
| Limited operational logs | May be kept longer than the visit, for abuse prevention, support and legal compliance. |
| Your request for Wassaaa at a place ("Bring Wassaaa here") | 180 days. |
| Your note that something is wrong with a place that has not joined | 180 days after it is handled. The count of such notes: until the day ends. |
| The people you blocked (who, the handle they had, when, and the place's name) | Until you unblock them, erase your data or delete your account. |
| The note that your list of people you blocked is full (200 people; a number) | Until your list is shorter, or you erase your data or delete your account. |
| The server's own note of who blocked you, and the line that tells your phone to leave them out of the people you are shown | The note: until they unblock you, or either of you erases their data or deletes their account. The line: while they are on the place's list and you have a visit there; it goes when either visit ends, when they unblock you, and when they leave the list. |
| The email address you linked to your account, if you did | Until you delete your account. |
| Wassaaa Plus on your account: whether it is on, when it ends, and through which store and plan (a copy of what Apple or Google reports; the payment itself stays with the store) | While the account lasts: it changes when the store reports a renewal or an end, and it is deleted with the account. Deleting the account does not cancel the subscription in the store. |
| Your push token, the language it is sent in, and your notification switches, with the end of a pause you set and whether the phone shows faces in notifications | Until you erase your data or delete your account. A pause's end stops counting when it has passed, but it stays here until you pause again, press "Resume", or erase your data or delete your account. |
| What your phone's app store said of your age at the last check: that you are 18 or over, or that it gave no answer, and when it was written (never your age, nor the age range the store gave) | Until you erase your data or delete your account, or the store says you are under 18; a later answer replaces it, though "no answer" never replaces "18 or over". Only our server can read it, and it is in the copy of your data. It is kept as the record that your age was checked (section 11). |
| Whether this phone's app answers from a notification, and whether it opens a message's words now (two yes-or-no values, kept with its push token) | As long as the push token: until you erase your data or delete your account. The second is rewritten whenever you turn "Show message text" off or on, or the app lock on or off. |
| The note that you reacted to a message in a private chat, so that the other person is told once: who reacted to which message, and never the emoji | Until the chat ends; it goes with the chat. Our server keeps it under the chat, where no phone can read it. |
| The note that you were asked how a visit went (a time, on the visit's records) | Until the visit ends, when it goes with the rest of the visit. |
| A boost's counts, numbers only (cards shown, walk-ins, how many came because of it), with nothing that joins a person to a card | 400 days. |
| Nearby Interaction pairing tokens | Usable for five minutes at a time, renewed only while in use; deleted when the conversation, order or request they belong to ends. |
| The colour Light up gave a pair, and the mark that two phones found each other | The colour: 30 seconds, then it is let go, even if neither phone could tell our server so; if the chat ends while it shows, it stays set aside, for no one, until the 30 seconds are up. What stays against the five colours of a place, with no chat and no person, is when each was last given and when it ends: until the last visit in the place ends. The chat's own record of the light (the colour and its two times): under the chat until a phone ends Light up or, if none does, until the chat ends or the two of you start to find each other again. The mark that you found each other (that and when): under the chat until the chat ends, or until the two of you start to find each other again. No phone but the two in the chat can read the light or the mark, and no phone can read the colours of a place. |
| On your phone only | |
| What your phone's app store said at the last check that let you in (that you are 18 or over, or that it gave no answer), when that was, and which account it was last sent with | Until a later check replaces it, you erase your data, or you delete the app. If the store says you are under 18, it is deleted from your phone; if that is after the age screen, the phone keeps only a note that the answer with your account is to be deleted, until the deletion has reached our servers. |
| The boosted cards your phone showed you | 24 hours, on the phone only; the list itself is never sent to us or backed up, and cleared when you sign out or erase your data. |
| A place's messages to everyone inside, in Chats | Until your next visit begins, or you erase your data. |
| A message you wrote that has not been sent yet | Until it is sent or refused, or you end the visit, sign out or change account; until the visit ends at the latest. |
| The list of messages you deleted from your own phone | Until you end the visit, sign out or change account; until the visit ends at the latest. |
| What your phone keeps of a visit you walked out of, for each place where one is kept, so that it can be carried on, read from outside or ended from outside (the pass for that place): the place's identifier and name, the visit's identifier, whether you are among the faces or here to order and whether our servers hold a selfie for it, the name you have there, your table there once you have given one, whether the place takes orders in the app, until when an order of yours there may still be open, the address of your photo and where the copy your phone uploaded is, the secret that opens its chats, from which each chat's own keys are made, a fingerprint of the key the other person promised in each of its chats, which account the visit belongs to, when you last came in there by your phone's own clock, and what tells the phone how long to keep them (the time the visit ends, the later time an open order may keep it until, and whether the door has since refused the visit); and, for the visit you are in, how many were there when you last looked, and when (a number and a time), so that the place's bar shows it as the app opens | Until the visit's end as your phone last heard it; sooner when the visit is ended, when you sign out or change account, or when it is the oldest of more than six kept visits with a selfie that no open order is keeping. Longer, by at most two hours, when your phone went down with an order open whose own two hours end later than the visit does: until those two hours end, or sooner when your phone hears that the order is done. And, after the door has refused the visit, until your next entry there is answered or the end your phone had been told. The app does not say the visit is kept in that time. With no connection, only once the phone's own clock shows more than 24 hours past the visit's end. One entry in the phone's secure storage, on this phone only, with a line for each place: never uploaded, and not restored to another phone. On an iPhone it stays if you delete the app: it is void once its time has passed, and removed the first time the app runs again and is connected, or once a day has passed by the phone's own clock. |
| The note of an End visit that our servers have not been told of yet: the place's identifier, the visit's identifier, the time the visit would end by itself, whether it was a visit to order, which account ended it, when it was ended by your phone's own clock, and, where an order of yours was open, which order and what you chose for it (to cancel it, that you had it, or to leave it as it was) | Until our servers have answered the request, or the visit's own end has passed (ten hours at most; with no connection, judged as for the entry above); or until you sign out, sign in to another account or erase everything. In the phone's secure storage, on this phone only and in no backup. On an iPhone it stays if you delete the app, as the entry above does. |
| Which conversation with a place's team belongs to which of your visits: the visit's, the place's and the conversation's identifiers, for the last ten such visits | Until your phone learns that the visit is over, or you sign out or change account. A line whose visit's end your phone never hears of: until ten newer visits push it out, or you erase your data. |
| What your phone remembers of "Keep in touch" in a chat: that you tapped, and that the chat has offered it once; and, for a chat where you found each other, the time of each "You met" line and that the chat has made its one offer after meeting | Until the chat or your visit ends; ten hours at most. |
| Your choice of "Meet people", once you have turned it off (on an older version of the app: this version has no such switch) | Until you turn it on again, sign out, start as a new guest, or erase your data, or until this version of the app first starts. Nothing is kept while it is on. |
| Your choice of "Blink to take your selfie", once you have turned it off | Until you turn it on again or erase your data; signing out or signing in to another account leaves it as it is. Nothing is kept while it is on. Never uploaded. |
| Your choice of "Read receipts", once you have turned it off | Until you turn it on again or erase your data; signing out or signing in to another account leaves it as it is. Nothing is kept while it is on. Never uploaded. |
| Your choice of "Sounds" (the sound when you both say yes) and of "Haptics", once you have turned either off | Until you turn it on again or erase your data; signing out or signing in to another account leaves it as it is. Nothing is kept while it is on. Never uploaded. |
| Your choice of the app's look under "Look and feel" (night, daylight or the phone's own), once you have chosen one | Until you erase your data; signing out or signing in to another account leaves it as it is. Nothing is kept until you choose. Never uploaded. |
| Your choice of "Remember people I've met", of "Stay visible when you put your phone away" and of "City moments" (each kept as on or off), and the city whose announcements your phone follows | Until you change it or erase your data; signing out or signing in to another account leaves it as it is. Kept in both positions, on your phone only. The city is a subscription with Google's messaging service, left while notifications are paused. |
| Your choice of "Help improve Wassaaa" | Until you change it. Signing out leaves it as it is; an erase keeps it only while it is off, so that erasing never switches measuring back on. Never uploaded. |
| For each chat, the number of the latest message of the other person's that you have seen there | Until the visit it belongs to ends at the latest; all of them when you sign out, change account or erase your data. Never uploaded. |
| The note of a place where our servers have still to be told that you left the faces (you tapped "Exit meet", or "Not this time" where they may still have you among the faces, or, on an older version of the app, turned "Meet people" off; one for each place, written before the place is asked, and kept until it has answered): the place's identifier and name, the visit's identifier where your phone has it and its end, which account asked, and when you asked by your phone's own clock | Until our servers have answered, or that visit's end has passed; or until you sign out, sign in to another account or erase your data. In the app's ordinary storage on your phone, and sent nowhere except as that request. |
| The note of an entry among the faces that a place has not answered yet (one for each place): the place's identifier and name, a random identifier of the entry itself, your account's identifier, when it was asked for and when it was sent, the name it asked with and where the copy of its selfie your phone uploaded is (neither for an entry that carries a kept visit on; both go when you end your visit there), the end of your visit there where your phone already knew one, and whether you have ended your visit there since and when | Until our servers have said what your visit there is, that visit's end has passed, or ten hours after it was sent; or until you sign out, sign in to another account or erase your data. In the app's ordinary storage on your phone, and sent nowhere except as a request to that place. |
| The moment your phone gave its last request that changes what you are at a place (one number), so that a new request never carries an earlier moment than the one before it, even if the phone's clock has been set back | Until a later request replaces it, or you erase your data; signing out or signing in to another account leaves it as it is. In the app's ordinary storage on your phone, and sent nowhere except as the moment that request carried. |
| The last tagline you used for a visit, typed or picked (up to 40 characters), so that the box starts with it on your next visit | Until you change it, sign out, start as a new guest or erase your data, or delete the app. Never uploaded. |
| A pass (a no) you gave someone | Until your visit ends at the latest. It is held in the app's memory, never written to your phone's storage and never sent to us. |
| The read-only copy of your chats | 24 hours from the last time your phone left the place with that chat: when you end the visit, or when you walk out without ending it. A chat with nothing written in it gets no copy. |
| Receipts of your orders (the place, when, what, with the choices you made and the menu heading each item was under, how much and how it ended), shown in "Your orders" and, for one place, under "Your past orders here" on its menu | 90 days. |
| On an earlier version of the app only: your last order at each place, for "Same again": the place's identifier, and for each item its identifier, the choices you made on it (their identifiers) and how many (the last twenty places) | Deleted from your phone the first time the app opens after it is updated: the app no longer keeps it, and your past orders at a place are your receipts. Until then, until you order at that place again (it is replaced), until twenty newer places push it out, or until you erase your data; signing out leaves it as it is. Never uploaded. |
| The last menu your phone read at each place you went into, so that it can be drawn while the new one comes: the place's items with their prices, choices and tags, the address and the words of an item's picture (not the picture), the hours and, at a shop that keeps a count, the number the place's answer carried (the last twelve places) | Until that place's menu is read again (it is replaced), until twelve newer places push it out, or until you erase your data. Never uploaded; the picture itself is not saved on your phone. |
| The places you follow: each place you asked to hear about when it gets lively or when someone arrives (the place's identifier and when you asked, on your phone, with a subscription to that place with Google's messaging service) | Until its one alert has been sent (your phone ends the follow when it sees that) or you undo it; for an ask about someone arriving, twelve hours at most; or until you erase your data. The subscription is left while notifications are paused and joined again once the pause has passed and the app is open. Neither is kept against you in our database. |
| The reminders you asked for ("Remind me"): for each, the place's identifier and name, the moment's identifier and name, its start and when you asked, on your phone, with a subscription to that reminder with Google's messaging service | Until the reminder has come, you come into that place, 30 minutes after the moment's start, you undo it or turn it off, or you erase your data; if the place moves the time your phone moves the ask, and if the place calls the moment off it ends. The subscription is left while notifications are paused and joined again once the pause has passed and the app is open. Neither is kept in our database. Never uploaded. |
| The name of a reminder your phone has not yet been able to stop: the place's identifier, the moment's identifier and its start (the name of the reminder's topic with Google's messaging service), and the time after which nothing is sent to it, on your phone | Until your phone has left that topic, or until 30 minutes after the moment's start, whichever comes first; tried again each time Wassaaa starts and each time you come back to it. It names the place and the moment, never a person. Erasing your data removes it, though an erase made with no connection can leave a topic still to be left, and its name kept again, until 30 minutes after the moment's start. Never uploaded. |
| Your choice of "Reminders you asked for", once you have turned it off | Until you turn it on again or erase your data; signing out or signing in to another account leaves it as it is. Nothing is kept while it is on. Never uploaded. |
| Your choice of "Live now" in the evening, once you have cleared it (one word) | Until you choose "Live now" yourself or erase your data; signing out or signing in to another account leaves it as it is. Nothing is kept until you clear it. Never uploaded. |
| Which of the three first-visit tips you have put away, and the identifier of the visit they began in | Until you erase your data; signing out or signing in to another account leaves it as it is. The identifier goes as soon as your phone is in another visit, and the three tips are then marked as put away. Nothing is kept until a tip has been shown or put away. Never uploaded. |
| The card of your visit on an iPhone's lock screen and in the Dynamic Island: the place's name (not while the app lock is on) and the time your visit ends | Until your visit ends or you end it, when the app takes it down; if it cannot (your phone asleep), it reads "Visit ended" until you open Wassaaa, and iOS removes it eight hours after it began at the latest, or up to four hours later. Kept by your iPhone, never uploaded. |
| The list of the places where you collect points ("Rewards"): the place's name, your points, your rewards and the day of your last purchase | Twelve months after your last purchase there, or until you erase your data, sign out or sign in to another account; at most two hundred places. The number of your card is also kept in your own iCloud Keychain or Google Block Store (section 1). Never uploaded. |
| What a visit that has ended leaves for its cards, so that the app's first screen can offer "Share your night": the place's name, kind and identifier, its cover picture's address (a place that has joined), the hotel it is inside, when you came in and when you left and, if your card there (Regulars) was full, how many counted orders it held | Twelve hours after you leave; or until you come in at that place again, end all your visits, sign out or erase your data. At most twelve places, one for each place. Never uploaded. Nothing is kept for a Campus class or building, a hotel itself, a place that asks for a code at its door or is not listed on the map, or a private event. |
| The list of people you have met | 180 days for each meeting, or until you turn it off, block the person or erase your data. |
| The random number sent with a GIF search | Until you erase your data or delete the app. |
| A block or an unblock you made that has not reached us yet (who, the handle they had, the place's name and when) | Until our servers have taken it or refused it, which is as soon as your phone has a connection and the app is open; or until you erase your data, delete your account or sign in to another account. |
| Whether the app lock is on, and your "Lock after" choice | Until you turn the lock off, erase your data or delete your account. |
| A copy of your notification switches, and any change to them that has not reached us yet; the end of a pause, while one runs; and whether this phone shows faces in notifications, once you have turned that off | Until you erase your data or delete your account. Nothing is kept once every switch is on, no pause runs and we have been told so; the faces choice is kept only while it is off. Your phone's copy of a pause's end goes when the pause has passed or you press "Resume". |
| Your choice of "Show message text", once you have turned it off | Until you turn it on again or erase your data; signing out or signing in to another account leaves it as it is. Nothing is kept while it is on. The choice is not uploaded as such: the push token's record says only whether this phone opens a message's words now. |
| For each chat that is going on, the key your phone's notification uses to show a message's words, with the chat's place, the moment it ends, the other person's account and whether a reply may be typed in it; and where your phone last knew you were inside a place, among the faces or here to order (one entry in the phone's secure storage; on an iPhone, shared with Wassaaa's notification extension) | A chat's line goes when the chat ends, which is when its visit ends, and when you sign out, change account or erase your data; none is kept while the app lock is on (the entry is deleted at once), and the keys alone go when you turn "Show message text" off. On this phone only, not restored to another phone, and never uploaded. |
| On an Android phone, the last lines of a chat's notification, with their words (up to six for each chat) | Until you open the chat or the visit ends; also when you sign out, change account or erase your data, turn the app lock on or turn "Show message text" off. Swiping the notification away does not remove them. Kept only where a key may be used, in the app's own secure storage; never uploaded. |
| A reply you typed in a notification that has not been sent yet | Until it is sent or refused, or the visit ends, whichever comes first; sealed in the phone's own file with any message of yours that waits, and left out of backups. On an iPhone the words you typed first wait in a file in the app's private storage, protected until the phone is first unlocked and left out of backups, until the app has taken them up and twelve hours at most. |
| A random identifier for each reply you typed in a notification, never its words, so that a reply handed over twice is sent once | Thirteen hours, or until you sign out, change account or erase your data. On an iPhone they are kept the ordinary way, so a backup of the phone can hold them; on Android they are out of the backup. |
| The counts that choose a moment for the store's rating sheet: visits begun, conversations in which you both wrote, orders picked up, when the app last asked, when something last went wrong, and when it was last told that an order had to be confirmed at the counter first | Until you sign out, change account or erase your data. The random identifier of each visit, conversation and order counted is kept for two days only, so that none is counted twice. The time of "confirm at the counter first" holds the sheet back for 30 days. Never uploaded. |
| Which visits you have already sent your stars for: a random identifier of each visit and the moment it ends, never your stars or your comment | Until that moment, which is never more than ten hours after you sent them, and until you sign out, change account or erase your data, whichever comes first; the app removes it when it is next opened after that. It is kept so that a visit you have rated is not asked about again, from the notification or at End visit, after the app is closed and opened again. Never uploaded. |
| The file of a copy of your data, while you save or share it | Only as long as that takes: the app writes it to a temporary file on your phone, offers it to you, and deletes it as soon as the share sheet has closed. On an Android phone the share sheet makes a second copy in Wassaaa's own cache, which the app deletes the next time it is opened or brought back to the front, and when you press Clear under Storage or erase everything about you; on an iPhone no copy is kept. Wassaaa keeps no copy of the file on our servers; where you save or share it is up to you. |
| What Wassaaa Team keeps on a team member's phone: the sign-in, the places you are on, the place chosen and the places' names; on Android, the time of each place's last count update and of its shift's end; the guests' voice messages you play and a voice reply of yours that has not been sent yet (temporary files); on an iPhone, a button pressed on an alert of a locked phone that has not been carried out yet (the place, the conversation and the button, never words); and, for the phone and not the account, on Android whether Wassaaa Team has asked the phone's question about alerts, and your choice of "Help improve Wassaaa Team" while it is off | Until you sign out of Wassaaa Team; the last two stay on the phone, the choice until you turn it back on. A guest's voice message you played is deleted when you close its conversation, when your shift ends, when you sign out and when you delete your account; your own voice reply, when it is sent or discarded; a pressed button is forgotten as soon as it is carried out, and after twelve hours at most. On Android none of it is in the phone's backup; on an iPhone the file of a pressed button is left out of backups and the rest is kept the ordinary way. |
| In a class (Campus) | |
| Your class selfie | Within one class day, and at most 16 hours. |
| Attendance, question counts, quiz answers and scores | 30 days after the class, unless the college has set another period between 1 and 365 days. After that the class keeps only its title, building, times and numbers that name nobody. |
| A browser student's request to join, with whether it came from the college's Wi-Fi (yes or no, never the address) | Until the class ends. |
| Whether an attendance a browser confirmed came from the college's Wi-Fi (yes or no, never the address) | As the attendance it belongs to. |
| The counter that tells your own page when your conversation with your instructor has changed (a number, nothing of the messages) | Until the class ends. |
| Your questions to your instructor | Closed when the class ends, and deleted with the other class records. |
| If you run a place | |
| Your sign-up or claim request | 180 days after it is decided, or 180 days if nobody has decided it. |
| The draft of your place, typed while you wait for approval (menu, hours, tagline) | Until your place is approved (it is copied into the place), the request is declined or you withdraw it, and 180 days at the latest. |
| A college's pilot request (name, email, college, role, buildings, instructors) | 180 days after you send it, whether or not it has been handled. |
| The terms you accepted, and the billing terms | While the place is on Wassaaa, and for six years after it leaves. |
| You on the place's team (email, name, role, and whether you joined by an invitation or in person), and the place's plan | While the place is on Wassaaa, or until you or we remove you. |
| The reference numbers of Stripe's messages | 31 days. |
| A refund or a dispute on a place's payment (the amount, the date, Stripe's reference) | Until our team has dealt with it, and 31 days after. |
| A staff phone's or browser's push token, with its yes-or-no marks (the number on the icon, and, from an older version of the app, the team's alert sound) | Until you sign out there or turn alerts off, or the staff account is deleted. |
| A Wassaaa Team phone's push token, with the language and its yes-or-no marks (the number on the icon, that it is Wassaaa Team's, and, from an older version, the team's alert sound) | Until you sign out of Wassaaa Team, or the staff account is deleted. |
| An instructor's push token in Teach ("Turn on alerts on this device"), with when it was last given and a mark that it is Teach's | Until alerts are turned off in Teach, you sign out of Teach on that device, a send to it fails, or the account is deleted. |
| How many quick classes an instructor started today in Teach, and which one is running | Two days. |
| A sign-in link sent to a team member: the address it was sent to, whether it is for the console, the app, Wassaaa Team or an invitation, the place and page it opens, when it was made, a one-way code of its secret, the identifier of an account that held the address without having confirmed it, and, once it is opened, which account opened it | A sign-in link: used for one hour, and deleted within eight hours. It works once. An invitation's link: 30 days, and the same account can open it again. |
| The proof that you hold an address's inbox (your account's identifier, the address and the time you opened its link or typed its code) | 30 days, or until the staff account is deleted. It is used only to let an invitation sent to that address join you to a team, and to let you set up two-step sign-in within 15 minutes of it. |
| Two-step sign-in, if it is on for you: which authenticator apps were set up through its steps (Firebase's identifier for each, and when) and eight backup codes, as one-way digests only; and, for thirty minutes after you open a sign-in link or start moving it to a new app, a one-way code of a key that lets that browser tab set it up | Until you turn it off, use a backup code, someone resets it, or the staff account is deleted; a key's code when it is used, or within a day. The app's secret key is held by Firebase Authentication (Google), never by Wassaaa. |
| Backup codes tried for one address, or from one network address: a one-way code of each, and how many this hour and today | A day, and deleted within seven hours after that. |
| That our server made your team account for an invitation, or that the Wassaaa team made it in the Admin Portal: the address, the time, and which of the two | Until the staff account is deleted. It is used only so that such an account is never treated as one someone else registered: its invitation finishes through it, and a first sign-in link or emailed code does not end its password or its phones. |
| That a join code made your team account: the address that was typed, the time and the place | Until the staff account is deleted. It is used only while that address is unconfirmed: the first time its real owner opens a sign-in link or types an emailed code for it that can join them to a team, the sessions the code made end. |
| A code to join a team or to sign in on another phone (a one-way code of it; for a join code, the place, the role, the account that made it and, as short one-way codes, up to three different addresses typed at it by people who were not signed in; for a sign-in code, the account it is for; and how many wrong tries it has had) | Used for ten minutes, once, and deleted within seven hours. Five wrong tries end it. |
| A 6-digit code to sign in to Wassaaa Team, emailed when someone asks for one: a salted one-way digest of the code (never the code), filed under a one-way code of the address (never the address), with when it was made, when it runs out, its wrong tries, and whether Wassaaa Team or the app's staff mode asked | Used for ten minutes, once, and deleted within seven hours. Five wrong tries end it, and a newer code replaces it. |
| What the screen that shows a join code keeps of it: when it ends, the role, and, once someone has joined, their first name, their email address, their role, the identifier of their account and the time | Ten minutes after the code was made, or after someone joined if that is later; sooner when the code is ended or a newer one replaces it. Deleted within seven hours. |
| That a join code told an address to sign in first: a one-way code of the address, and the time the code runs out | Ten minutes at most, and deleted within seven hours. It is used only so that a sign-in link can be sent to that address. |
| Counts that stop misuse of sign-in links and codes: how many links and emailed codes each address and each network address asked for (both only as one-way codes), how many codes each place and each account made today, and the wrong codes tried from each network address and account (one-way codes); an address's counts also hold its wrong emailed-code tries for the day | The counts of links and of codes made: until the day ends, and deleted within seven hours after. The wrong tries, of a code from the app or of an emailed code: ten minutes, and deleted within seven hours. An address's wrong emailed-code tries for the day: until the day ends, and deleted within seven hours after; once there have been ten, no emailed code works for that address until the next day. |
| A team member's open shift at a place: their name as they gave it, when it started and is due to end, whether its test alert reached the phone, whether a screen of theirs is open, the last time one was heard from, whether it was started by an older version's "On shift" switch, and whether the alert that it ends soon was sent | Until the shift ends: at the place's closing time plus half an hour (eight hours when it has no hours that day), or the end time picked when it started, at most 16 hours after it started, or sooner at "End my shift", at sign-out or when you leave the team. Deleted by the 15-minute clean-up at the latest. The place's active team can read it. |
| Which of your devices a shift was started on: the key of its alert registration, and whether it is a browser, an iPhone or an Android phone | As long as the shift: it is deleted with it. Only our server can read it. |
| What keeps the count on a Wassaaa Team lock screen up to date: the kind of phone, the key of its alert registration, the Live Activity's own token (an iPhone's only), when it registered, when it last sent an update, and the last numbers it sent (how many guests wait, since when the oldest has waited, how many orders are to close) | As long as the shift: it is deleted with it, or sooner when the phone's token stops working. Numbers only, never a name; only our server can read it. |
| The last test alert you passed at a place: the time and the kind of phone | Until you leave the team, the place leaves Wassaaa, or the staff account is deleted. Only our server can read it. |
| The markers of your open screens in the staff console and in staff mode, and in Wassaaa Team: a random key for each browser tab or start of the app, the time it connected, whether it is a browser or the app, and the time it went away | 24 hours after the screen went away, and deleted within 31 hours of it; a marker that never closed is deleted two days after it was made. Only our server reads them. |
| That your place has moved to shifts: the time the first shift was started there | While the place is on Wassaaa. |
| What your place has done for real towards "ready to open": the times the print kit was opened, a first answer to a guest, a first order, a first order brought to a table, a first reservation marked ready, a first order closed as not collected, and when every check passed (times only, nothing about a guest) | While the place is on Wassaaa. |
| Your choice to receive, or not, the Monday email of a place's week: on or off, and the time, under your account at that place | Until you leave the team or the staff account is deleted. |
| That an address stopped the weekly email: a one-way code of the address and the time | Kept, so that we never send that email to it again. |
| The week a place's weekly email was last made for an address, so that nobody is sent one twice: a one-way code of the address, the place and the week | Five weeks, then deleted by the next Monday's clean-up: within 42 days. |
| The stop link in an email we sent (an invitation or a weekly email): a random code that stands for the address's one-way code, the time it was made and, for a weekly email, that it is the weekly one | 180 days. |
| An email to someone who runs a place (an approval, a decline, an invitation, or a Monday email of a place's week or of all places), while it waits for a person at Wassaaa to read it and send it: the address, the account it is for (for a Monday email or the answer to a request), why they get it, the place, its subject and its words, when it was made, and when it was opened and by whom of our team | Until it is sent or skipped; at most 14 days (a Monday email eight days, or until the next Monday's replaces it), then deleted unsent by our clean-up. Only our server can read it, for the owners of Wassaaa's Admin Portal. |
| A place's hosted moments: the name the place typed, the start and the end, whether it repeats every week, whether stamps count twice, any dates called off and the next occurrence, on the place's own record | While the place keeps the moment: until the place calls it off, or, for a moment planned once, until it is over, and for a called-off date until it has passed (removed by our next clean-up). Words and times the place chose, public like its opening hours while its plan gives moments; no question, no prize and no guest. |
| The time of the next start of each place's hosted moments (a place's identifier and one time) | Written again whenever a moment changes and by our clean-up; removed when the place has no moment to come or leaves Wassaaa. Our server's own list, so that the 15-minute check reads one small list and not every place. Only our server can read it. |
| That a reminder for a moment was sent: the place, the moment and its start (never a person) | Two days after the moment's start, then deleted by our next clean-up. Used only so that one moment's reminder is sent once. Only our server can read it. |
| The most people counted here at once during each hosted moment: the moment's name, its start, when it ended and a number | 60 days after the moment's start, then deleted by our next clean-up. Only the place's own team sees it ("Most here", on the week's page and in the Monday email): a count, never who, and never how many guests asked to be reminded. |
| Your choice to be told, or not, on a slow night at a place ("Tell me on a slow night"): on or off, and the time, under your account at that place | Until you leave the team or the staff account is deleted. |
| The note that a slow-night alert went to a place's team for a night: the night, how many were here, the usual figures and hours (counts only, no guest) | Eight days, then deleted by our daily clean-up. Only our server can read it. |
| A place's Monday brief: its text, and whether a model or the fixed wording wrote it | Five weeks, then deleted by our daily clean-up. Seen by the place's team. |
| A tag a place's team hid from its Insights: the tag and the time | Until the team shows it again, or the place leaves Wassaaa. |
| A place's screen link: its secret key and when it was made | Until the screen is turned off, a new link replaces it, or the place leaves Wassaaa. Only our server can read it. |
| What a place's screen shows: the place's name, its door link, how lively it is in a word, tonight's moment, and its current question with its answers (each answer's share only from five answers, the right answer only once it has closed, a prize with its terms) | While the screen is on, as long as what it shows lasts; our server writes it again when one thing changes and deletes it with the key, or when the place may no longer show it (a lapsed plan, a hidden place). Public words and numbers, never a guest's name, face or message, and never a count of people. A signed-in browser that holds the key can read it; no one can list the keys. |
| Your place's link to the hotel it is inside, and an ask waiting for the hotel (when it was made, and which account made it) | The link: while the two places are linked, until either of them ends it or leaves Wassaaa. An ask: until the hotel answers it or your place withdraws it. The line our log keeps of each change (what was done, by which account, and when): 180 days. |
| Your place's Wi-Fi internet address | Until you remove it, or 120 days after it was last added or last used to let a guest in. |
| Your college's Wi-Fi internet address, recorded in Teach by one of its admins: the address (for IPv6, its first half), when and by whom it was added, and when it last matched a browser student's request | Until the college removes it, or 120 days after it was last added or matched. |
| An item's picture on your menu: its two small copies (800 pixels on the long side, and a 240-pixel square) and the words for a screen reader you wrote for it | While it is on the item. Replacing or removing the picture, or removing the item, deletes both files for good at once (see the next row if our storage does not answer); they go with your place if it leaves Wassaaa. Public like the menu while it stands. |
| How many pages of a scanned menu your place had read with AI today, and how many times it asked (two numbers, never the pages or what was read from them) | Two days. Only our server can read it. |
| The address in our storage of a picture file that our storage would not delete when you replaced or removed it, when we first tried and how many times we have tried since (never the picture, its words or a person) | Until the file is gone, or after 96 tries, one in each 15-minute check (a day in all); a file that is then still there stays in our storage, on no menu, for us to delete by hand. Only our server can read it. |
| A shop's counts: for an item, or for each size or colour of it, what is left to reserve (the number the shop typed for its shelf, less what open reservations hold, then moved by each reservation) | While the shop keeps counting that item. Taking the item (or a size) off the list, or turning the count off, ends it; it goes with the place if it leaves Wassaaa. The shop's own team reads it exactly. A guest's screen shows it only at five or fewer; the phone or browser of a guest at the shop is sent the exact number, so that the reservation can stop at it, and what anyone can read before entering carries a number only at five or fewer. |
| Your place's link to Square, if the owner made one: the access Square gives us (a code to read with and a code to renew it, both kept encrypted), Square's identifiers for the seller and the location, which team account connected it, the location the owner chose, whether your opening hours follow Square's, when the access was last renewed, and, only while the owner is choosing a location, the list of the seller's locations (each one's name, address, time zone and currency) | While the place is linked. The list of locations goes when the owner has used Square's menu, or when the link ends. When the link ends (Disconnect in the console or in Square, Square refusing the access, the owner's account erased, or the place leaving Wassaaa) our server asks Square to revoke the access and deletes the codes at once, whether or not Square answers; the owner can also remove Wassaaa in Square's own dashboard. Only our server can read it, not even the place's owner. A daily safety copy of our database (the last group) may still hold it until that copy is deleted; it is never used to put a link back. |
| A copy of what we read from Square, so that the next read takes only what changed: the seller's whole catalogue cut down to the items, headings, sizes, add-ons, prices and photos (so also the items sold at the seller's other locations), what is sold out, how many are in stock for a shop that keeps counts, the dietary details Square records, the location's name, address, time zone, currency and opening hours, and the notes kept beside them (what Square last said was sold out, and which of Square's pictures each of our copies was made from) | While the place is linked; deleted at once, with the codes, when the link ends. Never sales, payments, orders, customers or staff, and none of the product codes, barcodes, costs or tax references that Square sends with each item. Only our server can read it. A daily safety copy of our database (the last group) may still hold it until that copy is deleted; it is never used to put a link back. The menu it made stays the place's own. |
| Your Rewards card on our server: a SHA-256 of the card number and a random holder number; for each place, a one-way mark of your card and that place with your balance, the welcome points that card was given there (so that two cards joined into one get them once), the day of your last purchase and a reward you are holding; and the time and amount of each purchase of the last half hour, so that an order in the app and the same purchase at the till count once (deleted within a day) | Twelve months after your last purchase at that place, thirty days after the place leaves Wassaaa, or at once when you press Leave or erase your data. Never a card number, a name, what was bought or a list of your visits. |
| For each sale that earned points at a place whose till is linked: the amount that earned them, its time, the register and whether the points were collected | Thirty days, so that a refund can take its points back; a sale seen on the no-app page keeps its points for a day. Never a card number, a name or what was bought. |
| Points waiting for the team's OK on your card at a place, and points that lapsed (since November 19, 2026): how many and until when, under your card's one-way mark at that place; and your card's till receipts there, counted for the day | Points waiting: until they are added, or 24 hours; a lapse: shown for seven days; the receipts' count: three days at most. Never a card number, a name or why they waited. |
| For each place, the amounts and times of its last scans by the team (at most 200 within four weeks), its day's three largest scans with the first name of the team member who scanned, and its day's most receipts collected by one card | Four weeks for the amounts; 35 days for the largest scans and the most receipts. Never whose card. |
| The note that an owner pressed Connect Square (a code that works once, the place and the owner's account), and the preview of what Square's menu would bring in (with the catalogue read for it), before the owner chooses | The note: used for ten minutes. The preview: used for half an hour at most. Each is deleted when used, or by our daily clean-up within a day. Only our server can read them. |
| The reference numbers of Square's messages | 30 days, so that none is acted on twice. |
| The record of a link to Square that has ended: when it was made, when it ended and why (Disconnect, Square, an erase or a removal) | While the place is on Wassaaa; it goes with the place. Only our server can read it. The line our log keeps of each change (what was done, by which account, and when): 180 days. |
| Your place's link to Clover, if the owner made one: the access Clover gives us (a code to read with and a code to renew it, both kept encrypted, and the renewal code before, which Clover's recovery needs), Clover's identifier for the business, which team account connected it, whether orders are sent to Clover, the order type the owner chose and whether a ticket prints in the kitchen, whether your opening hours follow Clover's, and when the access was last renewed | While the place is linked. When the link ends (Disconnect in the console, Clover refusing the access, the owner's account erased, or the place leaving Wassaaa) our server deletes the codes at once; Clover gives an app no way to remove itself, so Disconnect also asks the owner to remove Wassaaa in their Clover dashboard. Only our server can read it, not even the place's owner. A daily safety copy of our database (the last group) may still hold it until that copy is deleted; it is never used to put a link back. |
| A copy of what we read from Clover, so that the next read takes only what changed: the place's items cut down to their names, headings, sizes, add-ons and prices, what is sold out, how many are left for a shop that keeps counts, the business name, address, time zone, currency and opening hours, and which Clover item or add-on each item or choice of the menu is | While the place is linked; deleted at once, with the codes, when the link ends. Never payments, cards, cash, customers, employees, taxes, costs or product codes. Only our server can read it. A daily safety copy of our database (the last group) may still hold it until that copy is deleted; it is never used to put a link back. The menu it made stays the place's own. |
| The note that an owner pressed Connect Clover (a code that works once, the place and the owner's account), and the preview of what Clover's menu would bring in, before the owner chooses | The note: used for ten minutes. The preview: used for half an hour at most. Each is deleted when used, or by our daily clean-up within a day. Only our server can read them. |
| For each order sent to your place's Clover account: Clover's order id and its number, whether it printed and, until it is sent, what is to be sent (the items, the choices, the guest's note, the first name the guest uses for the visit, the table or "Counter", and the number for the day); and the number of the last order sent that day | Two days for an order (the number of the day's last order: two days at most); deleted at once when the link ends. Only our server can read it. A daily safety copy of our database (the last group) may still hold it until that copy is deleted; it is never used to send an order again. |
| The line on an order's card that tells your place's team what happened with Clover ("Sent to Clover · Wassaaa 12", "Not sent to Clover. Ring it up by hand.", "Didn't print in Clover"); it holds no name and no note | Two days, or until the link ends. Your place's team reads it, and nobody else. |
| Clover's check code for its messages (a code that is not personal), and a note for your place that Clover rang or that a read of Clover is due, with the time | The check code: 30 minutes, long enough for the owner to paste it into Clover, and deleted within the quarter of an hour after. The note: a moment, until the read is done; the time of the last ring stays while the place is linked. Only our server can read them. |
| The record of a link to Clover that has ended: when it was made, when it ended and why (Disconnect, Clover, an erase or a removal) | While the place is on Wassaaa; it goes with the place. Only our server can read it. The line our log keeps of each change (what was done, by which account, and when): 180 days. |
| The one-way code of an address that asked for no more email | Kept, so that we never email it again. |
| Places that have not joined, and the website | |
| A request to remove a place from the map | 180 days after we answer it. The removed place's name, position and source identifier are kept, so that it is never brought back. |
| A seat when you use a place from your browser, and its conversation | Until eight hours after the seat was opened, whether the page stays open or not, and up to two hours more while an order of yours is still open; a page that is still open then is given a new seat. The conversation: with the seat, or 30 minutes after the place's team closes it. An order still open when the seat ends, or when you clear the conversation, leaves its card with the place's team, as in the app (the rows above). |
| A browser's push token ("Tell me when it's ready" or "Tell me when the team replies") | Until the seat ends. |
| Counts that stop misuse of forms, place cards, a place's menu and the browser path (your network's address only as a one-way code) | The hourly counts: until their hour has ended, within a day at most. The forms' daily counts: until the day ends. |
| A safety copy, in case of an accident | |
| A daily safety copy of our database | 30 days, then deleted. It holds what the rows above held on that day; photos, voice notes and the pictures on a menu's items are files, and are not in it (a menu put back from a copy may point at a picture that has since been deleted, and the place adds it again). It is used only to put back something lost by accident, such as a place's menu or a course. Visits and chats are never put back from it. |
Where it is kept, and on what ground. Everything in this table that is on our servers is kept in the United States, in Google's Firebase. Each group of the table, with the ground we keep it on:
- As a guest, on our servers: in the United States. To give you the service you signed up for, and agreed to on the app's first screen or on the page you joined from; and the safety records (reports, blocks, decisions that keep someone out, and the counts that stop a script), to keep the people at a place safe and because the law asks us to act on abuse.
- On your phone only: on your phone, and not sent to us. The app needs it to work as you use it.
- In a class (Campus): in the United States. To run the class your college set up with us, under its agreement with us (section 7).
- If you run a place: in the United States. The terms for places your place accepted; for a guest's Rewards card, the program the guest joined; and the counts that stop misuse of codes and links, to keep accounts safe.
- Places that have not joined, and the website: in the United States. What you asked for on the website (a removal, a seat, an alert); and the counts, to stop misuse.
- A safety copy, in case of an accident: in the United States. To keep your data safe, as the law asks of us, and to put it back after an accident.
What we send to Apple, Google and the other companies named in section 5 is kept by them, under their own policies.
7. Campus Classroom (colleges and universities)
Campus Classroom is a separate mode that only exists in a building a college has set up with us, and only for a student who enters that class's six-character code. Everything in this section applies to that mode alone; a student who never joins a class is never described by it.
The college decides. A college chooses to run classes in Wassaaa, chooses which buildings have them, and sets how long class records are kept. Attendance and quiz records made in a class are the college's education records. Sigmaton processes them on the college's instruction, as a school official with a legitimate educational interest under FERPA's school-official exception (34 CFR § 99.31(a)(1)); we do not use them for our own purposes, we do not use them to train models, we do not sell or share them, and we do not use them for advertising or profiling. A student's rights in those records — to see them, and to ask for a correction — are exercised with the college, not with us, and we support the college in answering such a request.
What joining a class asks for. Your full name as your instructor's roster expects it, a selfie, and a location fix that confirms you are inside the building. Attendance means nothing if it can be given from elsewhere, so the check is done at the door and while the class runs; your coordinates are not kept as a history and are never shown to your instructor or your classmates.
What your instructor sees. Your name as you typed it, when you joined, whether you are in class now, your attendance for each check, your answers and score on a quiz, and any questions you send them. For a question asked to the room, the instructor sees how many chose each option — never who chose what. A typed answer is shown to the instructor without a name attached.
What your college's admin sees. A college names one or more of its own staff as its admin in Wassaaa. The admin adds and removes the college's instructors, switches classes on or off for a building, sets how long class records are kept, and sees how the college's classes are going as numbers: how many classes were held, how many students joined a class, and what share were marked present, by course, by building and by month. Those numbers are added up when a class ends and have nobody's name in them; a student who comes to ten classes counts ten times, because nothing in them knows it is the same student. The admin does not see who was in a class, your attendance, your quiz or your answers by name, unless the college's agreement with us says the college itself sees those records; where it does, each time an admin opens a class's records by name is written to a log. If your course passes to another instructor, that instructor sees its classes that are still being kept, as the first did. The admin also sees whether an instructor they invited has signed in since the invitation. The admin never sees your selfie, your location, your messages to your instructor or your private chats. A college's admin sees their own college only.
What your classmates see. Your first name and your class selfie. Not your full name, not your attendance, not your quiz, and not what you answered. When a question closes, the class is shown the counts and percentages for each option and nothing else; typed answers are never shown to the class.
How long it is kept. The class selfie is deleted within one class day and at most 16 hours. Attendance, question counts, quiz answers and scores are deleted 30 days after the class, unless the college has set a different period between 1 and 365 days (the college's admin sets it; a shorter period takes effect within hours); after that the class record keeps only its title, its building and its times, and the numbers described above, which name nobody. Before then your instructor may download attendance and quiz results, as a spreadsheet or in the form the college's own learning system (Canvas, Moodle) imports; those files hold your name as you typed it and go to the instructor, who is responsible for them under the college's own rules. Answers are stored against a one-way hash of your account identifier rather than your name.
If you would rather not use the app. Whether a class is run this way is the college's decision, not ours. Wassaaa's roster is the students who joined in the app or from a browser, so if you do not want to take part, tell your instructor: attendance for you is then recorded outside Wassaaa, the way it was before.
Joining from a browser. The app is for people aged 18 and over. A student under 18, or one who cannot use the app or has no smartphone, may join a class at wassaaa.sigmaton.com/class with the class code and their name, unless the instructor has turned this off. The instructor lets each student in. A browser is not asked for a location or a selfie, and a student who joins this way is not shown to classmates; they answer questions, take quizzes, confirm attendance and message the instructor like anyone else. The instructor sees that they joined from a browser. Where the college has recorded its Wi-Fi in Teach, the instructor also sees whether each request to join, and each attendance a browser confirms, came from the college's Wi-Fi or not: only that yes or no is kept, never the internet address, which is compared and forgotten. The college's Wi-Fi is kept as its public internet address (for IPv6, its first half), when it was added, which of the college's admins added it and when it last let a request be matched, until the college removes it or 120 days after it was last added or matched. The request to join is deleted when the class ends; the class record is kept like any other student's, as described above.
Messages in a class. There is no class-wide chat. During a class you can send questions to your instructor; only your instructor sees them and can reply, and the conversation closes when the class ends and is deleted with the other class records. Saying yes and matching are never offered in a class, so in this version of the app classmates cannot start a private chat with each other there. (In versions of the app before this one you can say hello to a classmate and chat privately, as in any place; those chats end with the class.)
A class's alerts, and alerts for instructors. A question, a quiz or an attendance check reaches your phone while you are in the class, even when it is put down, under "From the place you're at" and "Pause notifications". They stop coming to your phone once you tap Leave class (the class's roster notes the time), or once your phone is seen inside another place or another class after it was last in the class (a phone that goes where we cannot see it, home for example, is still sent them until the class ends). If an instructor turns on alerts on a device in Teach ("Turn on alerts on this device"), we keep that browser's push token (from Google's Firebase Cloud Messaging) and when it was last given, with the instructor's account, and send it Teach's alerts and nothing else, so Teach can tell that phone or computer when a student has waited a minute at the class's door, or has written to them. An alert names the student by the first name they gave the class, and never holds what they wrote or the course. A browser has one push token for all of Wassaaa's pages, so Teach's alerts and the staff console's or the Admin Portal's can be on in it together: each keeps its own copy of the token with us. Turning alerts off in Teach deletes Teach's copy at once. Signing out of Teach asks us to delete it too; if that does not get through within a few seconds, it is deleted at the next sign-in to Teach in that browser, or when the next alert to it fails. Signing out of Teach also stops that browser's notifications, unless the staff console's, the Admin Portal's or another instructor's Teach alerts are on in it, which go on. A token the browser no longer accepts is deleted when a send to it fails. Only where a place's page has its alerts on can Teach's not be turned on: Teach's switch stays off there and says why. So if you wait at a class's door from a browser, or write to your instructor, your instructor may be told so on their own phone, with your first name.
8. If you run a place
This section is about owners and managers of restaurants, cafes, bars and other places, and the people who ask to bring their place to Wassaaa. Guests are never described by it.
- When you sign up or claim a place (at /start or from a place's claim link): your account's email address and whether you have confirmed it, your name, whether you own or manage the place, and what the first three screens of the sign-up ask about the place: the place you found on the map, or its name, address and kind if it is not there; the pin on the map; if you say it is inside a hotel that has joined, which hotel; and the terms you ticked, with the time. The sign-up no longer asks how close a guest must be, for a public phone number or for a note: a request sent before keeps what it holds until its 180 days end. The Wassaaa team reads it to decide, and may call the place's public number to check that you run it. It is kept for 180 days after it is decided, or 180 days if nobody has decided it, then deleted. When you add a place that is not on the map, pressing "Next: check the pin" sends the address you typed, and only the address, to the OpenStreetMap Foundation's address search to find where it is: by our server, not by your browser, and without your name, your email or your account. While you fill in the sign-up, the page keeps your answers (never your password) in that browser tab, so that a reload does not lose them: they stay on your device, are not sent to us until you send the request, and are removed when you send it or close the tab.
- Searching for your place before you have an account. The sign-up starts with a search by name, which needs no account. The name you typed is sent to our server to find the places it matches, and it is not kept. To stop abuse, our server counts how many searches your network made today, under a one-way code of its address (never the address itself); the count is deleted when the day ends. Nothing else about the search is kept.
- The draft of your place, while you wait for approval. After you submit, the staff console opens in a preview where you can type your menu, your opening hours and your tagline before your place is approved. What you type is kept on our server, tied to your request and to nothing else, is never shown to a guest, and is checked by our content policy like any words you type; the menu is typed or imported from a file that your browser reads, and a picture of a menu is not read by AI before approval. When your place is approved the draft is copied into the place (what the place's plan allows, and only where the place has none of its own) and the draft is deleted. It is also deleted if the request is declined, if you withdraw it, and at the latest 180 days after you made it.
- Asking for a pilot for a college (at /campus; no account): your name, your email address, the college, your role, its buildings and how many instructors it has, typed as short text. They are used to answer you by email and to set up the college with you, and nothing about any student is asked. To stop abuse, our server counts how many requests your network made today, under a one-way code of its address; the count is deleted when the day ends. The request is kept for 180 days after you send it, whether or not it has been handled, then deleted.
- To stop abuse of the form: how many requests your account and your network address made today. The address is kept only as a one-way code, and both counts are deleted when the day ends.
- The terms you accepted: which version of the terms for places, acceptable use and data-processing terms you ticked, when, and from which account. This is the record of our agreement: it is kept while the place is on Wassaaa and for six years after it leaves.
- Once your place is approved: you are its owner on its team in the staff console, with your email, your name and your role, until you or we remove you. The place's plan (its name, a trial's end, and, if you pay by invoice, the invoice or customer reference from Stripe and the date of the next invoice) is kept while the place is on Wassaaa and is never shown to guests.
- Adding someone to your team. An owner can add a manager or a member of staff, and a manager can add a member of staff, in two ways. By email: you give their email address, name and role. Our server files them on your place's team as an invitation that can be claimed for 30 days, and sends that address one account message with a link to sign in on the phone they will use. If the address has no account yet, our server makes one for it at once, with a password nobody sees, so that nobody else can register the address before the person opens the link, and keeps a note that it made it (section 6). After 30 days the invitation shows as expired until someone invites the address again or removes it. An invitation is claimed only by someone who proves they hold that inbox (section 1), never with a password alone on an account someone else made. In person: you show a code on your own screen (section 1) and the person joins at once; nothing is emailed. The person types their own first name and email address, and a note is kept that the code made their account (section 6). Either way, the person is on your team, with their email, name and role, until you or we remove them. When a team account signs in on a new device with a code, or someone joins or leaves a place's team, the place's owners are notified on their devices. Nothing is kept.
- Insights, and the Monday email. In the staff console, Insights has "This week", "Patterns" and "What worked" for the owners and managers of a place whose plan includes them (Host and up; a place on the free listing sees only a seven-day head count). "This week" holds "The week on one page": last week and this week so far, Monday to Sunday in the place's own time, as counts that the place's own team sees as they are, however small (how many guests asked, how many were taken within the minutes the place set for answering, how long the usual and the slowest first answer took, how many guests tried to reach the team or order while it was away and in which hours, how many were told that nobody had picked up, how many orders were completed, declined, not collected or not closed, how many guests came and how many used the place from a browser, wall posts, counted orders and rewards given, the average of the month's stars, the questions asked and how many guests answered, and, for each hosted moment held that week, the most people our 15-minute checks counted here at once while it ran: "Most here", a count and never who, and never how many asked to be reminded). Patterns and What worked are the same kind of counts over many weeks: which hours and days are busy or quiet, how long visits lasted against whether an order was counted, how quickly the team replied against the stars given, which menu items were ordered or talked about more or less than before, which tags a crowd used, and what a hosted moment, a deal or the place’s question did. Where there are too few weeks or visits to say, the page says so in words. It never says who and never shows a yes or a match. Its money. “This week” opens on the place’s own sales: what the orders paid in the app came to, without the tip or any tax added to the prices, with their tips, by day with the busiest hour, its top sellers, and the rewards given; and, where the place runs Rewards and its owner allowed reading sales, the till’s own sales read for Rewards (below), the tip apart. Sales, orders, tips and rewards are each shown against the week before. It is worked out from the place’s orders and those sales each time it is asked for, and nothing more is kept for it; it never says who paid, and never shows a card. Only Insights has the money: the email and the figures below are counts. The people who run Wassaaa see the same counts summed for all places in the Admin Portal. The email. On Monday from 8 am in the place's own time, once a week, our server emails that page to each owner of the place, unless they have stopped it, and to each manager who has switched on "Email me this page on Mondays" for themselves; a week with nothing to count is not emailed. It comes from our email sender, with the company's postal address and "Stop these weekly emails". That link stops only this email, for that address, and nothing else. The people who run Wassaaa get the whole fleet's page the same way, on Monday at 8 am in Los Angeles. None of these emails is sent by itself: each waits until a person at Wassaaa has read it and sent it, and one not sent within eight days, or before the next Monday's is made, is deleted unsent. The brief. The short paragraph at the top of “This week” and of the email is written by a model, Claude, made by Anthropic, from one sheet that our server builds: the place’s counts for the week, the place’s name, the names of its menu items, and the place’s most used wall tags (each used by 3 or more different guests, never who wrote them). No guest’s name, handle, photo, account, message or visit is sent. Our server checks every number in the answer against the sheet; if the check fails or the model does not answer, the page and the email use fixed wording instead. Anthropic handles what we send as our service provider: its commercial terms, which we read on November 8, 2026, do not let it train its models on it, and its pages on the API say that it deletes inputs and outputs within 30 days by default. The slow-night alert. On a night that looks quieter than that place’s usual, our server can send one alert, at most, to the place’s team: to each owner and manager of the place unless they have switched “Tell me on a slow night” off for themselves, and to nobody else; it carries counts and never a guest. What we keep: your choice to receive it or not at that place (on or off, and the time), your choice to be told on a slow night (the same), the brief’s text for five weeks, the note that a slow-night alert went out for eight days, a one-way code of an address that stopped it, with the time, and, so that nobody is sent the same week twice, a one-way code of the address with the week a place's email was last made for it (kept five weeks, then deleted by the next Monday's clean-up: within 42 days), the email itself with its address while it waits to be sent (at most eight days), and the stop link's random code (section 6). For a place's team, our server counts each week, per member and under a code that stands for them at that place (never their account), the rewards they confirmed, the orders they declined after starting and the orders they closed as not collected, for three weeks. A place's owner is emailed a member's name only when a count is at least 3 and twice the team's average.
- If you pay for a plan by card: the owner chooses a plan in the staff console and pays on Stripe's own checkout page; the card is changed, the plan changed or cancelled on Stripe's own portal. We send Stripe the place's name, the email address of the owner who started it (Stripe sends its receipts there) and which plan was chosen. Stripe tells us which plan is paid for, whether the last payment went through, the date of the next payment and whether the subscription was cancelled; our server sets the place's plan from that. Stripe also tells us when a payment for the place is refunded, or disputed at the card's bank: the amount, the date and Stripe's reference for it, never the card. We keep Stripe's reference for the place and that state while the place is on Wassaaa, the reference numbers of Stripe's messages for 31 days so that none is acted on twice, and the record that the owner accepted the billing terms (the version, when, and from which account) for as long as the other terms you accepted. We never receive or keep a card number, its expiry date or security code, or a bank account: those stay with Stripe, as do its invoices and receipts. The place's team sees the plan, the next payment's date and whether a payment failed; only the owner can open Stripe's pages.
- Emails: we email you when your place is approved. If you asked for Wassaaa in the app and gave your email, we may send you one invitation to sign up; it carries a link that stops every further email from us. If you use it, we keep a one-way code of your address, so that we never email it again; nothing else about you. Every email we send you about your place (an approval, a decline, an invitation or the Monday email) is read first by a person at Wassaaa, who then sends it: until then we keep it, with your address, for at most 14 days (eight days for the Monday email), and after that we delete it unsent. When you add someone to your team by email, we also send that address one account message, the invitation's sign-in link, at once: in our own words, delivered by Resend, once Wassaaa switches its email on, and in Firebase's own sign-in email until then or if ours cannot be sent. It is not marketing, so it carries no stop link, and it is not sent again unless you invite the address again. Adding someone in person sends no email at all.
- Your place's own card, and the small copy of your cover. In the staff console, "Print kit" offers "We're on Wassaaa": a story and a post for your own Instagram, or anywhere you post, with your place's name, your cover picture and a code that opens your page. It is drawn in your browser and downloaded to your device; nothing about it is sent to us, and it says only what is true of your place, never a guest's face, name or number, and no prize. When you save a cover picture, or open that card, the console also makes a small copy of the cover (1200 by 630) and uploads it to our storage, so that your page's link shows it when it is pasted in another app (section 5); it stops being used when you change the cover.
- Your menu from Square (optional). On Host, Host Pro and Event, an owner of a place can connect the place's own Square account from the staff console's menu ("Your menu from Square"). Square is a till, the system a place rings up its sales on. Only an owner connects or disconnects it, and nothing else depends on it. The owner signs in on Square's own page, never ours, and approves three permissions, all of them to read (more only if the owner later allows reading sales, or allows orders and payments, as described below). What we read from Square: the seller's whole catalogue (the items of all its locations, not only the one chosen) and the list of the seller's locations (each one's name, address, time zone, currency and opening hours), so that the owner can choose one; and, for the one location the owner chooses, how many are in stock, for a shop that keeps counts. Only what sells at that one location comes onto the menu: the items, their headings, sizes, add-ons and prices; the items' photos; which items are sold out there; dietary details (the tags above), only where Square itself records them; the location's name, address, time zone, currency and opening hours; and Square's own identifiers for the seller and the location. These become the place's menu, public like the rest of it (section 1); none is about a guest. What Square sends and we drop at once: with each item, Square also sends its product codes (SKUs), barcodes (UPCs), costs and tax references; our server receives them, drops them at once and keeps none. What we never ask for or read: customers or staff, ever (no request we make to Square asks for them); and sales, payments and orders only once the owner allows reading sales, or allows orders and payments, as described next. Reading sales, for a place with Rewards. An owner whose place runs Rewards (section 1) may also tap "Allow reading sales" and approve two more read permissions, payments and orders, on Square's own page. Then, for each completed sale at the chosen location, Square tells our server what was paid (the tip apart), when and on which register, and we read its tax and whether the "Wassaaa reward" discount was rung, to give its points and to show the place’s owners and managers their own sales in Insights (Insights, and the Monday email, above). We keep that for 30 days with the sale, so that a refund can take its points back, and never with a card number, a name or what was bought; a refund takes its points back. Until the owner allows it, none of this is read. We write nothing to Square, and nothing about a guest is ever sent to it, unless the owner taps "Allow orders and payments". Orders and payments, where the owner allows them. An owner may tap "Allow orders and payments" and approve the permissions to write orders and payments, and to be told of the disputes on them, on Square's own page. Then our server sends the place's own Square the orders its guests place in the app, and takes their payments there, as Paying for an order in the app says: for an order, the items and their prices, the tax, the tip, the first name the guest uses for the visit, the table and the guest's note; for a payment, its amount and the single-use token Square's sheet gives, never a card. An order that a guest paid through Stripe at such a place goes into the place's Square as paid elsewhere, and no money moves through Square for it. Nothing more about a guest is sent. Until the owner allows it, none of this is sent. Opening hours follow Square's only while "Keep my opening hours in step with Square" stays ticked, which it is until the owner unticks it; the place's own closed dates are kept. What we keep: while the place is linked, on our servers only, where no phone or browser can read it, not even the owner's: the access Square gives us (kept encrypted), which team account connected it, a copy of what we read, so that the next time we read only what changed (the seller's whole catalogue, including the items of its other locations, cut down to what is listed above), and a note of what Square says is sold out (section 6). While the owner is choosing a location we also keep the list of the seller's locations (each one's name, address, time zone and currency), until the owner has used Square's menu or the link ends. A photo is fetched from Square by our server, just after the owner presses "Use Square's menu" or later when Square changes it, never while the owner waits for it; it is made small and stored as our own copy, like any menu picture (above): a guest's phone never loads anything from Square. When the link ends (the owner presses Disconnect, or disconnects in Square's own dashboard; Square refuses the access; the owner's account is erased; or the place leaves Wassaaa) our server asks Square to revoke the access (unless Square has already ended it, or another place of the same Square account is still linked, which needs it) and deletes the access Square gave us and every copy of what we read, at once, whether or not Square answers (the owner can also remove Wassaaa in Square's own dashboard); only the daily safety copy of our database can still hold them, for up to 30 days, and a link is never put back from it (section 6). The menu stays as the place's own ordinary menu, photos included, for its team to edit again. The record of the link keeps only when it was made, when it ended and why, and our log keeps a line of each change (what was done, by which account, and when: 180 days). Square is a service the place chooses to connect, the way it chooses Stripe for its plan: we only receive from it, on the place's instruction, and the place's Square account stays under Square's own terms and privacy policy.
- Your menu and orders with Clover (optional). On Host, Host Pro and Event, an owner of a place in the United States can connect the place's own Clover account from the staff console's menu ("Your menu from Clover"), or by opening Wassaaa from Clover's App Market once Wassaaa is listed there. Clover is a till, the system a place rings up its sales on. Only an owner connects or disconnects it, and nothing else depends on it. It is not open yet: it starts when Clover has approved Wassaaa's app, and the staff console marks it "(coming)" until then. Wassaaa charges nothing for it. The owner signs in on Clover's own page, never ours, and approves four permissions: to read the place's items, to read its business details, to read its orders and to write orders (and, once Clover has approved Wassaaa's app and only for a place with Rewards, a fifth, to read payments). Wassaaa never asks for or holds the online-payments key of a place's Clover account. What we read from Clover: the place's items (names, prices, sizes, add-ons and headings), which are sold out and, for a shop that keeps counts, how many are left; the business name, address, time zone, currency and opening hours; and the place's order types, so that the owner can choose one. After we send an order, we also read that order back from Clover, only to find it again, to delete it if the team declined it while it is still open, or to see that it was paid. The items, headings, sizes, add-ons, prices and what is sold out become the place's menu, public like the rest of it (section 1); none is about a guest. Clover does not share photos, descriptions or dietary details, so those stay the place's own, typed in Wassaaa. What we never ask for or read: cards, cash, customers, employees, costs or product codes (no request we make to Clover asks for them); and payments only for a place that runs Rewards, from Clover's approval of Wassaaa's app, through a fifth permission, "Read payments" (its reason: the amount, time and register of a sale and a "Wassaaa reward" discount, to give its points and to show the place its own sales in Insights, kept for 30 days with the sale so that a refund can take its points back, never with a card number, a name or what was bought). Orders sent to Clover. If the owner turns on "Send orders to Clover" (the owner picks which of the place's own Clover order types they use, and may add a ticket printed in the kitchen), each order a guest places at the place (in the app, at a table with its code or anywhere inside; at a hotel, a request from a browser too) is also sent to the place's own Clover account as an open order: what the guest ordered, the sizes and add-ons, their note, the first name they use for that visit (for example "Sam" or "Guest 427"), the table or "Counter", and a number for the day ("Wassaaa 12 · Sam · Table 4"). Nothing else about the guest is sent: no account, photo, phone number, email address or location, and no customer record is made in Clover. An order marked "Confirm at the counter first" is sent only when the team starts making it. The order is in Wassaaa first, exactly as before, so a guest never waits on Clover; if Clover does not answer, we try again for a short while, and then the team's order card says "Not sent to Clover. Ring it up by hand." If the team declines an order that is still open and unpaid in Clover, we delete it there; once it is paid, the team refunds it in Clover. We never take, see or refund a payment through Clover: guests pay for their orders in the app, to the place itself (section 1), and each order reaches Clover marked as paid in Wassaaa, with its amount. Opening hours follow Clover's only while "Keep my opening hours in step with Clover" stays ticked, which it is until the owner unticks it; the place's own closed dates are kept. What we keep: while the place is linked, on our servers only, where no phone or browser can read it, not even the owner's: the two keys Clover gives us (one to read with and one to renew it, kept encrypted) and, for Clover's recovery, the renewal key before; which team account connected it; a trimmed copy of Clover's item list, so that the next time we read only what changed; what Clover says is sold out; and which Clover item or add-on each item or choice of the menu is. For each order sent, we also keep Clover's order id and number, whether it printed and, until it is sent, what is to be sent, and the line on the team's order card about Clover ("Sent to Clover · Wassaaa 12", "Not sent to Clover. Ring it up by hand."), each for two days; and Clover's check code for its messages, which is not personal, for 30 minutes, so that the owner can paste it into Clover (section 6). When the link ends (the owner presses Disconnect; Clover refuses the access; the owner's account is erased; or the place leaves Wassaaa) our server deletes both keys and every copy of what we read, at once; only the daily safety copy of our database can still hold them, for up to 30 days, and a link is never put back from it (section 6). Clover gives an app no way to remove itself, so Disconnect also asks the owner to remove Wassaaa in their Clover dashboard. The menu stays as the place's own ordinary menu for its team to edit again. The record of the link keeps only when it was made, when it ended and why, and our log keeps a line of each change (what was done, by which account, and when: 180 days). Clover is a service the place chooses to connect, the way it chooses Stripe for its plan: we send it only the orders described above, on the place's instruction, and the place's Clover account stays under Clover's own terms and privacy policy.
- Rewards (every paid plan): you choose how many points a dollar gives (the card suggests 10), up to four rewards from your menu at points prices (never alcohol, and none for a rating or a review), and whether a first purchase gives welcome points. Your till's sales (Square or Clover, once you allow reading sales), your app orders when your team taps Picked up, and, where no till is linked, your team's scan give a guest points; the points belong to the guest's card, kept as section 1 says. You see how many guests hold points, how many rewards you gave and, for each team member, the points given each day; never who holds a card or how often anyone comes. A counter screen, which shows each till sale's code for the guest to scan, is paired by an owner or a manager; you see which of your team paired each one, and when, and removing someone from your team takes away every counter screen they paired. When a guest uses a reward, your team sees the name they go by for that visit, as in any conversation with them. Points are not given for a rating, a post, a share, or a hotel's room order.
- Hosted moments (Host Pro and Event). In the staff console, More › Your place › Tonight, an owner or a manager can plan a moment: a name the place types (up to 60 characters, checked by the content policy, with no link and no reward for a rating), a start and an end on the quarter hour (15 minutes to 6 hours), once or every week, up to 60 days ahead, at most 10 at a time, and, for a place with Regulars, whether orders count twice during it ("Stamps count twice") (section 1). It is kept on the place's own record beside its deals, with its times, and holds no question, no prize and no guest; who planned it or called it off is in the line our log keeps of each change (what was done, by which account, and when: 180 days), not on the record. While the place's plan gives moments, and only for a place anyone can walk into, its name and times are public words, like its opening hours: they show on the place's pin and card, in the app and on its door page, and a city's badge says "Something's on tonight" (section 1). A moment is never shown for a hotel itself (a place inside a hotel may plan its own), in Campus, for a place that has not joined, that is hidden from the map or asks for a code at its door, during a private event, or once the plan has lapsed: our server asks again each time. What our server keeps (section 6): for each place, the time of its next start, as one number in a small list of its own, so that our 15-minute check reads that list and not every place; a note, with no person in it, that a guest's reminder was sent (section 1), for two days; and, for the place's own team only, the most people our 15-minute checks counted here at once while a moment ran, with the moment's name and start, for 60 days. The team sees it on the week's page and in the Monday email (The week on one page, above) as "Most here": a count and never who, and never how many guests asked to be reminded, a number our server does not keep. The same owners and managers can also make a link to the place's screen for a TV (section 10).
- What your place sees about guests: counts, never people. Your team sees the counts of your own place as they are, however small: how many guests are in right now, the counts for a day, an hour or a month, Regulars' figures and a question's numbers. A count is never a name: nothing in it says who came, who said yes to whom or who chatted with whom, even when the count is one. What your team handles one at a time, such as a conversation or an order, it sees as it is. Your team is never shown a yes or a pass, who said yes to whom or who matched, and no count of yeses is kept for your place; of all that, its numbers hold only how many private chats began between guests. Your team never sees a guest's face: nothing its tools show, and nothing a team member's account can read or is sent, carries a guest's photo or the address of one. Your team does see the name a guest goes by for the visit, on what the guest starts with you, on the shared wall and for the winner of your question's prize: an automatic one, such as "Guest 427", for a guest who came in to order, and the one on the guest's pass, automatic or chosen (or the one the guest has since changed it to on their card), for a guest who took a selfie in that visit; a conversation keeps the name its guest had when it began. An order a guest asked to have brought names the guest's table. One brought to a room names the room. When a guest with an order open ends their visit, or their phone is seen outside your place, your team is told, and the order's card stays until someone on your team closes it, or for up to four hours: its items, the guest's note, the table or the counter (at a hotel, or for an order brought to a room, the room number), and the name for the visit. Your team is told when the guest's phone was last seen, as a time, never where anyone is or went. An order may arrive marked "Confirm at the counter first": your team starts it once the guest is at the counter or it has checked at their table, and is never told why. At a shop, an order is a reservation: your team reads the name for the visit, the items and the note, never an account or a face; it is not a sale, and the guest pays your price at your counter when they collect it. It is kept for the time you set in the staff console, two hours at most, and ends by itself when that time is up. At a hotel, your front desk is not told when the phone of a guest with a request open is seen outside, and the request says nothing about where the phone is; it is still told when the guest ends their visit. At a hotel itself, Wassaaa shows nobody and counts nobody in public: your hotel's counts are for your team alone, and it has no faces, no shared wall, no matching and no question (section 1). The address of your own website, or of your own online store if you are a shop ("Website", or "Shop online"), if you give one, is shown to guests and opens in their own browser, with nothing about them. Two limits: a member of your team who is also in your place as a guest among the faces sees those faces as any guest does; and for a guest whose phone has an older version of the app, your team's tools still show the guest's photo beside an order that guest asked to have brought, and our server still keeps the address of that photo on the record of each conversation the guest starts with you, until that visit ends. You can switch matching off for your place in the staff console ("Guests can match and chat here"; a hotel has no matching to switch); guests can still write to your team. Your menu and the documents you post can be read by anyone before entering, in the app and on the page your door and table codes open, unless you switch that off in the staff console ("Show our menu before guests enter") or your place asks for a code at its door. Guests' star ratings reach your place as its public stars and, on its monthly page and Activity, as counts by month and by star, as they arrive, from the first rating on; never a comment and never who rated (How stars work). What Wassaaa does with guests' information on your place's behalf is in our data-processing terms.
- A place inside a hotel. A bar, restaurant or other place that has joined Wassaaa can be listed inside a hotel that has joined, when both agree: an owner or a manager of the place asks the hotel from the staff console (or says so when signing up, with "My place is inside a hotel"), and an owner or a manager of the hotel approves or declines it; someone who manages both does it in one step; and the Wassaaa team can set or end it in the Admin Portal. Either place can end the link on its own at any time. A link is never made from an address, from open data or by guessing: only in these ways. What is kept: which place is inside which hotel, while they are linked; an ask waiting for the hotel, with when it was made and which account made it, until the hotel answers it or the asking place withdraws it; and, for each change (asked, linked, declined, ended, or set by the Wassaaa team), a line in our log of what was done, by which account and when, kept for 180 days. Guests see the link: the place says "Inside" with the hotel's name, and the hotel's card lists it. Each place keeps its own team, plan, counts and stars, and the place inside keeps its faces. Orders brought to rooms: a place inside a hotel may switch on "Bring orders to guests' rooms" in its staff console; it is off until it does, and goes off if the link ends. Its guests can then ask for an order to be brought to their room, with the room number: your team brings it there, the guest pays your place as for any order, and nothing is charged to the room or through Wassaaa. Like a request at a hotel, such an order says nothing about where the guest's phone is, and your team is not told when it is seen outside; it is still told when the guest ends their visit. When nobody answers at the room, your team can close it as "Couldn't hand it over", the step "Not collected" in a request's or a room order's words, which counts in the same way. The front desk from a place inside: a guest with a visit at a place inside your hotel can message your front desk and ask it for something without leaving that place, and stays counted at the place they are in: their visit at your hotel is one of your guests "here now" for up to ten minutes each time they open your front desk from there (an announcement to your guests here now reaches them in those minutes), and is one more visit in your figures for the day.
9. Places that have not joined yet
So that the map shows the places people actually go to, Wassaaa lists restaurants, cafes, bars, music and event venues and hotels in its launch cities before their owners have joined. Each is marked as one that "hasn't joined Wassaaa yet", and guests can still meet and chat there, except at a hotel, which shows nobody and counts nobody in public whether it has joined or not (section 1).
- Where the list comes from: Overture Maps Foundation's open places data (overturemaps.org), which brings together data from Meta, Microsoft, Foursquare, AllThePlaces and others under open licences. We keep only the place's name, kind, position, address, town and public phone number, and the source's identifier for it. We never show a business's logo or photos, and never add opening hours, ratings or anything the business did not publish. A restaurant, cafe or bar that has not joined can show stars from Wassaaa's own guests, rated as they ended a visit there, the same way as any place (How stars work). Schools, health care, places of worship, shelters, government buildings and homes are left out.
- How the public phone number is used: it is not shown in the app. The Wassaaa team may call it to check that a person claiming the place runs it.
- Counts: like any place, a place that has not joined keeps daily counts of visits and of private chats begun between guests, as numbers only. The page where its owner claims it shows them, never a number under five, and none for a hotel; once the place is theirs, its team sees its counts as any place's team does (section 8).
- Removing a place: anyone who runs a listed place can ask us to remove it at wassaaa.sigmaton.com/remove-my-place. We answer within five working days. The request (the place's name and address, your name, email address, how you are connected to the place and your note) is read by the Wassaaa team, used to reply to you, and deleted 180 days after we answer it. To stop abuse of the form we count requests from your network address for the day, kept only as a one-way code. Once a place is removed we keep its name, position and the source's identifier for it, and nothing about you, so that a later update of the list never brings it back.
- Never inside a hotel from this list: a place is listed inside a hotel only once both have joined and agreed (section 8), never from this list or from an address.
- Claiming a place instead: its owner can claim it from the place's claim link or at /start; see the section above.
10. The website
Wassaaa's website is wassaaa.sigmaton.com. Most of it is information; this is what its pages do with data.
- The page a place's code opens (
/v/…from a door poster or a friend's invitation,/t/…from a table or the counter, when the app is not installed): it shows the place's public card, which it asks our server for. That is the place's name and kind, its opening hours, what is on there now, a moment of today or tonight if the place has planned one ("Today" if it starts before 5 pm at the place, "Tonight" from 5 pm; a name the place typed and a time, in the place's own words), its cover picture if the place has joined Wassaaa (never a logo or photo of a place that has not), and how lively it is in a word ("Quiet", "Buzzin’", "Packed"), the same word the app's map shows anyone nearby (never for a hotel itself: its page shows no such word, and lists the places inside it, each with its own), and a place's own website address if it has one ("Shop online" at a shop) (section 5). Nothing about any person: no names, no photos and no number of people. Like any web page, opening one sends the page's address, with whatever is written in it (a table or a name, for example), and the internet address of the phone or computer asking, to the servers that answer: Google's. For our server's own answers (a door poster's or an invitation's page, a claim page, and the place's card), Google's request logs keep them for about 30 days (technical diagnostics and security logs, section 1). For a door poster or a friend's invitation (/v/…), our server reads from the address only the place's identifier, the page's language and whether the link is a friend's invitation, to write the place's name, kind and one picture into the page's title and into the preview other apps draw from it (a moment is never part of it), which also names the hotel for a place inside one (section 5), and our code stores none of it. (A place's claim page,/claim/…, is read the same way for its title and preview.) A table's or the counter's code (/t/…) opens a page that is the same for everyone, with nothing of the place or the table written into it. Then the page asks our server for the place's card with only the place's identifier. For a place that has joined and has not switched it off, the page also offers "See the menu" (the button takes the place's own word, such as "See the guide" at a hotel): the place's menu and the documents it has posted, to read (section 1). The page asks our server for them only when you tap it, with the place's identifier and the page's language and nothing else, and keeps nothing in your browser; a posted document opens from the storage the place uploaded it to (Google's Firebase Storage). At a place that offers its menu and its team from the browser, the page does more, described under Using a place from your browser below. - To stop abuse of that card and of the menu, our server counts how many of each your network asked for in the hour. The network's internet address (for IPv6, the network part of it) is kept only as a one-way code, never as the address, and the count is deleted once its hour has ended, within a day at most.
- A class code's page (
/j/…) is the page for joining a class from a browser (the browser class seat, below): it talks to our server and signs your browser in as that page does. - Language. The pages a guest sees are written in English, Spanish and Arabic and follow the language your browser asks for. The page reads that in your browser. When a page asks our server for something, it says which of the three languages to answer in; that is not stored, except beside a browser's push token as described below.
- The page for getting Wassaaa Team (
/team, which the QR code on a place's staff console opens, or a link on a team member's phone): it says where to find Wassaaa Team in the stores and, when it was opened with a sign-in code, shows that code so that you can type it in the app; the code works once and for ten minutes. It asks our server for nothing, sets no cookie, runs no analytics and no advertising tracker, loads nothing from anywhere but this site, and keeps nothing in your browser. Like any web page, opening it sends the page's address, with the code written in it, and the internet address of the phone or computer asking, to the servers that answer: Google's. By the time anyone could read a record of that, the code has run out. - A place's screen for a TV (
/screen/…; Host Pro and Event). In the staff console's Print kit, an owner or a manager can make one secret link to a page that the place opens on its own TV, or on a tablet by the till; nobody else can, and the link holds a long random key that is the whole of what the page needs. The page signs your browser in with a random, anonymous account kept in that browser's storage and runs Google reCAPTCHA Enterprise to check that the request comes from a genuine copy of the website (section 1); it sets no cookie of ours, runs no analytics and no advertising tracker, and loads nothing but this site's own files and Google's reCAPTCHA. It listens to one small record that our server writes for that link. That record holds only public words and numbers: the place's name; the code to come in, which is the place's door link drawn as a QR code (never a door's access code); how lively the place is in a word ("Buzzin’", never a number); the moment of today or tonight, in the place's own words with a time; and the place's current question with its answers, each answer's share only once at least five guests have answered (below that the screen says "Fewer than five answers so far"), a closing time as "Until 9:30", the right answer only once the question has closed, a prize always with its terms ("No purchase needed." and that Sigmaton LLC sponsors the draw and the place provides the prize) and, once a draw has been made, only "The winner has been told." Never a guest's name, handle, face or message, a winner's name, how many people are here, how many answered or asked to be reminded, or anything of matching. Our server writes the record again whenever one of those changes. The page is not offered to search engines. Turning the screen off, or making a new link, stops the old link at once, and the page then says "This screen is turned off."; the same happens when the place's plan lapses or the place may no longer show a moment, and the link comes back if the plan does. Turning the screen off stays in the console on any plan, a lapsed one included (the old link then never comes back); making a new link needs the plan. A screen is never made for a hotel itself, in Campus, or for a place that has not joined, that is hidden from the map or asks for a code at its door, or that is holding a private event. Like any web page, opening it sends the page's address, with the key written in it, and the internet address of the TV or tablet, to the servers that answer: Google's, whose request logs may keep them for about 30 days (technical diagnostics and security logs, section 1); a new link makes any key that was logged useless. Our server keeps the key and when it was made, and not who made it, until the screen is turned off, a new link replaces it, or the place leaves Wassaaa (section 6); who made or turned off a link is only in the line our log keeps of each change (what was done, by which account, and when: 180 days), not on the key's record. - No cookies, no analytics and no advertising trackers on the place pages and the information pages (a place page that offers the place from your browser keeps a random sign-in in your browser's storage and runs Google reCAPTCHA Enterprise, which sets a cookie of Google's own: both are described below; the form that asks for a college pilot on /campus runs reCAPTCHA Enterprise too, as the forms at /start do). Our fonts are served by Wassaaa, not fetched from Google Fonts, and a joined place's cover picture comes from the storage the place uploaded it to (Google's Firebase Storage), as does the small copy of it that a link's preview shows, and so do the pictures on a joined place's menu items. As for any website, Google's Firebase Hosting and our server see your internet address in order to answer.
- The forms at /start (to sign a place up or claim one), /remove-my-place, /campus (to ask for a college pilot) and the email-stop page, the browser class seat, a place used from your browser, a place's screen for a TV, a place's counter screen, the page a sale's code opens without the app, and the consoles talk to our server through Firebase, check that a request comes from a genuine copy of the website with Google reCAPTCHA Enterprise, and, where you sign in, keep that sign-in in your browser's storage. Those are the only pages reCAPTCHA Enterprise runs on. On a place's page it runs only where the place offers its menu and its team from your browser, from the moment that page opens. What it reads, and the cookie it sets, are described in section 1. It does not run where a place's page only shows a menu to read.
Using a place from your browser
At a place that offers it, the page a table or door code opens lets you use the place without the app: read its menu, what is on, its deals and opening hours, and its instant answers (the Wi-Fi password, for example); write to its team; and order (the page shows the menu and points you to the app to pay). Nothing social is offered there. You are not asked for a name, a selfie or your location; you are never shown to the people in the place, or counted among them; and you cannot see them. Because the page offers a menu and a counter and no way to meet anyone, it has no age screen. (A guest who is here to order in the app is shown to nobody either, but is not the same thing: that guest is checked by the phone's location and counted in the place's number, as section 1 says.)
- What is kept: a seat. Your browser signs in with a random, anonymous account, and our server keeps a record that this browser is a guest of that place: a made-up name the team sees ("Browser guest 41"), the table or counter written in the link you opened (at a hotel, the room number), how you were checked (next point), and times. The seat is kept until eight hours after it was opened, whether the page stays open or not, so a locked phone finds its order still there (the same rule a visit in the app has). Then it is deleted, and a page that is still open is given a new seat. If an order of yours is still open at that moment, the seat is kept until the order is done, at most two hours more.
- How you are checked. A browser cannot prove where it is. If the place has added its own Wi-Fi, our server compares the internet address your request comes from with that network, keeping nothing about your address, and the team is told you are on their Wi-Fi. Otherwise the team is told your message or order came "from a browser, not location-checked". A place may take browser orders only from its own Wi-Fi.
- Your conversation with the team, and your order. What you write, what you order, the total, your table and an optional note, sent to that place's team. Text only: no photos and no voice. As in the app, it is not end-to-end encrypted: the place's team and the Wassaaa operators can read it, and what you write is checked against the content policy by our server, which masks a swear word ("f**k") and keeps only the masked words. The page takes no payment details and offers no payment: it shows the menu and points you to the app to order and pay. At a shop an order is a reservation, kept for you for the time the shop set and then ended by itself, as in the app (section 1).
- When it is deleted. The conversation is deleted with the seat. If the place's team closes it sooner, it is deleted 30 minutes after it is closed, as in the app, and writing to the team again within those 30 minutes opens it again. "Clear this conversation" on the page deletes the seat and the conversation at once. If an order of yours is still open when the seat ends or you clear the conversation, the place's team keeps that order's card (what you ordered, your note, the table or counter, or at a hotel the room number, and your browser's made-up name) until someone on the team closes it, and for up to four hours after, as in the app (section 1); the card says how the seat ended, and nobody on the team is alerted. While such an order is open, the team is shown when your page was last open, as a time. An order from a browser is never counted as not collected against anyone, and never marked. The place's own record of an order (items, prices, total, table, times, how it ended, and that it came from a browser, with no name, note or account) is kept 90 days, as for any order.
- Limits. To stop misuse, our server counts seats, messages and orders by the hour: for your browser (by its random account), for your network, and for the place. The network's internet address (for IPv6, the network part of it) is kept only as a one-way code, never as the address, and the counts are deleted once their hour has ended, within a day at most.
- "Tell me when it's ready" and "Tell me when the team replies". The second is offered after you first write to the team, until you tap it. Only if you tap one and allow notifications: your browser's push token is stored under that anonymous account, with the language of the page, and used only to tell you the team replied or your order is ready, in that language. The notification never contains what was written. The token and the language are deleted when the seat ends.
- In your browser. The random sign-in, so that a reload carries on, until you clear the site's data; and, until you close the tab, the order you are building, with the choices on each item, and whether you have already answered "Tell me when the team replies". No cookies of ours, no analytics and no advertising trackers; the one cookie is the one Google reCAPTCHA Enterprise sets to check the page (section 1).
- If the place's team removes you from the place for the day, as they can any guest they are talking to, the seat ends and a decision to keep that browser's account out is kept until the day ends, as described in Age and Safety.
11. Age and Safety
Wassaaa is intended for people who are at least 18 years old. The app includes a declared-age gate and safety controls, but no online age check can guarantee a person’s age. On its age screen, in every country, the app asks the phone's app store whether the account is 18 or over (Apple's Declared Age Range on iPhone, Google Play's Age Signals on Android), and does not let in an account the store says is under 18. On an iPhone, Apple shows its own sheet asking whether to share your age range with Wassaaa; on Android, Google Play answers by your own setting in Play, and may ask you first. What the store gives is an age range; it is judged on your phone, and the range itself is never stored, logged or sent to us. What is kept is one answer: that the store said you are 18 or over, or that it gave no answer. It is kept on your phone with the time of the check, and with your account on our servers with the time it was written there, as the record that your age was checked (section 6), and it is never used for analytics or advertising. Where the store has no answer, or none within a few seconds while nothing of its own is on your screen, your own answer on the age screen stands. The app asks again after 30 days, on an iPhone only where a law has Apple share the age; a later "no answer" never replaces "18 or over". If the store says you are under 18, on the age screen or later, the app stops there and nothing about the answer is kept: on the age screen no account is made, and later the answer kept with your account is deleted and the app stops measuring your phone. A student under 18 can still join their class from a browser. Do not share sensitive personal information during a visit, even though it is temporary. Messages are checked against a content policy before they are sent — on your phone for private chats, which are encrypted, and on our servers everywhere else — and a photo sent to you by someone at the place arrives covered until you choose to view it. Where your phone has its own check of photos for nudity, a photo it flags stays covered until you tap a second time (section 2); the check is not a guarantee. Reports reach a named person, who answers within the window the app shows you when you report someone. After a report, that person can end the reported person's visit and keep them out of the place for the day, 7 or 30 days, or pause their access to Wassaaa everywhere for 7, 30 or 90 days or until lifted. If three different people in one place report the same person, they are removed from that place until the end of its day automatically and the reports wait for review. A place's owner or manager can also remove a guest they are talking to from their own place for the day; that is reported to us with the reason. A person who is kept out is told so, and how to ask us to look again; they are never told who reported them. The rules everyone agrees to are at Community rules.
12. Security
We use technical and organizational safeguards to protect data in transit and at rest. No system is absolutely risk free, but we continuously improve controls and monitoring.
13. Account Deletion and Privacy Requests
A copy of your data. In the app, Settings › Your data › Download a copy of my data makes one file of what Wassaaa keeps under your account, which you can save or share from your phone's share sheet. It holds: when your account was made and the address linked to it, if any; the people you blocked (the name you saw, the place and the time, never their account); your notification choices, including the end of a pause if one is still stored; your phones (the kind, the language, whether the phone shows faces in notifications, whether it shows message text, and when its record was last updated, never the code that sends notifications to it); when a place's team closed one of your orders as not collected, or a reservation of yours ran out before you collected it; what your phone's app store said of your age at the last check (18 or over, or no answer) and when; and whether you have Wassaaa Plus and when it ends. It leaves out, and says so in the file: anything that belongs to a visit (chats, orders, posts, answers, and where you are counted), which goes with the visit and is not kept under your account; who has blocked you, which Wassaaa never tells anyone; safety records; the codes that send notifications to your phones; counters and checks that keep Wassaaa safe and fair; and what lives only on your phone, such as the people you have met. You can make three copies an hour. Wassaaa makes the file when you ask and keeps no copy of it on our servers: the app writes it to a temporary file on your phone, offers it to you, and deletes it as soon as the share sheet has closed. On an Android phone the share sheet first copies the file into Wassaaa's own cache on the phone, where it stays until the app is next opened or brought back to the front, or until you press Clear under Storage or erase everything about you, and then Wassaaa deletes it; on an iPhone no copy is kept. Where you save or share it is up to you. So that the limit can be applied, Wassaaa counts the copies you ask for in each hour, with your account; the count goes when the hour has ended, within a day at most (section 6).
As a guest, you can erase everything about you from the app: Settings → Erase everything about me. Wassaaa deletes what it holds about you on its servers (your selfie, chats, blocks, settings, notification token and safety history about you, except as said below), the app deletes what it keeps on your phone (the list of people you have met included), and you start again as a new guest. This also ends at once every visit that is still kept after you walked out of a place, with everything in it: like End visit in Settings, it does not wait for the visit's eight hours. Your ratings leave places' public stars at the same time, and the one-way marks places keep of your visits, with any counted orders on them, are deleted. So is the count of the orders that teams closed as not collected for your account (section 1); and an order's card that a place's team still holds from a visit of yours loses your name, your note and the account beside it at once (its items stay until it is closed). A yes another guest said to you is deleted too. In every place you have a visit, so are the line that names you in that guest's own list of the people they said yes to and any note that a yes of theirs to you was taken back. In a place you had already left, a line that guest's phone had been shown goes within about 15 minutes of your visit's end; a line it had not been shown stays in that guest's own record, read by nobody, until their phone next asks for its list or their visit ends at the latest; and such a note stays with that guest's visit, where no phone can read it, and goes when that visit ends at the latest. You can delete a linked Wassaaa account from the same screen, and that clears what the app keeps on your phone in the same way (on an older version of the app, deleting an account left those files on the phone until the app was removed). Either one also switches usage measurement off on the phone and makes Google Analytics forget what it kept there and take a new random identifier; nothing is measured again until you agree on the age screen once more. A sign-in to staff mode on the same phone is a separate account and stays, with its alerts, until you sign out of staff mode. An account that owns a place cannot be deleted until the place has been handed to someone else, and an account that is on a place's team leaves that team when it is deleted. If your account has an email address on it, you can also ask us to delete it by writing to support@sigmaton.com from that address: we write back to that address to check the request is yours, and delete the account once you answer. An account with no email address on it (most guests) can only be erased on the phone that holds it, with the step above, because an email cannot show us which account is yours. The line our own log keeps of a deletion we carried out says who on our side did it, when and the reason given, never whose account it was, and is kept for 180 days. If the account once owned a place, the log also notes, for that place, that a former owner's account was deleted, without a name. Deletion removes the account and associated ephemeral session data that Wassaaa can identify, subject to limited safety, fraud, billing, and legal records that may need to be retained: reports other people made stay with your name removed (if you erase within 30 days of a report about you, or of a removal or a pause, the safety record about you and your account's id and name on the reports still open stay for 180 days first, then go, as section 1 says), a decision that keeps you out of a place or pauses your access stays in force until it ends, and if someone blocked you, the note of it in their own list (the handle you had on that visit, when and where) stays until they remove it. What you erase or delete can remain for up to 30 days inside the daily safety copy described in section 6; it is not used, and it goes when that copy is deleted. Deleting an account does not cancel an Apple or Google subscription; cancel that subscription through the applicable app store. For questions or requests, contact support@sigmaton.com.
Who is responsible for your data. Sigmaton LLC decides how your data is used. Our database and stored files are kept in the United States. They are kept there because that is needed to give you the service, and you agreed to it when you signed up: the app's first screen, and the page you join from in a browser, say so. As a company established in the United Arab Emirates, we follow the UAE's Personal Data Protection Law (Federal Decree-Law No. 45 of 2021) where it applies to us. If a breach of our security puts your data at risk, we tell the UAE's data regulator, and you, as that law asks, and say what happened and what we are doing about it. The UAE's law on children's safety online (Federal Decree-Law No. 26 of 2025) protects anyone under 18: the Wassaaa app is for adults, and we keep no data of anyone under 18 on purpose, except a student who joins a class from a browser, whose class record belongs to their college (section 7). Wherever you live, you can ask us for a copy of your data, to correct it, to delete it, or to stop or limit a use of it: write to support@sigmaton.com, and we answer within 30 days. For an account with no email address on it, the steps in the app above are the way, because an email cannot show us which account is yours.
14. Contact
Sigmaton LLC, Sharjah Media City, Sharjah, United Arab Emirates. For privacy requests, contact support@sigmaton.com. In the app, Settings › Help › Report a problem opens an email to that address in your own mail app, with the app's version and build, your phone's model and its system version already written in it. You see all of it before you send it, Wassaaa adds nothing else, and nothing is sent unless you send it.