Privacy policy
Last updated 11 November 2026. This covers the Soapbox app for iPhone, iPad and Apple Watch, the web display at soapboxtimer.app/display and this website.
The short version
- Soapbox has no accounts, no ads and no tracking, and the apps have no analytics. This website and the web display count visits with Cloudflare Web Analytics, which sets no cookies (see This website, below).
- Soapbox doesn't ask for your name, email or any account details. Whatever you type into a session, including a speaker's name in the topic or notes, is used only to run that session and is deleted with it, apart from the storage history and server logs described below. We sell nothing and share nothing with anyone but Cloudflare, which runs our server.
- A timer session holds only what it needs to run, and is deleted after 12 hours without use, or as soon as our server receives the display's request when you get a new code. Cloudflare's storage also keeps a recoverable history of it for up to 30 days, and server logs are kept for up to 7 days (details below).
What a session holds
When you open the display, Soapbox creates a session on our server, which runs on Cloudflare. The session holds:
- the 8-digit code (6 digits on older displays), and a random key that proves which display owns the session (only that display is given it);
- the names you give any extra displays you add, and one invite key for each (with its key a display can show the clock but can't control it; controlling takes the session's code, as it does for a phone);
- the clock: its length, time left, and whether it is running;
- the topic, notes and messages you send, and the profile settings in use (colours, timings, quick messages, clock face);
- if you run a show, its name and its segments: each segment's title, speaker, length and settings, any notes and quick messages you give it, and how far the show has got (which segment is on and the time spent in each);
- the name of each paired phone, as iOS reports it (on current iOS versions this is usually just “iPhone”), so the display can show who is connected;
- a random connection number for each connected app or page, which the app or page makes afresh each time it starts and does not save, kept with its connection so that a device that reconnects is counted once;
- if the display is the Soapbox app (usually an iPad), its address on your local network and port, so phones can find it if the internet drops. The display sends this whenever it has a local network address, whether or not you ever use local mode, and the server passes it on to every phone and display connected to the session.
- for each Apple Watch that follows the session: the name of its iPhone in the session, a random id and a random key made for this session, whether that iPhone is connected through our server or in local mode, when the watch last asked for the clock and when its iPhone was last connected, when the server last told the session's phones and displays about that watch, when following ends, whether wrist alerts are on, off (notifications or their sound are switched off on that iPhone or for the watch) or stopped, and the kind and time of each alert that iPhone has set, and when it set them. The server passes the name, the id, the last-asked time, the status and the time following ends on to every phone and display connected to the session, so that the producer can see which watches are following. A watch is listed by itself when its iPhone joins a timer. Leaving the timer on the iPhone removes it when the iPhone is connected through our server at that moment; otherwise it can stay until the session is deleted. The watch's key lets it read the clock and not change it.
Anyone with the code can see and change the session, which is how you share control with a colleague. Get a new code on the display to end the session and disconnect everyone.
The session is deleted after 12 hours without use (a phone or display connecting, or anything a phone or display changes in the session (the clock, the topic, notes, messages, settings, a show, the extra displays or the display's local address), counts as use; a watch following or stopping does not), or as soon as our server receives the display's request when you get a new code. We don't make backups of it, but Cloudflare's storage keeps a recoverable change history of a session for up to 30 days before it is gone for good.
To delete a session sooner, get a new code on the display: that deletes it as soon as the display's request reaches our server. The display sends that request once and does not retry, so if it is offline at that moment the old session stays until it expires. We can't delete a session for you. Cloudflare's change history and the server logs expire on their own, and we have no way to shorten that or to remove single entries. If you have a question about your data, email info@soapboxtimer.app.
On your devices
- The web display keeps the session's code, its key and the last clock state in your browser's storage (the clock state includes the topic, notes, the show being run, if any, and the names of the connected phones), so a reload picks up where it left off. It also stores its own files for offline reloads. Clear the site's data in your browser to remove them.
- A browser that joins another display as an extra display keeps that session's code and the invite key in this browser's local storage, along with the last clock state it received (with the same topic, notes, show being run and phone names), until it is removed from the session, the session ends or you tap Leave, and clearing the site's data in your browser removes them too.
- The app on the phone or iPad you control the timer from keeps your profiles, the shows you save (up to 50, each with its name and its segments: titles, speakers, lengths, notes and quick messages) and the last session's code on that device, along with the display's local network address or name when it has learned one, so it can reconnect in local mode. A saved show stays on the device until you delete it, and is sent to the timer only when you run it. Deleting the app removes all of this.
- The Soapbox app, when it is the main display (usually an iPad), keeps the session's code, its key, the last clock state (with the topic, notes, the show being run, if any, and the names of the connected phones), and the names and invite keys of any extra displays you add, on the device. A display that joined with an invite keeps its pass (the session's code, its invite key, the name you gave it and, when it has one, the main display's local network address or name) and the last clock state it received, with the same topic, notes, show being run and phone names, on the device it runs on. Deleting the app removes all of this.
- The Apple Watch app keeps the session's code, its own id and key, the name and the last clock it was given (with the topic, the message on screen and, during a show, the speaker and segment names). It deletes them once it learns that the iPhone has left the timer or that the timer has ended, and otherwise the first time the watch app starts, or comes on screen, more than 12 hours after the iPhone last handed them over. Once it finds that the timer has ended it keeps only the code, to say so, and deletes that the first time it starts, or comes on screen, more than 12 hours later. For the Soapbox complication on the watch face, the watch app also keeps a copy of the last clock, with the topic and, during a show, the speaker and segment names, but not the message, and deletes it whenever it deletes its own; the complication shows nothing from a clock more than 12 hours old or after the time following ends. Until the iPhone hands the watch app something else, watchOS also keeps on the watch the last code, id, key, name and clock the iPhone handed it. Once the iPhone learns that the timer has ended, or leaves it, it hands the watch app the code alone or nothing, so if the iPhone could not be reached when the watch found the end, that copy stays until the iPhone learns of it. Deleting the app removes them. The iPhone keeps the watch's id and key with the saved session, and the wrist alerts it has set; an alert that has been shown stays in Notification Centre until you clear it or leave the timer. With the saved session the iPhone also keeps the last clock it handed to the watch, with the same topic, message and names, until it leaves that timer or joins another.
Permissions the app asks for
- Camera: only to scan the QR code on the display to pair. Images are not saved or sent anywhere.
- Local Network: only for local mode (below): so the display (usually an iPad) can share the clock on your Wi-Fi or hotspot, and the controller (a phone, or an iPad used as one) can find it and connect when the internet drops.
- Notifications (iPhone): only for wrist alerts. At a talk's warning, danger and zero times the iPhone sets an alert that iOS shows on your Apple Watch, or on the iPhone when it is unlocked. Soapbox asks only on an iPhone paired with an Apple Watch that has Soapbox. Turning notifications off stops the wrist alerts at once.
You can turn any of them off at any time in iOS Settings > Soapbox. Scanning a QR code needs Camera: if it is off, type the code instead. Local mode needs Local Network.
Local mode, when the internet drops
Local mode is an optional fallback. The main display (usually an iPad) never starts it by itself: when it loses its connection to our server it offers to switch, and it does so only when you tap. A phone goes to the display over the local network only after you tap Connect locally or scan the QR code the display shows in local mode. While local mode is on:
- the display advertises itself on your local network as “Soapbox” and shares the clock over your Wi-Fi or hotspot;
- the controller (a phone, or an iPad used as one) finds it, using an address it learned earlier, by searching your network, or from a QR code the display shows, and connects with the session's code;
- every Soapbox display advertises the same name, so if more than one is in local mode on your network (at a venue, say), the controller tries each one it finds in turn with its session code and device name until one accepts it, so a display that is not the right one may receive that code and name. Use your own hotspot or a network you trust;
- the display also serves the display web page to browsers on the same network, so a computer can show the clock too. Opening the display's address gives that device the session's code, which is all it takes to see and change the session, so anyone on that network who finds the display can show the clock or take control of it. Use your own hotspot or a network you trust;
- the clock and the phones' commands stay on that network and don't go through our server. This local connection is not encrypted;
- about every 10 seconds the display asks our server whether it can be reached, so it can tell you when the internet is back. That request carries no session code and no clock.
One part does not wait for a tap. A display that joined with an invite (an extra display) tries the main display's saved address by itself when it has not been able to reach our server for about 10 seconds, for example because the internet is down. It goes back and forth between that address and our server until one answers, whether or not the main display is in local mode, and it sends the session's code and its invite key to whatever answers at that address. It can only do this if it learned that address earlier, from our server (as described above) or from a local-mode QR code. Use your own hotspot or a network you trust.
When the internet is back the display tells you, and when you tap it hands its clock back to our server and the phones follow. What it hands back is everything the clock holds as it stands then, including what was typed or changed while in local mode: the time, the topic and notes, the message on screen, the show being run and how far it has got, and the profile settings in use (with their quick messages). From then on it is an ordinary session, as described above.
Our server and Cloudflare
The server and this website run on Cloudflare, which handles every request as part of delivering it. To stop people guessing codes, the server counts the requests to start or join a session, and a watch's requests for the clock, from each IP address (for IPv6, also from the network around it). It keeps these counts, with the codes tried that don't belong to a session, for up to 10 minutes and then deletes them; like a session, Cloudflare's storage keeps a recoverable change history of them for up to 30 days. The server does not keep a log of the requests it handles. Until 22 October 2026 it did: Cloudflare kept a record of every request for up to 7 days, with its IP address, the details the app or browser sends with it and the approximate location Cloudflare works out from the IP address, and the last of these were deleted by 30 October 2026. Now it writes a note to logs that we can search to fix problems, which Cloudflare keeps for up to 7 days, only in three cases: when the app or a page asks to join a code that doesn't exist, when the server refuses an address or network for trying too many codes that don't exist, and when something goes wrong on the server. A note holds the time and the web address of that request, which contains the session code and, when the app joins as a controller (a phone, an iPad used as one, or a display's own controls), its name, and a random connection number the app or page makes each time it starts, so the server can tell a reconnect from a second device; it is not saved on the device and identifies nothing else. A note about a refused address or network also holds that address or network; no other note holds your IP address. While we fix a problem, we can also watch requests as they arrive, with what Cloudflare sees of them, including the IP address, without storing them. We use these logs only to fix problems, and we don't combine them with anything else or use them to identify you.
This website
This site sets no cookies and loads no fonts or ads from other companies. It counts visits with Cloudflare Web Analytics: Cloudflare adds a small script to each page of this website and the web display, which reports the page, the site that linked to it, the browser, operating system and type of device, the country, and how fast the page loaded. It sets no cookies and stores nothing on your device, and we use it only to see how many people visit and how fast the pages are, not to identify you or follow you across sites. Apart from that count, the live demo runs entirely in your browser and sends nothing.
Children
Soapbox is a general tool for running events. It is not aimed at children and does not knowingly collect personal information from them. What a session holds and what Cloudflare's logs record are described above.
Changes
If this policy changes, the new version will be posted on this page with a new date.
Contact
Questions about privacy: info@soapboxtimer.app.