How we handle your information.

Your private music library

Google sign-in lets you save and reopen your music. We use your Google account identifier to keep your library separate from other users, and a session cookie to keep you signed in. Your original uploads and saved score versions stay in your library until you delete them. They are not added to the public catalog.

We process your files to create previews and transposed editions. When you choose PDF conversion, a PDF without supported embedded notation is processed privately on our hosting infrastructure after you confirm that processing. We do not send these PDFs to an external music-recognition provider. Temporary recognition files are removed after each run. Raw recognition output expires after seven days and is removed by the next daily cleanup job. Deleting a score removes its original file and saved versions from the active library. Temporary rendering files are removed after processing; database backups may retain earlier copies for the hosting provider's configured recovery period. Files you have already downloaded remain on your device.

Open-source license and source-code information is available in our software notices.

Private score views and downloads are excluded from our first-party product analytics. If you use the shared catalog search on a library or sign-in page, a search with no results may still be recorded as described below.

Customer support chat

We use Crisp to provide customer support and collect feature requests through the chat widget. If you use it, Crisp processes your messages and any contact information you choose to provide, and may use cookies or similar browser storage to keep the conversation available. See Crisp's privacy policy for more information.

Analytics

We use first-party analytics to understand page views, sessions, returning visitors, and successful PDF downloads. It uses random browser identifiers: a session cookie that expires after 30 minutes of inactivity and a visitor cookie with a sliding one-year lifetime. Before those cookies are established, matching provisional identifiers may be coordinated in first-party browser storage and expire after five minutes of inactivity so concurrent tabs use the same anonymous session. These identifiers do not identify an account or connect activity across browsers or devices. We store page paths, entry referrer hostnames, and the IP address observed when a visitor identifier is first recorded. When a catalog search has no results, we may store the cleaned search phrase, the page where it was entered, and whether the visitor explicitly requested the piece. Missing searches are deduplicated within each anonymous session, values resembling contact details or URLs are rejected, and detailed records are retained for up to 180 days. We do not store URL query strings or user-agent strings, and we honor Do Not Track and Global Privacy Control signals for this attribution.

We may also use Google Analytics and Microsoft Clarity to improve the product. These services may use cookies or similar technologies. Those integrations remain disabled when their project identifiers are not configured.

Information you provide

Please avoid sending sensitive personal information in support messages. We use the information you provide to respond to your question, evaluate your request, and improve Transposify.