Privacy Policy

Last updated: November 14, 2026

This policy explains what personal information TrackScore Holdings, LLC collects when you use TrackScore.AI™ (the "Service"), why we collect it, who receives it, and the choices and rights you have. We've tried to keep it plain. If anything is unclear, write to us at privacy@trackscore.ai.

The short version

  • Your audio is analyzed in memory and never stored.
  • In the European Economic Area, the United Kingdom, Switzerland, Jersey, Guernsey, the Isle of Man, Gibraltar, California or Quebec, and wherever we can't tell where you are, our analytics and advertising partners get data about your visit only if you allow it, apart from the cookie-free, anonymous pings that Google's tag sends (section 4). Everywhere else they're on, and you can turn them off at any time in Your Privacy Choices, at the bottom of our pages.
  • We don't sell your personal information for money. Our advertising partners do receive some of it, as section 6 explains, and you can turn that off.
  • You can ask to see, correct or delete your information by writing to privacy@trackscore.ai.

1. Who We Are

TrackScore Holdings, LLC is the controller of your personal information: the company that decides how and why it is used.

TrackScore Holdings, LLC
7901 4th St N, STE 300, St. Petersburg, FL 33702, United States
privacy@trackscore.ai

Our representatives in the EU and the UK

Because we are established in the United States, we have appointed representatives under Article 27 of the GDPR and of the UK GDPR. You, and any data protection authority, can contact them instead of, or as well as, us about anything to do with how we process your personal information.

If you are in Quebec

The person in charge of the protection of personal information is our legal representative, whom you can reach at privacy@trackscore.ai. Your information is processed outside Quebec, mainly in the United States, by us and by the partners this policy describes.

2. Your Audio

We built TrackScore.AI™ so that your music is never stored.

  • Your audio file travels from your browser to our analysis server over an encrypted connection (TLS).
  • It is held in memory (RAM) only while it is analyzed, usually for under 60 seconds.
  • When the analysis is done, the audio is discarded from memory. It is never written to disk, copied, cached or backed up, and we cannot play it back or rebuild it afterwards.
  • We never use your audio to train machine learning models or for anything except your analysis report.
  • Your audio is never sent to any AI provider or other third party. The Klaus™ features work from your analysis measurements, not from your audio.

3. What We Collect

Analysis results

We store the results of each analysis with your account so you can see your track history: scores, technical measurements (such as BPM, key, loudness, duration and stereo width), feedback and Klaus™ comments, and your file's name. We don't keep the tags embedded in your file, such as its artist or title. If you analyze a track without an account, we store the analysis the same way, with your file's name, but linked to no account until you claim it by signing up or signing in (section 11 says how long we keep it).

  • Reports you share: if you turn on a full-report link for one of your reports, anyone who has that link can read the report, including the written notes, until you turn the link off or make a new one; your audio is never part of it. We store when the link was made, whether it has been turned off, how many times it was opened and when it was last opened. We do not record who opened it beyond the page analytics described in this policy.

Genre information

The genre you choose for a track, including any genre you type in. We use it to label your report and to decide which genres to support.

Klaus™ Live conversations

If you use Klaus™ Live, we store the messages you send, the replies, and the analysis each conversation belongs to, with technical details for each message (such as response time and error status). Only you see your conversations in the product. Our staff may look at them to run the Service, investigate abuse or errors, and check answer quality.

Ask Klaus™ on our website

On our homepage and pricing page you can ask Klaus™, the TrackScore™ AI assistant, about our plans, features and policies, or about genres and mixing. If you do:

  • What we keep: the messages you send, which suggested questions you tap, the replies, the note about your visit that we send with each message (section 9), the cards Klaus™ shows you (such as a plan or an article) and which of them you dismiss, where on our site the conversation started, and technical details for each message (such as response time and error status). We store at most 8,000 characters of any one message, and we remove the email addresses and phone numbers we detect in what you type before it reaches the AI provider or our database.
  • Your connection: we never store your IP address. We keep a one-way hash of it, made with a key that changes every day, and the country it comes from, to apply message limits and prevent abuse.
  • Who processes it: our third-party AI infrastructure provider writes the replies, as section 9 describes. Our staff may look at your conversations to run the Service, investigate abuse or errors, and check answer quality.
  • How long: 90 days, for answer quality and abuse prevention. After that they are deleted automatically.
  • Your session cookie: a necessary cookie (ts_ka), set only when you first send Klaus™ a message or tap a suggested question. It keeps your conversation together and applies message limits, and it expires after 24 hours. Our Cookies page lists it.
  • Legal basis: our legitimate interests in answering the questions you ask and in keeping the Service safe from abuse (section 8).
  • Deleting a conversation: "Delete this conversation", in the Ask Klaus™ panel, deletes the words of the conversation you are in (your messages, the replies and the notes about your visit) and its cards at once, and clears the session cookie. So that deleting cannot reset the message limits, the rest of what we keep (such as the times, the technical details, the hash of your IP address, the country and, if you were signed in, your account) stays until the 90 days are up. To have an earlier conversation deleted, write to us at privacy@trackscore.ai. If you are signed in, your conversations are linked to your account, and deleting your account deletes them.

Your account

  • Email address: to sign you in, send receipts and service emails, and, if you allow it, marketing emails (section 7).
  • Password: stored only as a cryptographic hash; we never store the password itself.
  • Google sign-in: if you use it, Google sends us your name, email address, profile picture and a Google account ID; we use them to create and match your account, and we keep them with it. If you let us publish feedback you send us with your name and leave the display name empty, we may credit it with the name from Google. We never receive your Google password.
  • ChatGPT ad click ID: if you came to us from an ad on ChatGPT, allow advertising and sign up with your email address, we keep the ad's click ID with your account so the sign-up can be credited to the ad when you confirm your address, even on another device.

Giving us an email address is necessary to create an account, and payment details (which go to Stripe) are necessary to buy credits; without them we can't provide those parts of the Service. Everything else is optional. We don't need your name, phone number or postal address to provide the Service.

Payments

Stripe, Inc. processes all payments. We never receive your card number or security code. Stripe tells us the amount and currency, any tax charged and the country it was charged for, your VAT ID if you gave one, and a transaction reference. When you buy, the checkout record we create at Stripe also holds your email address and account ID, what you buy, the country and city of your connection and your analytics and advertising choices and, depending on those choices, your browser type, your Google Analytics IDs, your IP address, the click IDs from the ad you came from and Meta's browser ID. Stripe's own privacy policy is at stripe.com/privacy.

Location and device information

When you sign up, run an analysis or buy something, we work out an approximate location (country and city) from your IP address and store it with your account, your analyses and your payments. We use it for tax, fraud prevention and reporting on where our users are. We also use the country and region of your connection, on each visit, to decide which privacy rules apply to you (section 4). Each time our privacy banner or notice appears and each time you make a privacy choice, we log the country and region, which privacy rules applied, whether your browser sent Global Privacy Control, which version of the banner text you saw, the choice you made (if any) with a random ID for that choice, the campaign tags (UTM source, campaign and content) of the link you arrived through and, if you are signed in, your account ID. Separately, we keep IP addresses in a few records: as proof of consent when you subscribe from the newsletter form on our website or turn on Aggregate Insights (together with your browser type), in short-lived counters that limit how often an address can use some features, and in the checkout record described above.

Contact form

If you write to us through the contact form, we keep your submission so we can answer and keep a support history: the name and email address you give, your message and inquiry type, any optional details you add (phone number, website, a screenshot or analysis link), the approximate location from your IP address, and your browser type. We use it only to answer you and to filter spam. An AI assistant may help us read your message and prepare our reply (see “Support messages” below).

Feedback form and beta program

If you answer our feedback form, we store your ratings, your answers, any quote and notes, the publication choice you make, and any display name, organization and links you add, with your achievement tier, how many analyses you had run and whether you were a beta tester at the time. If you let us publish your feedback, we may use your words with that name, organization and links on our website, in emails, on social media and in our ads (or, with no display name, with the name from Google sign-in). If you apply to our beta program, we store your name, email address, producer name, genre, DAW and experience level, any portfolio link and social handle you give, why you want to join and whether you are open to giving a testimonial.

Developer API

  • API keys: we store a hashed form of each key, never the key itself, with its label, its prefix and last four characters (so you can tell your keys apart), its creation date and when it was last used.
  • Usage records: for each request, the time, the endpoint, the response status, how long it took and which billing mode applied, to enforce limits, bill correctly, investigate errors and detect abuse.
  • Webhooks: the URL you register, its signing secret in encrypted form, and a log of deliveries, which includes the analysis results each delivery carried (never audio).
  • Analyses created through the API: marked as API-originated and linked to the key that created them, with any reference ID you supply. Analyses made with a sandbox test key are deleted automatically within 48 hours.
  • Product analytics: we record events about how your account uses the API (such as a key created or a daily quota reached) in PostHog, our product analytics tool, to understand and improve the API, and we send these events to no other analytics or advertising service. They carry your account ID and no device identifier. These events come from our server, not your browser, so your choices in Your Privacy Choices don't change them; we rely on our legitimate interest in improving the Service (section 8), and you can object to them by writing toprivacy@trackscore.ai.

Audio sent through the API is processed in memory and never stored, exactly as on the website. The API Terms of Service describe the same commitments for API use.

Your setup

If you tell us which DAW you use and which plugins you own, we store them with your account and use them to tailor Klaus™ advice.

Surveys

We sometimes show short, optional surveys in the Service (for example about your role and production experience). Answers are stored with your account, used to improve the Service, and sent to Klaviyo with your email profile (section 7).

Published statistics

We may publish anonymous, aggregate statistics computed across all analyses, for example the share of tracks under their genre's sub-bass target, on our website, in emails and on social media. They come from stored analysis results, never from audio or Klaus™ Live conversations, and never include anything that identifies a person or reveals one track's results. We never use them to train any music-generation or other generative AI model.

Aggregate Insights

Separately, and only if you turn it on, we may include anonymous, aggregate insights derived from your analyses in insight datasets that we share with or license to third parties. It is off unless you turn it on. Insights never include audio, Klaus™ Live conversations, or anything tied to you or a single track, and are never used to train generative AI. The switch for this setting is not in your dashboard yet; to turn it off, or to ask whether it is on, write to privacy@trackscore.ai.

4. Cookies and Your Choices

We use cookies and similar technologies (such as local storage) in three groups: necessary (always on: they keep you signed in, remember your choices and keep the site secure), analytics and advertising. Our Cookies page lists every partner, what it receives, its cookies and how long they last.

  • In the European Economic Area, the United Kingdom, Switzerland, Jersey, Guernsey, the Isle of Man, Gibraltar, California or Quebec, and wherever we can't tell where you are, analytics and advertising stay off until you turn them on.
  • Everywhere else they're on when you arrive, we show a one-time notice, and you can turn them off.
  • You can change your choice at any time in Your Privacy Choices, at the bottom of our pages. If your browser sends Global Privacy Control, advertising stays off (section 14).
  • Google's tag loads on our pages even before you choose. While analytics and advertising are off, it sets and reads no cookies and sends Google only cookie-free, anonymous pings that report the pages viewed and actions such as a sign-up (if you are signed in, with your plan and credit balance), which Google uses to estimate visits and ad results it can't measure directly.

5. Analytics

When analytics is allowed:

  • Google Analytics measures visits, where they came from, sign-ups and purchases. It receives the pages you view and the page you came from, actions such as uploads and sign-ups, your device and browser type and approximate location and, when you are signed in, your account ID, plan and credit balance.
  • PostHog records the pages you visit, product events (such as an analysis completed or a feature used) and your browser and device, runs short surveys and, where it runs, session recording. If you are signed in, it links events to your account and receives your account ID, email address, plan, credit balance and sign-up date.
  • Session recording captures a replay of your visit (clicks, scrolling, cursor movement and page changes) so we can see where the Service is confusing or broken. It never runs for visitors in the European Economic Area, the United Kingdom, Switzerland, Jersey, Guernsey, the Isle of Man or Gibraltar, or when we can't tell where you are, and it does not run when your browser sends Global Privacy Control. Form inputs, your account email, track file names and API credentials are masked in your browser before anything is sent; administrative pages are never recorded; and a recording never includes your audio.
  • Sentry counts healthy and crashed visits so we can spot broken releases.
  • Our own counters count views of presentations we share by link (the address of the page, your browser type and a one-way hash of your IP address) and remember which tips you have already seen.

Separately, and always on, Sentry receives reports of errors on our pages so we can fix them: the error, the address of the page without its query string, and your browser and device type.

6. Advertising

We advertise, or may advertise, on Meta (Facebook and Instagram), Google, TikTok, X and OpenAI's ad platform. When advertising is allowed, we share some information with these platforms to see which ads work, to show our ads to people likely to be interested, and to avoid showing them to people who already use TrackScore™:

  • From your browser: each platform's tag (often called a pixel) records the pages you view and actions such as viewing our pricing, choosing a pack or plan, starting a checkout and signing up (OpenAI's tag records no sign-ups, and Meta's also records first analyses), along with your browser, device and IP address and its own click ID if you came from one of its ads; Meta's and TikTok's tags also send the browser ID they keep in a cookie and a hashed copy of an email address or phone number you type into a form on our site. Klaviyo's on-site script recognizes returning visitors for our email marketing.
  • From our server: when you view our pricing, choose a pack or plan, start a checkout, sign up or make a purchase, we send that event to Meta, TikTok and OpenAI (TikTok gets no pricing views, OpenAI also gets the start of a subscription, and Meta also gets an event when the first analysis on your account or in your browser completes). Depending on the platform and the event, it carries a hashed (scrambled) copy of your email address, your account ID (hashed for Meta), your IP address and browser type, the click ID from the ad you came from (if any), the address of the page, Meta's browser ID, and a value: for choosing a pack or plan and starting a checkout, its list price; for a purchase, the amount you paid; and, for Meta, a fixed estimate for sign-ups, first analyses and pricing views. Meta also gets a hashed copy of your city and country. We can also send X sign-ups, choices of a pack or plan, checkout starts and purchases, but that connection is switched off at the moment. Google receives sign-ups and purchases through Google Analytics, which reports them to Google Ads; each one tells Google whether you allow advertising.
  • Renewals: we send subscription renewals to no ad platform. When analytics is allowed for your account, a renewal can reach Google Analytics as a purchase, and, like every event we send Google Analytics, it says whether you allow advertising.
  • Customer-list matching: when advertising is allowed for your account, we give Meta lists that carry a hashed copy of your email address and, in some lists, a hashed copy of your account ID, so it can match them with Meta accounts. We use them to show our ads to people who signed up but have not bought, to keep our ads away from customers, and to keep our ads for new visitors away from people who signed up or joined our email list.

In the European Economic Area, the United Kingdom, Switzerland, Jersey, Guernsey, the Isle of Man, Gibraltar, California or Quebec, and wherever we can't tell where you are, none of this happens until you allow advertising, apart from the cookie-free pings from Google's tag (section 4); if you allow analytics but not advertising, Google Analytics still receives your sign-ups and purchases, marked as not allowed for advertising. Elsewhere it is on until you turn it off in Your Privacy Choices, and Global Privacy Control turns it off for you. Each platform also has its own ad settings, such as Meta's ad preferences. Google Ads, TikTok, X and OpenAI use what they receive as independent controllers, under their own privacy policies; Meta shares control with us, as described next; and our Cookies page shows each partner's role.

Meta and joint control

For the information that Meta's pixel and our server events collect on our site and send to Meta, we and Meta Platforms Ireland Limited (Merrion Road, Dublin 4, D04 X2K5, Ireland) are joint controllers under Article 26 of the GDPR. For people in the United Kingdom, our joint controller is Meta Platforms, Inc. Our arrangement with Meta is set out in Meta's Controller Addendum. In short: we are responsible for telling you about this collection (this policy), for asking for your consent where it is needed, and for how Meta's tools are set up on our site. Meta is responsible for handling your requests to access, correct, delete or move the information it stores once it has received it, and for its own use of that information, which Meta's Privacy Policy describes. You can contact either of us, and we will pass on any request that is Meta's to answer.

7. Email

Service emails, such as sign-in links, receipts and notices about your account or a failed payment, are part of the Service. You get them even if you don't get marketing emails.

Marketing emails (The Mixdown, our newsletter, plus member offers and our welcome emails) are sent through Klaviyo, which tells us when an email is opened or a link in it is clicked. Our server also sends Klaviyo, with your email address, what it needs to choose and send these emails: account events such as signing up and confirming your email, your analyses as they complete (your file's name, its scores, BPM, key and genre) or fail (with the file's name), your credit balance and plan, which features you have tried (for our engagement emails), purchases, subscription changes and failed payments, offers, achievements you unlock, your survey answers, your feedback ratings and, if you use the Developer API, events such as a key created, a first call or a quota warning.

  • When you create an account in the European Economic Area, the United Kingdom, Switzerland, Jersey, Guernsey, the Isle of Man, Gibraltar or anywhere in Canada, or if we can't tell where you are, we send marketing emails only if you tick the box that offers them, or say yes when your analysis report offers them again.
  • Everywhere else, creating an account subscribes you, and every marketing email has an unsubscribe link.
  • Subscribing with the newsletter form on our website needs a ticked consent box; we keep the time and your IP address as a record of your consent.

If you create an account in the places the first point lists and don't tick the box, we don't add you to our mailing list or send you marketing emails unless you say yes later. Klaviyo still receives your email address with your account details (your account ID, when and how you signed up, your credit balance, plan, purchases and payment status, whether your email is confirmed and whether you allow customer-list matching) and these account events: signing up, confirming your email, purchases, subscription payments and changes and, if you use the Developer API, a key created, a first call or a quota warning. We use them only for emails about your account, such as a reminder to confirm your address or a failed payment, and to count sign-ups.

Your right to object to direct marketing

You can object to our marketing emails at any time, free of charge: use the unsubscribe link in any of them or write to privacy@trackscore.ai, and we will stop.

8. Why We Use It: Our Legal Bases

If the GDPR, the UK GDPR or Switzerland's Federal Act on Data Protection applies to you, these are the legal bases we rely on. Where we rely on a legitimate interest, you can object (section 13).

What we doLegal basis
Running your account, analyzing your tracks, Klaus™ features, purchases and service emailsPerformance of our contract with you
Ask Klaus™ on our website: answering your questions, applying message limits and preventing abuseOur legitimate interests in answering the questions you ask and in keeping the Service safe from abuse
Payment, tax and accounting recordsLegal obligation
Rate limiting, abuse and fraud prevention, and securityOur legitimate interest in keeping the Service safe and available
Error monitoring (reports of faults on our pages, with page addresses stripped of their query strings)Our legitimate interest in finding and fixing faults
Notifications to our team about sign-ups, failed sign-ins and uploads, contact messages, feedback and outagesOur legitimate interest in noticing and fixing problems quickly and in following how the Service is used
Product analytics on account events, such as how the Developer API is usedOur legitimate interest in understanding and improving the Service (you can object)
Analytics tools and session recording on our site, apart from the cookie-free pings from Google's tag (section 4)Your consent
Advertising tags, ad events from our server and customer-list matchingYour consent
Marketing emailsYour consent, for accounts created in the places section 7 lists once our sign-up forms offered the box (given then or later on an analysis report), and for the newsletter form; accounts created there before that were subscribed when they signed up, and every marketing email lets you unsubscribe or object (section 7)
Publishing anonymous, aggregate statisticsOur legitimate interest in sharing what we learn about music production (the statistics identify no one)
Aggregate Insights datasetsYour consent
Keeping a record of your privacy choices and consentsLegal obligation to be able to show your consent, and our legitimate interest in proving your choice

Outside the European Economic Area, the United Kingdom and Switzerland, where those laws don't apply, analytics, advertising and marketing emails work as sections 4 to 7 describe.

Information we get from others

Google, if you sign in with Google (your name, email address, profile picture and a Google account ID); and Stripe, about your payments (as described in section 3).

9. Who Receives It

  • Service providers that work only on our instructions: hosting and computing, our database and sign-in provider, error monitoring, analytics tools, our email services, and our AI infrastructure provider.
  • AI processing: to generate Klaus™ diagnostic feedback and Klaus™ Live replies, we send the technical measurements of your analysis, the DAW and tools you told us you use (if you did), the track parts you set (if you did) and the genre you chose (if you did) and, for Klaus™ Live, the text of your conversation, the file name and scores of the track you are discussing (for a stems session, the session name and scores and the name of each stem) and the file names or session names and scores of up to 15 of your recent analyses (long names shortened), to a third-party AI infrastructure provider located in the United States. These requests carry no account identifier or email address and never include your audio. Diagnostic feedback requests for a single track carry no file name; for a stems session they carry the session name and the name of each stem (taken from its file name), so Klaus™ can refer to each stem by name. Under our agreement with the provider, this data is not used to train AI models and is retained by the provider for no more than 30 days, except where a longer period is required by law or by the provider's safety systems.
  • Ask Klaus™: to answer you, we send the same provider what you type (with the email addresses and phone numbers we detect removed), the earlier messages of the conversation, excerpts from our website and our own notes that match your question, and a short note about your visit: the page you are on, whether you have an account, credits or a subscription and whether you have analyzed a track, which cards you were shown and which plans you turned down, which plans would get an offer price at checkout and, near your limit, how many messages you have left. Tapping a suggested question sends nothing to the provider: its answer is prepared in advance. If you then type a message, the question and its prepared answer go with the earlier messages of the conversation. These requests carry no account identifier, email address or IP address, and the agreement with the provider described above covers them.
  • Support messages: to help us answer what you send through the contact form, the beta application or by email to our support address, we send the same provider your message and the name and email address that come with it, so an AI assistant can help us sort it and prepare our reply. The agreement with the provider described above covers them.
  • Partners that also use it for their own purposes: our advertising partners (section 6) and Stripe, for payments and fraud prevention.
  • Our team's tools: a notification channel (Slack), whose messages about sign-ups, email confirmations, failed sign-ins and uploads, contact messages and feedback can include your email address and, for some of them, your name, a file name or your IP address; and our private code repository (GitHub), which holds a daily snapshot of account, credit and payment records, analysis details such as scores, BPM and key (never your file names or full results), survey answers, contact form submissions with their messages and a record of which subscribers our engagement emails reached.
  • When the law requires it: we may disclose information to comply with the law, a court order or a regulator, or to protect our rights, property or safety, or those of our users or the public.
  • People you share a report with: when you turn on a full-report link and give it to someone, they see that report's track name, genre, scores, measurements and written notes. They do not see your account details, and never your audio. Their visit is counted and processed like any other visit to the Service.

Every company that receives personal data from us is on our Subprocessor List, apart from our hosting and computing providers, which we name on request.

We don't sell your personal information for money. Our advertising partners do receive some of it (section 6), and some of them use it for their own advertising purposes. You can turn that off at any time in Your Privacy Choices or with Global Privacy Control.

Notice to Consumers Regarding the "Sale" and "Sharing" of Personal Data

We send online identifiers (such as cookie identifiers and ad click identifiers), information about your browser and connection (such as IP address, browser type and the city and country of your connection), your actions on our site (such as pages viewed, sign-ups and purchases, including purchase amounts) and hashed email addresses and phone numbers to third-party advertising platforms: Meta, TikTok, X, OpenAI and Google. We do this to measure how our ads perform and to show you targeted ads on other platforms. Under the Connecticut Data Privacy Act (including Public Act 25-113) and similar state laws, this exchange of data for advertising is a "sale" or "sharing" of personal data for valuable consideration. These laws apply to us regardless of our size, and we apply the opt-out in section 14 to everyone, wherever you live.

10. International Data Transfers

We are based in the United States, and so are our servers and most of our partners. When we transfer personal information out of the European Economic Area, the United Kingdom or Switzerland, we rely on the standard contractual clauses approved by the European Commission, as adapted for UK and Swiss transfers in each recipient's terms, and, where a recipient is certified, on the EU-US Data Privacy Framework and its UK and Swiss extensions. We don't rely on your consent for these transfers.

RecipientWhereSafeguard
Hosting, computing, database and sign-in providersUnited StatesStandard contractual clauses
Stripe (payments)United StatesStandard contractual clauses
Our AI infrastructure provider (Klaus™ features and support messages)United StatesStandard contractual clauses
Google (analytics, ad measurement, transactional email)United StatesStandard contractual clauses
PostHog (product analytics)United StatesStandard contractual clauses
Sentry (error monitoring)United StatesStandard contractual clauses
Klaviyo (email)United StatesStandard contractual clauses and the EU-US Data Privacy Framework
Meta (advertising)Ireland and the United StatesStandard contractual clauses in Meta's data transfer terms
OpenAI (advertising)United StatesStandard contractual clauses
TikTok and X (advertising)United States and other countriesThe data transfer terms of each platform
Slack and GitHub (our team's tools)United StatesStandard contractual clauses (Slack also the EU-US Data Privacy Framework)

You can ask us for a copy of these safeguards at privacy@trackscore.ai.

11. How Long We Keep It

  • Audio: not kept; discarded from memory as soon as the analysis is done.
  • Analyses and Klaus™ Live conversations: while your account exists, or until you ask us to delete them, apart from the analysis details in our backups (below). Deleting an analysis deletes its conversations.
  • Full-report links: kept with the report, including after you turn a link off, and deleted with the analysis or with your account.
  • Analyses you run without an account: you can claim one by signing up or signing in, and it is then kept like your other analyses; an unclaimed one, and any Klaus™ Live conversation about it, is kept for now with no set end date. To have one deleted, write to us with its link.
  • Ask Klaus™ conversations: 90 days, then deleted automatically. "Delete this conversation" deletes the words of the conversation you are in at once (section 3), apart from the copy in our backups (below).
  • Account data: until you ask us to delete your account. We then delete your personal information within 30 days, except what the law requires us to keep and the backups described below.
  • Payment records: as long as tax and accounting law requires, including the checkout record Stripe keeps with each payment.
  • API usage records and webhook delivery logs: while your account exists (deleting a webhook deletes its log); removed with your other account data. Sandbox analyses are deleted within 48 hours.
  • Contact form submissions: as long as needed to answer you and keep a support history, or until you ask us to delete them, apart from the copy in our backups (below).
  • Feedback form answers and beta applications: until you ask us to delete them.
  • Rate-limiting counters: kept for up to about a day after their last use. Most count by IP address; for the Developer API, some count by your account or by an API key and enforce each key's limits per minute and per day.
  • Your privacy choices: the choice cookie on your device, as our Cookies page describes (in the places section 4 lists, an accepted choice is asked again after 12 months); our log of the banners and notices shown and the choices made on the site, for 3 years; and the record on your account, for as long as the account exists.
  • Cookies and similar technologies: for the times listed on our Cookies page.
  • Analytics and advertising data: our analytics tools keep data under the retention settings we choose for them, for as long as it helps us understand how the Service is used; advertising partners keep what they receive under their own policies.
  • First analyses reported to Meta: our record of which first analyses we reported (section 6), kept for 7 days.
  • Backups: our database's daily backups hold a copy of everything for 7 days. The daily snapshot our private code repository keeps holds account, credit and payment records, analysis details such as scores, BPM and key (never your file names or full results), survey answers, contact form submissions with their messages and a record of which subscribers our engagement emails reached; its history keeps every earlier copy, so they stay there after a deletion. We use backups only to restore lost data.

12. Security

We protect your information with encryption in transit (TLS) and at rest, hashed passwords, and database rules that let each user reach only their own data. No system is completely secure, but we take reasonable and appropriate measures against unauthorized access, change, disclosure or destruction.

13. Your Rights

Depending on where you live, you can:

  • Access a copy of the personal information we hold about you.
  • Correct anything inaccurate or incomplete.
  • Delete your personal information, analyses, Klaus™ Live conversations and Ask Klaus™ conversations.
  • Move your analyses and conversations, in a machine-readable format.
  • Restrict how we use your information while a concern is being resolved.
  • Object to processing based on our legitimate interests, and to direct marketing at any time.
  • Withdraw your consent to analytics, advertising or marketing emails at any time, in Your Privacy Choices or with the unsubscribe link. Withdrawing doesn't affect what happened before.

To use any of these rights, email privacy@trackscore.ai, ideally from the address on your account. It's free, and we reply within one month. We may need to confirm it's you first.

You can also complain to a data protection authority: in the European Economic Area, the authority where you live or work (the list of authorities); in the United Kingdom, the Information Commission (formerly the Information Commissioner's Office); in Switzerland, the Federal Data Protection and Information Commissioner; and in Quebec, the Commission d'accès à l'information. We'd be glad of the chance to help first.

14. Global Privacy Control, Do Not Track and Your Privacy Choices

We honor Global Privacy Control (GPC) automatically, for every visitor, wherever you live. If your browser or an extension sends the GPC signal (the Sec-GPC header and the navigator.globalPrivacyControl property):

  1. We check for the signal on every page load (in the property) and on every request your browser makes to our server that could pass information to an advertising partner (in the header).
  2. We treat it as a valid, binding request to opt out of the sale or sharing of your personal data and of targeted advertising.
  3. The Meta, TikTok, X and OpenAI tags and Klaviyo's on-site script don't load. Google's tag and the events our server sends Google Analytics run with Google's restricted data processing, so Google may use them only to provide its measurement service to us, not for its own advertising. We send our other advertising partners no server-to-server events about your visit (such as Meta's Conversions API, TikTok's Events API, X's Conversions API or OpenAI's Conversions API). If you are signed in, we record the opt-out on your account the first time we see the signal, and from then on our server applies it to your account on every visit while you are signed in, even from a browser that doesn't send it, and we stop adding you to the customer lists we share with advertising platforms.
  4. While your browser sends the signal, our footer shows "GPC signal honored" next to Your Privacy Choices.

To opt out without a browser signal, use Your Privacy Choices in our website footer at any time and turn advertising off. GPC doesn't turn analytics off, so you can still do that in Your Privacy Choices. We don't respond to Do Not Track signals, because there is no common standard for what they mean; GPC is the signal we act on.

15. Children and Age

You must be at least 13 to use TrackScore.AI™, and at least 16 if you live in, or use the Service from, the European Economic Area, the United Kingdom or Switzerland, as our Terms say. If you are under 18, you need a parent's or guardian's permission. The Service is not directed to children, and if we learn that we have collected personal information from someone below these ages, we will delete it.

16. Changes to This Policy

When we change this policy, we update the date at the top. If a change matters, for example a new kind of partner or a new use of your information, we will tell you before it takes effect: by email if you have an account, and with a notice on our site. If we add an analytics or advertising partner, we will ask for your consent again where the law requires it.

17. Contact Us

Questions about this policy or your information: privacy@trackscore.ai, or by post to TrackScore Holdings, LLC, 7901 4th St N, STE 300, St. Petersburg, FL 33702, United States.