Privacy Policy
Last updated 2 November 2026
TeaBoy is an office hospitality request app. A company signs up, its employees request tea or coffee from their desks, and its service staff see those requests and mark them delivered. This page describes exactly what the product stores to do that, and nothing more flattering than the truth.
Who is responsible. The company that invited you decides what TeaBoy is used for inside their office; Cloudics operates the service on their behalf. Where the law distinguishes a controller from a processor, the company is the controller of its employees' data and Cloudics is its processor. Cloudics is the controller of demo enquiries sent from this website.
The operator is Cloudics LLC. Privacy enquiries go to support@teaboy.net.
Cloudics LLC is a limited liability company formed on 22 June 2026 in the State of Wyoming, United States, filed with the Wyoming Secretary of State under entity ID 2026-002011294. Its registered agent is Registered Agents Inc.
Registered and principal office:
30 N Gould St, STE R
Sheridan, WY 82801
United States
Privacy enquiries may be sent to the email address above or to that postal address.
What the product stores
Company and administrator account information
A company administrator creates an account with a work email address and a password. The password is handled by our authentication provider and stored only as a hash; nobody at Cloudics can read it. For the company we store its name, optionally its city, an optional logo you upload, a join code, the company's status, its three priority settings and a timezone used to decide what "today" means in the admin reports.
Employee and service-staff profile information
Employees and service staff do not create a password. The app signs the device in anonymously and the person then joins a company with its code and waits for an administrator to approve them. For each member we store a display name, an optional department, which office or room they usually order to, their role, whether an administrator has marked them as an executive, and — for service staff only — whether they are currently available. We also store a preferred app language.
No phone number is required and none is verified. There is no SMS anywhere in TeaBoy.
Company structure
The offices and meeting rooms an administrator adds, and the hospitality menu they choose — including any custom item they create and the optional translations they type for it.
Request history
Every request stores who sent it, which office or room it was for, what was asked for and how much, whether it was for a guest or a meeting, the priority it was given at the moment it was created, which member of service staff accepted it, and the times it was sent, accepted, delivered or cancelled. Item names are copied onto the request when it is created, so renaming a menu item later does not rewrite what someone ordered last week.
There is no payment anywhere in TeaBoy. We hold no card details, no bank details and no prices.
Meeting-room bookings
A booking stores the room, the day and times it covers, the title the person typed, whether it is an internal team meeting or a client or guest meeting, who made it, and whether it is waiting for approval, confirmed or cancelled. If it is a client or guest meeting, the guest's name is stored when the person chooses to enter one; it is optional and nothing in the product requires it.
A title is company-authored free text and is visible to the person who booked the room and to that company's administrators. Everybody else in the company is shown only that the room is busy for that interval — not the title, not the guest's name, and not who booked it.
When an administrator has allowed client meetings to take priority, a client booking can shorten or cancel a conflicting internal one. TeaBoy keeps a record of that: the original times, what the booking became, the reason, which booking caused it, and whether the product did it automatically or an administrator chose to. The displaced booking is marked cancelled rather than deleted, so the person who lost the room can still see what happened. A notification is created for them.
Push notification tokens
If you allow notifications, we store the push token your operating system issues for that installation, which platform it is, the company it belongs to, your chosen language and when the token was last seen. A token identifies an installation, not a person, and is replaced whenever the operating system reissues it. Tokens that the push service reports as dead are disabled.
Application and device technical information
The app sends ordinary technical information that any network request carries — an IP address, and the information our providers log to operate the service. We do not use advertising identifiers, we do not track you across other apps or websites, and there is no analytics SDK, no advertising SDK and no third-party tracker in the TeaBoy app or on this website.
Demo enquiries from this website
The form on teaboy.net stores four things: your company name, your name, an employee-count range and a work email address. It is used to contact you about TeaBoy and for nothing else. It creates no account — there is no account to create on this website.
Security and operational records
We keep a short operational log of significant events — a company being created, a join code being reset, a notification that could not be delivered. It records what happened, which company it concerned and who acted, never the contents of a request.
What we do not do
- We do not sell personal data, and we do not share it for advertising.
- We do not profile people or make automated decisions about them.
- We do not read request contents for any purpose other than delivering the product: the operator's own platform view is deliberately limited to counts and events and cannot show a request's contents or an employee's name.
- A company administrator sees usage totals, per-item counts and how many requests each member of service staff delivered. They cannot see a per-employee breakdown of who ordered what; that restriction is enforced by the database, not by a screen.
- One company can never see another company's data. Every table is isolated per company inside the database.
Who processes data for us
| Provider | What it does |
|---|---|
| Supabase | Database, authentication, file storage for company logos, and the serverless functions that send notifications and receive demo enquiries. |
| Google Firebase Cloud Messaging | Delivers push notifications to Android devices and, through Apple's service, to iPhones. It receives the push token and the notification text, which names the requester, the place and the items. |
| Apple Push Notification service | Delivers notifications to iPhones. |
| Cloudflare | Serves this website. If the demo form's bot check is enabled, it also verifies that check. |
The TeaBoy database, authentication and file storage run in Supabase's eu-central-1 region, in Frankfurt, Germany. Push notifications are delivered by Google Firebase Cloud Messaging and, for iPhones, by Apple's Push Notification service; both are global services operated by those companies. TeaBoy data is not hosted in Saudi Arabia.
Security
Connections to TeaBoy use HTTPS. Administrator passwords are stored only as hashes by our authentication provider. Access to each company's data is enforced inside the database rather than in the app, so a modified client cannot read another company's rows. Privileged service keys exist only in server-side functions and are never shipped in the mobile app or in this website.
We do not claim any certification, audit or compliance standard. If that changes, this page will say so specifically.
How long data is kept
A nightly job applies the schedule below. Outside it, a company's data stays until the company asks us to remove it.
- A deletion asked for in the app completes 14 days later, and can be cancelled from the same screen at any point before that. Notifications stop as soon as it is asked for.
- Request history: 24 months.
- Operational logs: 13 months with their references, then the company and person references are blanked and the row survives only as a count.
- Push tokens: deleted once not seen for 90 days.
- Demo enquiries: 12 months after arriving, or 90 days after we handle one, whichever comes first.
When one person is deleted, their name, department, profile and device go. The company's record of what was ordered stays, with that person's name removed from it — the counts an administrator relies on would otherwise change when somebody left. See deleting your data.
Your choices
- Notifications. Turning them off in your phone's settings stops delivery. Service staff who turn them off will miss requests, which is the point of asking.
- Language. Each person picks their own; it is stored so the app opens in it.
- Your data. Ask your company administrator, or write to us — see deleting your data.
Children
TeaBoy is a workplace tool. It is not directed at children and we do not knowingly collect data from them.
Changes
If this policy changes we will update the date at the top. Material changes will be communicated to company administrators.