Privacy Policy

Introduction

We respect your privacy and are committed to protecting your personal data. This Privacy Policy explains how we collect, use, and safeguard your information when you use our service.

Information We Collect

We collect the following types of information to provide and improve our service:

1. Account Information — Your name, email address, and other details you provide when creating an account. We also record the IP address the account was created from, the country our network reports for that request, and the interface language you signed up in.
2. Prompts and Creative Input — What you type into the creation tools: prompts, lyrics, song titles, and the style, genre, vocal and language settings you choose, including the briefs you submit for batch and multi-scene generation. We store these alongside the creation they produced, so you can reuse and edit them.
3. Reference Images You Upload — Images you attach to an image, video, batch or multi-scene request, and screenshots you attach to a support ticket. These are stored on storage we control and served from our own media domain. (Generated files usually live there too, but not always — see the next item.) Alongside the file itself we keep a record of it: which account uploaded it, which kind of upload it was (a creation reference, a support-ticket attachment, a profile picture, an image placed in an article), its type and size, and a checksum of its contents. The record notes the kind, not the individual request or ticket it belonged to.
4. Generated Media — The music, images and videos the service produces for you, together with the model used and the status of each job. We normally copy finished files onto storage we control (Cloudflare R2) and serve them from our own media domain. Where that copy does not happen — no storage is configured, or the copy fails — the file stays where the model provider put it, on that provider’s own temporary host, and the link we keep for you points there instead.
5. Usage Data — Information about how you interact with the service, including features accessed, frequency of use, and interaction patterns.
6. Device Information — Device type, operating system, and browser type, used to optimize compatibility and performance.
7. Cookies — Small data files stored on your device to remember preferences and improve your experience. These include your cookie consent choice and, when you arrive from a campaign or an advertisement, the campaign source and the advertising platform's click identifier (kept for 30 and 90 days respectively). If you then create an account or check out, we store those values with your account.
8. Payment Information — Billing details handled by trusted third-party payment processors. We do not store full card numbers on our servers.

How We Use Your Information

We use the data we collect to:

• Provide, maintain, and improve the service.
• Process transactions and send related confirmations.
• Send technical notices, security alerts, and support messages.
• Respond to your questions, feedback, and support requests.
• Detect, prevent, and address fraud and abuse.

Data Sharing

We do not sell your personal information. We may share data only in these limited cases:

• With service providers who help us operate the service, under confidentiality agreements.
• With the AI model providers that run your request. Your prompt, your lyrics and song settings, and the web address of any reference image you uploaded are sent to Kie.ai, which routes each request to the provider of the model you selected: Suno (music), Google (Veo, Gemini and Nano Banana), OpenAI (GPT Image), ByteDance (Seedance and Seedream), Kling, MiniMax, Grok Imagine, and HappyHorse. The model provider fetches your reference image directly from the address we give it, and returns the finished file on its own temporary host, from which we copy it onto our storage. The same route carries the text you type when you ask us to enhance a prompt or write lyrics, and when you use a free tool that does not require an account.
• With OpenAI's moderation service, to screen content. Before a generation starts, and again before a creation can be published, we send the prompt text there. When the creation being published is an image, we send the image's address instead, so the picture itself can be checked.
• With Shotstack, to assemble a multi-scene video: the web addresses of your generated clips and audio track, which it fetches in order to return the finished cut.
• With everyone, if you choose to publish. Publishing a creation to Explore makes it readable by visitors who are not signed in and have no account: the media itself, its title, the full prompt you wrote, and for a song the full lyrics. Publishing is per creation, is off unless you turn it on, and can be switched off again. Separately, the files we serve from our media domain are retrieved by web address and are not behind a sign-in, so anyone who has a link can open that file. Images you upload are stored under a randomly generated address that does not depend on the contents of the file, so each upload is kept as its own stored file; older stored images are kept under an address derived from their contents, so where two accounts uploaded a byte-for-byte identical image it is one stored file at one shared address.
• With PostHog, our product analytics provider, once you accept cookies: the pages you view and leave; and, after you sign in, your account id, email address and name. We may also use session replay or similar diagnostics on this channel, depending on the settings in force on our analytics project, your consent, and the region your request comes from.
• With Sentry, our error-monitoring provider, when something in the page fails: the address of the page and technical details of the failure. Unlike the analytics, advertising and live-chat scripts, which load only after you accept cookies, this one runs either way.
• With an advertising or measurement platform, if one is connected and you arrive through an advertisement, so that it can measure the campaign. The service can report account creation, checkout, purchase and refund events over three channels: Meta's Conversions API, Google Ads conversion upload (the Data Manager API), and Google Analytics 4's Measurement Protocol. Each channel stays switched off until its own credentials are configured, so which of them, if any, is active depends on our configuration at the time; where none is configured, nothing is sent. Where a report is sent, the personal data in it is the platform's own click identifier, the analytics or advertising cookie identifier your browser carries, the IP address and browser user agent we recorded with the click, an identifier for your account, the amount and currency of the order, and an irreversible (SHA-256) hash of your email address. We never send your prompts, your uploads, or your creations to an advertising platform.
• To comply with legal obligations or respond to lawful requests from public authorities.
• To protect our rights, property, or safety, or that of our users.

Data Security

We implement industry-standard security measures including encryption in transit, access controls, and regular reviews. No method of transmission over the Internet is 100% secure, but we work continuously to protect your information.

Your Rights

You have the right to access, update, export, or delete your personal information. You can change your profile details yourself in your account settings. Access, export, and deletion are handled by us on request rather than through a self-service control: open a support ticket at /settings/tickets, or email contact@synthpulseai.com if you cannot sign in. We will confirm what we hold, provide a copy, or delete it. If you wrote articles or categories in our content management system — something only staff accounts can do — closing your account does not change whether they are published: whatever was published stays published, and whatever was not stays unpublished. We remove your name and photo from the byline, but our records keep a link between the article and your now-anonymised account, so we can still tell which pieces share an author and answer questions about them later. Deleting data from our own systems does not by itself remove copies already sent to the third parties described above; where a provider offers a way to do so, we will pass your deletion request on to them.

Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of any material changes by updating the date at the top of this page and, where appropriate, sending a notice through the service.

Contact Us

If you have questions about this Privacy Policy, email us at contact@synthpulseai.com. If you have an account, you can also reach us through the support ticket system referenced above (/settings/tickets).