Privacy Policy

Account data — the minimum needed for an account to exist:

• Email address, and a password stored only as a bcrypt hash (we never store or see the password itself).
• If you sign in with Google: your Google account identifier and email. We do not receive your Google password.
• A username, assigned automatically when the account is created — a random word and number, not taken from your email. You can change it in your profile, once a week.
• Optional profile fields you fill in yourself: display name, avatar, bio, headline, location and social handles. These and your username are public by design.
• Email verification and password-reset tokens, which expire and exist only to complete those two flows.

Content you create:

• Prompts and generation settings, the model you chose, and the resulting image, video, audio or text.
• Chat conversations: your messages and the models' answers, the model used for each answer, and its token count and price.
• Reference images and other files you upload, and the elements, projects, canvases and studio boards you build from them.
• Community activity: published works, likes, follows, comments, contest entries and votes.

Billing data:

• Your credit balance and a transaction record for every top-up, bonus, refund and generation charge.
• Payment status and identifiers returned by the payment provider. Card numbers and crypto wallet credentials never reach Seedara — payments happen on the provider's side.

Technical data:

• Standard server logs (IP address, browser user-agent, requested URL, timestamp), used for security, rate limiting and debugging.
• Error reports, if error tracking is enabled. These can include the URL and a stack trace, and may incidentally contain an account identifier.
• API keys, if you create one — stored as a hash, and revocable by you at any time.

We do not use advertising trackers. With your consent, two web analytics services count visits and how pages and features are used, linked to a random browser identifier and, if you are signed in, to your account number, your plan, the way you sign in and the day you signed up — never to your e-mail. One of them also records how a page is used — clicks, scrolling and movement. A recording shows the site itself — its words, buttons, pictures and videos — and hides what is yours: everything you type, the files you upload, your own generations and your account and payment details. Without consent the first receives only signals without cookies or identifiers, and the second receives nothing.

• To run the service you asked for: authenticate you, route a generation to a provider, return and store the result, and show you your own library.
• To bill correctly: calculate the credit cost of a generation, keep your balance accurate and give you a transaction history you can check.
• To keep the service safe: rate limiting, abuse prevention, moderation of content submitted for public sharing, and investigating incidents.
• To send transactional email — verification, password reset and account notices. We do not send marketing email without your consent.
• To fix problems: logs and error reports are what make a bug findable.

We share personal information only with the categories of recipients described below, and only to the extent needed for the purposes in section 3. We do not sell your personal information, and we do not share it with advertisers or advertising networks.

• AI model providers. Seedara does not run its own models. When you start a generation, your prompt, any reference files attached to it, and the generation parameters are sent to the third-party model provider or model aggregator that serves the model you selected. Aggregators may pass the request on to the developer of the underlying model. These providers do not receive your email address, your name or your payment data, and they process the content under their own terms and privacy policies, including their own rules on data retention and model training. In the chat, each new message is sent together with the earlier messages of that conversation that fit its memory window (with “Remember everything” on, up to the model's own limit), because that is how the model remembers the conversation. Please do not include personal information about yourself or others in prompts, chat messages or reference files unless you are entitled to share it.
• Voice from your recordings. If you turn a «Voice» element into a voice for songs or for voice-over, the recording — and, for songs, the phrase you read aloud to confirm it — is sent to the provider of the model that makes the voice (Suno for songs, MiniMax for voice-over), which keeps the voice under its own terms. Forgetting the voice, or deleting the element or the account, removes it from Seedara; the providers give us no way to delete it on their side. Only make a voice from a recording of yourself, or with the consent of the person whose voice it is.
• AI assistance and moderation providers. We use third-party AI services to power the prompt-enhancement helper and the help-centre assistant, and to run automated moderation checks on content submitted for public sharing. A question to the help-centre assistant is sent to the model provider together with the earlier questions and answers of that conversation, without your email address or name.
• Payment processors. Payments are handled directly by our payment processors. They return only the payment status and transaction identifiers to us; card details and wallet credentials never reach Seedara. Payment processors may collect additional information under their own terms, for example to meet anti-fraud or anti-money-laundering requirements.
• Authentication providers. If you choose to sign in with a third-party account, that provider takes part in the sign-in process and shares with us the limited account information described in section 2.
• Service and infrastructure providers. Companies that help us operate the service: hosting and data storage, content delivery and network security (including bot protection at registration and sign-in), transactional email delivery, and error monitoring. They process data only on our behalf and only as needed to provide their services.
• Web analytics services. Only with your consent: visits and the use of pages and features, a browser identifier and your account number (not your e-mail) with your plan, the way you sign in and the day you signed up, the answer you pick in a short question on the site, confirmed payments as an amount and the plan or pack bought, and recordings of how pages are used that show the site itself and hide everything you type, the files you upload, your own generations and your account and payment details. Without consent, one of them receives only signals without cookies or identifiers and the other nothing.
• Other users and the public. Content and profile information you choose to publish becomes visible to others, as described in section 5.
• Professional advisors. Lawyers, accountants and auditors, where needed for the services they provide to us.
• Business transferees. If Seedara is involved in a merger, acquisition, sale of assets or a similar transaction, personal information may be transferred to the acquirer or successor, who will remain bound by this policy for the data transferred.
• Authorities and legal requests. Law enforcement, government authorities or other parties, where we are required to do so by law or by a valid legal request, or where it is necessary to protect the rights, safety or property of our users, Seedara or others.

A list of the specific service providers we currently use is available on request at [email protected].

Your generations are private by default. A work becomes visible to others when you publish it yourself — or automatically, if you turn on “Publish new generations automatically” in your settings. That setting is off until you switch it on; with it on, a new work is published when it is ready and has passed the automated moderation check. Turning it off stops new works being published; works already published stay public until you unpublish them.

Files you upload as references — photos, audio, video — are visible only to you and, through short-lived links, to the model provider that uses them. Two uploads are public by nature: your avatar, and the cover of a project you have published.

• When you publish, the output and your public profile fields become visible to anyone, and so do the work's prompt and settings: other people can read them and repeat them in a remix. The files you uploaded for the work are not passed on to a remix.
• Entering a contest makes your entry, and the profile attached to it, visible to other participants and to whoever judges the contest.
• Unpublishing removes a work from public surfaces. Copies that other people already downloaded or reposted are outside our control.

• Account data and the content in your library are kept while your account exists.
• Transaction records are kept longer where accounting or tax rules require it, even after an account is closed.
• Server logs and error reports are short-lived and rotate out on their own.
• Questions to the help-centre assistant are kept for 90 days together with the answer, the page language and your rating, so we can see what the help centre is missing. They are stored without your IP address and without a link to your account — only a salted hash, used to spot abuse — and are then deleted.
• Answers to the short question at the bottom of the screen — a choice from a list, without your own text — are kept together with the question, the section of the site, the model, the plan and the language, so we can see what gets in the way. They are stored without your IP address and without a link to your account, so they cannot tell who answered.
• Verification and password-reset tokens expire on their own: the email confirmation link after 24 hours, the password-reset link after one hour.
• When you delete your account, it disappears from the site: we sign out every device, revoke your API keys and agent connections, free your username, erase your password, two-factor setup and all your chat conversations, and take your published works and projects off public pages. Your email address and the profile details you had at that moment (username, name, profile fields, Google link) are kept in a record of the closed account that only the Seedara team can see — for security, abuse prevention and accounting; they are not shown anywhere on the site. Your generations, uploads and elements, with their files, are erased from storage 30 days after the account is deleted; you can delete them yourself sooner, before closing the account. The record of charges stays as well, without the files — we are required to keep it.

Passwords are stored only as bcrypt hashes and API keys only as hashes. Traffic is served over HTTPS. Sessions use signed tokens, and changing your password invalidates every token issued before that change, so a leaked session stops working as soon as you reset.

No system is perfectly secure. If you believe your account has been accessed by someone else, change your password immediately and write to us.

Depending on where you live, you may have the right to access your data, correct it, export it, delete it, restrict or object to certain processing, and withdraw consent. You can exercise the everyday parts of this directly in the product:

• Profile fields can be edited or emptied in account settings.
• Individual generations and uploads can be deleted from your library, and published works can be unpublished.
• A chat conversation, or all of them at once, can be deleted on the chat page; its messages are erased straight away.
• API keys can be revoked at any time.
• The account itself can be deleted with the “Delete account” button in settings, confirmed with your password (and your two-factor code, if it is on). What is erased is listed in section 6.

Data export is handled manually for now: write to [email protected] from the address on the account and we will confirm and carry it out. We will tell you honestly if some records (billing history, for example) have to be kept for legal reasons.

We use what the site needs to work; two notes that keep web analytics from counting a sign-up or an order twice, set whatever you choose in the cookie notice; and, only with your consent, web analytics cookies. There are no advertising or cross-site tracking cookies:

• A language cookie, so the site renders in your language on the very first response instead of flashing the wrong one.
• A session token in your browser's local storage, so you stay signed in.
• A media cookie (HttpOnly, lasts as long as the session) — a copy of the session token that lets your own images and videos load, because a picture on a page cannot send the token any other way.
• Two short cookies during Google sign-in (10 minutes each).
• A referral cookie for up to 30 days if you arrive through a contest participant's link, so that person can be credited when you sign up.
• A cookie that remembers your choice in the cookie notice for 180 days.
• A note in your browser's local storage that a short question on the site was already asked, so it is not asked again.
• Whatever you choose in the cookie notice: in the first 15 minutes after you create an account, a cookie notes that the sign-up has been recorded, so that it is not counted twice.
• Whatever you choose in the cookie notice: while the browser tab is open, its session storage keeps a note of the last order you started (the plan or pack and the amount, nothing about the payment), so that the same order started again within the next 30 minutes is not counted twice.
• Only with your consent: web analytics cookies (up to 2 years) and similar browser storage that tell one visit from another and show which pages and features are used. If you withdraw consent, the site deletes them and leaves in the browser only a mark that keeps analytics switched off. You can change or withdraw your choice at any time under “Cookie settings” in the site footer.
• Cookies set by our network and security provider, including its bot-protection check (see section 4).
• Local browser storage for small interface preferences that never leave your device.

Seedara is a service for adults. You must be at least 18 years old to create an account — the registration form asks you to confirm it — or older if the law where you live sets a higher age for this kind of service. If we learn that an account belongs to someone below that age, we will delete it.

The providers listed in section 4 operate in different countries, so running a generation or sending an email can mean your data crosses a border. We choose providers that commit to appropriate safeguards for such transfers.

When this policy changes we update the date at the top of the page. If a change materially affects how your data is used, we will tell you in the product or by email before it takes effect.

Questions about this policy, or a request about your data: [email protected].