This policy explains how Sheet Music Catalogue handles information when you use the app, its online features, purchases, or contact the publisher. It applies to the iOS and Android app and its supporting services. It does not describe any separate analytics, cookies, or forms that may be used by the website hosting this policy.
You do not need to create an app account. Your catalogue is stored on your device, but using online features and purchase services involves sending certain information to the providers described below.
1. Your catalogue, backups and exports
Your pieces, books, collections, composers, favourites, notes, practice sessions, performances, settings and local backups are stored on your device. Adding entries manually, creating a book manually, or typing or pasting a contents list does not by itself send your catalogue to our lookup service.
The app does not automatically sync your catalogue to a cloud account. Your operating system or device-backup service may separately back up app data according to your settings.
If you export or share a backup, you choose its destination. Email, cloud-storage and other services you select handle that copy under their own terms and privacy policies. Removing the app or clearing its data may remove your local catalogue, but does not necessarily remove device backups or exported copies. Export a backup before removing the app if you wish to keep your catalogue.
2. Optional online book searches
When you search for a book, scan an ISBN for lookup, or request or verify book contents, the app sends the search terms, ISBN and relevant edition details to our server. Depending on the request, these details can include a title, author or composer, publisher, catalogue number, instrument, grade, edition and a public reference URL you provide.
The service uses Open Library and Google Books for book records, and may use Exa for web search and page retrieval and OpenAI through Replit's AI integration to process relevant details and source text. Book covers can load from external image providers, which receive the network requests needed to display those images.
The server may cache edition metadata and suggested piece lists so results can be reused and checked. Reporting incorrect contents sends a reference to the cached edition and may update a report count.
These features do not upload your entire catalogue. However, text or URLs you enter may contain personal information if you include it. Avoid entering sensitive information in search fields. Check suggested results against your own edition before saving them.
3. Optional composer searches
Matching composers against entries already in your catalogue takes place on your device.
If you choose an online search for an individual piece, the app sends its title and relevant available context, such as its book title, ISBN, publisher, instrument, arranger or editor, to our server. Relevant context is used by Exa for search and by the AI service, together with retrieved text, to suggest a composer.
An online search is requested separately for each piece, including during a multi-piece review. This feature does not send your entire catalogue, practice history or personal notes. You can review, change or reject suggestions before applying them.
4. Optional contents-page photos
If you choose to photograph a contents page, the app requests the device permissions needed for that action and asks for confirmation before sending the image for transcription.
After confirmation, the image is sent to our server and the AI processing service to produce suggested text. The app's book cache does not store the submitted photo. This does not mean that hosting or AI providers never retain request data: their processing, security and retention practices also apply.
Avoid photographing people, contact details or other personal or sensitive information. You may decline to send the photo and type or paste the contents instead. You can manage camera permissions in your device settings.
5. Purchases and restoration
The app offers an optional one-time Unlimited in-app purchase. Apple or Google processes payment through its store, and RevenueCat helps the app retrieve products, recognise purchase entitlement and restore purchases.
This involves purchase-related identifiers, transaction records, entitlement status and technical information needed to operate the purchase service. RevenueCat can assign an app-user identifier even though the app does not require an account. Product and entitlement checks can occur when you use the app, not only when you make a purchase or use online book lookup.
The app does not receive your full payment-card details. Apple, Google and RevenueCat handle information under their applicable terms and privacy policies. Deleting the app does not erase store transaction records or automatically delete information held by these providers.
6. Technical information and service operation
The app generates a per-installation identifier and includes it in requests to our API. The server uses this identifier and IP-based controls to limit excessive requests and protect the service.
Hosting and network providers, including Replit for the app's supporting server and AI integration, process information needed to deliver requests. This can include IP addresses, request timing, response status and diagnostic information.
Our application-level request logger is configured to omit query strings and request headers. That setting does not apply to every infrastructure or third-party log. Provider retention and security practices may differ.
Information sent for an optional feature is used to deliver that feature. Technical information is also used to operate, protect and troubleshoot the service; purchase information is used to recognise and restore access.
7. Service providers and international processing
The services involved, depending on the features you use, include:
- Replit: server hosting and the AI integration used by the app's supporting services.
- OpenAI: AI processing for book contents, composer suggestions and confirmed photo transcription.
- Exa: web search and retrieval for book and composer lookups.
- Open Library and Google Books: book metadata and related resources.
- RevenueCat: purchase and entitlement management.
- Apple App Store and Google Play: store purchases, transaction records and restoration.
- External book-cover hosts and any backup or sharing services you choose.
Data sent to these providers may be processed outside Alberta or Canada, including in the United States or other countries where they operate. Laws in those locations may differ from Canadian law, and information may be accessible to authorities as permitted by applicable law.
Providers may handle some information on our behalf and some under their own terms. Their policies govern their separate processing and retention. Information may also need to be disclosed to comply with a lawful requirement.
8. Retention and security
Local catalogue information remains on your device until you change or delete it, clear app data, or otherwise remove it, subject to your device's backup behaviour.
Server-side book and contents caches may be retained to provide and recheck lookup results. Hosting logs, AI requests, purchase records and other provider-held information have separate retention periods determined by the relevant service and applicable obligations. This policy does not promise immediate deletion of all copies or a single retention period across all providers.
No transmission or storage system can be guaranteed completely secure. Please avoid submitting sensitive personal information in searches, reference URLs or photos, and protect any backups you export.
9. Your choices and privacy requests
You may use manual catalogue features without requesting online book searches, online composer suggestions or photo transcription. Declining those features does not prevent you from maintaining your catalogue manually. Purchase-service communications are separate from those optional lookups.
You can edit or delete catalogue entries and manage local backups and exported copies. Device and cloud-backup settings are controlled separately. We cannot remotely edit or delete catalogue data held only on your device.
To ask about information handled by our services, or request access, correction or deletion where applicable, use our contact form. Describe your request and the relevant feature, but do not send passwords, payment-card details or an entire catalogue.
We may need limited information to verify and locate a request. Because there is no app account, it may not be possible to associate a request with all technical records. Requests are considered under applicable privacy law and any legal retention requirements. We cannot promise deletion of independently held store records or copies in services you control; you may also need to contact those providers.
If you contact us, we receive the contact details and information you supply and use them to respond to and manage your request.
10. Children
An app-store age rating is a content rating, not a statement that no information is processed. The online features and purchase services described above can process information regardless of a user's age.
Parents and guardians should supervise children's use of online searches, photos and purchases and use available device controls. If you believe a child has sent personal information to our services, contact us so we can investigate and address the request under applicable law.
11. Changes and contact
Updates to this policy will be posted on this website. Please review it when deciding whether to use an online feature or purchase service.
For privacy questions or requests, contact:
David W.N. Benjamin
Contact us about privacy