Privacy

What is stored about you

• Your account. Email address, a bcrypt hash of your password (never the password), and the display name you give. Signing in with Google instead stores the Google account id and the profile name and picture Google returns.
• What you make. Pack names, the briefs you write, every icon — generated, drawn by hand, imported from a file or pasted in — and each saved version of it, where you place icons on the board, and the chats you have with the AI editor, including its replies.
• Credits and purchases. A ledger row for every credit granted, spent or refunded. If you buy credits, Stripe handles the payment and we keep the Stripe identifiers, the amount, the currency and the status. Card numbers never reach this service.
• Usage events. Named events such as “pack generated” or “export”, with your user id and a few non-sensitive properties. On this deployment they are stored in this application's own database and are not sent anywhere else.
• Page views. This deployment uses Vercel Web Analytics to count traffic. It sets no cookies. It records which page was opened, the referring site, and coarse details of the request such as country, browser and device type; returning visitors are counted with a hash that is rotated daily rather than by storing your address. The address is cleaned before it is sent: query strings are stripped and record identifiers are replaced, so a page view reads /packs/[id] rather than naming a pack — and a password-reset link can never travel with its token.
• A record that the free credits were claimed. The welcome credits are offered once per mailbox, so one row is kept saying that an address has had them. It holds no address and no IP: both are stored as keyed hashes, which can answer “has this one been seen before?” and cannot be read back or looked up. This row deliberately outlives the account — deleting an account and signing up again does not reissue the credits — and it identifies nobody on its own.
• A session cookie. One signed, HTTP-only cookie that keeps you signed in. There are no advertising cookies, and nothing here follows you to other sites.

Who else sees it

Your icon briefs, the icons you ask to edit, your editing instructions and, when you run a consistency analysis, every icon in that pack are sent to the AI provider configured for this deployment (currently anthropic), which processes them under its own terms. Payments are processed by Stripe. Page-view counts are processed by Vercel, which also hosts the application. Everything else stays in this application's database and object storage, which Iconzzi operates.

Your packs are private to your account. Nothing you make is published or shown to other users by this software.

Deleting your data

Settings → Delete account removes your user record, and with it your packs, icons, every stored version, your chats, your credit ledger and your payment records. The SVG files in object storage are deleted first. Usage events are kept but detached from you — the user id on them is set to null, so they survive only as anonymous counts.

Deletion is immediate and cannot be undone. Export anything you want to keep before you do it.

Security

Passwords are hashed with bcrypt. Every API request is checked against the signed-in session, and every database read and write is scoped to the account that owns the record. Sign-in attempts, AI operations and the rest of the API are rate limited. No system is perfect: if you find a problem, please report it to legal@iconzzi.com.

Questions

For anything about your data, including a copy of it, write to legal@iconzzi.com.