Last updated 14 November 2026
This policy explains what Cove Sound Studio's online service stores about you, why, and for how long. We collect only what sign-in, licensing, cloud projects, your inbox, payments and keeping the service secure need. We don't sell your data, and we don't use it for advertising.
1. What we store
- Account: your username and password. Your password is stored only as an Argon2id hash, which can't be turned back into the password. We don't ask for your email address, and we never send you email.
- Discord: your Discord user ID, username, display name and avatar, from Discord's authorization with the "identify" permission. We can't see your email address, your other servers or your messages on Discord, and we don't keep your Discord access token. The Cove Sound Studio bot, as a member of the Cove Sound Studio Discord server, can see whether you're in that server and which of its roles you have; it uses this only to give or take back the customer role, and to tell the team's answers in a ticket apart from others'. Your connected Discord account is also how you can prove an account is yours to reset its password, and to sign in on the account website.
- Devices: for each computer you sign in on, its name, its Windows version, the app version, a public key the app creates, and a device identifier. The device identifier is a one-way hash of hardware identifiers, made on your computer. The service stores only a keyed hash of it, never the hardware identifiers themselves.
- Licenses: the plan, dates and status, the computers a license is active on, and a hash of the license key.
- HWID changes: each time a computer is released from your license (an HWID change): its reference, your account's username and Discord user ID, the license (the last five characters of its key), the name of the computer it released, whether it was your free change, a paid one or a reset by the Cove Sound Studio team, its price, where you asked for it (the app, the account website or Discord), the reason you gave if any, and what happened to it. For a paid change, also the references of Stripe's payment page, of the payment and of any refund, and the amount paid. When the team resolves a change that didn't go through, its notes are kept with it. We also keep that your account, and your Discord user ID, used the free change.
- Paid extensions: which paid extensions (such as the Sound Lab) your Discord account owns: your Discord user ID and username, the extension, whether it's active, suspended or removed, when it started and ends, whether you bought it (and the order) or the team gave it (who, and a note for the team), and why it ended if it did.
- Inbox: the messages in your account's inbox, such as security notices, messages about your license, HWID changes and payments, and messages from the team: their title, text, category, when they arrived, whether you've read or archived them, and whether a notification of them was sent to you on Discord (and, if not, why). For a message the team sends to a group of accounts (such as everyone with a license), we keep who it was for and how many people read it.
- Notification settings: which optional messages you want in your inbox, and which messages also reach you on Discord.
- Cloud projects: the settings of packs you save to your account, such as names, weapon assignments and processing settings, and the names and properties (such as length and sample rate) of your sound files. Never the audio itself. File locations on your computer are removed before a project is uploaded.
- Purchases: when you buy a license or the Sound Lab on the website, the order: what you bought (the plan, or the Sound Lab and for how long), its price, whether you paid by card with Stripe or with crypto through Paymento (and the payment's reference there; for crypto, also the coin and amount paid and a link to the transaction on its blockchain, where transactions are public) or chose to pay in a purchase ticket, the Discord account it's for, the order's status, and whether the bot gave your Discord account the customer role. Stripe handles card payments itself, for purchases and for HWID changes: we don't receive your card details, and we don't keep the email address you give Stripe. We also keep a record of each payment notification Stripe sends (its reference and kind, so each one is handled only once), and of each time the bot gives or takes back the customer role (your Discord user ID, the order, and the result). If you pay in a purchase ticket, the order also says which ticket it was paid in, how you said you'd pay, and who on the team confirmed the payment. If you use a promo code, the order also keeps the code, the price before it and the promoter's share; the promoter isn't shown who you are.
- Promo codes: if you promote Cove Sound Studio with a promo code, your code, your Discord user ID and username, its discount and your share, who made and changed it, the orders made with it, and the payouts the team recorded (amount, when, and a note).
- Tickets: when you open a ticket in the Cove Sound Studio Discord server, its number and topic, your Discord user ID and username, your answers to its questions, the Cove account connected to your Discord account (if any) and the order a purchase ticket is about; who on the team claimed, closed, reopened or deleted it, when, and the reason they gave; when you and the team last wrote in it (not what); the rating and comment you gave it; and a transcript of the conversation (what everyone wrote in the ticket channel, with the names and pictures Discord shows, and small images posted there), saved when the ticket closes or is deleted. You read the transcript on the website, from a link in a direct message: only you and the service's administrators can open it, after signing in with Discord (which records your Discord user ID and username, and gives your browser tab a pass for that one ticket for six hours). If the website isn't set up, the transcript is sent to you as a file in the direct message instead. A link to it (or the file) is also posted in a private channel only the team can see, if the team set one up. If the bot can't read message text (a Discord setting), the transcript only shows who wrote when. Your rating is posted in the server's public review channel: everyone there sees your stars, your comment and the ticket's topic, without your name unless you choose to show your Discord name and picture. You can take it down from the same direct message.
- The Cove Sound Studio Discord server: when you join, which invite you used, whose it was, when you joined and left, and whether your Discord account was less than a day old; the bot keeps this to count each member's invites, and posts it in a channel only the team can see. If you post in the server's spam trap channel (a channel that says nobody should write in it), the bot deletes your message, sends you a direct message saying why, and removes you from the server, which deletes your messages there from the last day; it keeps only how many people it caught.
- The sound pack drop: when you upload a sound pack in its channel, the bot reads it and then deletes your upload there. It keeps your sound channels (or forum), a short fingerprint of each pack you took and of each sound it posted to you (so it can say when you upload one again and leave out sounds you already have), where each sound was posted with its file and pack name (for /find-sound), and your choices for trimming and loudness. Each upload is also compared with the fingerprints of packs Cove's creators made; when it matches one, the team is told who uploaded it. When you send sounds from the app to your sound channels, the service keeps them only until the bot has posted them, and at most a day; for an import, it keeps the message link and the links to its sounds for a day. A copy of the pack drop's data (who has which sound channels, and what was posted to whom) is kept on the service once a day, the last 7 copies, so it can be brought back if the bot loses it.
- What the app reports: when a build starts, finishes or fails, and when a pack is exported, with the pack's name and a few numbers, such as the number of weapons. Never file locations. With each license check, the app also sends a fingerprint (a SHA-256 hash) of its own program files, which is compared with the published version to notice copies that were changed; if they differ, that's kept as a security record. If an update fails its checks, the app reports why.
- Update checks: the app asks for updates with its version, its release channel and a random number made on your computer (it decides when a gradual update reaches you). Not your account.
- Security records: sign-ins (in the app and on the account website), license checks, account changes and suspicious activity, with a shortened IP address (the network part only, not your full address) and the app version. An attempt to use the service while restricted also records the computer's name.
- Website sign-ins: when you sign in on the account website, or a team member signs in to the admin panel on the website, which kind of browser and system it was (such as "Chrome on Windows"), so the sign-in can be recognised in the list of places you're signed in and in your inbox.
- Restrictions: if the Cove Sound Studio team restricts your account, one of your licenses, one of your computers (for your account, or for every account used on it) or some services (for example HWID changes, or after a breach of the Terms of Service), a record of it: what it applies to, the general reason, the team's explanation and notes, when it started and ends, who decided, any security records it refers to, and every change to it. It keeps the Discord user ID of the account it applies to and, for a computer, its device identifier (the keyed hash above). Restrictions are never based on your IP address or on details of your computer other than the device identifier above, and never decided automatically.
- Announcements: which of the team's announcements you have opened, and which were already shown to you as a notification, so they're marked the same way on all your computers.
- The creator program, if the team gives you a creator key: your terms (your revenue share and anything else agreed); each time you accept the creator agreement (when, which version, a SHA-256 hash of its exact text, your share at the time, and the computer's name); your creator lobby and the packs in it (they are cloud projects, see above, kept in a Cove Sound Studio staff account); and for each creator build: when it was made, the pack and its saved version, your username, the computer's name, the app version, the mark hidden in its sounds, and a fingerprint (a SHA-256 hash) of each file it wrote and of each sound bank and sound in its archives, and of a .zip or .rar you made of it in the app. Never the audio itself, and never file locations on your computer.
- Pack checks: when the team checks whether a pack found elsewhere came from a creator build ("Who made this?"), the app on the team member's computer reads the pack there. The service receives only fingerprints of its files and what was read of the hidden mark, and keeps a security record that a check was made, by whom, and its result.
2. On your computer
The app keeps your sign-in and license information (including which paid extensions your account owns, as the service signed it) on your computer, encrypted with Windows' own data protection for your Windows user account. Unsaved changes to your projects are kept in the app's folder on your computer, so they can be recovered after a crash. They are never uploaded. If you have a creator key and a build's fingerprints can't be sent right away (you went offline), they are kept, encrypted the same way, until they can be.
The Project Assistant runs on your computer: it reads only the project you have open, and sends nothing to us or anyone else.
The Sound Lab's library (the sounds you generate, extract from videos or import, their versions, and what they came from, such as a video's file name and location) is kept on your computer and never uploaded. Videos you open in the Sound Lab are read on your computer and never changed; nothing from them leaves it unless you use AI recognition, as below.
The Sound Lab's AI features use your own ElevenLabs account, never our service. The ElevenLabs API key you connect is kept on your computer, encrypted with Windows' own data protection for your Windows user account, and sent only to ElevenLabs, never to us. When you generate a sound, the description and the settings you chose go from your computer straight to ElevenLabs. When you use AI recognition of sounds in a video (only after you allow it in the app), up to four short clips of the video's sound (16 kHz mono, a few seconds each, no picture) go from your computer straight to ElevenLabs' Speech to Text. We don't receive or keep any of this: it's between you and ElevenLabs, under your ElevenLabs account and ElevenLabs' terms and privacy policy.
When you connect Discord or reset your password with Discord, Discord's own page opens in a window of the app. That window has a separate browsing session of its own: whatever you enter there goes to Discord, not to us, and the session is erased when the window closes.
The account pages on the website keep your sign-in in that browser tab only, until the tab is closed, you sign out, or after two hours without use (twelve hours at most). The admin panel on the website (for the Cove Sound Studio team) does the same. Neither uses cookies.
3. Why we use it
- To let you sign in and to keep your account secure, including locking it for a while after repeated wrong passwords, and telling you in your inbox about new sign-ins on the account website and other security events.
- To let you reset a forgotten password: by confirming your connected Discord account in the app or on the account website, with the /reset-password command in the Cove Sound Studio Discord server, or with a one-time code an administrator gives you after checking it's you. None of these uses your inbox or email.
- To check that your license is valid and used on the computers it allows. The device identifier is what limits a license to its computers.
- To let you change your license's computer (an HWID change): to release the computer, to charge the fee for changes after the first, free one, to confirm that payment with Stripe, to let the team fix or refund a paid change that didn't go through, and to make sure the free change is used only once, also after an account is deleted and made again with the same Discord account.
- To unlock paid extensions, such as the Sound Lab: the license check tells the app, in its signed answer, which ones your Discord account owns and until when.
- To tell you about your account: messages in your inbox when something happens to your account, your license, an HWID change or a payment, and messages from the team. Security, verification, HWID and payment messages are always kept in your inbox; the others, and the Discord notifications of all of them, follow your notification settings. A Discord notification has only a message's title, one line and a link, never its full text.
- To tell you about a license given to your Discord account: the Cove Sound Studio bot sends you a direct message on Discord with the license's details, and its key when the license is new.
- To answer the bot's commands you use about your own account (such as /my-account, /inbox and /hwid), always for the Cove account connected to the Discord account that used them.
- To answer your tickets: to open a private channel only you and the team (or, for a private matter, only the server's administrators) can see, to show the team the account, license or order the ticket is about, to let you close, reopen and rate it (and to show your rating in the public review channel, anonymously unless you add your name), to let you read its transcript and tell you in your inbox that it closed, to give you a license you paid for in it, and to see how quickly and how well tickets are answered. At most five tickets a day, and three open at once, can be opened from one Discord account.
- To keep copies of your projects that you can open on another computer.
- To run the creator program: to show you the creator agreement and record that you accepted it, to keep creator packs in your lobby, to register creator builds, and to find out where a copy of a creator pack came from (the fingerprints and the hidden mark), including to enforce the agreement.
- To sell licenses and the Sound Lab on the website: to know which Discord account what you buy goes to (you sign in with Discord, with the "identify" permission), to add you to the Cove Sound Studio Discord server so the bot can send you a license's key, and so you can open a purchase ticket there if you pay another way (Discord's "join servers for you" permission, used once, right after you sign in), to confirm card payments with Stripe (the service asks Stripe only about its own payments: whether they went through, and which order or HWID change a refund or dispute belongs to) and crypto payments with Paymento (the service asks Paymento only about the payments it created for your orders), to give your Discord account the customer role in the Cove Sound Studio Discord server once your payment is confirmed (and take it back if the payment is refunded or charged back), and to keep the records accounting requires.
- To apply restrictions the team decides on, also after the app is reinstalled or the account is made again with the same Discord account. When you create an account, your computer's device identifier is checked, so a computer restricted for every account used on it can't be used to make a new one. To restrict a computer, the team can look it up by its name. We also use this information to show you that access is restricted, until when, the general reason and a reference; and to let the team review and correct its decisions. Some patterns, such as many failed sign-ins from one network, are flagged for the team to look at; they never restrict anyone on their own.
- To prevent and investigate abuse. The service's administrators see accounts, licenses, HWID changes, paid extensions, the team's messages and how they were delivered, and account, license and security events in the admin panel (in the Cove Sound Studio app, or on its website after signing in with their password and their Discord account), and some events in private channels of the Cove Sound Studio Discord server that only the team can see. These include purchase logs (what was bought, its price, how you paid, your Discord and Cove Sound Studio accounts, the last five characters of a license key, the order and payment references, and whether you got the customer role) and restriction logs (who and what is restricted, the general reason, until when, and who decided; never the team's explanation or notes), and ticket logs (a ticket's number and topic, who opened, claimed, closed or deleted it and why, and its rating).
4. How long we keep it
- Account, Discord, device, license and project data: until you delete your account, or remove the device or project.
- Unfinished sign-ups: 30 minutes.
- A Discord connection in progress (what Discord answered, before it's added to your account): about a day.
- Password reset codes (stored as hashes): they work for 15 minutes through Discord, or 24 hours when an administrator gives you one, and are deleted a day after they stop working.
- A direct message from the bot (about your license, or a notification of a message in your inbox), while the bot sends it: its content is stored encrypted, and erased as soon as it's sent (or can't be). The record that a message was sent is deleted after a month.
- Messages in your inbox: security, verification, HWID and payment messages until you delete your account; other messages until 30 days after they expire, or 180 days after you archive them, or else until you delete your account.
- Notification settings: until you delete your account.
- Ended sign-in sessions (in the app and on the website): deleted after 90 days.
- Earlier versions of a cloud project: the last 20.
- Orders: paid ones for as long as accounting rules require us to keep them; unpaid ones end after three days and are deleted after 90 days, like orders sent to a purchase ticket.
- HWID changes and their payment records: for as long as accounting rules require us to keep them, also after you delete your account (then without a link to the account, but with the username and Discord user ID they were made for).
- The record that your account used its free HWID change: kept with your Discord user ID, also after you delete your account, so the free change can't be used again with a new account.
- Paid extensions: like licenses, they stay attached to your Discord account until you ask us to remove them; one you bought is also a purchase record (see Orders).
- Tickets: your answers, the reasons given for closing or deleting it, your comment and its transcript are erased a year after the ticket closed; its number, topic, times, who on the team handled it and your star rating are kept for the statistics. The ticket channel stays in the Discord server until the team deletes it, and copies of transcripts in Discord (in your DMs, or the team's channel) stay there. A review you posted stays in the review channel until you take it down or the team removes it. Passes to read a transcript on the website end after six hours.
- Invites: the record of which invite you joined with is kept to keep invite counts right; ask us and we'll delete yours.
- Records of Stripe's payment notifications: 90 days.
- Records of customer role changes: 90 days after the change is done.
- Which announcements you've read: until you delete your account, or the team deletes the announcement.
- Security records: 12 months. Attempts to use the service while restricted are security records.
- Restrictions: while they apply, then 24 months after they end, after which they are deleted with their history.
- Creator builds and their fingerprints: 6 years after the build, also after you delete your account (then without a link to the account, with the username), because they are how Cove proves where a creator pack came from. Creator agreement acceptances and your terms: as long as your creator key exists. Packs in a creator lobby belong to Cove and are kept in Cove's account.
5. Deleting your data
In the app, Account, then Delete account, deletes your account, devices, sessions, cloud projects, inbox and notification settings at once. A license or paid extension you were given or bought stays attached to your Discord account, so it isn't lost if you create a new account; ask us if you want it removed too. Orders you paid for and HWID changes are kept for accounting, and the record that your account used its free HWID change is kept with your Discord user ID (see above). Creator builds, their fingerprints and your creator agreement acceptances are kept for the time above, without a link to your account, and packs in a creator lobby stay in Cove's account. Security records are kept for the time above, without a link to your account, and records already posted to the administrators' Discord channels stay in Discord. A restriction that still applies is kept with the account's Discord user ID (and, for a computer, its device identifier), for the time above, so it can't be escaped by making a new account; nothing else of the account is kept with it.
6. Who else processes your data
- Discord: when you connect your Discord account, sign in on the account website or sign in to buy something, for the direct messages the bot sends you (about your license, and notifications of new messages in your inbox if you leave them on), for the bot's commands you use, for tickets, for the customer role, and for the administrators' private channels.
- Stripe: when you pay by card, for a license, the Sound Lab or an HWID change, it handles the payment on its own page, under its own privacy policy. Refunds are made through Stripe too.
- Paymento: when you pay with crypto, for a license or the Sound Lab, it handles the payment on its own page, under its own privacy policy. Payments on a blockchain are public.
- When you pay in a purchase ticket: the service you pay with (such as PayPal, Cash App or Venmo), under its own privacy policy.
- ElevenLabs, only if you connect your own ElevenLabs account to the Sound Lab: your computer sends it your descriptions and, if you allow it, the recognition clips directly, not through us, under your own account with ElevenLabs and its terms and privacy policy.
- Cloudflare: when the website's buy dialog or its sign-in and password reset forms show Cloudflare's security check (Turnstile), it runs in your browser and Cloudflare checks it under its own privacy policy; we only receive whether you passed.
- Our hosting provider, which runs the service.
7. Your rights
You can ask for a copy of your data, for a correction, or for deletion. If your account, license or computer is restricted, you can ask us to review the decision: give the reference the app shows you. Contact us through the Cove Sound Studio Discord server.
8. Changes to this policy
We may update this policy. If a change matters, we'll tell you in the app or in the Cove Sound Studio Discord server before it takes effect.