Wassaaa Privacy Policy

Effective date: November 22, 2026

Leer en español · اقرأ بالعربية

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

2. Camera, Photos, and Microphone

3. How We Use Data

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:

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.

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.

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 is kept and for how long
WhatKept 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 selfieUntil 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 thereWhile 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 matchedDeleted 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 copyDeleted 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 hourUntil 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 everyoneUntil the other phone has used it, and within two days at most.
A "Keep in touch" tapUntil its chat ends.
A yes you said to someoneUntil 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 finishedUntil 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 itAs 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 soUntil 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 else30 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 onceFive 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 asked15 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 usedUntil 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 dayAt 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 recordThe 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 accountThree 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 thereUntil 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 itYour 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 kindKept, only as numbers for the place and the day, never tied to a person.
A star rating and its comment30 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 stars180 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 onceUntil 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 timeAs 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 timeTwo 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 removed180 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 youUntil 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 accessUntil 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 itUntil 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 logsMay 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 joined180 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 shownThe 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 didUntil 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 notificationsUntil 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 emojiUntil 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 card400 days.
Nearby Interaction pairing tokensUsable 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 otherThe 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 withUntil 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 you24 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 ChatsUntil your next visit begins, or you erase your data.
A message you wrote that has not been sent yetUntil 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 phoneUntil 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 opensUntil 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 visitsUntil 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 meetingUntil 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 offUntil 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 offUntil 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 offUntil 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 oneUntil 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 followsUntil 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 thereUntil 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 clockUntil 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 whenUntil 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 backUntil 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 visitUntil 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 someoneUntil 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 chats24 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 menu90 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 serviceUntil 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 phoneUntil 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 offUntil 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 inUntil 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 endsUntil 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 purchaseTwelve 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 heldTwelve 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 met180 days for each meeting, or until you turn it off, block the person or erase your data.
The random number sent with a GIF searchUntil 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" choiceUntil 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 offUntil 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 offUntil 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 yetUntil 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 onceThirteen 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 firstUntil 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 commentUntil 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 itOnly 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 offUntil 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 selfieWithin one class day, and at most 16 hours.
Attendance, question counts, quiz answers and scores30 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 instructorClosed when the class ends, and deleted with the other class records.
If you run a place
Your sign-up or claim request180 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 termsWhile 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 planWhile the place is on Wassaaa, or until you or we remove you.
The reference numbers of Stripe's messages31 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'sUntil 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 runningTwo 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 itA 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 upUntil 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 todayA 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 twoUntil 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 placeUntil 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 askedUsed 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 timeTen 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 outTen 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 dayThe 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 sentUntil 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 phoneAs 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 phoneUntil 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 away24 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 thereWhile 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 placeUntil 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 timeKept, 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 weekFive 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 one180 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 teamUntil 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 recordWhile 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 number60 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 placeUntil 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 itFive 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 timeUntil the team shows it again, or the place leaves Wassaaa.
A place's screen link: its secret key and when it was madeUntil 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 addressUntil 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 requestUntil 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 itWhile 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 collectedThirty 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 dayPoints 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 cardFour 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 choosesThe 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 messages30 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 renewedWhile 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 isWhile 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 choosesThe 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 dayTwo 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 noteTwo 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 timeThe 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 emailKept, so that we never email it again.
Places that have not joined, and the website
A request to remove a place from the map180 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 conversationUntil 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 database30 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:

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.

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).

10. The website

Wassaaa's website is wassaaa.sigmaton.com. Most of it is information; this is what its pages do with data.

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.)

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.