Track to Chords
Home

Tools

Chord detectorAudio to chords, key and tempo Chord identifierName a chord from its notes Song key finderKey and BPM of any song Chord progression finderRoman numerals for a song

Compare

Chordify alternativePrices and limits side by side Chord AI onlineChord AI for PC, in a browser
How it works Pricing My songs

Track to Chords

Privacy Policy

Last updated: 2 November 2026

Your recordings and account details deserve clear rules. Here we explain what Track to Chords collects, the reasons for processing it, retention periods and your data rights. Track to Chords determines how your personal data is used and acts as its controller.

Contents

  1. 1. Summary
  2. 2. What we collect
  3. 3. Cookies and local storage
  4. 4. Who we share with
  5. 5. International transfers
  6. 6. Your rights
  7. 7. Children
  8. 8. Security
  9. 9. Changes
  10. 10. Contact

1. Summary

We believe privacy policies should be short, specific, and accurate to the code that runs the product. Here is what we do and do not do with your information:

  • Audio deleted after 48 hours: Audio files you upload are stored only so we can run chord detection and lyrics transcription and let you replay the track, and are automatically deleted 48 hours after they are stored. The song page shows the exact date and time.
  • Saved results stay in your account: We retain detected chords, beat timings, lyrics transcripts, and your song library until you delete your account or ask us to remove them.
  • No card details held by us: All payments, renewals, and refunds are handled by Creem as Merchant of Record. We never receive or store your credit card or debit card numbers.
  • No advertising trackers or data brokers: We do not sell your personal data, we do not run third-party advertising networks, and we do not profile you for cross-site behavioral marketing.
  • We follow privacy principles: We follow the principles of modern data protection laws, including data minimization, purpose limitation, storage limitation, and prompt compliance with user rights.

2. What we collect

The table below lists every category of personal and operational data we collect, why we need it, where our infrastructure stores it, and its retention timeframe.

Data Why we collect it Where stored Retention
Email address To identify your account, send one-time verification codes, deliver trial end reminders, provide customer support, and link your purchases. Cloudflare D1 (database users table) Until you delete your account or ask us to.
Password hash To verify your identity when signing in with email and password. Stored as a salted PBKDF2 cryptographic hash; plain-text passwords are never stored or logged. Cloudflare D1 (users.password_hash) Until you delete your account or ask us to.
Google account ID To link your account when you sign in via Google OAuth. Only your Google subject identifier (google_sub) and verified email are kept. Cloudflare D1 (users.google_sub) Until you delete your account or ask us to.
Email verification codes & IP To verify your email address upon registration or password reset, and to protect the verification system against automated abuse. Codes are stored as SHA-256 hashes. Cloudflare D1 (email_codes table) Codes expire in 15 minutes; database rows are purged after 24 hours.
Failed login records & IP To prevent credential stuffing and brute-force attacks by rate-limiting repeated failed attempts per email and per IP address. Cloudflare D1 (login_failures table) Purged after 24 hours.
OAuth state & PKCE verifier Temporary random state token and PKCE verifier stored alongside requester IP to secure the Google sign-in redirect flow against CSRF attacks. Cloudflare D1 (google_oauth_states) and cookie Expires after 10 minutes; removed immediately upon sign-in completion.
Session token To keep you signed in across browser requests. The database stores only the SHA-256 hash of the random session token; a database leak cannot produce valid session cookies. Cloudflare D1 (sessions table) and cookie 30 days from creation, or until you sign out.
Uploaded audio Audio files (MP3, WAV, OGG, M4A, FLAC up to 50 MB / 15 minutes) to run chord recognition and vocal separation. Cloudflare R2 object storage (audio/{sha256}) Deleted 48 hours after it is stored. We stop serving it at that moment and a storage lifecycle rule removes the object, which can take up to 24 further hours.
Vocal stems Isolated vocal audio tracks extracted from the song by our separator model to transcribe lyrics. Cloudflare R2 object storage (stems/{jobId}/vocals.mp3) Deleted 48 hours after it is stored, by the same storage lifecycle rule.
Chord results & lyrics transcripts Detected chords, beat grids, key, tempo (BPM), song duration, generated lead sheet, lyrics transcript, and song title to display in your library and player. Cloudflare D1 (jobs and results tables) Until you delete your account or ask us to.
Song unlocks & credit ledger Record of unlocked songs, credit deductions, sign-up bonus credits, and pack purchases to track your balance and prevent duplicate charges for the same song. Cloudflare D1 (unlocks and credit_ledger tables) Until you delete your account or ask us to.
Subscription & checkout records Creem customer ID, subscription ID, product ID, status (active, trialing, past due, canceled), billing dates, trial end date, reminder status, and self-serve billing portal link. Cloudflare D1 (subscriptions and checkouts tables) Until you delete your account or ask us to.
Payment card & tax details Credit card numbers, security codes, billing postal addresses, and sales tax / VAT calculations needed to process payments and issue receipts. Creem (Armitage Labs OÜ, Merchant of Record) Retained by Creem in accordance with statutory accounting and financial record laws and the Creem Privacy Notice. We never see or store your payment card numbers.
Guest identifier & salted IP hash A random 36-character cookie identifier to associate guest uploads with your browser before registration, and a salted SHA-256 hash of your IP address to enforce the guest daily quota (5 songs per 24 hours). Cloudflare D1 (jobs.anon_id, jobs.ip_hash) Guest cookie lasts 365 days or until merged at sign-in; IP hash is evaluated against a rolling 24-hour quota window.
Usage event chronology Analysis attempts logged at /api/get_usage: public ID, user ID or guest key, client IP address, referrer path, landing path, traffic source token, job ID, source type (file, or YouTube for earlier submissions), outcome, and duration. Cloudflare D1 (usage_events table) Append-only operational log kept without foreign keys to users; retained for system monitoring and quota auditing.
Visit funnel events Anonymous per-tab session ID (funnel), funnel step (e.g. song requested, chords shown, checkout opened), page path, language, device type (mobile or desktop), country (via Cloudflare header), landing path, traffic source token, client IP address, and user ID if signed in. Cloudflare D1 (funnel_events table) Append-only operational log for /admin/visits to monitor conversion health without third-party tracking cookies.

3. Cookies and local storage

Track to Chords uses first-party HTTP cookies and browser storage (localStorage and sessionStorage) to maintain your login session, remember your preferences, and keep track of your active visit. We do not use third-party advertising cookies.

Name Storage mechanism Purpose Lifetime Classification
cd_session HTTP Cookie (HttpOnly, SameSite=Lax, Secure) Maintains your signed-in user session with a cryptographically secure random token. 30 days Essential
cd_anon HTTP Cookie (HttpOnly, SameSite=Lax, Secure) Identifies your browser as a guest visitor so you can view songs you analyzed before signing up. Transferred to your account and retired when you sign in. 365 days (cleared on sign-in) Essential
cd_oauth HTTP Cookie (HttpOnly, SameSite=Lax, Secure, Path=/api/auth/google) Carries the anti-tampering state token during the Google OAuth PKCE authorization redirect to prevent CSRF. 10 minutes (cleared upon callback) Essential
chord-theme Browser LocalStorage Remembers your visual theme preference (light or dark mode). Persistent until cleared in browser Functional
cd.song.<id> Browser LocalStorage Saves playback and display settings for a specific song (capo position, semitone transposition, speed). Persistent until cleared in browser Functional
cd.edits.<id> Browser LocalStorage Stores your in-progress chord modifications in the interactive chord editor before saving. Persistent until cleared in browser Functional
cd.sheet-size Browser LocalStorage Remembers your chosen chord sheet font size and zoom preference. Persistent until cleared in browser Functional
cd-auth-pending Browser LocalStorage (fallback SessionStorage) Remembers the email address and timestamp when a verification code was sent so you can return to the code step if the modal closes. Never stores passwords or verification codes. 15 minutes (auto-expires) Functional
cd_visit Browser SessionStorage Stores your current browser tab visit information: anonymous funnel ID, normalized landing path, and short traffic source token (e.g. google or utm:campaign). Strips full URLs and query parameters. Current browser tab session Operational / Analytics
cd-fresh Browser SessionStorage Passes a newly created song ID from the upload screen to the player page to trigger the introductory loading view. Read once and removed immediately Functional
cd-checkout Browser SessionStorage Temporarily preserves your selected checkout plan intent while opening and returning from the Creem checkout frame. Max 30 minutes (cleared upon return) Functional
cd-buy-intent Browser SessionStorage Remembers the plan you clicked so that signing in, including after an email code, opens that plan's payment form instead of sending you back to the prices. Max 15 minutes, or until the payment form opens Functional

4. Who we share with

We work with a minimal set of third-party service providers (data processors) strictly necessary to host our application, process machine learning models, handle payments, and deliver transactional emails. We do not sell your personal information or share it with data brokers.

  • Cloudflare, Inc. (Infrastructure, Storage, AI and Email): Track to Chords is hosted on Cloudflare Workers, Cloudflare D1 (database), and Cloudflare R2 (storage). Vocal separation and chord detection containers run on Cloudflare Containers infrastructure. Lyrics transcription is processed through Cloudflare Workers AI using the open Whisper Large v3 Turbo model. Transactional emails (such as verification codes and trial renewal reminders from noreply@tracktochords.com) are sent via Cloudflare Send Email service.
  • Armitage Labs OÜ / Creem (Payments & Merchant of Record): All paid plans, subscriptions, and credit packs are billed through Creem (operated by Armitage Labs OÜ, registry code 16977866, located at Rotermanni 14, Tallinn 10111, Estonia). Creem acts as the Merchant of Record, processes card payments and regional payment options, calculates and remits sales taxes/VAT, issues receipts and invoices, and manages subscription renewals and refunds. Creem processes your personal data as a data controller under the Creem Privacy Notice. Track to Chords never receives or stores your payment card credentials.
  • Google LLC (Optional Sign-In): If you choose to sign in using Google, Google authenticates your identity and provides your verified email address and account ID.

5. International transfers

Our service runs on Cloudflare's global edge network, which operates data centers worldwide, including within the United States and the European Union. Payment processing is managed by Creem (Armitage Labs OÜ, Estonia), and optional authentication through Google operates across Google's global facilities. When personal data is transferred across international boundaries, these transfers are conducted in accordance with applicable data protection laws using standard contractual clauses (SCCs) and robust technical safeguards to ensure that your personal information receives an equivalent level of security regardless of where it is processed.

6. Your rights

We respect your privacy rights and follow the principles of modern data protection standards (including the General Data Protection Regulation and the California Consumer Privacy Act). You have the following rights regarding your personal information:

  • Right of access: You can request a confirmation of whether we process your personal data and receive a copy of the data we hold about you.
  • Right to correction: You can ask us to correct inaccurate or incomplete personal information associated with your account.
  • Right to deletion: You can request that we permanently delete your account, your profile, your song library, and your linked subscription records. Because there is currently no automated self-serve delete button in the account dashboard, please email us to execute deletion.
  • Right to data export: You can request an export of your saved chord results, song records, and account profile in a structured, commonly used format.
  • Right to object or restrict processing: You can object to specific processing activities or ask us to restrict how we process your information in certain circumstances.

How to exercise your rights: To make any privacy, access, correction, or deletion request, send an email to contact@tracktochords.com from the email address registered with your Track to Chords account. We verify your identity by your email address, charge no fees for standard requests, and provide a full written response within 30 days.

When an account is deleted upon request, we remove your user record from the database, invalidate all active session tokens, delete all saved song results from your library, and detach your account link from our Creem records. Anonymized operational records that do not contain personal identifiers (such as aggregate usage counters) and statutory tax records retained directly by Creem for legal accounting compliance cannot be altered.

7. Children

Track to Chords is not directed to children under 16 years of age. We do not knowingly solicit or collect personal information from anyone under the age of 16.

If you are under 16, you must not register an account or submit audio files to Track to Chords. If we learn that we have inadvertently collected personal information from an individual under 16 without verified parental consent, we will promptly delete that account, its song library, and all associated records. If you are a parent or guardian and believe your child under 16 has submitted personal information to us, please notify us immediately at contact@tracktochords.com.

8. Security

We implement technical and organizational security controls designed to protect your personal data and uploaded content against unauthorized access, loss, or misuse:

  • Transport encryption: All web traffic and API communications are encrypted in transit using HTTPS (TLS 1.2 and TLS 1.3). Connections cannot be downgraded to unencrypted HTTP.
  • Hashed credentials and secrets: Account passwords are protected using salted PBKDF2 hashes. Active session tokens are stored in the database exclusively as SHA-256 digests, ensuring that a database compromise cannot expose usable session cookies. Email verification codes and OAuth states are likewise stored as cryptographic hashes.
  • Hardened cookie security: Authentication cookies are configured with HttpOnly (blocking JavaScript access and mitigating cross-site scripting attacks), SameSite=Lax (guarding against cross-site request forgery), and Secure attributes. State-changing POST endpoints enforce strict origin validation.
  • 48-hour audio deletion: Uploaded audio files and intermediate vocal stems are held in isolated Cloudflare R2 storage and are deleted 48 hours after they are stored.
  • Private song results: Results generated from your audio (chords, timing, lyrics) are private to your account or guest session identifier and are never published to public directories or indexed by web search engines.

9. Changes to this policy

We may update this Privacy Policy from time to time to reflect improvements to Track to Chords, changes in our technical architecture, or new legal requirements. When we make changes, we will update the "Last updated" date at the top of this page.

If we introduce material changes to how we collect, store, or share your personal data, we will provide notice through a prominent banner on the website or by sending an email notification to registered account holders. Continued use of Track to Chords after the effective date of an updated policy indicates your acknowledgment of the changes.

10. Contact us

If you have any questions, concerns, or requests regarding this Privacy Policy or how your personal information is handled, you can reach us at:

Support, privacy & deletion

contact@tracktochords.com

Write to this address for:

  • Privacy questions and data access requests
  • Account and data deletion requests
  • Questions about billing data and receipts
  • General product assistance and feedback

Legal notices

terms@tracktochords.com

Write to this address for:

  • Formal legal notices and inquiries
  • Questions concerning our Terms of Service
  • Copyright and takedown requests

For more details on billing terms and refund eligibility, please review our Refund Policy and Terms of Service, or visit our Contact page.

Track to Chords

Bring a recording. Leave with the changes. Chords, lyrics and the tools to make the song your own.

Tools

Chord detector Chord identifier Song key finder Chord progression finder

Compare

Chordify alternative Chord AI online

Product

How it works Pricing FAQ My songs

Company

Terms Privacy Refunds Contact About
© 2026 Track to Chords.