Skip to content
Policy outlineFrontend preview

Privacy

What the preview actually stores, and what must be defined for production.

Draft scope

This page documents preview behavior and launch requirements. Final operator details, legal terms, contact channels, and production commitments have not been established.

Applies toThe Noemad frontend previewEffective production dateNot set

Browser data

The preview stores display preferences and local demo records in browser storage. A shared browser profile can expose those records to other users of the same device. Use the relevant clear controls or clear site data to remove them.

Wallet information

An installed wallet is accessed only after the user chooses it. A public address and network may be displayed in the current page. Wallet connection alone is not a backend account or consent to transfer assets.

Prompts and files

Local sample prompts are processed by the demonstration code. The current build does not send them to an inference provider. Future API, upload, and voice features require a published processing contract before they are enabled.

Future service data

Production processing may involve wallet challenges, run metadata, payment receipts, prompts, outputs, support records, and technical logs. The operator must publish purposes, recipients, locations, retention periods, and request procedures before launch.

Provider review

Provider policies vary. No universal promise about training, storage, deletion, or geographic processing is made here. The chosen adapter and profile must document the actual service terms.

Contact and requests

A privacy contact and rights-request workflow have not been configured for this preview. Production activation requires a verified contact and a process for access, correction, deletion, and applicable legal rights.