01
The music and markings you create
When you import a PDF, draw an annotation, rename a piece, or build a setlist, that information is written to Partbook’s own storage area on your device. None of it is transmitted to us, to any server, or to any other party — it exists only where you put it, on your device.
If you use Partbook’s Share feature to send a piece elsewhere, you’re handing that file to iOS’s own share sheet, and you choose the destination yourself — Mail, Messages, AirDrop, Files, or a third-party app. Partbook doesn’t send it anywhere on its own, and has no visibility into where you ultimately send it.
02
The device identifier
Partbook generates a random identifier — not your name, email, or any account — and stores it in your device’s Keychain. Its only job is to let a guest hire code recognise that it’s being used on the same device that redeemed it, so a hired piece can be re-verified without asking you to type the code in again.
It’s stored in Keychain rather than in the app’s own files specifically so it survives deleting and reinstalling Partbook — that’s a deliberate design choice for the hire system, not incidental tracking.
03
Redeeming a guest hire code
If you redeem a hire code for a piece, Partbook sends the code and your device identifier to our backend to verify it and issue a time-limited license and a download link for that piece. The same two values are sent again periodically for a silent check-in, so an expired or shortened hire is caught reliably.
04
Screenshot counts on hired pieces
As a deterrent against redistributing hired content, Partbook counts how many screenshots you take while a hired piece is open, and locks that piece once the count crosses a threshold. That count — a number, not the screenshots themselves — is stored only on your device and is never sent anywhere.
05
What Partbook doesn’t do
No accounts, sign-in, or user profiles of any kind.
No advertising identifiers, and no ads.
No access to your contacts, location, camera, or microphone.
No selling, renting, or otherwise sharing your information with third parties for their own purposes.
06
How this is protected
Your library lives in Partbook’s private storage area, which benefits from the same on-device encryption iOS applies to every app’s data. Network requests to our backend use standard HTTPS. We take reasonable, standard measures to keep things secure, but as with any software, no method of storage or transmission can be guaranteed completely secure.
07
Retention and your choices
Your imported pieces, annotations, and setlists stay on your device until you delete them or delete the app. Deleting Partbook removes that local library entirely.
The device identifier in Keychain is designed to persist across a reinstall, by intent — it’s what lets a hired piece be recognized again without re-entering the code. If you’d like it cleared, or would like any redemption record tied to it deleted from our backend, contact us using the details below.
08
Children’s privacy
Partbook isn’t directed at children under 13, and we don’t knowingly collect information from them. Since the app doesn’t collect personal information from any user in the first place, this is largely academic — but we state it for completeness.
09
Changes to this policy
If Partbook’s features change in a way that changes what information is collected, this page will be updated and the effective date above will change accordingly. We’d encourage checking back if you have concerns, particularly after an app update that adds new functionality.
10
Contact
Questions about this policy, or requests relating to the device identifier or hire records described above, can be sent to adam@ahilton.com