← Back to SirenRender

Privacy Policy

Effective 2026-06-10 · Last updated 2026-07-27

This policy describes what sirenrender.com (the “Service”, formerly create.dabber.life) collects, why, how long it is kept, and the choices you have. It supplements the Terms of Service; if the two conflict, this policy controls for privacy matters.

Plain English summary. We collect the minimum needed to run an anonymous-friendly image generator: a per-browser ID, your prompts and outputs (deleted within ~24 hours), an email address only if you sign in, and a transaction hash only if you buy credits. We don't sell your data. Ads shown to signed-out visitors come from a third-party network that has its own privacy policy.

1. What we collect

DataPurposeRetention
Per-browser visitor ID (dabber_visitor cookie)Ties your generations to your browser so only you can view them; rate limiting; ad-frequency countersUntil cookie cleared; server-side generation history is short-lived
Prompts, model parameters, generated imagesOperating the Service; abuse detectionGenerated images auto-delete in ~24 hours; prompt/queue records are similarly short-lived
Uploaded edit-source imagesRunning the edit you requested; screened by automated nudity detectionProcessing only — never republished or browsable by other users; purged by scheduled retention cleanup and deleted on request
IP address & request metadataRate limiting, abuse detection, securityRolling logs, short-lived
Email address (only if you sign in via magic link)Account identity, credit balance, referral code, sign-in linksUntil you request account deletion
Credit purchase records (transaction hash, network, asset, pack, timestamp)Payment verification, double-redemption prevention, fraud preventionRetained while the Service operates (fraud/accounting)
Age-affirmation flagRemembers that you confirmed 18+ so we don't re-promptBrowser localStorage, until cleared
Passive browser fingerprint (user-agent, screen size, timezone, language, canvas/WebGL hash)Abuse detection and ban enforcement onlyOnly retained when attached to a safety incident
Safety-incident records (blocked prompts, ban entries, associated fingerprints)Legal compliance, abuse prevention, law-enforcement cooperationIndefinite

Transaction hashes you submit refer to records on public blockchains; the on-chain data was already public before you submitted it. We look it up via public RPC endpoints to verify payment.

2. Third parties

We do not sell personal data, run third-party analytics trackers, or share prompts/outputs with advertisers. Data may be disclosed to law enforcement pursuant to valid legal process, or where we have a good-faith belief disclosure is necessary to prevent imminent harm or protect our rights (e.g., suspected child exploitation is reported to NCMEC).

3. Cookies & local storage

NameTypePurpose
dabber_visitorCookie (functional)Anonymous per-browser identity; required for viewing your own generations
dabber_token / session cookieCookie (auth)Keeps you signed in
dabber_age_verifiedlocalStorageSuppresses the 18+ prompt after you confirm
Banner/announcement dismissal flagslocalStorageRemembers dismissed notices
Third-party ad cookiesCookies (advertising)Set by the ad network for visitors who have not purchased — see §2

You can clear cookies and localStorage at any time in your browser; the Service keeps working (you'll be re-prompted for age confirmation and lose access to prior anonymous generations).

4. Your choices & rights

Some records are exempt from deletion where retention is required for legal compliance, fraud prevention, dispute resolution, or enforcement of the Terms (notably safety-incident and purchase records).

5. Security

Traffic is encrypted in transit (TLS). Stored data lives on operator-controlled infrastructure with access limited to the operator. No system is perfectly secure; do not submit data you cannot afford to expose, and remember generated images are accessible to anyone you share a link with.

6. Children

The Service is strictly 18+. We do not knowingly collect data from anyone under 18; if we learn we have, we delete it and terminate the account. See the age-confirmation requirement in the Terms.

7. Changes

We may update this policy by posting a revised version here with a new effective date. Material changes will be announced with a notice on the Service.

8. Contact

Privacy questions and requests: admin@sirenrender.com