Privacy policy

Prompt Generator (trypromptgenerator.com) is run by GrubGuru Ltd., a company registered in British Columbia, Canada ("we", "us"). This policy describes the personal data we handle when you use the site, what we do with it, which companies help us, and the choices you have. Send any question about it through the contact page.

In short

• We collect what we need to run the prompt tools, the studio, your account and your payments.
• Text you type into a prompt tool and images you give to image to prompt are passed to an AI model to write your prompt. We keep them only if you save the prompt.
• We do not sell personal data, we do not show ads, and we do not use your prompts, uploads or results to train AI models.
• We keep our own record of how the site is used (pages viewed, tools run, sign-ups and payments) to run and improve it. It holds no IP address and no browser fingerprint, and it is never sold or shared. Until you press Accept in the cookie notice, it only counts what happens: no device id, no visit id and no record of where you came from.
• Google Analytics and Microsoft Clarity load only after you press Accept in the cookie notice.

What we collect

When you use the prompt tools. The idea or text you enter, the options you pick and, for image to prompt, the image you upload. These go to the AI model that writes your prompt (see the next section) and are not stored on our servers. If you are signed in and press Save, we store the prompt, your idea, the tool and the target on your account. To count free runs, the site gives your browser a random device id in a cookie, and our server keeps a count per device, per account and per network in memory. The network count uses a keyed hash of your IP address, never the address itself, and none of these counts are written to disk.

Account details. Your email address and, if you choose one, a password, which we store only as a scrypt hash. If you sign in with Google, Google gives us your name, email address and profile picture, and we store the link to your Google account and the tokens needed to keep that sign-in working.

When you use the studio. The prompts and settings you submit, the files you upload (photos, plus video or audio for the tools that use them), and the images, videos and audio that come back. Photos often show faces, sometimes of people other than you; the Terms explain whose photos you may upload.

Sharing, likes and templates. Whether a prompt or result is public, view and like counts, and likes on gallery items and library prompts, which are stored with the random device id and, if you are signed in, your account id. A library prompt's view counts once per network a day, checked with a keyed hash of your IP address held in memory. When you suggest a template, we store the title and note you write and our decision on it.

Free credits. Your daily check-ins and streak, your referral code, who invited you, and when a referral paid out. The free credits page shows the person who invited you a masked version of your email address (only its first letters and the domain ending) and whether you have made a purchase.

Credits and payments. Your plan, subscription status and billing dates, your credit balance and a ledger of every credit added, spent, refunded or expired. Stripe runs checkout and keeps your card details; we never receive your full card number. We store the Stripe customer and subscription ids that connect your account to Stripe. For each payment, refund or plan change we also keep a record of the amount, tax, Stripe fees, plan, any coupon and the Stripe ids, together with how you came to pay as far as we know it: the first and the latest place you came from (only if you had pressed Accept in the cookie notice, as described under product usage records) and the first tool you used on the site.

Your own API key. If you add an OpenRouter or fal key to your account, we keep it encrypted (AES-256-GCM) and never send it back to your browser.

Password resets. For a reset link, we keep only a hash of the one-time token and the time it expires.

Safety records. When a studio prompt is blocked by our checks, when a provider's safety filter rejects a run, or when something fails our publishing check, we record the prompt, the reason, the model or tool and the time. We use these records to pause accounts that keep sending blocked requests and to investigate abuse.

Reports. When you report a public item, we store the reason and any note you add, with your account id if you are signed in, or a keyed hash of your IP address if you are not, so that each person can report an item only once.

Support messages. When you write to us from the support panel or the contact page, we store your name, email address, subject, your messages and our replies, and link them to your account if you are signed in. Signed out, we use your IP address in memory to rate limit the form and check that the email domain can receive mail. New messages and our replies go through our support mailbox at Namecheap Private Email.

Browser notifications. If you turn on notifications in the support panel or on your account page, your browser gives us a push subscription: an address at your browser maker's push service (Google, Mozilla, Apple or Microsoft) and the keys to encrypt messages to it. We store it with your account and your browser's user agent and use it only for support replies and updates we mark as important; each notification passes through that push service encrypted. Turn notifications off on your account page or in your browser's site settings. We delete the subscription when you turn them off on your account page, or when the push service reports it is no longer valid (for example after you block notifications in the browser).

Request data. Our servers and Cloudflare handle standard request data (IP address, browser user agent, the address of the page) to deliver the site and stop abuse. The app also uses your IP address in memory to rate limit sign-in and sign-up attempts. Sign-in and sign-up forms may run a Cloudflare Turnstile check to tell people from bots. Apart from the hashed forms described above, your IP address is not written to our database.

Product usage records. The site keeps its own record of what happens on it, because we need it to run the free allowance, price credits, find broken tools and see which pages help people. Each record is one event, such as a page view, the start of a visit, a prompt tool run and whether it finished, a copy of a prompt, a like or save in the library, a studio run and its result, a credit added or spent, a checkout started, a payment, renewal or refund, a share, a template suggestion or a support message. For every visitor we store the event, its time, the page address, a country taken from Cloudflare's country header, the type of device (phone, tablet or computer) and the browser family (for example Chrome or Safari). Until you press Accept in the cookie notice, that is all: no device id, no visit id, no record of where you came from and no link to your account, so these events only add to totals. The exception is events that mirror something we keep anyway to give you the service you asked for (your sign-up, studio runs and their results, prompts saved to your account, likes and saves, items you publish, template suggestions, support messages, credit movements and payments): they carry your account id when you are signed in. If you press Accept, each event also gets the random device id from the pb_device cookie in hashed form, a random visit id, your account id if you are signed in, and where the visit came from: the campaign tags in the link you followed (utm_source and the like) and the name of the site that sent you. When you create an account after pressing Accept, we copy the first and the latest place you came from onto it, and when you pay we keep that with the payment. If you later choose Essential only, we stop adding these ids and delete the visit id and the record of where you came from from your browser; events already recorded stay until they expire. We never store your IP address or your full browser user agent in these records, and never the text of your prompts, uploads or results. These records stay with us; nothing in them goes to Google, Microsoft or anyone else unless you press Accept, as described next.

Usage statistics. Cloudflare Web Analytics, when it is switched on, counts page views and load times without cookies, without storing anything on your device and without an identifier that follows you to other sites, so it runs for every visitor. If you press Accept in the cookie notice, Google Analytics also records the pages you visit, your browser and device type, a rough location based on your IP address, and product events: sign-ups and sign-ins (with the method), studio runs started and finished (with the tool, model, credit cost and outcome, never the prompt or the photo), shares and downloads, and visits to pricing and checkout and completed payments (with the plan and amount, never card details). While you are signed in, Google Analytics also gets your account id, a random string that is not your email, so your visits from different devices count as one person; with the same id, our server reports renewals, refunds and failed payments, but only while your Accept stands. Accepting also loads Microsoft Clarity, which records how pages are used (clicks, scrolling, mouse movement and page layout) to build heatmaps and session replays. Text typed into forms is masked before it leaves your browser, and Clarity does not get your account id. If you choose Essential only, neither tool loads and our server sends nothing to Google Analytics.

We do not run face recognition or build biometric profiles. Photos are used only to produce the prompt or result you asked for.

How we use it

• To provide the service: write prompts, run studio jobs, keep your account, saved prompts and results, and show them to you.
• To handle payments: take payments through Stripe, add credits, and return credits automatically when a run fails.
• To keep the service safe: daily limits, rate limits, fraud and abuse prevention, and checks of prompts, uploads, results and public items against the content policy, automatically or by a person.
• To run the free credit programs: check-ins, referrals and template rewards.
• To help you: answer your support messages and look into problems with a run or a payment.
• To price fairly: we record what each studio run cost us at the gateway, so credit prices reflect real costs.
• To improve the site: our own product usage records, Cloudflare page view counts, and Google Analytics and Microsoft Clarity data if you accepted them, show which pages and tools are used and where people get stuck.
• To email you about your account (service emails): a link to confirm your email address and one reminder if it is still unconfirmed a day later, a welcome message, password reset links, a notice when your password or sign-in email changes, a receipt for each payment, failed payment and low balance notices, a reminder 14 days before a yearly plan renews and 5 days before a first-month discount ends, subscription changes, refund confirmations, template decisions and content policy notices. These arrive whatever your email setting.
• Product emails: a few emails about using the site and our plans: a first-prompt email a day after you confirm if you have not run anything yet, a note when your free credits run out, and a note when you keep reaching the daily limit of free prompts. They are on unless you tick "Don't send me product emails" at sign-up, never more than 1 a day or 2 a week, and none in the 14 days after a purchase. Each one has a one-click unsubscribe link, and your account page lets you turn them off or back on. When you sign up we record whether product emails are on and where you chose it, so we can show your choice later. To pick who gets which email, we keep a record on your account of when you first and last ran a prompt tool, when you last visited while signed in, and the days you used up your free daily prompts; this is part of running your account and does not depend on the cookie notice.
• Delivery records: for each email we send we keep its type, the address, the time and whether it was delivered, bounced or marked as spam. If an address bounces for good we stop sending to it, and if you mark one of our emails as spam we stop product emails to you.

If you are in the European Economic Area or the United Kingdom, we rely on these legal bases: performance of our contract with you (your account, prompts, runs and payments), our legitimate interests (security, abuse prevention, support and improving the service), compliance with legal obligations (such as tax records), and your consent where we ask for it (analytics cookies).

AI gateways and model providers

Prompt tools. The text you enter, and the image for image to prompt, go to OpenRouter, which passes them to the language model that writes your prompt. We do not send anything to the product the prompt is for (ChatGPT, Midjourney, Veo and so on); you paste the prompt there yourself, under that product's own privacy policy.

Studio. When you start a run, your prompt, settings and input files go to the gateway that serves the model you chose: OpenRouter for most image and video models, and fal for lip sync, speech, music, upscaling, background removal and some image models. The gateway either runs the model or forwards the request to the company that built it or hosts it. Studio models currently come from Alibaba, Black Forest Labs, ByteDance, Clarity AI, fal, Google, hexgrad, Kuaishou, Microsoft, MiniMax, OpenAI, Recraft, Runway, Sourceful, Stability AI, Sync Labs, xAI and ZhengPeng7.

Safety checks. Images uploaded to image to prompt, studio prompts and input photos, images made from your photos, and anything you make public can also be sent to OpenAI's moderation service. It only classifies content against safety categories, such as sexual content involving minors, and does not generate anything.

We send content to these providers only to produce your prompt or result or to check it, never for training. How long they keep request data is set by their own policies, linked in the table below; some keep it for a limited time to monitor abuse.

If you added your own OpenRouter or fal key, studio runs on that gateway go through your own account with that provider, under its terms.

Who can see your data

• You. Your saved prompts, uploads and results are private to your account.
• Everyone, only for what you make public. A prompt or result you share appears on the gallery with its prompt and the target or model; an accepted template appears in the prompt library. Your name and email are never shown. You can unshare a gallery item at any time. Anyone can report a public item, and we can hide or remove it.
• The person who invited you. They see a masked form of your email and whether you have made a purchase, as described above.
• Our administrators. A small number of administrators can see accounts, saved prompts, jobs and files in order to run the service, solve problems, review template suggestions and enforce the content policy.
• Service providers. The companies in the table below process data on our behalf, each only for the purpose listed.
• Authorities. We disclose data when the law requires it, or when it is needed to protect someone's safety or our rights.
• A buyer. If Prompt Generator is sold or merged into another business, your data goes with it and this policy keeps applying.

Cookies

Prompt Generator uses strictly necessary cookies to sign you in, keep sign-in secure and count free prompt tool runs; these are set for every visitor. The cookie notice asks whether you accept analytics cookies: our own pb_session and pb_touch, and, if they are switched on, Google Analytics (_ga and _ga_*) and Microsoft Clarity (_clck and _clsk). They are set only after you press Accept. Until then, or if you choose Essential only, none of them are set, Google Analytics and Microsoft Clarity do not load, and our own usage records only count events. We use no advertising cookies.

The site sets a few cookies of its own. pb_device holds the random device id used to count free prompt tool runs and to remember likes and saves on library prompts; it is strictly necessary for those and lasts up to 400 days. Only after you press Accept is it also used, in hashed form, to tell the events of one browser apart in our product usage records. pb_session holds a random id for the current visit and is deleted when you close the browser. pb_touch remembers where your first and latest visits came from (campaign tags and the referring site) so we can copy it to your account if you sign up; it lasts 400 days. pb_session and pb_touch are analytics cookies, set only after you press Accept. pb_ref holds a referral code when you arrive through an invite link, so the person who invited you can be credited when you sign up; it lasts 30 days. None of these hold your name or email.

On the live site, the sign-in cookies carry a __Secure- or __Host- prefix, so the browser sends them only over HTTPS.

Cloudflare, which sits in front of the site, may set strictly necessary security cookies (such as __cf_bm) when it checks traffic for bots. Stripe's checkout and billing portal run on Stripe's own domain and set Stripe's cookies there, as described in Stripe's privacy policy.

The site also uses your browser's storage. Local storage keeps your cookie choice, where your first and latest visits came from (the same as the pb_touch cookie, only after you press Accept), your favorites, prompts you save without an account, which gallery items you liked, and which product updates and support notices you have already seen; it stays on your device and is not sent to us unless you sign in and save something to your account. Session storage keeps the current visit id (only after you press Accept), a draft prompt and a picked photo while you sign in, and is cleared when you close the tab.

If you block the sign-in cookies, you cannot sign in, but the rest of the site still works. You can change your cookie choice at any time with the button below. Choosing Essential only turns off Google Analytics and Microsoft Clarity, stops the visit and device ids in our own usage records, and deletes pb_session, pb_touch and the Google Analytics and Clarity cookies from this site.

Cookie settings

How long we keep data

• Prompt tool input: not stored, unless you save the prompt to your account.
• Account, saved prompts, studio uploads and results, and safety records: kept while your account is open. You can delete saved prompts yourself. Studio runs cannot yet be deleted one by one from your account; send us a message and we will delete specific items or your whole account.
• Support conversations: kept so we can follow up on earlier questions. When you delete your account, conversations you had while signed in stay without the link to the account; ask us and we delete them too.
• Credit ledger and billing status: kept while your account is open. Stripe keeps invoices and payment records as tax and accounting law requires, and we keep the payment records the law requires us to keep. If you delete your account, our payment records stay for accounting without the link to your account.
• Accepted templates: an accepted template stays in the prompt library as the Terms describe, without your name or email.
• Password reset tokens: stored as a hash and valid for a short time only.
• Product usage records: each event is deleted automatically 13 months after it happened. We keep daily totals built from them (for example, how many prompts were run on a day), which hold no device, visit or account id. Deleting your account also deletes the usage records linked to it.
• Google Analytics data: deleted automatically after at most 14 months.
• Microsoft Clarity data: session replays are deleted after 30 days and heatmap data after at most 13 months.
• Free run counts and rate limit counters: held in memory only, never written to disk.
• Backups: deleted data can stay in database backups for up to 30 days, until those backups are replaced.

Your choices and rights

Things you can do yourself:

• Delete saved prompts on your account.
• Unshare any prompt or result from the gallery.
• Remove a saved API key on your account page.
• Accept or refuse analytics cookies, and change your mind later, with Cookie settings in the Cookies section.
• Cancel or change your subscription and download invoices in the billing portal, from your account's billing page.
• Turn product emails off or on from your account page.
• Turn browser notifications off or on from your account page.

For anything else, send us a message through the contact page while signed in: a copy of your data, a correction, deletion of particular runs, or deletion of your account. We check that the request comes from the account holder and reply within 30 days. Deleting your account removes your profile, saved prompts, studio history, uploads and results, and cancels any subscription. Credits left in the account are lost, as the Terms say.

Depending on where you live, you may also have the right to restrict or object to processing, to receive your data in a portable format, and to withdraw consent. You can complain to your local data protection authority, or in Canada to the Office of the Privacy Commissioner of Canada.

International transfers

We are based in Canada. The app and its database run on Hetzner servers in Helsinki, Finland. Several of the providers listed above are based in the United States, so your data may be processed there. Where the law requires it, we rely on the transfer safeguards those providers offer, such as the European Commission's Standard Contractual Clauses.

Security

All traffic uses HTTPS. Passwords are hashed with scrypt, saved API keys are encrypted, and our provider keys stay on our servers and are never sent to your browser. Stored files reach their owner only through access checks or short-lived signed links, except results you have made public. No system is completely secure; if a breach affects your data, we will notify you as the law requires.

Children

Prompt Generator is only for people aged 18 or older. We do not knowingly collect data from anyone younger, and we delete any account we learn belongs to someone under 18. Photos of children may be uploaded only by a parent or legal guardian, within the limits in the Terms.

Changes to this policy

When we change this policy, we update the date at the top. Before a material change takes effect, we tell account holders by email or with a notice on the site.

Contact

Prompt Generator is operated by GrubGuru Ltd.. Contact us through the contact page about anything in this policy. The help center article Uploading photos explains how uploaded files are kept private.