SPAWN Privacy Policy

This policy describes how the current SPAWN service handles information when you sign in, fund credits, use rooms and AI services, or connect social accounts. Contact: support@spawnbackrooms.com.

Wallet access and payments

SPAWN processes your wallet public address, signed sign-in proof, sign-in nonce, workspace identifiers and session records to authenticate access. Your wallet performs signing; SPAWN does not require your seed phrase or private key. Necessary cookies maintain the session. Optional remembered-device access lasts longer than an ordinary session.

For prepayments and paid work, SPAWN keeps quotes, transaction signatures, verified payment observations, invoices, credit and settlement records, and related recovery and audit information. Signed payment transactions and verification requests pass through the configured Solana network services. Blockchain transaction details are public. Browser storage keeps limited payment references so an interrupted flow can be recovered.

Rooms and media

SPAWN stores room names, descriptions, visibility choices, briefs and context, workflow activity, and generated artifacts and revisions under your workspace. Public room directory information includes the room name and description. Making a room private removes its public directory projection; it does not erase the underlying workspace records.

When you approve generation, relevant prompts, settings and approved references are sent to the configured model services to carry out the request. The implementation uses Cloudflare infrastructure and routes that include OpenRouter and selected model providers such as Recraft or Runway. Generated original media is stored in private Cloudflare R2 storage. The provider used depends on the selected model and request.

Social connections and publication

When you connect X, TikTok or Instagram, SPAWN receives account identifiers, available profile details, granted permissions, and authorization tokens with expiry information. Tokens are encrypted in server storage and used to perform authorized platform operations, including refreshing the connection.

When you approve a post, SPAWN sends the selected content and applicable settings to the chosen platform. This may include media bytes or media URLs, captions, descriptions, accessibility text, privacy choices and other platform options. Media export URLs allow the platform to retrieve the approved media. SPAWN records publication requests, status, provider post identifiers and links, errors and delivery history. Limited browser recovery records identify the request so its status can be retrieved.

Cookies, storage and service logs

SPAWN uses session and short-lived connection cookies, plus browser storage for request recovery. The Reown wallet integration has its analytics option disabled. The website uses Cloudflare Web Analytics to understand website performance and usage. SPAWN also records operational events and errors needed to run and recover the service. Wallet, infrastructure, model and social-platform providers process information under their own terms and policies.

Retention and your choices

SPAWN retains operational, workspace, payment and publication records; there is no single automatic deletion period covering all of them. Some temporary connection records, routine delivery events and media exports have cleanup rules. Export cleanup can wait until publication or review reaches a safe outcome.

Logging out ends session access but does not erase workspace or payment records. Disconnecting a social account removes stored token credentials and stops pending deliveries, while account identity and publication history remain. SPAWN attempts platform revocation for X and TikTok. Instagram access must also be removed in Instagram settings. Already submitted requests may finish, and disconnecting does not delete posts already on a platform.

Contact support@spawnbackrooms.com to request access, correction or deletion, or to ask about retained information. A request is not an automatic or comprehensive deletion process; its scope and handling must be confirmed. Do not include wallet secrets, passwords or access tokens in your message.