Privacy policy

What we collect

• Account details: your name and email address, and your password stored as a one-way hash. If you sign in with Google or GitHub, we receive your name, email address, profile picture and account ID from them, never your password.
• What you create: the prompts you write, the sounds made from them, and your ratings, favorites and names. API keys you create are stored as hashes.
• Connected apps: when you connect an AI app such as Claude or ChatGPT by signing in and choosing Allow, we record which app, what you allowed and when, and keep its access tokens (refresh tokens as hashes). The app can then make sounds with your credits and see your sounds and balance; if it asks, it also receives your name and email address. What it does with the results is covered by that app's own privacy policy. You can disconnect an app at any time in API & Tools.
• Billing: your plan, trial dates, credit balance and usage history, plus the customer and subscription IDs that Stripe gives us. Card details go straight to Stripe and never reach our servers.
• Email preferences: whether you want product updates and tips by email, and each time you chose: when, where (at sign-up or in Settings), the words you saw, and the country your connection came from.
• Technical data: a session cookie that keeps you signed in, and request logs (including IP addresses) kept by our hosting provider for security and debugging.
• Anonymous usage events: which steps of the site a visit reaches (for example playing a sample, pressing Generate or opening sign-up), the site or ad campaign it came from, and whether it's on a phone or a computer. They use no cookies, store nothing on your device and include no IP address. Once you have an account, we also note when you create it (and the site or campaign of the visit that led to it), use your free sounds, go to checkout and start a trial. We keep these events for 180 days.
• Ad measurement: our pages load the Google tag (Google Ads), which tells Google about your visit and, if you came from one of our Google ads, whether you then signed up, started a trial or bought something, so we can see which ads work. It sets cookies for this. When you start a checkout, we keep that ad click's identifier with your account, so our servers can tell Google Ads when your trial starts or your first payment goes through (with the amount), even if that happens later. Ad personalization (remarketing) is turned off. In the EEA, the UK and Switzerland, and whenever your browser sends a Global Privacy Control signal, it sets no ad cookies.
• Free sounds without an account: if you make a sound before signing up, we keep what you typed and the sound. To allow one free sound per visitor a day, we also keep a code computed from your IP address that can't be turned back into it, works only for that day, and is deleted after two days. Your browser keeps a random key for the sound (and, if you asked for one before signing up, what you asked for), so you can save it to your account when you sign up. Sounds nobody saves are deleted after 7 days.

How we use it

To make and store your sounds, run your plan, trial and credits, answer support requests, keep the service secure, and prevent abuse such as repeated free trials (we keep a fingerprint of the card used for each trial for this, never the card number). The people who run Blipsmith may look at prompts and sounds to help you, investigate problems or abuse, and improve sound quality. We use the anonymous usage events to see where people get stuck on the site, so we can fix it. If you agree, we email you product updates and tips; every one has an unsubscribe link, and you can turn them off in Settings at any time. Account emails, like password resets, aren't marketing and always arrive. We don't sell personal data and we don't show ads. The Google tag is our only third-party tracker, and we use it only to measure our own ads. Apart from its cookies, the only cookies are the ones needed to keep you signed in.

Who helps us run Blipsmith

• Vercel hosts the app and keeps request logs.
• Neon hosts our database.
• Stripe handles payments, subscriptions and invoices.
• Resend sends our emails.
• Anthropic processes your prompts so our AI can decide how to make each sound and design layered sounds.
• fal.ai processes a description derived from your prompt to generate audio.
• Google and GitHub confirm your identity if you choose to sign in with them.
• Google also measures whether our ads lead to sign-ups, trials and purchases (Google Ads).

Each of them processes data under its own terms and only for the service it provides to us. We don't use your prompts or sounds to train our own models.

How long we keep it

We keep your account, prompts and sounds while your account exists. When you ask us to delete your account, we delete them. We keep billing records for as long as tax and accounting law requires.

Your choices and rights

You can see and edit most of your data in the app. To get a copy of your data, correct it, or delete your account, email support@blipsmith.ai. Depending on where you live (for example in the EU, UK or California), you may have further rights, such as objecting to processing or complaining to a data protection authority.

Blipsmith isn't meant for children under 16.

Changes

If we change this policy, we'll update this page and the date at the top, and tell you by email if the change is significant.