Limbo policies
Privacy policy
What Limbo processes, why it is needed, and the choices you have.
Updated
Information we process
Account information includes your email, display name, account settings, authentication-provider identifiers and security records. Passwords are hashed. Authenticator secrets and wallet key material are stored in encrypted form where those features are used. Limbo also holds its own platform signing keys. The statement that we hold no cryptographic material would be incorrect.
If you request email updates, we record your email address, the signup source, the consent notice version and time, confirmation and withdrawal state, and the security records needed to confirm or stop the signup. Confirmation links expire, and delivery retry material is encrypted. This signup is separate from ordinary account creation and browser tracking choices.
When you use the marketplace, we process listings, uploaded media, payout and refund addresses, orders, payment references, reviews, support messages and dispute evidence. We record the policy version and acknowledgements associated with an account or purchase. Do not put passwords, recovery phrases or unencrypted private keys in a listing, message, support ticket or review.
Purposes and legal bases
We use account and transaction information to provide the services you request, including sign-in, profiles, checkout, delivery and support. Security logs and abuse controls protect the service and its users. Depending on applicable law, these purposes rely on performing a contract, legitimate interests in security and service operation, or a legal obligation.
Optional product and marketplace email updates start only after you explicitly request them and confirm the email. You can stop these updates through the unsubscribe link without signing in. Confirmation and request-limit records help prevent unwanted repeated messages. We retain the minimal consent and suppression records needed to honour your choices; stopping optional updates does not stop account-security or order messages you request.
Optional browser analytics, browser diagnostics, personalized recommendations, embedded media, saved search history and referral attribution depend on separate choices. Personalized recommendations use on-platform purchases and product interactions to select labeled sponsored listings and eligible platform offers. You can refuse these purposes without losing ordinary account or purchasing functions. Withdrawing a choice stops future processing for that purpose; it does not erase an already completed transaction or referral credit.
Public profiles and blockchain records
The profile, storefront, listing and review information you publish can be viewed by others and may appear in search engines. Public addresses and transactions are visible on their blockchain. Other people, search engines and independent blockchain services may retain copies; deleting a Limbo account does not erase a blockchain or every third-party cache.
Only publish information you intend to share. Private account security data, private inventory and moderation details are not intended for public responses.
Service providers and third-party content
Limbo uses hosting, database and media-storage infrastructure, Cloudflare for delivery and abuse protection, and Resend for account and transactional email. Discord processes information when you choose its sign-in or community services. Blockchain explorers, RPC providers and price services receive the public network information needed to check payments and quotes. WalletConnect and your wallet provider are contacted when you request their connection features.
Resend also delivers the email-update confirmation and optional updates you choose. It receives the recipient address and email content needed for that delivery. Publicly listed addresses and previous correspondence are not treated as permission for optional updates.
Where configured, Sentry receives minimized server diagnostics. Optional browser diagnostics and Vercel Analytics require the relevant browser choice. We disable SDK collection of request bodies, cookies, headers and user information in diagnostics. YouTube and Spotify players load only after you allow embedded media. User-selected remote images and media can contact their host to display the content you requested. Third parties receive connection information such as an IP address and apply their own notices.
Providers may process information in other countries. Applicable transfer safeguards and provider agreements must cover those transfers. Consented recommendation interests stay within Limbo. Sellers receive aggregate product and campaign statistics, without buyer identities or individual browsing histories. Limbo does not sell personal information.
Retention and security
Account and saved settings remain while needed to provide your account. Order, consent and dispute records may remain for unresolved transactions, fraud prevention, accounting duties and legal claims. Operational logs are subject to rotation and operational retention. Deletion requests are assessed against those purposes and applicable law; this notice does not promise immediate removal of records that must be retained.
Optional product observations and individual sponsored exposure records are pruned after 90 days. Consent revisions remain for up to the 180-day consent lifetime to prevent stale requests from restoring withdrawn purposes. Aggregate campaign delivery totals and purchase records remain available for billing and support.
Optional browser choices last up to 180 days. Referral attribution expires after 30 days, saved marketplace navigation after six hours, and the temporary listing cache after ten minutes. Authentication and wallet-access expiry are separate. Your cart, saved settings and drafts are not cleared merely because an application update is deployed.
Your rights and contact
Depending on applicable law, you may request access, correction, erasure, restriction or portability of your information, object to processing, withdraw consent, or complain to a supervisory authority. Some requests require proportionate identity verification. We handle requests within the applicable legal deadlines and explain any lawful restriction or extension.
Contact the Limbo team through a support ticket or the linked Discord community. If you cannot sign in, use the Discord contact route. This notice describes processing; reading it is not a request to consent to every purpose. Material changes will be identified, and new consent will be requested when required.
Contact and support
Open a support ticket or use the Limbo Discord community (opens in a new tab).