Privacy policy
Less data, more clarity. Here is what this preview does—and what must be settled before a live launch.
For this interface preview only. Legal review and operator-specific details are required before a live launch.
Who is responsible
Swapee is currently an interface preview. A legal data controller, registered address, applicable privacy jurisdictions, and verified privacy contact have not yet been designated. They must be published before the service collects data for live exchange operations.
Data in this preview
Amounts, asset selections, recipient addresses, and order-search inputs are held in temporary browser memory for interaction. They are not submitted to an exchange provider or saved in an application database. Do not enter sensitive information or use real funds. Hosting infrastructure may process technical request data.
Hosting and analytics
The site uses Vercel hosting and Vercel Analytics in production. These services may process page views and technical usage information under their own documentation and applicable agreements. Google-hosted fonts are downloaded at build time by Next.js and served by the site. This preview does not use localStorage to persist swap data.
Proposed live-service data
A production exchange may need wallet addresses, transaction hashes, order details, support communications, and, where required, identity or source-of-funds documents. The controller must identify purposes, lawful bases, providers, international transfers, and retention periods before collecting that information.
Disclosure and security
A live service should disclose data only to necessary exchange, infrastructure, compliance, and support providers, or when legally required. Encryption and access controls reduce risk but cannot guarantee absolute security. Never provide a seed phrase or private key.
Your rights
Depending on applicable law, you may have rights to access, correct, delete, restrict, object to processing, or receive a copy of personal data, and to complain to a supervisory authority. Legal retention and compliance obligations may limit deletion. A verified request channel must be published before launch.
Changes
This draft must be updated to match the actual service and approved by counsel before production. Material changes should be clearly dated and communicated.