Privacy Policy

Track ID Deck · Last updated: 28 October 2026

Your music library stays on your phone. Audio only leaves your device when you choose to identify a song, and it is passed on to be recognised and not kept by us. We show no adverts and use no analytics or tracking software.

Who we are

Track ID Deck — the Android app (“the App”) and the website at trackidentify.com — is a trading name of Ozayr Basseer, who runs it as a sole proprietor in South Africa. Ozayr Basseer is responsible for your personal information and is our Information Officer under POPIA. For any privacy question, or to make a request about your data, contact trackiddeck@gmail.com.

Address: 90 Round The Green Street, Sunningdale, uMhlanga, KwaZulu-Natal, 4051, South Africa. Phone: 074 834 9096 (from outside South Africa: +27 74 834 9096).

What stays on your device

The App scans your device for audio files in order to show your library. That scan — filenames, titles, artists, albums, durations and folder locations — is read on your device and is never uploaded. Your playlists, favourites, rename history, settings and any background picture you choose are stored in the App’s own storage on your device. Renaming, tagging and trimming change files on your device only. To sort your library by genre and mood, the App listens to a few seconds of each song with a model that runs on your device: that audio is not uploaded or kept, and only the genre and mood it finds are stored, in the App’s own storage. Uninstalling the App deletes what it stored on your device.

If backup is switched on for your phone, Android also copies the App’s settings, playlists, favourites, rename history and each song’s genre and mood — not your music, your pictures or the App’s identifier and key described below — to your Google Account, and puts them back if you reinstall the App. That backup is kept by Google under your Google Account, not by us, and you control it in your phone’s backup settings.

Exporting your library as a playlist

Move to Spotify or YouTube Music writes a list of your songs — the artist, title, album and length the App knows for each — to a file, and Android asks you where to save it. That happens entirely on your device: the list is not uploaded, and it is not sent to us, to Spotify, to YouTube or to anyone else. We never see it, and no credits are used.

What happens to the file afterwards is up to you. If you choose to upload it to a transfer service such as Soundiiz or TuneMyMusic so that it becomes a playlist, you are giving that company your list of songs under their privacy policy and terms, and you will sign in to Spotify or YouTube Music with them rather than with us. We have no connection to those companies, receive nothing from them, and cannot see or control what they keep. Read their terms before you upload, and delete the file afterwards if you would rather it did not sit in your Downloads.

What is sent when you identify a song

In the App, identifying a song uploads up to three short clips of it (about 15 seconds each, cut from different parts of the song) to our server. If clips cannot be cut from a file, or the recognition service cannot use them, the whole audio file is uploaded instead. The App does not send the file’s name. On the website, a 12-second sample of the file is sent; if your browser cannot read the file to cut a sample, the whole file and its name are sent.

Our server forwards the audio to AudD, a music-recognition service, which returns a possible artist and title. The audio is passed through to answer your request and is not stored on our server afterwards. AudD’s handling of it is governed by AudD’s own privacy policy.

AudD says it does not keep the audio itself permanently, but it does keep the digital fingerprints it makes of it, and its terms allow it to use what it receives — stripped of details that identify anyone, and combined with other data — to improve its own service. AudD is run by companies in the United States and the United Kingdom.

Because the audio itself is sent, do not identify voice notes, personal recordings or anything containing private or confidential information.

The identifier we use

The App generates a random identifier the first time it runs, with a secret key that proves the identifier belongs to your copy of the App. It is a random value, not linked to your name, phone number, Google account or advertising ID, and it is not used to track you across other apps or websites. It is sent with identification, purchase and credit-balance requests so we can find your credits. Both are stored encrypted, with a key kept in your phone’s secure hardware, and neither is included in your phone’s backup. Credits can only be bought once you have signed in with an email address, so they belong to your account: clearing the App’s data, reinstalling it or moving to a new phone gives the App a new identifier, and signing in again brings your credits back.

The App also sends a one-way hash of your phone’s Android ID (a value Android gives each app, which changes only if the phone is reset to factory settings). We cannot turn the hash back into the Android ID, and we use it for one thing only: preventing refund abuse.

For every purchase we keep a purchase record: which account the credits went to (your email address if you are signed in, otherwise the App’s random identifier), how many credits it gave and when, and — for a purchase in the App — the hashed Android ID or — on the website — the amount paid and the code Paystack gives us for the card (not the card number). If a purchase is refunded or charged back, we use that record to take back its credits. If some had already been used, what is still owed is recorded against hashes of the account, the phone and the card, so that the next purchase by any of them pays it off first, and we count how often that has happened. Purchase records and these refund records are kept for about 13 months, and are not removed when you delete your account, because their purpose is to stop the same refund being claimed again under a fresh account. Someone who uses credits and then refunds more than once may be refused further purchases.

Checking that the App is genuine

When you buy credits, identify a song or sign in, the App first asks Google Play for an integrity check, using Google’s Play Integrity service. Google looks at the App and your phone — whether this copy of the App is the one we publish on Google Play, whether it was installed or licensed through Google Play, and whether the phone passes Android’s integrity checks — and gives the App an encrypted result, which our server asks Google to read. We receive only that result, use it to decide whether to allow that one request, and do not keep it, except that we count failed checks against your identifier for one hour to spot abuse. If the check fails, buying, identifying and signing in are off on that phone; the music player keeps working. Google processes this under Google’s privacy policy.

Signing in

You can sign in with your email address so your credits survive reinstalling the App and move with you to a new phone or to the website. We email you a six-digit code in the App, or a one-time link on the website, sent through Resend. Codes are kept for 10 minutes and links for 15 minutes, then deleted.

Once you sign in, your email address becomes the key to your account: we store it with your credit balance, and we link your device’s random identifier to it until you sign out. Signing out removes that link. Your account and its credits remain, so you can sign back in.

You can also sign in with Google, in the App or on the website. Google shows you which account you are signing in with and, if you agree, tells our server that account’s email address, that Google has verified it, and the account’s ID number at Google. We do not ask Google for your name, photo or anything else. We use the email address as described above, and store the Google account ID with your account so that only that Google account can sign in to it; it is deleted with your account. On the website, starting Google sign-in sets a second cookie for up to 10 minutes, holding a random code that ties Google’s answer to your browser. Google’s part in signing in is governed by Google’s privacy policy.

The sign-up gift. A new account made by signing in with Google in the App can be given 5 free credits. To give them only once per Google account and once per phone, we keep scrambled (hashed) copies of the Google account ID and of the phone’s hashed Android ID, with the date, for about 13 months, including after you delete your account. Deciding uses the result of the integrity check described above, which we do not keep.

On the website, opening the link signs that browser in. We set one cookie, holding a random session code that is used only to keep you signed in, and keep a scrambled (hashed) copy of it with your email address for up to 7 days or until you sign out. To stop sign-in being abused, we send at most one sign-in email to an address per minute, and after five wrong codes we pause sign-in for that address for 10 minutes; each is noted against your email address for that long.

Purchases

In the App, payments are processed by Google Play and we never see your card details. When you buy credits, a subscription or a visualiser pack, the App sends the purchase token Google issues, the product you bought and your identifier (or account) to our server so the purchase can be verified and the credits granted or the pack unlocked. We keep a record that each purchase token has been used for about 13 months, so the same purchase cannot be credited twice. For a visualiser pack we also keep, on your account, which packs it owns, when each was bought and a one-way code made from each purchase (never the token itself), for as long as the account exists, so your packs come back when you sign in on another phone and a refunded pack can be removed. Google’s handling of your payment is governed by Google’s privacy policy.

On the website, payments are processed by Paystack, which receives your email address and payment details. We store your email address against the payment reference for up to 30 days so the payment can be matched to your account and support questions answered. Paystack keeps its own record of you as a customer, including any subscription, under Paystack’s privacy policy.

Cancelling a subscription

A subscription bought in the App is cancelled in Google Play, under Payments & subscriptions; we receive no data when you do that. To cancel a subscription bought on the website, you enter your email address and we ask Paystack whether that address has an active subscription. If it does, we email a one-time cancel link, kept for 30 minutes. We also note the request for one minute to stop repeated emails to the same address.

What we store, and for how long

• Your credits — your random identifier, or your email address if you signed in, with your credit balance and each batch’s expiry date. Credits you pay for expire three years after purchase, and free credits from the sign-up gift after 30 days; expired batches are removed automatically. An account is kept until you delete it.
• Your Google account ID, if you sign in with Google — with your account, until you delete it.
• Sign-up gift records — hashes of the Google account ID and of the phone, with the date, about 13 months, including after you delete your account.
• Google sign-in on the website — the random code tying Google’s answer to your browser, up to 10 minutes.
• Device-to-account link — until you sign out or delete your account.
• Sign-in codes, sign-in links, cancel links and deletion links — 10, 15, 30 and 30 minutes.
• Website sign-in sessions — a hashed session code with your email address, up to 7 days or until you sign out.
• Sign-in abuse limits — that a sign-in email was just sent (1 minute) and a count of wrong codes (10 minutes), against your email address.
• Website payment references, with your email address — up to 30 days.
• Google Play purchase tokens — about 13 months.
• Visualiser packs — which packs your account owns, when each was bought, and a one-way code for each purchase — until you delete your account.
• Purchase records — the account each purchase credited (email address or identifier), its credits and time, and the hashed Android ID or the card code — about 13 months, including after you delete your account.
• Refund records — what is still owed after a refund, and how many times used credits were refunded, against hashes of the account, phone and card — about 13 months, including after you delete your account.
• A per-minute request count against your identifier, to limit abuse — 2 minutes.
• Answers to identifications and purchases — the result of each, against a random request code, for 24 hours, so a request the App or website repeats after a dropped connection gets the same answer and is not charged twice.
• Failed app checks — a count against your identifier, 1 hour (see “Checking that the App is genuine”).
• Encrypted backups — encrypted copies of your credits, purchase records and refund records, kept by Cloudflare for up to 30 days so they can be restored after a fault. Deleting your account deletes its copies.
• A note that an account was deleted — a hashed copy of the email address and the time, 7 days, so browsers signed in before the deletion are signed out.
• Server logs — technical records of requests to our server, kept by Cloudflare for up to 7 days (see “Your IP address and server logs”).

We do not store your audio, your library, or a history of what you have identified.

Deleting your account

You can delete your account yourself at any time. In the App, open Settings, expand Account and tap Delete account. On the web, go to trackidentify.com/delete-account: if you are signed in there you can delete straight away, and otherwise we email a one-time link to your address, kept for 30 minutes, and delete the account when you confirm.

Deleting removes your account and every credit on it (they cannot be restored or refunded), the link from each phone signed in to it, website sign-in sessions in every browser, and the sign-in codes, links and limits held against your address. A subscription bought on the website is cancelled. A subscription bought in the App is billed by Google Play and is not stopped by deleting your account, so cancel it in Google Play first. Deleting in the App also removes the credits held for that phone and replaces its random identifier with a new one.

What remains afterwards is only what is listed above as kept for a fixed time: the note that the account was deleted, website payment references until they expire, the records of used Google Play purchase tokens, which hold a token and a date but not your address, and the purchase and refund records, which are kept for about 13 months to stop refund abuse. Your music, playlists and settings are on your phone, not with us; uninstall the App or clear its data to remove them.

Who processes data for us

• AudD — music recognition; receives the audio you choose to identify.
• Cloudflare — hosts our server and website, stores the records listed above and their encrypted backups, and runs the Turnstile check on the website’s sign-in, account-deletion and cancel forms.
• Google — Sign in with Google; and, through Google Play, in-app purchases, subscription billing and Play Integrity checks.
• Paystack — payments and subscriptions on the website.
• Resend — delivery of sign-in codes, sign-in links, cancel links and deletion links.

Each processes data under its own privacy policy. We do not sell your personal information, and we do not share it for advertising.

Your IP address and server logs

Like any online service, requests from your device reveal its IP address to our hosting provider, Cloudflare, which uses it to deliver the request and protect the service from abuse. Cloudflare also keeps short technical logs of requests to our server for us — such as the address requested, the time, where the request came from (which can include its IP address and approximate location) and error messages, which can include an email address — for up to 7 days, so we can find faults and stop abuse. We do not keep IP addresses anywhere else.

When you visit the website, your browser also loads its fonts from Google Fonts, one code library from cdnjs and Cloudflare’s Turnstile check, so Google and Cloudflare see your IP address when those load. The App does none of these.

Cookies

The website uses one cookie, and only when you sign in. It is named tid_session, it holds a random session code and nothing else, and it exists so that the site knows you are signed in as you move between pages. It is set only after you open a sign-in link from your own inbox, it is marked HttpOnly, Secure and SameSite=Strict so no other site can read or send it, and it lasts 7 days or until you sign out — whichever comes first. Signing out deletes it, on your browser and on our server.

That is the whole list. We set no advertising, analytics, tracking or profiling cookies, and we do not use cookies to recognise you across other websites. The site stores nothing else in your browser: no local storage, no session storage, no tracking pixels and no fingerprinting scripts of our own. Browsing the site works with no cookie at all; identifying songs and buying credits need you to be signed in.

Because the one cookie we set is strictly necessary to provide a service you asked for — signing in — we do not show a cookie consent banner, and none is required. You can still refuse or delete it in your browser settings; the only consequence is that you will not stay signed in.

Third parties your browser contacts. Three things on the site come from other companies, and your browser fetches them directly, which means those companies see your IP address and browser details in the request:

• Fonts from Google Fonts (fonts.googleapis.com, fonts.gstatic.com). Google states that Google Fonts sets no cookies and logs requests only to operate the service.
• The JSZip library from Cloudflare’s cdnjs (cdnjs.cloudflare.com), used to package renamed files as a download. It sets no cookies, and the file is checked against a fixed fingerprint so a substituted copy will not run.
• Cloudflare Turnstile (challenges.cloudflare.com), a check that the sign-in, account-deletion and cancel forms are being sent by a person and not a bot. It loads with the page and runs when you send one of those forms, looking at technical signals from your browser to decide. Anything it stores is on Cloudflare’s own domain, under Cloudflare’s privacy policy, and it is there only to keep those forms from being abused.

Paystack sets its own cookies on its checkout pages when you pay by card. That happens on Paystack’s site under Paystack’s privacy policy, not here.

The App sets no cookies at all. It is not a browser and does not use one; what it keeps on your phone is described under “What stays on your device”.

Advertising and analytics

There are none. The App contains no advertising SDK, no analytics SDK and no third-party trackers, and it does not collect your location, contacts, camera, microphone input or browsing activity. The App asks for access to your audio files, for permission to show notifications so playback controls can appear, and — only if you use “Set as ringtone” — permission to change that system setting.

Children

The App and website are for people aged 18 and over. We do not knowingly collect personal information from anyone under 18. If you believe a child has provided us with personal information, contact us and we will delete it.

Your rights

If you are in South Africa, the Protection of Personal Information Act (POPIA) gives you the right to ask what personal information we hold about you, to have it corrected or deleted, and to object to its processing. You can also complain to the Information Regulator at inforegulator.org.za. People elsewhere may have similar rights under their own laws.

The quickest way to erase what we hold about you is to delete your account, as described above. For anything else, or if you cannot use the App or the website, email trackiddeck@gmail.com from the address on your account. We respond to requests within 30 days.

International transfers

Our service providers may process data on servers outside South Africa and outside your own country: Cloudflare and Google run servers around the world, and Resend is based in the United States. We use them because we cannot provide the service you ask for without them, and each processes data under its own data-protection commitments.

Security

Traffic between the App or website and our server is encrypted in transit using HTTPS, backups of what we store are encrypted, and paid requests from the App are checked with Google Play Integrity before they are allowed. No system can be guaranteed completely secure, and we cannot guarantee the absolute security of information sent to us.

Changes

We may update this policy. The date at the top shows when it last changed, and material changes will be brought to your attention in the App before they take effect.

Contact

Questions or privacy requests: trackiddeck@gmail.com.