PRIVACY NOTICE · UPDATED OCTOBER 5, 2026

Your ideas stay in your workspace.

PRISM uses the information you provide to operate accounts, create artwork, manage credits, and deliver purchases.

Social sign-in requests basic identity information. It does not give PRISM access to your ChatGPT conversations, Google files or Apple account content. Your browser may keep a selected upload for up to one hour to preserve your draft during sign-in, when browser storage is available.

What we store

• Your email address, account role, sign-in code hashes, and hashed session tokens. If you choose a password, we store its salted, keyed password hash; we do not store your plaintext password. Password changes close other signed-in sessions and send a security notice. If you connect ChatGPT, Google or Apple, we store the provider’s stable account identifier, email and optional display name to let you sign back into the same PRISM account. Provider tokens are verified on the server and discarded.
• Uploaded images, creative briefs, saved destinations, managed QR addresses, brand kits, campaigns, generation attempts, final artwork, and automated review results.
• A credit ledger, payment event identifiers, subscription status, and Stripe customer references.
• Operational timestamps and rate-limit records. When available, a hashed network address helps limit sign-in abuse.

How the service works

OpenAI receives the images and prompts needed for generation and art review. Resend receives your email address and transactional email content. Stripe receives payment and billing information directly through its checkout and billing pages. Upstash QStash delivers background job identifiers; the image and prompt stay in the studio until sent to the image provider. Cloudflare-backed site storage holds account data and private image files.

Artwork downloads require your account or a scoped API key. We do not publish your uploaded images or generated artwork in a public gallery. The studio owner can access operational records to support the service.

QR scan analytics

A published QR address redirects visitors to the destination chosen by its owner. We count redirect visits, the UTC date, broad device category and, when supplied, a referring hostname or source label. We do not store a referring page path or query string. Known bots, link previews, prefetch requests, Do Not Track and Global Privacy Control requests are excluded from application analytics.

Daily unique scan estimates use an account-specific, daily rotating keyed hash of the network address and browser information. The analytics database stores this hash, not the raw network address or full browser identifier, and sets no tracking cookie. Shared networks may merge visitors; a returning visitor can count again on another day. Infrastructure providers may maintain separate operational or security records.

Location analytics is off by default. An account owner may enable approximate country or city reporting after confirming that this is appropriate for their audience and notices. Location comes from the network provider and may be unavailable or inaccurate; we do not request device location permission or store precise coordinates. City totals below five visits are withheld. Disabling location collection affects future visits. Scan aggregates and daily deduplication hashes remain with the account while the service operates and can be included in content-removal requests.

Launch availability requests

If you join the launch list, we store your email, plan preference, consent version and timestamps. Launch emails require email confirmation; joining does not create an account or payment. Unconfirmed requests expire after 30 days. Confirmed requests remain until removed. The confirmation receipt and browser provide a private removal link. The owner can view requests and export confirmed emails for availability updates. The launch-list flow does not send announcements automatically.

Cookies and browser storage

An essential, secure, HTTP-only cookie keeps you signed in for up to thirty days. Your browser also keeps the current creative brief and active job identifier so a return visit can resume your work. The application does not include advertising cookies or third-party marketing trackers.

Retention and requests

Saved artwork, project data, and credit history remain associated with your account while the service operates. Expired sign-in and rate-limit records are periodically removed. Payment providers may retain their own records. Contact support to request access, correction, or removal of your account content; billing and abuse-prevention records may need to be retained separately.

Contact

The privacy and support contact will be published before paid plans open.