OMA collects the minimum data needed to run the service: the email address or wallet address you choose for sign-in, a SHA-256 hash of API keys, per-call usage records, and on-chain deposit or settlement identifiers.
We do not sell personal information. The OMA gateway does not save prompt or completion content. Website conversations and drafts are saved in this browser. Request content is forwarded transiently to the selected inference provider so it can generate a response; provider handling is described below. You can export or delete the account data OMA stores from the dashboard.
What we collect
Account, usage and security records
What we store
Email address: Stored when you choose magic-link sign-in and used for authentication and account messages.
Wallet address: Used for authentication via SIWE (EVM) signatures.
Session and audit metadata: Can include IP addresses, user agents, timestamps and account actions.
API usage: Token counts and timestamps for billing.
Transaction hashes: For on-chain deposit verification.
API keys: The server database stores SHA-256 hashes, prefixes, names, timestamps, model scope and optional IP allowlists. The raw key is returned once at creation; browser chat can also install it in an HttpOnly authentication cookie for up to seven days.
What the OMA gateway does not persist
Prompt text: Request content is forwarded for inference without being saved by the gateway.
Completion text: Model output is streamed to you without being saved by the gateway. Website chat keeps a local copy in your browser.
Private keys: Signing stays in your wallet. OMA reads payment-relevant balances and transfer receipts to verify funding.
Profile enrichment: No legal name or demographic profile is required beyond the email or wallet identifier you choose for authentication.
Authentication
Passwordless email or SIWE wallet
You can authenticate with a passwordless email magic link or Sign-In With Ethereum (SIWE). OMA stores the identifiers for the method you choose, together with session and security metadata.
Email sign-in: Stores your email address so we can deliver magic links and account messages.
Wallet sign-in: Stores your public wallet address after you prove control with a SIWE signature.
Usage attribution: Associates token spend, keys, and credits with your account for billing.
If you use wallet sign-in, OMA does not crawl your wallet history or build a profile from unrelated on-chain activity.
Logs and billing
Usage and content handling
For billing
Model id: e.g. "kimi-k3"
Token counts: Prompt and completion tokens per request.
Cost in cents: Computed at settlement time.
Request timestamp: UTC, to the second.
We do not log
Prompt text: The gateway does not include request content in usage logs.
Completion text: The gateway does not include response content in usage logs.
Tool payloads: Function-call arguments and outputs are not retained.
File contents: Uploaded files are processed transiently and dropped.
Retention
How long we keep things
Website chat saves conversations, drafts, and preferences in this browser, with separate histories for guests and each signed-in account. History does not sync between devices. Manage, export, or delete threads from Chat history. Clear this site's browser data to remove all local copies and preferences. Account data exports and deletion apply to the server records listed below.
Account and sessionsUntil deletionProfile, linked wallets and sessions are removed with the account. Sessions can include IP addresses and user-agent information.
API keysUntil account deletionRevocation or expiry stops authentication. A revoked or expired key's hash and metadata can remain until the account is deleted. Browser chat can hold an installed raw key in an HttpOnly cookie for up to seven days.
Usage historyUntil cleared or deletedAccount usage records remain until you clear history or delete the account. Separate financial records are retained as described below.
Spendable creditsUntil account deletionCredits do not expire while the account is active. Deletion removes its balance and account-linked deposit records.
Financial recordsRetained for reconciliationPayment claims, settlement records, card orders and detached inference receipts can survive account deletion. Order records can contain account identifiers and provider-supplied customer details.
Security and signup recordsRetained after deletionAudit records can retain IP addresses, user agents and resource identifiers. Historical signup-grant records retain a normalized email or wallet-derived identifier to prevent repeat grants.
Third parties
Who sees what
Inference cannot happen without sending request content to the service that runs the selected model. OMA forwards that content transiently for inference and does not persist it. Provider retention and privacy guarantees depend on the selected provider and model; review the provider terms for sensitive workloads.
Venice AIInferencereceives request content to run the selected model; Venice privacy mode and provider policies apply
OMA-AI / OpenBrokerInferencerequest content is processed by the Gonka/OpenBroker-backed model that serves the call
BaseSettlementon-chain transaction verification
~ When configured, Google Analytics loads on the site and initializes measurement on the production apex and www hosts. Measurement runs on every pageview with IP addresses anonymized, and no advertising signals are collected. Inference prompts and answers are not explicitly sent as analytics events by the site.
Sub-processors
Operational vendors
Hosting services process requests in transit. Other configured vendors handle account, payment, rate-limit, email or analytics data for their service. Contact support@nosytlabs.com for questions about provider handling and data agreements.
VercelWebsite hostingweb requests and proxied inference content in transit
NeonAPI and databaseinference content in transit; stored account, usage and financial records
Base / on-chain RPCSettlementtx hashes for deposits
ResendEmail deliveryauthentication and support email content
Google AnalyticsSite analyticsconfigured Google tag and page measurements with IP addresses anonymized; no advertising signals
PolarPayment processingcard checkout; no prompt content
Your rights
What you control
Delete your account
Delete your account from Settings. Profile, sessions, keys, usage and account-linked balances are removed. Financial, audit and historical signup-grant records described above can remain. Clear browser chat history separately.
Revoke API keys
Revoke a key from the dashboard to stop future requests authenticating with it. Requests already in progress can still complete and incur a charge.
Export account data
Download the account export from Settings. It includes the profile, key metadata, active sessions, deposits, balance and account audit history exposed by the export API. Export local conversations separately from Chat history.
Ask a privacy question
Email support@nosytlabs.com for access, correction, processing or deletion questions, including records retained after account deletion.