# Access, data & control

Know what is private, where records live, and which actions need your authorization.

State: Product reference · Updated September 21, 2026

## Site access and studio authorization

Studio accounts use a signed, expiring Solana wallet challenge. No transaction or seed phrase is requested. The existing funded operator can also use GitHub. Every project request checks account ownership. Sessions expire after 12 hours; Sign out revokes the current session immediately.

Projects, images, receipts, and content plans are scoped to their owner. A project name or ticker is not a verified token-ownership claim. There is no community role reassignment without a publishing integration.

## Where data goes

Browser data does not sync between devices. Creator studio records do. Deleting browser storage does not delete saved studio records. A self-service account-data deletion workflow is not yet available.

| Data | Location / use |
| --- | --- |
| Demo wallet, coins, trades | This browser’s local storage. Cleared by demo reset. |
| Devnet receipt | This browser; token and transaction records are public on devnet. |
| Studio projects and plans | Turso SQLite storage, restricted to the authorized studio account. |
| Generated image bytes | Private Vercel Blob storage, served only after studio authorization. |
| Image direction | Sent to the configured generation provider to perform the request. |
| Provider credentials | Server-side secrets; not entered into the public walkthrough. |

## Wallet and spending control

The devnet launcher asks your wallet to sign a reviewed transaction. It does not collect a seed phrase or private key. Studio sign-in uses a separate message signature that authorizes no transaction.

Image submission spends operator-prepaid provider credit within app limits. A pause prevents new submissions; it cannot reverse a request already accepted by the provider. Social posting would require its own account authorization.

## Assurance boundaries

No independent security audit or uptime guarantee has been published. Functional tests and request checks are not substitutes for an independent review.

Receipts help inspect activity, but do not certify creative ownership, token safety, market demand, or marketing results. Mainnet fee custody and public role transfers require further engineering and review.

[Current product scope](/docs/capabilities)