Skip to content

Privacy Policy

Last updated: 10 October 2026

In short: if you join the waitlist, we keep your email address, and your Discord handle if you give it, so we can invite you and send you news about Sapio. In the testnet apps, your wallet address and what you do in the testnet are recorded on our testnet chains, where anyone can see them. We also keep access requests, reviews and invite records, including the email address an invite was sent to and the wallet address registered with it. The website sets no cookies. The apps use device storage for access, wallet connections and interface choices. To have your data deleted, write to privacy@sapio.network.

Who is responsible

Velvoe Labs AB (company registration number 559592-8853, registered office in Stockholm), Sweden, operates sapio.network, the Sapio waitlist and the Sapio testnet apps at alpha.sapio.network, app.sapio.network and quick.sapio.network, and is the controller of the personal data described in this policy.

Contact: privacy@sapio.network

The website and the waitlist

WhatWhyLegal basis (GDPR)
Your email address, and your Discord handle if you give itTo keep the waitlist, confirm your sign-up, invite you to test Sapio, and send you updates and news about SapioYour consent, Art. 6(1)(a)
That you consented, and when you signed upTo be able to show that we have your consentLegal obligation, Art. 6(1)(c)
The link parameters you arrived with, for example a campaign tagTo see which channels bring people to the waitlistLegitimate interest, Art. 6(1)(f)
Usage data: pages viewed, referring site, browser, operating system, device type and countryTo understand in aggregate how the website is used, and to improve itLegitimate interest, Art. 6(1)(f)
Server logs: IP address, time and requested pageTo run and secure the websiteLegitimate interest, Art. 6(1)(f)

The testnet apps

WhatWhyLegal basis (GDPR)
Your wallet address and your testnet activity: stakes, positions, claims, deliveries and the test tokens you receiveTo run the testnet competitions you take part inProviding the service you use, Art. 6(1)(b)
If you request access: your wallet address, and the handle and contact channel you give usTo give you access and send you test tokensProviding the service you use, Art. 6(1)(b)
If you register with an invite: the email address the invite was sent to, the one-time codes we send there, and the wallet address you registerTo check that the invite reached you, then approve that address and send it test gasProviding the service you use, Art. 6(1)(b)
If you publish a profile: the name, description, website and picture you chooseTo show your profile publicly, for example on the leaderboardYour consent, Art. 6(1)(a)
Crash reports: error type, app version, the page (without wallet addresses), network and browser typeTo find and fix errorsLegitimate interest, Art. 6(1)(f)
Server logs: IP address, time and requested pageTo run and secure the appsLegitimate interest, Art. 6(1)(f)

When you request alpha access, we check a signed wallet message and a Cloudflare Turnstile result. Our access database stores your wallet address, the handle and contact channel you give us, a request number, the request time, the check results and the request status. It also stores review actions, the reviewer's team email and Google account identifier, transaction hashes, errors and an audit history. For test-ETH top-ups, it records the amount, status, transaction hash and team member who sent them. These records let the team review requests and check what happened if a transaction fails.

Invite records contain an invite ID, the email address the team sends it to, the label the team gives it, who created or revoked it, and creation, expiry and revocation times where set. We also keep the status and attempts of team notification emails.

When you register with an invite, we send a one-time code to the email address the invite was sent to, using Resend, and check a Cloudflare Turnstile result. We never store the code itself, only a keyed hash of it, with its times and the number of checks. When the code is right, we record the address you chose and how: your connected wallet, which signs a message, or an address you enter, such as your agent's. We then approve that address on the testnet chain and send it test gas. The access database keeps the registration's status, times, any problem and the transaction hashes. An invite registers one address, and that address is public on the chain like any other.

To limit abuse, the apps also keep some IP addresses in memory only, never on disk or in logs: the time of the last access request from each address until the app restarts, failed password attempts for a minute, and registration code requests and checks for about ten minutes.

Testnet activity is public. We run the testnet chains, but anyone can read them through the apps' public interfaces, so wallet addresses and activity on them are visible to everyone. An invite limits who can view the alpha app; it does not make chain data private. Records on a chain cannot be changed or deleted one by one. Before its public launch, the alpha chain may be reset once, which erases its earlier records; after the launch it has no planned reset. Test tokens have no value.

Profiles can be edited or hidden in the app at any time, and we delete them on request. Pictures are published exactly as uploaded, so remove any location data from a photo before you upload it.

We do not sell personal data, and we do not use it to make automated decisions about you. The waitlist and the apps are not intended for children under 16.

Cookies and storage on your device

Website: no cookies and no other storage. Our analytics, Vercel Web Analytics, runs without them, so no identifier follows you from one visit to the next. Fonts, images and video are served from the website itself.

Testnet apps: only what the apps need to work. On password-protected testnets, a sign-in cookie holds an expiry time. On the invite-only alpha, a signed viewing cookie contains the invite ID and its issue and expiry times. It lasts for 180 days. The app checks whether the invite is still active, so revocation or invite expiry can end access earlier.

Team sign-in uses a short-lived login cookie and a one-hour session cookie containing the team email and Google account identifier. The apps also store your wallet connection (the connected address and network), the session data of the wallet libraries, and interface choices such as the colour theme. This lets the connection and your choices survive a reload. Nothing is used for tracking or advertising, and crash reports are sent without cookies or identifiers.

Who processes the data

We use service providers that process personal data on our behalf, under data processing agreements:

  • Vercel Inc., USA: website hosting and web analytics
  • Neon Inc., USA: the waitlist database, hosted in the United States
  • Resend Inc., USA: sending waitlist confirmation emails, alpha invites, the one-time codes for registering with an invite, and access-request notifications to the Sapio team. A code email contains only the code and how long it is valid. The notification text contains the request number, a shortened wallet address and a link to the access board.
  • Railway Corporation, USA: hosting the testnet apps and their servers and databases
  • PostHog Inc.: crash reports from the testnet apps, hosted in the EU (Frankfurt), with IP addresses discarded

Cloudflare Turnstile checks for automated abuse when you request access or ask for a registration code. Your browser connects to Cloudflare. Our server sends it the verification token and, when available, your IP address to check the result. Google verifies team members' accounts when they sign in to the access board; the app receives their verified email and Google account identifier.

The testnet apps also rely on services that handle data under their own terms:

  • WalletConnect (Reown, Inc., USA): connecting wallets. Its library contacts Reown's servers when the app opens.
  • The wallet you choose, for example MetaMask or Coinbase Wallet, and its connection service, when you connect it.
  • CoinGecko: some token images are loaded from its image service.

We may also disclose personal data where the law requires it.

Transfers outside the EU/EEA

Several of these providers are based in the United States, and the waitlist database is stored there. These transfers are protected by the European Commission's Standard Contractual Clauses or, where the provider is certified, the EU–US Data Privacy Framework.

How long we keep it

  • Waitlist details (email, Discord handle, consent record and link parameters): until you withdraw your consent or ask us to delete them, or until the waitlist closes, whichever comes first.
  • Testnet chain records: for as long as that testnet runs. App restarts do not erase them. The alpha may be reset once before its public launch and has no planned reset after it.
  • Profiles: until you ask us to delete them, or the testnet ends.
  • Registration codes: unused ones are deleted 24 hours after they were made. The one used to register is kept, as a keyed hash, with the registration.
  • Access requests, reviews, audit history, invites, registrations, notifications and gas top-up records: stored in our access database. They survive app restarts. The app does not delete them automatically when a request is rejected, an invite is revoked or a cookie expires.
  • Server logs: kept for a short period by our hosting providers, in line with their standard retention.
  • Usage data and crash reports: used only in aggregate or to fix errors, and deleted when no longer needed for that purpose.

Your rights

You have the right to access the personal data we hold about you, to have it corrected or deleted, to restrict or object to its processing, and to receive it in a portable format. You can withdraw your consent at any time; this does not affect processing that took place before you withdrew it. Records on a testnet chain cannot be erased individually.

To use any of these rights, write to privacy@sapio.network. We reply within one month.

If you believe we handle your personal data incorrectly, you can lodge a complaint with the Swedish Authority for Privacy Protection (Integritetsskyddsmyndigheten, imy.se).

Changes

If we change how we handle personal data, we will update this page and the date above.