PRIVACY & DATA RETENTION
Only what the factory needs.
Effective 2026-09-09 · Version 3
No email, no password, no tracking pixels. Your wallet address is your account.
Your art is private to your signed-in wallet and never shown to other users or used by GenFT to train models. Optional AI processing is subject to the provider’s terms.
Renders expire after your plan's retention window; reports stay so hashes remain verifiable.
1. What we store
The free artwork workspace processes files in your current browser tab. It does not upload your artwork or save it automatically. Editable project files and prepared PNGs stay wherever you download them. Project files contain your original images and placement settings; deleting server data does not delete your downloaded files.
- Wallet address and short-lived sign-in sessions (a random token in an HttpOnly cookie, hashed on our side).
- Invoices and entitlements: plan, amount, invoice reference, the finalized Solana transaction signature, and timestamps. Payment data lives on the public Solana ledger regardless of us.
- Project data: the mascot reference you upload (each upload kept as an immutable revision), generated base candidates, the locked base, trait layers, configuration (names, weights, rules, seed, metadata text) and rendered outputs.
- Job records: status, timestamps, error messages and the provider cost of AI jobs, plus an internal usage ledger of provider spend.
- Server logs: request paths, status codes and the connecting IP address, kept briefly for security and rate limiting.
2. What we do not do
We do not use analytics or advertising trackers, sell or share your data, train models on your uploads, or show your projects to anyone but the signed-in wallet that owns them. Files are stored with restrictive permissions on our servers and served only through authenticated, no-store responses.
3. Third parties that process data for you
- Image model provider (currently Leonardo.AI, private production mode): receives your mascot reference and art direction only when you request AI candidates or background removal. Using your original artwork does not send it to the image provider. Provider terms apply to their processing.
- Solana RPC provider: receives payment-verification and, when you launch, transaction requests. Wallet addresses and transactions are public on-chain by nature.
- Cloudflare: fronts the site (TLS, DDoS protection) and sees request metadata.
- When you launch a collection you choose your own permanent storage and RPC providers; we do not upload your artifacts anywhere on your behalf.
4. Retention and deletion
- Rendered images and token metadata from a full render are deleted automatically after the plan's retention window (7 / 14 / 30 days) starting at render completion. The expiry date is shown on your project. Download your bundle before then.
- Manifest, rarity and provenance reports (small JSON files with hashes) are kept after expiry so published provenance stays verifiable.
- Mascot uploads, candidates, locked base and trait layers are kept while the project exists so you can re-render; you can ask support to delete a whole project at any time.
- Invoices, entitlements and the usage ledger are kept for accounting for as long as required by law.
- Sign-in sessions expire after 7 days or when you disconnect.
- Server backups use restricted file permissions. Backup copies may persist after files are deleted from an active project; contact support for deletion requests.
5. Your rights and contact
You can export your project at any time by downloading the bundle, and you can request access to or deletion of project data by contacting [email protected] from a message signed by, or otherwise clearly linked to, the owning wallet. We answer within 14 days. Depending on where you live you may have further statutory rights, which we honour.
6. Security
Traffic is TLS-only with HSTS. Sessions are HttpOnly, SameSite=Strict cookies. Uploads are size- and pixel-limited and decoded with hardened settings. Project files are written with owner-only permissions under a dedicated service user. No customer private keys are ever requested, transmitted or stored.
7. Changes
We update this notice when the Service changes; the version and effective date above change when we do.