Privacy Policy

Local audio processing

TrackGleam processes uploaded audio locally in your browser. Your audio file does not need to be uploaded to a remote server for analysis, preview, or export. When you pick or correct a genre, the numeric measurements of that track (loudness, tonal balance, spectrum — never the audio itself or its file name) and your pick are stored so genre detection can improve.

Optional AI lyric transcription

The Music Visualizer normally keeps audio and video rendering on your device. If you explicitly press Find lyrics with AI, your browser creates a compact 16 kHz mono copy and sends it through TrackGleam to Groq for Whisper speech-to-text transcription and word timing. Groq processes that copy under the Groq privacy policy. TrackGleam does not store the audio copy or returned lyrics in its database. You can avoid this transfer completely by pasting or timing lyrics manually. This is the only feature that sends audio off your device. In the iOS app, the first use asks for your OK before anything is sent.

Album cover image generation

The Album Cover Creator lays out and renders your cover on your device. AI images are available to GleamAI users (credits, a pass, Lifetime or a paid Producer subscription). When you ask for one, the description you typed and your credit code are sent to TrackGleam: the code is checked against our records to confirm access and is never passed on, and to apply the daily fair-use limit we keep a record of each AI image request per code per day — a one-way hash of the code, the time, which service answered and whether it was made or refused — deleted after eight days. The description alone is then sent from our server to Cloudflare Workers AI, or, when that is unavailable or its daily allowance is used, to Pollinations.ai's image API, which returns the picture under that service's own terms (Pollinations may keep a copy of images it generates). The request is server to server, so your IP address is not passed on, and no audio, file name, email address, credit code or account information goes to either service. TrackGleam does not store the description or the image. You can avoid this transfer completely by choosing a stock photo, a backdrop or your own image. AI images are not offered in the iOS app or the Google Play app, where the Album Cover Creator uses stock photos, backdrops and your own images only.

Stock photos, stock video and fonts

The Album Cover Creator's stock photos and the Canvas maker's stock videos come from Pexels. Your search words go through TrackGleam to Pexels' API, and the photos and videos you see load directly from Pexels' servers, so Pexels receives your IP address and browser details when they load, under the Pexels privacy policy. Some tool pages load typefaces from Google Fonts, so Google receives your IP address and browser details when those pages load, under the Google privacy policy.

Community Showcase

The Community Showcase is a website feature and is not part of the iOS app. On the Community Showcase, the song search box sends what you type (3 or more characters, after a short pause) from your browser directly to Apple's iTunes Search API, so Apple receives that text and your IP address under the Apple privacy policy. A pasted or shared Apple Music link is looked up the same way (your browser sends Apple only the song's id), and the song's public details from Apple's answer (title, artist, artwork and preview links) travel with your request to TrackGleam, so the song can still be added when Apple does not answer our server; such songs are re-checked with Apple later. Apple Music previews stream from Apple when you press play; Spotify's player loads only when you press play on a Spotify song. When you add a song, TrackGleam checks it server to server with Apple or Spotify, and for an Apple Music song it asks MusicBrainz which Spotify artist page belongs to the artist (only the public Apple artist id is sent) so the independent-artist listener limit can be applied. Songs on the wall are public. To enforce the two-songs-a-month limit we keep a one-way hash of your IP address for 30 days.

Plays on the wall are counted without any account, name or code, to rank “Top this week”. A play counts once at least 10 seconds of a song have actually played on the wall, and each device and each network (internet connection) counts once per song per week. Your browser keeps a random id (not linked to your code, email or account) and a list of the songs added from it (since October 2026) and the songs it already counted this week, so it does not count songs added from it, or the same song twice in a week. For each counted play we store only the time, whether the song was featured, and three keyed hashes, each made together with the song: one of that random id, one of your network address (your IP address, shortened to its network part for IPv6) and one of the wider block of addresses it belongs to (so one block adds at most three listeners to a song in a week). The hashes are made with a random key that is replaced every week and deleted 8 days after its week starts; after that they can no longer be linked to any address or device. The play records are deleted after 8 days; your IP address itself is never stored with them (our host's standard request logs are kept for up to 7 days), the hashes cannot be linked across songs or weeks, and they are used only to count one play per device and per network and to apply that block limit. Shared networks (offices, campuses) therefore count once. The per-connection limit on these requests is a short-lived rate counter that is not stored. A play while a song is featured counts only toward that member's own numbers, never the public chart, and no play counts are shown publicly. Hiding a song is kept in your browser and hides it for you only; only a report we review removes a song for everyone. Earlier anonymous vote records (a one-way hash of the random id, never your IP address) are no longer used and expire on their own. Featured songs count how often their card was on screen (at least half visible for a second, once per device per song per day, not on a device that holds the featuring member's code): only the number is kept, never who saw it, and only the featured member sees it. Each song on the wall carries a coarse language tag, worked out from the script of its title and artist or the page language of whoever added it, and the country Cloudflare reports for the connection that added it; these sort the wall for visitors who use the same language. The wall uses your browser's language setting for that sorting; it is not stored.

If you hold a TrackGleam code, your account card can show your own numbers: GleamAI masters (counted from your code's download records: one entry per GleamAI download, holding only when it happened, kept for up to 400 days and deleted with your account; for single and Creator Pack codes this is how the card shows how many you made this month), when you joined, and your featured songs with how often they were shown this week (your featured-songs list on the Community Showcase also shows how often each was played). The favorite engineer and loudest master on that card come from a short list of your GleamAI downloads kept only in this browser (time, engineer, loudness and the file's name); it is never sent to us.

Basic website data

Like most websites, this site collects limited technical information such as browser type, device type, and referrer. With your consent, we use Google Analytics 4 and Microsoft Clarity — Clarity records anonymized session interactions and heatmaps — to understand site usage, improve performance, and detect abuse. These load only after you accept analytics in the consent banner (and are not loaded if your browser sends a Do Not Track or Global Privacy Control signal). The names of files you load are masked in these recordings — file names, like your audio, stay on your device. If your browser cannot open a file you load, the page tries to read it itself, on your device: it may load one or two more files from trackgleam.com to do that (our own file reader and, for some MP3 files, the open-source mpg123 decoder — its licence (LGPL-2.1) and source), and your audio is never sent anywhere. On the website, if something on the page fails (a file that will not load, a master that errors, a script error), your browser sends TrackGleam a short error note so we can find and fix the problem. The note is sent whether or not you accept analytics: it is used only to fix errors, never for analytics or advertising, and it carries nothing that identifies you. Each note holds the kind of failure; the error's text, with web-address parameters, e-mail addresses, access codes, quoted text and your file's name removed; for a script error, where in TrackGleam's own code it happened (a script name, or the page, and a line and column number); the page's address without its query; your browser and operating-system family (for example, Chrome on Windows); the app version; and the time it arrived. When loading a file, a master or a measurement runs out of memory, the note also holds a few rough facts about the track and the device, so we can tell which devices need a lighter path: the track's length, sample rate and channel count; the memory the browser reports (for example, 8 GB); whether it has a touch screen; its operating-system platform (for example, ChromeOS); whether the browser's memory limit for this page's scripts is above or below 3 GB (only some browsers report it); whether the app is in its low-power mode; whether an earlier attempt on this device ran out of memory; how many renders and measurements were running; which step failed (a free master, a GleamAI master or a preview); and which attempt it was. When a file will not open, the note also says what kind of file it is, as read from its first bytes (for example, an AIFF file, or a video with no sound track), and for an MP4 or WebM file which sound and picture formats it holds and whether its index is complete; whether the page’s own reader for WAV, AIFF, MP4 or MP3 files also tried to open it (and failed); its extension, from a fixed list of audio and video extensions, only when its bytes are a text file, a web page or a kind that is not recognised; a rough size range (for example, 1–10 MB); the memory the browser reports; and where the file came from (chosen by you, a saved copy, a recording or another TrackGleam page) — never its name. If the page reloads while a master or a render is running (for example, because the device ran out of memory and closed the page), the next visit sends one note saying so: which step it was on (a free master, a GleamAI master, a preview or a bulk run, and its stage), how many render passes and measurements it had started, how far it had got, how long it had run, whether the page was in the background and for how many seconds, which attempt it was and whether the same kind of track was interrupted shortly before, the track's length, sample rate, channel count and file size (in whole megabytes), the memory the browser reports and whether the app is in its low-power mode. To keep that possible, while a master runs the page keeps a note of its progress, made of the same numbers, in this tab's own session storage, and deletes it when the master ends. The free Spotify Canvas Maker and Music Visualizer send the same kind of note when a video export fails or the page reloads while one is being made: which tool, the error's text (for a failure), how far it had got, how long it had run, whether the page was in the background and for how many seconds, the video's length and frame size, whether it was made frame by frame, in real time or as a still picture, the track's length, sample rate and channel count, and the memory the browser reports; while a video is being made, the page keeps those numbers in this tab's session storage and deletes them when it ends. If a master stops making progress for several minutes, the note says so with the same kind of numbers: how long it had been silent and how long it had run, how far it had got, which attempt it was, the track's length and sample rate, the memory the browser reports and whether the app is in its low-power mode; to judge "several minutes" on each device, the page remembers in its own storage how long this device's renders usually go quiet (a number of milliseconds, nothing else). It carries no audio, no file names and no account or device identifier; your browser may send this site's cookies along with it, as with any request to this site, but TrackGleam does not read or keep them with the note, and your IP address is not stored with it. At most five notes are sent per page view. Each note is kept for 30 days and then deleted automatically. The Google Play and App Store apps do not send these notes.

Render counts. So we can tell whether mastering works on each kind of browser, the website counts masters (and the video exports of the Spotify Canvas Maker and Music Visualizer) anonymously: when a free or GleamAI master starts, when it finishes, when you stop it before it finishes, when the page was closed while it ran (counted on your next visit), when it stopped making progress, and when it ran out of memory and a second, lighter try worked or did not, your browser sends TrackGleam a count of that one event. Each count holds only the event, the kind of master (free, GleamAI or paid GleamAI) or which of the two tools made the video and the browser family, which TrackGleam reads from the standard browser identification your browser sends with every request (for example, Safari on iPhone or Chrome on Android); whether the device has a touch screen is also sent, only to tell an iPad from a Mac. A count carries no audio, no file names, no facts about the track, no cookies and no account or device identifier, and your IP address is not stored with it. Counts are kept for 14 days and then deleted automatically. The Google Play and App Store apps do not send them.

Reports you choose to send. When a master fails on the website, the message on the page offers a “Send report” button. Nothing is sent unless you press it, and the page lists what it sends before you do: the app version; your browser and operating-system family and version number; rough facts about the device (the memory the browser reports, the number of processor cores, the screen size and pixel density, whether the site runs as an installed app, how much memory the page's scripts use and their limit where the browser reports them, and whether the app is in its low-power mode); the track's length, sample rate, channel count and file size; the kind of failure, the step it was on, how far it got, how long it ran, whether the page was in the background and for how long, which attempt it was, whether the same kind of track was interrupted shortly before, whether an earlier attempt on this device ran out of memory, and how many renders and measurements were running; the engine version, the mastering intensity and style; and the note you type, if you type one. Web-address parameters, e-mail addresses, access codes, payment references and long numbers are removed from your note before it is stored. A report never carries your audio, your file's name, your access code, your e-mail address or a device identifier, and your IP address is not stored with it. Each report is kept for 30 days and then deleted automatically. The Google Play and App Store apps do not offer it.

When a paid master fails. On the website, if a GleamAI master that you have paid for, or that your credits or plan cover (a pass, Lifetime, a Producer subscription or its free trial), fails, stalls or is cut off because the page closed, your browser sends TrackGleam your access code with the failure report, so we can check your credits, restore one if needed and contact you. The report also holds which step it was on, the kind of failure, your browser and operating-system family, whether the device is a phone, tablet or computer, roughly how long it ran, the app version and a random number for that master — never your audio, your file's name or your e-mail address. So that one master is reported only once, even if the page reloads or you try again, this tab's own session storage keeps that random number, and whether the report was sent, until the master ends. The report is kept for 14 days (or until you delete your account); the alert we send ourselves shows only the last four characters of the code and your plan type (for example, credits or Producer). A GleamAI credit is used only when you download a finished master, so a failed master never uses one. The page also counts paid masters that start and finish, with no code or other identifier. The Google Play and App Store apps do not send these reports. In every version of TrackGleam — the website and the Google Play and App Store apps — a help-chat question sent while your device holds a paid code is marked as a paying customer's, and one that mentions a problem (such as a crash, a refund or a charge) alerts us with only the last four characters of the code, your plan type and the words it matched.

Bug reports you choose to send. In the help chat, “Send a bug report” opens a short form, and nothing is sent unless you press Send report. It sends what you typed, the email you add if you’d like a reply, and, while “Include technical details” is checked (you can uncheck it), the page you were on, your device and browser type, screen size and device memory, the app version, the tool you were using and its settings, the track’s length, sample rate, channels and file format, and recent error messages from that page — never your audio or your file names. If this device holds your access code, we use it to find an email on your account so we can reply when you don’t add one, and the report keeps only the code’s last four characters. Reports are emailed to our support inbox and kept for 120 days; deleting your account deletes the reports sent with its code or one of its email addresses. To limit abuse, a one-way keyed hash of your network address is kept for 2 days.

Advertising

TrackGleam does not currently show ads, and no advertising network runs on this site.

Payments

On the website, payments for GleamAI downloads are processed by Stripe, on Stripe's own secure checkout pages or in Stripe's secure checkout form shown inside a TrackGleam window (purchases in the iOS app: see the next section). That form is served by Stripe from Stripe's own servers: this site never sees or stores your card number. When the checkout opens inside a TrackGleam window, Stripe's script runs on this site for that checkout and Stripe sets its fraud-prevention cookies (__stripe_mid and __stripe_sid), which Stripe uses to protect the payment; they are part of the checkout you started, not analytics or advertising. For credit purchases we store an anonymous credit code and its remaining balance. We also store the email address you enter at checkout, linked to your code(s), so we can email your code and receipt and let you recover a lost code later — no name, address, or card details are stored on our servers. If you add another email for sign-in (from your account, after confirming it from that inbox, or by asking support), we store that address linked to your code the same way and use it only to sign you in; deleting your account removes it. Receipts still go to the checkout email. You can ask us to delete your stored email at any time (see Contact below). For mastering, your audio is never uploaded: only numeric analysis measurements (loudness, tone balance, and similar) are sent to configure AI processing. The optional Music Visualizer lyric transcription described above is the sole audio-upload exception and runs only after an explicit click. With these requests your device also sends TrackGleam your credit code (if it holds one) and, for GleamAI and website checkouts, a random device id; we use them to check credits, to apply the device limit of a Producer or Lifetime code (which keeps the device ids of the browsers that use it), to pick which checkout offer a browser sees and to limit abuse, and neither is passed on. The measurements are processed by our AI infrastructure providers — currently OpenAI, with Groq and Cloudflare Workers AI as fallbacks (and, for the help chat and the GleamLab tools only, OpenRouter, which passes the request to one of the open models it hosts); which one handles a given request depends on availability. For mastering and the GleamLab tools they receive only a short list of numbers describing the recording (loudness, tone balance and similar), the genre and style you chose, and the processing instructions; they receive no audio, no file name, no personal information, no account information, and no credit code. This list is kept deliberately narrow: our own server trims the measurements before they go out, so the detected musical key, for example, is never forwarded to an AI provider. AI providers may use the requests they receive to improve their models.

iOS app and App Store purchases

In the TrackGleam iOS app, purchases use Apple's In-App Purchase: Apple processes the payment, and TrackGleam never sees your payment details. To deliver and restore what you bought, TrackGleam stores the App Store transaction id and original transaction id, the app transaction id, an appAccountToken (an identifier the app derives from the credit code or device id on your device, so a purchase lands on the right code), the random device id the app creates, the product, the storefront country, and the purchase and renewal dates, linked to the credit code the purchase created. No email address is collected for an App Store purchase.

The purchase sheet has an optional box, unticked by default. If you tick it and later ask Apple for a refund, TrackGleam answers Apple's request for usage details: how much of each pack or period you used, how long you have had a code, rounded totals of what you have bought and been refunded here, and our refund recommendation — no audio and no email. You can untick it at any time.

The iOS app does not load Google Analytics, Microsoft Clarity or Google AdSense, shows no advertising, and shows no cookie-consent banner, because it loads nothing that needs one. TrackGleam keeps only its own anonymous usage counters. The website's Community Showcase is not part of the app. To delete your account from the app: ☰ menu › Account › Delete my account & data — it happens immediately (see Delete your account).

Help chat

The help chat is an AI assistant. When you send a message, the conversation (your recent messages and its replies) goes to TrackGleam and on to a third-party AI provider — OpenAI, with Groq, OpenRouter or Cloudflare Workers AI as fallbacks — to write the reply. Messages are passed on as you typed them, so don't include passwords, card numbers or other sensitive details. If your device holds a credit code, the chat also sends it to TrackGleam so the assistant can answer about your plan: our server looks up facts such as your plan, balance, and renewal and charge dates and passes those to the AI provider — never the code itself, an email address or a billing id. AI providers may use messages to improve their models. For support, TrackGleam keeps the opening question of each conversation (with anything shaped like a credit code removed), the page it was asked on and, if your device holds a code, that code and the email address on file for it (if there is one). That log keeps only the latest 100 questions; older ones drop off, and the whole log is deleted automatically 120 days after the last new question. In the iOS app, the chat asks for your consent before your first message is sent.

Ratings and reviews

On the website, when a master or an export finishes or fails in the mastering app, the Music Visualizer, the Spotify Canvas Maker or the Song Finisher, a small card may ask you to rate it, and anyone can rate at any time from trackgleam.com/reviews. When you tap a star, TrackGleam stores your star rating, any words and name you choose to show, which tool it was about, the page's address without its query, your language, whether you used Gleam or GleamAI (and which AI engineer), the genre setting of that master, whether you were on a phone or a computer, the time, and a random rating ID kept in your browser (stored on our side only as a keyed hash); never your audio, your file's name or your IP address. To count a rating we check that this browser finished a master or export on trackgleam.com: your browser keeps a signed receipt for that (it names the tool and the time, nothing else) and sends it with the star. When you tap a star, your browser also runs Cloudflare Turnstile, an automatic check that you're not a bot (it shows nothing in most cases); Cloudflare processes technical signals from your browser for that check under its own Turnstile privacy terms, and we receive only a pass or fail. A rating that doesn't pass is stored but not counted. When your words go public, we send just those words (never your name, your code or anything else) to OpenAI, our AI provider, once, to translate them into the site's other languages. Visitors see the translation in their language, with your original one tap away. If you rate while signed in with an access code, we store a keyed hash of the code to keep one rating per purchase and to check, without changing anything, whether the code received free credits or complimentary access (those ratings are labeled and not counted) and whether it carries a paid GleamAI purchase with no refund or dispute (that review then shows "Verified GleamAI customer"; we re-check this daily and remove the label if the purchase is refunded or disputed or the code is deleted). When a browser that holds an access code is about to show the rating card, it sends the code to our server once to ask whether that code has already rated on another device, so you are not asked again; the answer is yes or no, and nothing is stored. Words you type in the box marked "shown on trackgleam.com", with the name you chose (or "Anonymous"), are published on trackgleam.com after a 48-hour check; a private note is never shown. If you add an email address, it is used only to reply to you: your words and note are sent to the developer's inbox with that address to reply to, and the address is kept in our support log, never with your rating. Each entry in the support log, with any email address in it, is deleted automatically after 120 days, and the log keeps only the latest 200 entries (messages from the help chat's feedback form go into the same log), so an entry can go sooner. The developer is emailed only when there are words or an email address, whatever the stars; a star alone is not emailed. Words removed in moderation are deleted at once; the star and its status are kept so the counts stay checkable. When the card appears in the mastering app and you accepted analytics, Google Analytics and Microsoft Clarity count that it was shown, closed or answered, or that a send failed, and Google Analytics also records which tool, the star you tapped and whether you typed any words (never the words themselves or your email address); on the Music Visualizer, Spotify Canvas Maker and Song Finisher pages and on trackgleam.com/reviews these are not counted. Our iOS and Google Play apps never show this card. You can change or remove your rating from the same browser at trackgleam.com/reviews, or email support@trackgleam.com with your RV- reference.

ChatGPT plugin

The TrackGleam plugin for ChatGPT can ask TrackGleam's server (trackgleam.com/mcp) for a link to one of our pages. That request carries only the options the plugin picked from fixed lists — which page, the page language and, for the mastering studio, a starting genre, loudness intensity and style amount — never audio, file names, your messages or other personal information. ChatGPT may attach its own technical details to the request (such as a language setting or a coarse location hint); our server does not read them. TrackGleam does not store the options in the request or the link it returns; our host's standard request logs record each call (the time, the address called and the result, never its contents) and are kept for up to 7 days. Your conversation in ChatGPT is handled by OpenAI under the OpenAI privacy policy.

Master counts

When a master finishes, TrackGleam keeps a count of it: the day and time it was made, whether it was a free or a GleamAI master, where it was made (the website, the installed web app or its Studio mode, the Google Play app or the iOS app), the device type (phone, tablet or computer, from your browser's user-agent and whether the screen is a touchscreen), whether the request came from a TrackGleam page and, for the website and the installed web app only (never the Google Play or iOS app), the country, worked out from the connection, and the kind of site that sent you to TrackGleam in that browser tab. That last one is a single category word — for example Google, ChatGPT, Reddit, "another site" or "direct" — worked out in your browser from the referring address, which is never stored or sent; your browser keeps the word only for that tab's session, and it is not recorded at all when your browser sends a Do Not Track or Global Privacy Control signal. A count never holds audio, a file name, an IP address, an e-mail address or a code. Each count is deleted automatically after 45 days.

On the website and the installed web app (including the Microsoft Store app; never the Google Play or iOS app), a count can also carry a scrambled device number, whether the master came from a bulk run (many tracks queued at once) and whether your browser has a TrackGleam code saved (never the code itself), so we can see heavy use, such as one browser mastering many tracks. The scrambled device number and these two details are only added if you accept analytics cookies in the cookie banner: none of this is sent or kept before you choose, after you choose Decline, or when your browser sends a Do Not Track or Global Privacy Control signal; the master is still counted, without it. The device number is made on our server, one way and with a secret key, from a random number your browser keeps for TrackGleam; it is not made from your name, e-mail address or IP address, and the random number itself is not kept with the count. Another browser, or clearing this site's data, gives a different number. The same random number is also sent with GleamAI requests and website checkouts (see Payments above), and TrackGleam keeps it with a Producer or Lifetime code used in this browser, to apply that code's device limit, so a website count could in principle be matched to that code and the e-mail address stored with it. That is why these website counts are pseudonymous rather than anonymous. Counts from the Google Play and iOS apps carry no device number. Like every count, they are deleted automatically after 45 days.

On the website and the installed web app, if you accept analytics cookies, a finished master is also counted by the length of the track: under 10 minutes, 10 to 30 minutes, 30 to 60 minutes, or an hour or more. That count is kept apart from the counts above and holds only the day, that length range and whether it was a free or a GleamAI master: no device number, country, file name or anything else about you or the file. It is not sent before you choose, after you choose Decline, or when your browser sends a Do Not Track or Global Privacy Control signal, and never from the Google Play or iOS app. Each is deleted automatically after 14 days.

Sales and subscription counts

When you buy on the website, the Stripe checkout also carries three words about the purchase: whether it was started from the website or the installed web app, the device type (phone, tablet or computer, from your browser's user-agent and whether the screen is a touchscreen) and the referring-site category described above. A checkout shown inside a TrackGleam window carries one more word saying so (and a checkout that had to move from that window to Stripe's own page, a word saying that). Stripe keeps them with the purchase (and, for a Producer subscription, with the subscription). TrackGleam also keeps a count of each sale: the product, the amount, where it was bought (the website, the installed web app, the Google Play app or the iOS app), whether it was a free-trial start or a free trial converting to paid, the date and, for website purchases only, those three words and the first TrackGleam page you visited. And it keeps a count of each Producer subscription event — a free trial or a subscription starting, renewing, being cancelled or resumed, a failed payment, a refund, or the subscription ending — holding only the store (Stripe, the App Store or Google Play), the kind of event (including whether it happened during a free trial, was a trial converting to paid, was a chargeback, or ended the subscription at once) and its date and time. These counts hold no name, e-mail address, code, card details, device identifier or IP address. Each carries a one-way scrambled number, made from the store's or payment provider's id for that purchase or event, so that a count is never entered twice; TrackGleam keeps many of those ids with the purchase itself, so a count could be matched back to its purchase, which makes these counts pseudonymous rather than anonymous. These counts record no country, device type or referring site for a Google Play or App Store purchase. Each count is deleted automatically after 400 days.

Prices and buy buttons. On the website, prices are shown for the country your connection comes from (Cloudflare tells the site the country; it is used to show the price with that country's VAT or sales tax and an approximate amount in your currency, and it is not stored). We are testing two layouts of the GleamAI prices; your browser is put in one of them at random and stays there. The website counts which buy buttons were shown and tapped - only the button's place on the site (for example the pricing page or the credits card), the product, the layout, the device type (phone, tablet or computer) and the date - and a website checkout also carries which button and layout it came from, kept by Stripe with the purchase. These counts hold no name, e-mail address, code, card details, device identifier or IP address, are never sent from the iOS or Google Play app, and are deleted automatically after 400 days.

Your choices

You can manage cookies through your browser settings. If a consent banner or privacy message is shown in your region, use those controls to accept, reject, or modify choices where available.

In the iOS app, each AI feature (GleamAI and the GleamLab tools, the help chat, and Find lyrics with AI) asks before its first use. To withdraw every answer at once, open the help chat and tap Turn off next to "AI features: allowed", or delete the app; each feature then asks again before it sends anything.

Contact

Privacy questions: support@trackgleam.com, or see the support page.