Privacy

Last updated 17 October 2026.

What we do not collect

No passwords and no payment details. Our generation database stores a salted hash rather than your raw IP address. We delete your uploaded photo from that database when processing ends, as described below. Analytics providers receive browser and request information separately; see Analytics and cookies.

Your Google account

Generating requires signing in with Google. From that sign-in we keep your Google account id, your name and your email address. They are used to link your images to you, to apply the daily limit, to show you your own results, and — only if you tick “Email me when it’s ready” — to email you about that image. Resend processes your email address to deliver those notifications. We do not send you marketing. Sign-in uses cookies to maintain your session.

What we do store

One database row per generation: which generator you used, your account id, timestamps, the status, a link to the generated image, and a one-way SHA-256 hash of your IP address combined with a server-side secret. The hash is used for daily free limits and abuse prevention; a shortened hash also appears in moderation logs. It cannot be turned back into your IP.

The image we generate for you

The result is copied to our own CDN and kept there, so that the link does not stop working after a day (the model provider signs its own links to expire), and it is shown on a result page on this site whose address contains the same random id; that page carries a noindex tag. It is not listed or indexed anywhere, and the address contains a random job id, but it is reachable by anyone who has that address — treat it as unlisted, not private. We will delete a specific result on request; see Contact.

Your photo

Before an accepted upload is stored for generation or sent to a generation provider, we send the whole photo to OpenAI for a content-safety check using omni-moderation-latest, when moderation is enabled and configured. The image is sent inline as a base64 data URI, not as a public image link; the moderation request does not include your account name or email address. We do not save a separate copy of the photo for moderation. Our logs record the decision, category scores, generator and a shortened salted IP hash; a blocked attempt leaves a job record without the photo. OpenAI’s own handling and retention are governed by its API data policies, not by our database deletion window.

Until your image is made, your photo is stored in our database. It is deleted as soon as your image is made or the request fails, and it is never kept longer than three days.

To make your image, the photo is sent to the image-generation model that renders your result. That model is Doubao Seedream, reached through one of two providers: first Volcengine (ByteDance), and, only if that fails, kie.ai as a backup. With Volcengine the upload is passed through in the request. kie.ai needs the photo at a URL, so on that path it is uploaded to kie.ai’s temporary file storage, which deletes it automatically after about three days. We do not control those providers’ own retention beyond that — if that matters to you, do not upload the photo.

Analytics and cookies

We use Plausible, Google Analytics 4, Microsoft Clarity and Cloudflare Web Analytics to understand visits and improve the tools. Plausible, GA4 and Clarity are currently configured through this site; Cloudflare injects its own performance beacon as described below.

For visitors in the European Union (27 countries), Iceland, Liechtenstein, Norway, the United Kingdom and Switzerland, we load GA4 and Microsoft Clarity only after you choose Accept. We use Cloudflare’s country header to determine this rule; if the country is missing or unknown, including on local previews, we ask for consent first. A first-party session cookie stores only whether consent is required, not your country. In other countries these two services load by default until you choose Reject. Reject prevents them from loading on subsequent pages; if they have already loaded, we reload the current page to unload them. This cannot undo data already sent or remove cookies they previously set.

We save Accept or Reject in your browser’s local storage for one year, then ask again. If browser storage is unavailable, we cannot remember the choice for later visits. You can reopen the notice and change your choice at any time using Change cookie settings. Plausible and Cloudflare RUM continue regardless of this choice; sign-in session cookies are also unaffected.

Plausible is self-hosted at plausible.a3i.ai. It measures page views, referral sources, browser/device summaries, outbound-link and file-download activity, and tool-use events without setting analytics cookies.

Google Analytics 4 (GA4) sends Google page-view and session information, page URLs and referrers, browser/device details, approximate location and tool-use events. GA4 uses cookies such as _ga to distinguish browsers and sessions. See Google’s data-collection documentation.

Microsoft Clarity sends Microsoft interaction data such as clicks, scrolling, browser/device information and page content used for heatmaps and session replays. Visible page content and result-page URLs may be captured; do not assume session replays exclude everything shown on a result page. Clarity can use cookies such as _clck and _clsk to associate visits, subject to browser settings and regional consent restrictions. See Clarity’s data-collection documentation and cookie documentation.

Cloudflare Web Analytics / Real User Monitoring (RUM) uses a beacon that Cloudflare automatically injects into HTML as it passes through its network, separately from this site’s analytics scripts. The browser loads static.cloudflareinsights.com/beacon.min.js and sends measurements to /cdn-cgi/rum on this domain. These include page views, page paths and referrers, browser/device and operating-system information, country-level location, page-load timings and Core Web Vitals. According to Cloudflare, the RUM beacon does not use cookies or browser storage and does not track individuals across sites; its service receives the source IP as part of the HTTP request, then discards it at the nearest Cloudflare data center without storing it in core databases or logs. See Cloudflare’s RUM data and privacy documentation and analytics dimensions.

Our custom tool-use events sent to Plausible and GA4 contain coarse values such as the generator, selected style, status or error code, rather than the uploaded photo, account name or email. Automatic page measurement, Cloudflare performance measurements and Clarity session replays are separate from these custom events. Each provider’s own policies govern the data it receives and how long it retains it. You can use browser privacy settings or content blockers to limit analytics requests and cookies.

Contact

For privacy questions or deletion requests, contact the dramagenerator.ai operator at admin@dramagenerator.ai. Include the result link, or the approximate date and time of the request if you do not have a link, and the email address you used to sign in. Please do not attach the original photo. We usually reply within 7 business days.