Document status: beta draft, revised 2026-11-05. The team has not yet supplied the legal operator's registered name, correspondence address, country or data-controller identity. These documents describe current operations but are not a completed legal disclosure or a claim of commercial readiness. Contact support@unbound-me.com for clarification before purchasing or submitting personal data. Statutory rights remain unaffected.
Who handles your data
The unbound.ai team operates the service interfaces. A brand and a shared mailbox do not identify the legal data controller. Controller identity, address, establishment and any joint-controller arrangement must be provided before this becomes a final privacy notice. Privacy requests currently go to support@unbound-me.com.
Data used by the service
- Welcome-offer enrollment, bonus ledger entries and a keyed fingerprint of the account email for one-time eligibility checks, including preventing repeat claims after account recreation.
- Account email, account identifier, creation time and a salted password hash; passwords are not stored in plaintext.
- Hashed session and administrator reset tokens, keyed hashes of email codes and authenticator recovery codes, encrypted authenticator secrets, expiration times, mailbox verification and security-alert preferences.
- API key metadata, model permissions, spending caps, usage totals, billing reservations and receipts; downstream key-management infrastructure holds inference credentials. Some delivery secrets must be recoverable in encrypted form for Seal or idempotent MCP results.
- Deposit invoices, asset/network/address, transaction identifiers, confirmation state, credited amounts and ledger/audit records. Blockchain addresses and transactions can be public and permanently traceable.
- Optional Discord community linking: Discord user ID/name, your internal account identifier, rules-acceptance version/time, one-time hashed pairing requests, join-greeting delivery markers, and boolean email-verification/confirmed-payment eligibility. The API Customer role is visible to Discord members. The bot does not receive API keys, passwords, email addresses, payment amounts or wallet credentials. Unlink with /unlink in Discord or the account connection page; eligibility roles are removed on the next sync. Discord processes community membership, messages and roles under its own policies.
- MCP client names, granted scopes, hashed pairing proofs and grant tokens, activity dates and encrypted results for retried account changes.
- Request content, model selection and generated outputs while routing inference. Operational request metadata is used for settlement and troubleshooting. Successful-login alerts, if enabled and sent to a verified mailbox, contain the sign-in time, method and client IP address. Support correspondence contains whatever information you choose to include.
- IP addresses and HTTP metadata processed by the edge and server for transport and abuse prevention. In-memory rate limits distinguish clients through authenticated proxy headers; they are not a separate public user profile.
Purposes and legal bases
The intended service purposes are creating accounts, authenticating access, routing authorized model requests, settling usage, confirming deposits, preventing abuse and responding to support or legal obligations. Contract performance may cover necessary service processing; security and fraud prevention may rely on legitimate interests after assessment; legally required records depend on the operator's applicable obligations. Consent must be obtained separately for optional uses that require it. These are purpose descriptions, not a substitute for the operator confirming each applicable legal basis and retention duty.
No marketing subscription, behavioral-advertising system or optional analytics consent flow is currently implemented. Sending a support message does not subscribe you to marketing.
Providers and international transfers
Requests are forwarded to Refuseless inference infrastructure and potentially its downstream model hosts. Cloudflare handles public edge/tunnel traffic. home.pl hosts the team's mailboxes. Configured blockchain RPC providers, mempool.space and price-data services receive relevant public addresses, transaction or market queries; they do not need your account password. Server hosting and operational administrators can access information necessary to operate the service.
Do not assume zero retention, no training, end-to-end encryption or exclusively local/EU processing. Local message-log settings do not control a provider's own retention or training practices. The current service does not publish a verified data-processing agreement, complete subprocessor register, processing-country list or transfer safeguards. Those items require operator/provider confirmation before sensitive or regulated workloads are accepted. Do not submit confidential or sensitive personal data on the assumption that such guarantees exist.
Storage and retention
Customer account, billing, invoice and audit records are persisted in the service database and backups. There is currently no automatic general deletion schedule for these records; the operator must establish and publish appropriate retention periods before a final notice. Contact support for review, access or deletion rather than relying on an invented fixed retention promise. Backups may retain earlier copies until their own rotation; a backup rotation period has not yet been confirmed.
Customer sessions expire after seven days; administrator sessions after eight hours. Administrator-issued password reset codes expire after fifteen minutes. Email codes and sign-in challenges expire after ten minutes and permit at most five verification attempts. Authenticator recovery codes work once until replaced or 2FA is disabled. Encrypted mail content is erased after SMTP acceptance or delivery expiry/failure; delivery metadata is eligible for deletion after seven days. SMTP acceptance does not prove arrival in the inbox. MCP pairing requests expire after ten minutes, grants after seven days, and completed idempotency results are eligible for cleanup after twenty-four hours. Expiration revokes usability; it does not necessarily mean immediate physical erasure of every row or backup. Public-chain transactions cannot be erased by us.
Your choices and rights
Depending on applicable law, you may request access, correction, erasure, restriction, portability, information about recipients, or object to processing based on legitimate interests. Where consent is used, you can withdraw it without affecting earlier lawful processing. Some requests have exceptions, including necessary legal records and third-party public-chain data. No automated credit scoring or solely automated decision with a promised legal effect is offered; security and billing decisions can be raised with support for human review.
Send a request from your account email with the subject Privacy request. We may ask for proportionate proof of account control; never provide your password, private key or seed phrase. The service has no self-service export/deletion button yet. Statutory response periods apply where relevant. You may complain to your competent supervisory authority; in Poland this is UODO. See UODO's rights information.
Security and changes
Passwords are hashed; stored customer sessions and MCP tokens are hashed; certain recoverable secrets are encrypted. Public production access uses HTTPS. These measures do not eliminate all risk. Report suspected exposure privately to support. Revisions will be dated here; additional processing will require an updated notice and any required consent.
