The long version
Privacy Policy.
Last updated: 26 October 2026
Who and what
BITS & SETS is a notebook and setlist app for stand-up comedians,
for iPhone and iPad, and for Android (bundle and package
be.grunt.bitsandsets), published by
Grunt SRL, Rue du Couvent 20, 1332 Rixensart,
Belgium, VAT BE 0738.575.618. You write bits — a premise and
its beats — build setlists from them, read them on stage, and log
how each show went.
It is one app, and the part of it you work with — the screens, the timing, the editor — is written once and built for both phones. The parts underneath that touch a file, a key or a share sheet are written separately for each, because the two platforms do those differently and a shared version of them would not be true of either. That is why this page names a platform wherever the answer depends on one, and why anything here that names no platform is true of both.
Contact: bits@grunt.be
The core statement
BITS & SETS collects no personal data. There are no accounts, no sign-up and no login. Your bits, beats, setlists, shows and settings stay on the phone, encrypted. Nothing it holds is ever sent to a server of ours — no bit, beat, setlist or show of yours reaches us at all, and there is no service of ours for one to be sent to. Nothing in the code we write asks the network for anything either, and How this is enforced below is what is actually in the way, stated with its limits. Two things do leave the phone, you create both of them, and both go through your own phone rather than through us. One is the backup, encrypted with a passphrase only you know before it is written: you set it up, and after that the app writes it when you tap Back up now and automatically when you leave the app — into your own iCloud Drive on an iPhone or iPad, or into the app's own private folder on an Android phone, which is where it stays until you move it. The other is plain text you export yourself — a setlist, or your bits as one Markdown file — which is not encrypted, so anyone who has that file can read your material. That is deliberate, because the point of an export is to send it to somebody, and the app says so in one line beside the row that makes the file. Both are set out below.
An app is one thing and the store it arrives through is another. Everything in this policy is about BITS & SETS itself, and where somebody else's service is involved instead — Apple and Google for the beta builds, Apple for iCloud Drive — this page says so in plain words rather than letting a promise about the app be read as a promise about the platform. It is not a technicality: while the app is in beta, the store that distributes it passes us information about the build and about the people running it. Apple does that now. Google will when the Android build goes out, which it has not. Beta builds below is the whole of it, platform by platform.
How this is enforced
Everything below this section is the precise version. This one is the plain one: not what the app promises, but what is actually in the way. A promise is a sentence someone wrote; these are the parts of the app that would have to change for it to stop being true, and where one of them is weaker than it sounds we say so rather than leaving you to find out.
Nothing we write calls the network
There is no service of ours for the app to talk to —
no account system, no sync, no server of ours that holds anything of
yours — so there is nowhere for your material to be sent. Nothing in
the code we write calls the network either, and we check rather than
assume: a scan over our own code, the shared app and both platforms'
native parts, fails if it finds one of the known ways to reach a
network — fetch, a socket, a beacon, a remote URL, each
platform's own HTTP classes — or the name of one of the common
analytics and crash-reporting kits. It plants examples of those in
scratch files first and fails if it misses any, so a clean run means
the scan works rather than only that it looked. It runs among the
checks before a release.
Being exact about what that scan is: a list of patterns, not a proof. It knows the ways we know about, so something written in a way the list does not name could get past it — which is why it is not the only thing in this section, and why the Android line below is the one we lean on. It also reads our code rather than the finished package, so the honest claim is about what we wrote, not about every byte that ships. And a link that opens this page, or the support page, in your browser is not the app reaching a network: your browser makes that request, after you tap it. It does change the check, though, and that is worth saying: a written-out web address is one of the things the scan rejects, so when the app carries those two links the scan holds a named exception for those two addresses on this site and nothing else.
On Android the operating system enforces this rather than
us. The installed app holds no INTERNET
permission, so the process could not open a connection even if
something in it tried. There is no iPhone equivalent — iOS has no
such permission to withhold — so on an iPhone this rests on there
being no service of ours to call and nothing of ours calling out,
rather than on the system refusing to let it.
What we are not claiming: that the app is made of nothing but our own code. It is built on Capacitor and on the phone's own browser engine, and those bring general-purpose machinery for making web requests with them, as anything built this way does. That machinery is in the installed app on both platforms. Nothing we write calls it, and there is no service of ours for it to reach: that is the claim. It is smaller than saying the app could not possibly connect, and it is the one we can show you.
Your material is encrypted on your phone
The database holding your bits, beats, setlists and shows is encrypted at rest (SQLCipher, AES-256). The key is generated on first launch and bound to that device: on an iPhone or iPad it lives in the Keychain; on Android it is kept as ciphertext in the app's own private preferences, under a key that is generated inside the Android Keystore and never comes out of it. Copied off the phone, the file reads as noise. This has been true on every install from the first version; it is not a setting and not a paid feature.
Your material is kept out of device backups
Photos and messages ride your iCloud or computer backup. Your material deliberately does not. On iPhone and iPad the database folder is flagged so that iOS excludes it from every backup channel. Android has had two such channels since Android 12 — the backup into your Google account and the direct transfer to a new phone — and the app shuts both, listing every one of its own data areas by name rather than trusting a default: the database, the app's files and its preferences. A copy in a device backup would be unreadable anyway — the key never leaves the phone it was made on — so excluding it costs nothing and keeps ciphertext out of places it cannot be used. It also means a new phone starts empty unless you restore your own backup file, which is the next section.
The backup file
Backup is off until you set a passphrase. Once you do, the app
writes one file, bits-backup.enc, and everything about
it is designed so that nobody but you can open it:
- Encrypted before it is written. The file is your whole notebook — bits, beats, setlists, shows, settings — encrypted on the phone with AES-256-GCM. The key is derived from your passphrase (PBKDF2-SHA256, 600,000 rounds, a fresh random salt every time), and the passphrase itself is never stored anywhere but the phone it was typed on: in the iPhone's Keychain, or on Android as ciphertext in the app's own private preferences, under a key that lives inside the Android Keystore and never comes out of it — the same arrangement as the database key above. Either way it is bound to that device and excluded from device backups.
- Where it goes, on iPhone and iPad. Into your own iCloud Drive, in a folder named BITS & SETS — so it survives losing the phone and you can find it in the Files app. That is Apple's service, under your Apple account, governed by Apple's terms; what it holds is ciphertext that Apple, Grunt and anyone else can see exists but cannot read. If iCloud Drive is off for the app, the file is written to the app's own folder on the phone instead, and the Backup screen says so.
- Where it goes, on Android. There is no iCloud Drive here, so the file is always written to the app's own private folder on the phone, and the Backup screen says On this phone. No other app can reach it there and no storage permission is involved — the app has none. It is still yours to move anywhere you like, through Export below; what it does not do is go to a cloud by itself, because there is no cloud of ours to go to and on Android the app holds no permission that would let it reach one.
- When. Once when you set the passphrase, whenever you tap Back up now, and automatically when you leave the app — only if something changed since the last backup, and at most once every ten minutes. There is no schedule running in the background; the app writes the file as you put the phone down.
- Export. You can also hand the encrypted file to anything on the phone through the share sheet — AirDrop or a message on iOS, whatever the Android share sheet offers on Android. On Android the app grants that sheet access to the one backup folder and nothing else, so no other file of yours can be handed out by mistake. Where you send it is your decision; it is the same file, no less encrypted.
- There is no recovery. If you lose the passphrase, the file cannot be opened — not by you, not by Grunt, not by Apple, not by Google. The app says this before it lets you set one and asks you to confirm you have written it down. It is a real limitation and we would rather state it than soften it.
Restoring reads a backup file, asks for its passphrase, shows you what the file holds against what the phone holds, and replaces everything on the phone only after you type REPLACE. Nothing about the restore is transmitted anywhere.
Plain text you export
Two exports are plain text rather than ciphertext, and that is the point of them rather than a weakness in them: with the backup you are storing your material, and with these you are choosing to put it in front of somebody.
- A setlist. The running order with each bit's chosen beats, through the same share sheet, for sending to a producer or a booker. It contains only the material you picked for that set, and nothing about your device.
- Your bits as one Markdown file. Either the bits the list is showing at the time — a single one, or everything matching a filter — or the whole library: each bit with its premise, beats, status, language, labels and notes, under the folder it sits in, archived bits included, with your setlists appended as a readable list. What is not in it: how each show went, your settings, the database key and the backup passphrase.
Neither one is encrypted. Anyone who has the file can read your material. That is a deliberate choice rather than an oversight — a file the person you sent it to cannot open is no use to either of you — and the app puts that same sentence on the screen beside the row that makes the file, rather than leaving it to this page.
A setlist is not a file at all: the text goes straight to the share sheet, on both platforms, and nothing is written anywhere to make it. The Markdown export does need something to hand over, and what that something is differs by platform — in both cases deliberately, because a plaintext copy of your material left lying on the phone is the one risk an export of this kind actually creates.
On iPhone and iPad the file is written into the app's own temporary folder with iOS file protection on it, handed to the share sheet, and deleted as soon as the app you chose has taken it or the sheet was dismissed — whether you sent it or cancelled. Two cases where it lasts longer: the app being killed while the sheet is still open, and a deletion that fails, which the app reports rather than hides. In both, the next launch empties that folder — it tries, and if that attempt fails too it is logged and tried again at the launch after, so the honest version is that it is cleared at a launch rather than guaranteed gone at the next one. The app's own screens never receive the path; only the native code that writes the file and hands it over holds one.
On Android no file is written anywhere. The text is held in the app's own memory and streamed to the app you chose at the moment it asks for it, through a one-time permission the share sheet carries and nothing else can use. It is dropped as soon as the receiving app has read it and the sheet has closed; if nothing ever reads it, it is dropped ten minutes after the sheet closes at the latest, and in any case at your next export or when the app stops running. There is at most one of these, and it is never on disk.
Keeping a copy is one of the share sheet's own destinations, so where the file ends up is your decision; from the moment you send it, it is wherever you sent it and whoever has it can read it. The app transmits nothing in any of these cases — you perform the share, and no machine of ours is anywhere in that path.
What is stored, and where
Stored on the phone, in the encrypted database:
- Bits: the premise, each beat's text and type, status, language, tags, and when it was last edited or archived
- Setlists: name, venue, date, target length, which bits and which of their beats, per-bit notes
- Shows: when a set was performed, how each bit did (killed, OK, died) and any note you added
- Settings: your speaking pace, pause lengths, default language, appearance, and when the last backup was written
Held outside the database, bound to this device and excluded from every backup channel — in the Keychain on an iPhone or iPad, and on Android as ciphertext in the app's own private preferences under a key that never leaves the Android Keystore:
- The database key, generated on first launch
- The backup passphrase, once you set one
The search index is derived from your bits and lives in the same encrypted database. Nothing is stored anywhere else — no plain preferences file holds anything that names a bit, a beat or a set.
What the platform can see
"Nothing leaves the phone" and "nothing leaves the app" are different claims, and the first one needs its qualifications, so here they are. Three things can leave the phone: the encrypted backup, if you turn backup on and you are on an iPhone or iPad, because that one is written into your own iCloud Drive; plain text you export, once you send it somewhere; and the beta diagnostics in Beta builds below. None of the three is the app sending your material to us, and they are not equally in your hands: you set backup up once and after that the app writes the file by itself whenever you leave the app; an export is yours each time you make one; the beta diagnostics cannot be turned off from inside the app, and deleting the app is the way out of them. Nothing else the app records goes anywhere at all. The second claim — what leaves the app while staying on the phone — is this. In performance mode the app asks the phone to keep the screen awake; that is a request, not data. If you use backup on an iPhone or iPad, iOS and iCloud Drive see that a file of a certain size exists, and nothing about its contents; on Android the file sits in the app's own private folder, where nothing else on the phone sees it at all until you hand it somewhere yourself. The app hands nothing to the lock screen, to Siri, to Spotlight or to any widget, because it has none of those.
Permissions, and the one that is missing
On iPhone and iPad the app asks for no permission at all: no location, no camera, no microphone, no contacts, no photos, no notifications, no tracking. Its only capability is its own folder in your iCloud Drive — the one named BITS & SETS — which it writes the backup into and reads back when you restore. That is the whole of it: read and write in that one folder, and no sight of anything else in your iCloud Drive or on the phone.
On Android the installed app asks the system for exactly one thing,
VIBRATE — the taps you feel under your thumb. It also
defines a permission of its own, which asks the system for nothing and
is in the footnote below. Nothing else is on the list, and the name
that is absent from it is the one worth reading: the app
holds no
INTERNET permission, so the process could not
open a connection even if a bug in it asked for one. It is the
strongest form of the promise at the top of this page, because it is
enforced by the operating system rather than by us.
Two footnotes for anyone who checks this against the installed app
rather than taking our word for it, which is the right instinct.
Alongside VIBRATE you will find a permission named after
the app itself, ending
DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION: Android
defines that for an app so the app's internal messages stay private
to it, and it grants nothing outside the app. You will also see
android.permission.DUMP beside one component, which is
the opposite of a request — it is a condition another program would
have to satisfy before it could query that component. Both of these
are read out of the signed, installable package, not out of the
source code, because the package is what you run.
What we declare to the two stores says the same thing: Data Not Collected on Apple's privacy label, and no data collected and no data shared in every section of Google Play's Data safety form. Both are statements about what the app collects, and both are answers we give rather than pages you can go and read today — the app has no App Store release and the Android build has not been rolled out, so neither store has a public listing for it yet. Those are the answers it will carry when they do. What a store collects while it distributes a beta is the next section — which is a live arrangement on TestFlight today, and not yet one on Play.
Beta builds
There is no crash-reporting code and no analytics code in the app, and the scan described in How this is enforced above is what would catch one being added. Installing it as a beta is a different arrangement, because the store distributes the build, the store collects information about it, and the store passes that to us. This is the one part of BITS & SETS where we receive anything at all. We did not write it, we cannot switch it off, and it is why this page does not tell you that nothing whatsoever reaches us. The two stores do it differently, so here is each of them.
Apple, on TestFlight
Apple's own notice governs what it collects and shares; these are examples of what that notice says can be shared with a developer, where applicable, and not the whole of the list:
- whether the build was installed, how many installs there have been, and which app and build versions
- the device identifier and model, the operating system and the language
- the number of sessions, the number of crashes, and crash logs
- any feedback a tester sends — which can carry screenshots and their own written comments, and arrives with device detail attached: carrier, time zone, connection type, free disk, battery level, screen resolution and more
That is a summary, and summaries leave things out. Apple publishes the complete list in TestFlight & Privacy, and that document rather than this page is the authority on what Apple collects from a beta and passes on.
Two things we are not going to soften, and the first one matters more here than it would in another app. A crash log can contain diagnostic detail from inside the app, and a feedback screenshot shows whatever was on the screen, so this is not guaranteed to be free of your material. If you are about to send a screenshot, that is worth a look first. And this collection is part of how TestFlight works: if you would rather none of it happened, the way out is not to join the beta. We describe it here because a policy that said "no crash reporting" and stopped would be leaving out the only data we ever get.
What Apple shows us about the people testing. Apple keeps a list of a build's testers and shows it to the developer. We invite nobody by email: the beta is joined through the public link on the front page, and a tester who joins that way is on that list with no name and no address against them — beside their status, their app version, device and platform, their session and crash counts, and their feedback. One name and one address are on that list, and they belong to the person who wrote the app: Apple requires an internal tester to be a user of the App Store Connect account, so the author is a named tester of the author's own app. There is no way for us to put anybody else on that list without inviting them by email, which we do not do. Feedback is the part that can carry anything: a tester's own written comments, a screenshot of whatever was on their screen, and an email address if they typed one in, which Apple then shows on that piece of feedback. A device identifier is an identifier too — the GDPR counts an online identifier as personal data whether or not a name sits beside it. Apple describes both views itself: tester information and tester feedback.
We use it to fix bugs, and for nothing else. We keep it no longer than Apple does. How long Apple keeps it, and what Apple does with it, is Apple's notice to answer and it is linked above.
Google, on Play's testing tracks
The Android build goes out through a testing track on Google Play. It has not gone out yet — nothing has been rolled out to an Android tester as this is written, and this page is one of the things Play wants before it can be — so what follows is the arrangement it will go out under, written down before anybody can install anything rather than after. What Google passes a developer is put together differently from Apple's. Two things arrive on their own, and only the second of them can carry anything of yours:
- Numbers about the build. How many people installed it, kept it or removed it, and which app versions, device models, Android versions and countries those installs are on. It is counted and aggregated, and it names nobody.
- Crash and "app not responding" reports, each with the technical trace of what the app was doing when it stopped, the device model and the app version. These come only from phones whose owner has turned on sharing usage and diagnostics data with Google. That is a setting on the phone, between you and Google; we cannot see whether it is on, and we certainly cannot turn it on for anybody.
The caveat from the TestFlight half applies here for the same reason and we are not going to soften it either: a crash report can carry diagnostic detail from inside the app, so it is not guaranteed to be free of your material. The console shows us these reports for 90 days; Google's own reporting interface holds the underlying data for longer than that, and how long is in Google's pages rather than in our gift. We read them to fix bugs and for nothing else.
A third thing can arrive, and only if you send it. A tester on a Play track can send us private feedback through Google Play: a message you choose to write, carrying whatever you decide to put in it. It is not in the list above because nothing produces it but you — and like a TestFlight feedback note, it can hold anything you put in it, so the same caution applies. Public reviews are not possible on a test build. We invite nobody by email on Play either: the track is an open one reached by a link, so we hold no list of tester addresses.
That is a summary, and summaries leave things out. Google publishes what it collects and shows a developer in its own pages, and those rather than this page are the authority: crashes and application-not-responding errors and app statistics. As on TestFlight, this collection is part of how testing on Play works: if you would rather none of it happened, the way out is not to run a beta build — and turning off diagnostics sharing in the phone's own settings stops the crash half of it, for every app at once rather than only for this one.
Retention and deletion
Data is kept until you delete it. A bit is archived first, and deleted for good from the archive in the app; a setlist is deleted from its list; deleting the app removes the database, and on Android the backup file in the app's own folder with it — what deleting the app does not remove is at the end of this section, and it is worth reading. A backup file in your iCloud Drive is yours to delete in the Files app, and so is any copy of either file you exported anywhere else. Nothing the app records is ever transmitted to us — the backup goes to your own iCloud Drive or stays on your own phone, and anything you exported as plain text goes wherever you sent it, none of it through any machine of ours — so there is no copy of your material here and nothing of it to ask us to delete. The one exception is the beta and crash data above: that we do receive — from Apple now, and from Google once the Android build is out — we use it only to fix bugs, and it carries a device identifier rather than a name, with two additions both named above: an email address where a TestFlight tester types one into a feedback note, along with whatever else they chose to put in it — comments, a screenshot — and the name and address of the person who wrote the app, on the tester list of that person's own app. We are not going to call that anonymous. What there is, and what Apple's and Google's own pages say about it, is the beta section above.
How to have it deleted. Write to bits@grunt.be and say which build or which piece of feedback it concerns. The date you sent it, the build number, and which kind of phone you were running it on are enough to find it; we are not going to ask you for a device identifier, because the store shows that to us rather than to you. Three separate things then happen, and it is worth knowing which is which, because only the first is wholly ours to do:
- More of it stops arriving — and deleting the app is the part that actually stops it. Being removed from a tester group does not take the build off your phone; Apple says as much, and a build you still have installed can still report a session or a crash. So if you want it to stop, delete the app: nothing further is produced once it is gone.
- We delete what the console lets a developer delete. The tester record and the feedback we can see live in Apple's and Google's consoles, and what those consoles offer a developer is what we are able to act on. We will do it and tell you what we did — and if something cannot be deleted from there, we will say that instead of leaving you to assume it was.
- What Apple and Google hold themselves is theirs. Their own copies are kept for as long as their own notices say, we cannot reach into them, and a request about those goes to them. Apple's route is in TestFlight & Privacy, which sets out what Apple keeps and sends requests about a beta build to the developer of it; Google's is in its own privacy pages. We will say plainly which of the two any particular item was, rather than letting one answer stand for both.
What deleting the app does, and what it does not. It removes the database, and on Android the backup file in the app's own folder with it. Two things it does not remove:
- Beta data already sent is already sent. Apple says so in its own terms: deleting a beta app does not delete what has been supplied through it. That is why the three steps above exist.
- On an iPhone or iPad, the two secrets. The database key and the backup passphrase are Keychain items, and iOS keeps Keychain items when an app is deleted — so they can still be on the phone if you install the app again. The database key opens nothing, because the database went with the app. The passphrase is the one worth knowing about, because it is what opens a backup file you may still have in your iCloud Drive, and the app has no switch today that clears it.
Worth repeating at the end of a section about deletion: none of what you have written is in any of this in the first place. The beta data is about the build and the device, except where a feedback note you wrote yourself carries more.
Third parties, ads, children
No advertising, no third-party analytics kits, no data brokers, no sale or sharing of personal information. BITS & SETS is not directed at children under 13.
This website
The same standard applies to grunt.be itself, including
this page and the BITS & SETS pages. They are plain static files.
- No cookies. Nothing is written to your browser's storage, so there is no consent banner — there is nothing to consent to.
- No analytics and no advertising. No Google Analytics, no Google Ads, no Meta pixel, no tracking pixels of any kind, and no third-party tags.
-
No third-party requests at all. Fonts are
self-hosted rather than loaded from Google Fonts, and every image,
stylesheet and script is served from
grunt.be. The pages carry a content security policy that forbids the browser from connecting anywhere else. Loading them sends your browser to no other company's server. - Nothing to submit. There are no forms, no newsletter, no sign-up, and no account.
One honest caveat: the site is hosted by Netlify, and like any web host it necessarily receives the IP address of each request in order to send the page back. That is ordinary server operation, not analytics — it is not used to profile visitors, and it is not combined with any app data, because the app sends none.
GDPR
Grunt SRL is established in Belgium, and the General Data Protection Regulation (EU) 2016/679 applies.
All processing of your material happens locally on your own device and none of it is transmitted to the publisher, so for that there is no record here to access, rectify, port or erase. You retain full control through the app itself: your material is yours to view, export, back up or delete at any time.
The one thing the publisher does hold is the beta and crash data a store sends us — Apple's today, Google's once the Android build is out — set out above. Being straight about it means not calling it anonymous: a device identifier is an online identifier, and Article 4(1) treats an online identifier as personal data with or without a name beside it — and a feedback note can carry an email address you typed in yourself. What we can say is narrower and still worth saying: we ask no tester for a name or an address, and we invite nobody by email on either store — with the one exception named in the beta section, the record Apple requires the author of the app to hold as a tester of it, which carries a name and an address and is the author's own. What the stores show us instead is described in the beta section above, with their own pages linked — which is not the same as holding nothing of yours, and we are not going to write it as though it were. Deleting the app stops any more of it arriving, and Retention and deletion above sets out both why that is the step that does it and how to have what is already there deleted — what we can delete ourselves, and what belongs to Apple or Google and has to be asked of them. If you think we hold something of yours in spite of all this, ask, and we will tell you honestly what we find.
Questions can go to bits@grunt.be. You also have the right to lodge a complaint with the Belgian supervisory authority, the Autorité de protection des données (autoriteprotectiondonnees.be).
Changes
Material changes will be reflected on this page, with an updated date at the top.