For places
Data-processing terms
Version 2026-11-18b · Effective November 18, 2026
How Wassaaa handles information for your place. These terms are part of the terms for places.
1. Two kinds of information
- Your place's information: your team's accounts (names, email addresses, roles, availability, and, while a person is on shift, when the shift starts and ends, whether its test alert reached their phone, and the last time one of their screens was heard from), what you publish (menu, posts, hours, deals, your Wi-Fi's address), your plan, and its invoice references; and, if your place is inside a hotel or has places inside it, that link (which places are linked, with the hotel's name and the area of the map the place's card is filed under), an ask waiting for the hotel (which hotel, when it was made and which account made it), and our log's line of each change (what was done, to which two places, by which account and when: who asked, who agreed or declined, who ended it). If your place connects its own Square or Clover till, that is also your place's information: what we read from it and the access Square or Clover gives us (section 3). We handle it for you, to provide Wassaaa, as your service provider.
- Guests' information: guests use Wassaaa under our own Privacy Policy, and we decide how it is used. When a guest writes to your team or orders, we pass it to your team during that visit, and an open order's card for up to four hours after it, as section 5 of the terms for places describes. If your place sends its orders to its own Clover account, each order a guest places there (what they ordered, the choices, their note, the first name they use for that visit, and the table or "Counter") also goes to that account, on your place's instruction, and nothing else about the guest does (section 4).
2. What we do with your place's information
Only what it takes to provide, secure and support Wassaaa for you. We do not sell it or share it for advertising. We do not combine it with other places' information, except as totals that identify nobody (for example, how many places take orders in the app).
3. How long it is kept
- Your team's accounts: until a person is removed from your team, or your place leaves.
- A team member's shift: until it ends, at most 16 hours after it starts; the markers of their open screens, a day after the screen went away.
- Conversations between guests and your team: deleted when the guest's visit ends (at most eight hours after the guest came in, and up to two hours more while an order is open), or 30 minutes after they are closed. Voice messages go with them, and within a day at most.
- Order records: 90 days, with no name, photo, note or account attached.
- Counts: while your place is on Wassaaa. The one-way code that tells a returning guest from a new one: 60 days, and never for a college.
- Your Wi-Fi's address: until you remove it, or 120 days after it was last used.
- Your place's link to a hotel: while the two places are linked. An ask waiting for the hotel: until it is answered or withdrawn. The line our log keeps of each change: 180 days.
- A daily safety copy of our database: 30 days, then deleted. It holds everything above as it was on that day (not photos or voice messages, which are files), so something already deleted can remain inside a copy for up to 30 days. It is used only to put back something lost by accident, such as your menu; conversations and visits are never put back from it.
- Your plan and its invoice reference: while your place is on Wassaaa. If you pay by card: Stripe's reference for your place and what Stripe tells us about your subscription (the plan, whether it is paid, the next payment's date), for the same time. Stripe keeps invoices, receipts and your card under its own terms; we never have the card.
- What we read from your own Square account, if you connect it (its whole catalogue, with the items of all its locations, and the list of its locations; only the chosen location's items, headings, sizes, add-ons, prices, photos, what is sold out, name, address and hours come onto your menu; the product codes, barcodes, costs and tax references that Square sends with each item are dropped at once and none is kept) and the access Square gives us: while it is linked, on our servers only (the list of locations only until you have used Square's menu). When you disconnect (in the staff console or in Square), Square refuses the access, the owner's account is erased or your place leaves, we ask Square to revoke the access, unless Square has already ended it or another place of the same Square account still needs it, and delete the access and every copy of what we read, at once, whether or not Square answers; you can also remove Wassaaa in Square's own dashboard. The menu stays yours, as an ordinary menu. The record that a link was made and when and why it ended is kept while your place is on Wassaaa. If you run Rewards and allow reading sales, we also read from Square, for each completed sale at your chosen location, what was paid (the tip apart), its time, register and tax and whether the "Wassaaa reward" discount was rung, to give its points and to show your place its own sales in Insights, and keep that for 30 days with the sale so that a refund can take its points back, never with a card number, a name or what was bought. We write nothing to Square, and nothing about your guests is ever sent to it.
- What we read from your own Clover account, if you connect it (its items with their headings, sizes, add-ons and prices; what is sold out and, for a shop that keeps counts, how many are left; the business name, address, time zone, currency and opening hours; and the order types you can pick from; Clover shares no photos, descriptions or dietary details, so those stay your place's own, typed in Wassaaa) and the access Clover gives us (a code to read with and a code to renew it, and the one before, which Clover's recovery needs): while it is linked, on our servers only. We never read cards, cash, customers, employees, costs or product codes (payments only for a place with Rewards, from Clover's approval of Wassaaa's app, kept as described for Square), and we never ask for or hold your Clover online-payments key. For each order we send to your Clover account, if you turn that on, we keep Clover's order number and whether it printed, and, until it is sent, what is to be sent, for two days; the same for the line on your team's order card about Clover (for example "Sent to Clover · Wassaaa 12"). Clover's check code for its messages is kept for 30 minutes. When you disconnect (in the staff console), Clover refuses the access, the owner's account is erased or your place leaves, we delete both codes and every copy of what we read, at once; Clover gives an app no way to remove itself, so we also ask you to remove Wassaaa in your Clover dashboard. The menu stays yours, as an ordinary menu. The record that a link was made and when and why it ended is kept while your place is on Wassaaa. A daily safety copy of our database can still hold a link's data for up to 30 days and is never used to put a link back.
4. Who helps us
- Google (Firebase and Google Cloud): hosting, the database, file storage, sign-in, notifications and reCAPTCHA.
- Apple: notifications on iPhone, and App Attest and DeviceCheck, which check that a request comes from a genuine iPhone app.
- Stripe: our payment processor for your plan's invoices, card payments and subscriptions; it handles your place's payment details for them. And, if you take cards in the app through Stripe, the platform your own Stripe account is connected to, run by Sigmaton's sole proprietorship in Alameda, California, for the places' payments only: a guest's card goes from Stripe's own sheet to Stripe, never to us, and the money goes to your own account.
- Square: the till your place chooses to connect, only if its owner does, so that your menu, what is sold out and your hours can come from it. We read from it what your place allows. Only if your place's owner also taps "Allow orders and payments": Square tells us when a guest disputes an app order's payment, so that account stops paying in the app (we read nothing else of a dispute); we send your app orders into it (the items, prices, tax, tip, the first name your guest goes by for the visit, the table and the note), and, where you choose Square to take your payments, the payment is made there from a single-use token from Square's own sheet, on your own Square account, which Square holds, takes, lets go and refunds as we ask; an order paid through Stripe goes in as paid elsewhere, with no money moved. Otherwise we write nothing to it and it is sent nothing about your guests.
- Clover: the till your place chooses to connect, only if its owner does, so that your menu, what is sold out and your hours can come from it. We read from it what your place allows. If your place turns on "Send orders to Clover", each order a guest places there is also sent, on your place's instruction, to your place's own Clover account, as an open order, already paid in the app where something is sold, with "PAID IN WASSAAA" and its amount at the start of its note, so that your team does not take payment for it again: what the guest ordered, the choices, their note, the first name they use for that visit, the table or "Counter" and a number for the day, and nothing else about the guest (no account, photo, phone, email or location, and no customer record in Clover). We never take, see or refund a payment through Clover.
- Resend: our email delivery service, for account emails about your place, such as an approval, a decline or an invitation, and for the Monday email of your place's Insights. It receives the address and the message, never anything about your guests.
- Anthropic: its model, Claude, writes the short brief at the top of your place's Insights and of the Monday email, and, if you press "Read it with AI", reads a scanned menu you give it. For the brief it is sent your place's own counts for the week, your place's name, the names of your menu items and your place's most used wall tags (each used by 3 or more guests); for the menu, the pages you give it. Never anything about a guest. Under its commercial terms it may not train its models on what it is sent, and it deletes it within 30 days by default.
- OpenStreetMap: the map on the sign-up page loads from its servers.
We tell your place's owner by email before adding a service that would handle your place's information. If you object, you can leave (terms for places, section 10).
5. Where
In the United States.
6. How it is protected
Encryption in transit; your place's information reachable only by your team and by the people who run Wassaaa, who need it to support and secure the service; every operator action written to an audit log; when Wassaaa support opens your place's staff console, your place's owners are told, the visit ends by itself within an hour unless kept open, and every change is written to the log and listed in the console under Settings, Team; a separate sign-in for each person on your team; and checks that requests come from the genuine app or website.
7. If something goes wrong
If we learn of a breach that affects your place's information, we tell your place's owner without undue delay, with what we know and what we are doing about it.
8. Requests from guests and from your team
If a guest asks you about their information, send them to support@sigmaton.com: we answer under our Privacy Policy. Anyone on your team may ask us for a copy of their own account information, or for it to be deleted.
9. When you leave
We delete your place's information as section 10 of the terms for places describes.
10. Questions
Once a year, on request, we answer reasonable written questions about how we protect your place's information.