Skip to main content

Privacy Policy

Last updated

This policy explains what personal data DesignPrompts collects, why we collect it, which providers process it for us and what you can do about it. Mellow Studios LLC, based in California, United States, runs DesignPrompts and is responsible for this data.

  1. 1.What we collect

    • Account details: your email address and your name. If you sign up with a password, we store a hash of it, never the password itself. If you sign in with Google, we ask Google only for the openid, email and profile scopes, which share your Google account ID, name, email address and profile picture.
    • Sign-in sessions: when each session started, when you last signed in, and the browser and device each session came from. Our sign-in service also uses your IP address to slow down repeated sign-in attempts.
    • Purchases: what your account owns, Pro or a System, with the Polar order and grant it came from and the date it was granted or revoked. Your first checkout creates a customer record at Polar with your email address and our ID for your account. Polar holds your payment details. We never see your card details.
    • Licence key checks: when you install a component, our registry sends your Licence key to Polar to check it. We do not store the key. We record which component was served, against a one-way hash of the key's ID.
    • Support: what you write to us at the support address.
    • Analytics, error reports and logs from the live site, described under Analytics below.

  2. 2.How we use it

    We use this data to:

    • run your account and sign you in, including the email that verifies your address and the email that resets your password;
    • sell and deliver what you buy: the checkout, the Licence key check and System package downloads;
    • protect the service, for example by limiting repeated sign-in and checkout attempts;
    • answer your support requests;
    • learn how people use the site, and find and fix errors.

    We do not sell your personal data, and we do not use it for advertising.

  3. 3.Who processes it

    • Convex runs our backend and database in the United States (US East). Your account, sessions and purchase records are stored there.
    • Cloudflare hosts the site on Cloudflare Workers and stores System packages in Cloudflare R2. Like any host, it handles your IP address and the pages you request.
    • Polar processes payments as the merchant of record, issues Licence keys, receipts and invoices, and runs the billing portal. It tells us about orders and grants through webhook events. Polar's own privacy policy covers the data it holds.
    • Google signs you in, if you choose to sign in with Google.
    • Resend sends our account email (address verification and password reset) from no-reply@designprompts.dev.
    • PostHog receives analytics, error reports and logs from the live site. PostHog stores this data in the United States.

    Better Auth, the software that handles sign-in, runs inside our own backend. It is not a separate service.

    Our administrators can see an account's email address, name and purchases, and can sign in as a user to resolve a support request.

    We may also disclose data when the law requires it.

  4. 4.Analytics

    Only the live site sends analytics; our test sites send none. The live site sends these events to PostHog through our own /ingest address:

    • page views and page leaves, including anonymous visits;
    • error reports from your browser and from our servers;
    • account events, such as a sign-up or a completed checkout, which carry our internal account ID or the provider's ID, never your email address;
    • actions an administrator takes on an account, recorded with internal IDs, the names of the fields changed and, for a role change, the new role;
    • when you choose a style in the Explorer: the style's ID, its name and whether it is a light or dark style;
    • when you copy a free prompt: the style, the prompt variant, where you copied it and the prompt's revision, never the prompt text or your brief;
    • when the registry serves a component: the component's name and a SHA-256 hash of the Licence key's ID, never the key itself, with no profile attached.

    To count visitors without storing anything in your browser, PostHog derives an identifier for the day from your IP address and the browser and operating system details your browser sends with every request. That identifier is not stored on your device, cannot be turned back into your address and changes every day, so if you come back on another day, you count as a new visitor. Anonymous visits do not create a profile.

    When you are signed in, the browser identifies you to PostHog by our internal account ID only, never by your email address or name. Nothing in your browser keeps that ID, so the browser sends it again each time the site loads while you are signed in.

    We do not use session replay.

    Our /ingest address passes your IP address to PostHog, which may use it to estimate your rough location before discarding it; we have set PostHog not to store the address. It never forwards your cookies.

    On the live site our servers also send warning and error logs to PostHog, with email addresses removed, and operational events such as a Polar webhook arriving, an account email being sent or your account being linked to its Polar customer record. Those events record what happened with at most our internal account ID and a provider's ID, never an email address or a password. A log of a failed call to a provider can include that provider's error message. When your browser blocks something on our pages under our security policy, it can send us a report with the page address and what it blocked, and we log that report.

  5. 5.Cookies and browser storage

    • Sign-in cookies. When you sign in, we set a session cookie and a few related cookies that keep you signed in and protect the Google sign-in. Scripts on the page cannot read them. A session lasts seven days and is extended while you keep using the site.
    • Analytics on the live site. PostHog's script sets no cookie and stores nothing in your browser's local storage or session storage.
    • The Builder keeps your working page and your saved pages in your browser's local storage.
    • A password reset keeps its reset token in that tab's session storage while you choose a new password.

    We do not use advertising cookies. If you block cookies, you can still browse, but you cannot sign in. We do not respond to browser Do Not Track signals.

  6. 6.The Builder

    The Builder needs no account. The page you are working on and the pages you save stay in your browser's local storage. We do not store them on our servers, and clearing your browser's data for the site deletes them.

    A share link carries the page's contents inside the link itself, so anyone with the link can open the page. Opening a share link sends its address, page contents included, to our site, and our page-view analytics can record that address.

  7. 7.How long we keep data

    • Account details and purchase records: until you delete your account.
    • Ended sign-in sessions: a session expires seven days after it was last extended, and we extend it at most once a day while you use the site. We delete its record when your browser next presents the expired session, when you sign out, or when you delete your account.
    • Sign-in attempt counters: the counters that hold your IP address last one minute, and we remove them within five minutes after that.
    • Analytics and error reports in PostHog: PostHog keeps analytics events, error reports among them, for up to seven years, its retention on our paid plan. We can delete a person's events on request.
    • Server logs in PostHog: for the period PostHog's logs product keeps them.
    • Support email: two years after the last message in the thread.
    • Backups of our database: none of our own today. Convex runs the database and its own infrastructure protects it; if we add backups, we will say here how long they are kept.
    • Polar keeps your orders, receipts and Licence key under its own policy.

  8. 8.Your choices and rights

    • On the Account page you can change your name and your password and see your sign-in sessions.
    • To delete your account, write to us from the email address you sign in with. Deleting it removes your account, its sessions, the sign-in methods linked to it and its purchase records from our database. It does not delete your orders, receipts or Licence key at Polar, or analytics PostHog already holds, and it does not refund anything. Polar keeps the order and customer records it must hold for tax and accounting.
    • To get a copy of the personal data we hold about you, or to correct it, write to us at the support address.
    • To remove your Builder pages, clear your browser's data for the site.

    If you live in the European Union, the United Kingdom or a US state whose privacy law applies to you, you have the rights those laws give you, such as the right to access, correct and delete your data, to receive a copy of it and to object to some processing. To use them, email us at support@designprompts.dev. We answer within 30 days.

  9. 9.Security

    We store password hashes, not passwords, and we encrypt the Google sign-in tokens we keep. Page scripts cannot read the sign-in cookies. No system is completely secure, so if you think your account or your Licence key has been exposed, write to us.

  10. 10.Children

    DesignPrompts is not meant for children under 18, and we do not knowingly collect their data.

  11. 11.Where we operate

    We operate from California, United States, and our database runs in the United States. If you use DesignPrompts from another country, your data is transferred to the United States and processed there. Our other providers process data in the United States; Polar may also process it in Canada. Cloudflare's network handles requests in many countries.

  12. 12.Changes to this policy

    We will post changes on this page and update the date at the top. For a material change, we also email account holders at least 14 days before it takes effect.

Questions about this policy or your data: support@designprompts.dev