In short
None of your records are collected. Your events, venue access notes, gate codes, contact numbers, timelines and gear lists stay on your phone. None of it is sent to us. We hold no copy, and there is no server of ours for it to be sent to.
One thing is disclosed on the store forms: purchase history. RevenueCat, the service that checks whether a subscription is active, stores that status on its own servers. It is tied to an anonymous identifier, it says nothing about you or any event, and it is the only thing that leaves the device without you choosing to send it.
"No data collected" would be the easier line, and it would be false.
There is no account, no sign-in and no password, because there is nothing to sign in to. Your phone's own lock screen is what keeps your run sheets private.
There is no analytics SDK, no crash reporting, no advertising and no tracking of any kind in the app. The store privacy labels disclose exactly one data type — purchase history, not linked to you, not used for tracking — and nothing else.
Who we are
Bump In is published by Gap Found. For any privacy question, email gapfound.apps@gmail.com.
What is on your phone, and nowhere else
Everything below is written to an encrypted file in the app's private storage on your device.
| What | Why the app holds it |
|---|---|
| Event name, date, venue and address | So the run sheet knows which job it is and where |
| Bump-in and bump-out times | The two times that decide your whole day |
| Access notes — which gate, which door, keypad codes | So you can get in when there is no signal to check an email |
| Parking and unloading notes | So the van ends up where the venue expects it |
| Day-of contact names, roles and phone numbers | So you can call the venue manager from the run sheet |
| Timeline items and the moments you must be present for | So you know where to be, without reading a whole schedule |
| Gear checklist and deliverables | So nothing is left behind or forgotten after the event |
Some of this is other people's information — a venue manager's mobile number, a couple's names. You entered it, it stays on your device, and we never see it. Share a run sheet only with people who need it.
How it is protected
All of your records are serialized to a single document and encrypted with AES-256-GCM before being written to disk.
- The 256-bit key is generated on your device the first time you open the app, using the operating system's secure random generator.
- It is stored in the iOS Keychain or the Android Keystore, never in a file, never in a log, and never transmitted.
- It is marked as not migrating to another device, so it never rides an iCloud Keychain backup somewhere else.
- Every single save uses a fresh random nonce, and the encryption is authenticated — an altered file is rejected outright rather than partially read.
Encrypted backups you make yourself
Settings → Export encrypted backup produces one file, encrypted with a key derived from a passphrase you choose (scrypt). We never see the file or the passphrase. Neither can be recovered by us, or by anyone else, if you lose the passphrase.
Run sheets you share
Sharing a run sheet produces a self-contained file that you send yourself, through whatever app you choose. It is not hosted by us, there is no link for us to track, and there is no account for the recipient. Once you send it, that copy is theirs — it does not update and cannot be recalled.
Third parties, and what the store forms say
| Who | What they receive |
|---|---|
| Apple / Google, if you subscribe | The purchase itself. We never see your payment details. |
| RevenueCat, our subscription checker | An anonymous random ID and the store receipt, so the app knows the subscription is active. No name, no email, and nothing from any run sheet. |
There is no analytics provider, no advertising network and no crash reporter, so there is no fourth row to this table.
Apple — App Privacy
| Question | Answer |
|---|---|
| Do you or your third-party partners collect data? | Yes |
| Data type | Purchases → Purchase History |
| Linked to your identity | No |
| Used for tracking | No |
| Purpose | App Functionality |
Everything else — contact info, location, identifiers, usage data, diagnostics, user content — is No.
Apple’s question covers “you or your third-party partners”. Apple excuses what it collects to process an App Store transaction; it does not excuse a third party’s copy, and RevenueCat is one we chose. Not linked, because we never send a name, an email or an identifier of ours — RevenueCat generates an anonymous one. Not tracking, because there is no ad network, attribution SDK or data broker anywhere in the app.
Google Play — Data safety: the same single disclosure. Purchase history, not linked to identity, not used for tracking, for app functionality. Data is encrypted at rest. There is no account, so no account-deletion flow is required; Settings offers “Erase all data”.
Children
Bump In is a professional tool for people working events. It is not directed at children and we do not knowingly collect anything from anyone — including children — because we do not collect anything at all.
Your rights
Access, correction, export and deletion are all things you perform yourself, in the app, without asking us — because we hold nothing to give you, correct or delete. See Deleting your data.
If a law in your country gives you a right we have not covered, email us and we will answer honestly, including when the honest answer is that we have no data to act on.
Changes
If this policy ever changes, the effective date at the top changes with it. If a change ever meant Bump In started collecting something, that would be announced in the app before it took effect, not quietly added here.