Privacy & Encryption Policy
How goongen.ai protects your data through end-to-end encryption and minimal data collection.
Last updated: August 2026
What we collect
- Login email - used only as your login name. We send no verification or marketing emails. Accounts created before email login may have a username instead. We never see your password - our login protocol proves it is correct without it ever leaving your device.
- User ID - a randomly generated UUID
- Public encryption key - your RSA-2048 public key, generated in your browser
- Payment info - only if you pay: the crypto transaction on our self-hosted payment processor, or which credit code was redeemed. No card data, no payment account.
- IP address - held briefly for rate limiting and abuse prevention (for example the free demo limits), never linked to your creations. If an account is permanently banned, known exact addresses are retained only as keyed cryptographic hashes to prevent ban evasion.
- Browser security signature - a hashed combination of browser and device characteristics used only for account security and permanent-ban enforcement. It is not used for advertising or analytics.
- Support messages - only if you contact us (contact form or in-app support chat)
We do not collect your real name, and we never see your password or your content. No ad tracking of any kind.
What we cannot see
The following data is encrypted with your public key before it ever reaches our storage. We do not hold your private key and have no way to decrypt it.
- Your uploaded images
- Your generated images and videos
- Your prompts (encrypted before database storage)
- Your private key (stored encrypted on the server with a key derived from your password - we cannot decrypt it; for key-file-only users it exists only in your browser's sessionStorage)
- Your password (it never leaves your device, even during login)
How encryption works
- We use RSA-OAEP + AES-256-GCM hybrid encryption
- Your RSA-2048 keypair is generated client-side using the Web Crypto API
- Your private key lives in your browser's sessionStorage - it is never sent to our servers in readable form
- Every image and prompt is encrypted with a unique AES-256 key, which is itself encrypted with your RSA public key
- This is a technical guarantee, not a policy promise - even if we wanted to, we could not access your content
GPU processing
During generation, your images are briefly decrypted in memory on the GPU for processing - on our own GPU servers and, for some modes, on dedicated GPU instances provisioned just for your session. Nothing is persisted to disk in readable form, nothing is logged, and session instances are wiped after your session ends.
Data deletion
- You can delete your images at any time from the editor
- You can delete your entire account - this removes your data and unlinks anything that cannot be removed outright
- Administrators can revoke public keys, which makes all associated encrypted data permanently inaccessible - no one can decrypt it
- No backups of decrypted content exist at any point in the pipeline
Cookies & local storage
- gg_auth cookie - a login session cookie so you stay signed in. It identifies your account, nothing else.
- sessionStorage - private key and user UUID (cleared when you close the tab; logging in restores them, key-file-only users should keep their .pem backup)
- localStorage - disclaimer acceptance and UI preferences only
- No tracking cookies, no analytics cookies, no ad cookies
Third parties & analytics
- GPU infrastructure - our own GPU servers, plus trusted providers for on-demand session instances (no persistent storage, wiped after use)
- Payments - self-hosted crypto payment processor on our own infrastructure (only if you choose to pay)
- Rybbit analytics - open-source, cookieless web analytics (rybbit.io), self-hosted on our own domain. Collects anonymous page views, referrer, device type, and country only. No cookies, no fingerprinting, no personal data. IP addresses are used only for geolocation and are never stored.
- Affiliate attribution - if you arrive through an affiliate link, a lightweight script records which affiliate referred you so they can be paid. It does not track you beyond that.
- No ad networks, no data brokers
Questions
If you have questions about our privacy practices, reach out via our contact page.