Access, data & control
Know what is private, where records live, and which actions need your authorization.
On this page
Site access and studio authorization
The product preview and handbook are separate from the private studio. The studio uses GitHub sign-in and checks an explicitly authorized account identity on every request. No repository permissions are requested. 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 in this pilot.
Where data goes
Browser data does not sync between devices. Private 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 is separate from wallet signing.
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
This is an early pilot. No independent security audit or production 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.