Cookies Policy

Sowee sets no cookies of its own. There is no analytics service, no advertising tag, no tracking pixel and no third-party script that follows you between sites. This page describes the small amount the site does keep in your browser, and what the identity step brings with it.

What Sowee stores on your device

One thing, and only after you connect a wallet. The wallet library the app uses (wagmi) writes a couple of entries to localStorage — wagmi.store and wagmi.recentConnectorId — recording which browser wallet you connected and which chain you were on, so that a page reload does not drop the connection.

That entry is first-party, stays on your device, is never sent to our servers and is never read by anyone else. It holds no personal data — a connector name, a chain id and your wallet address, which is public anyway.

What Sowee does not store

• No cookies at all. The site sets no Set-Cookie header and writes no document.cookie.
• No session identifier. The API authenticates a request by a signature from your wallet that you send with it, not by a session held in your browser.
• Nothing about the identity check. Your name, documents and answers are never written into browser storage by this site.
• Fonts are served from this site, not fetched from a font CDN, so loading a page contacts no third party.

The identity step loads a third-party widget

When you reach the identity step of the onboarding wizard, the page loads the Sumsub WebSDK script from static.sumsub.com, and that script mounts an iframe served from Sumsub. Anything Sumsub stores inside its own frame — cookies or otherwise — is set by Sumsub, under Sumsub's policy. We do not control it, cannot read it and cannot clear it for you. It only loads if you open that step.

The World Selfie Check step, when it is enabled, uses World's IDKit. As of this revision IDKit writes nothing to browser storage, and the step is not yet exercised end to end because access to the feature is still pending from World.

What you can do about it

• Clearing site data in your browser removes the wallet entry. The only effect is that the site forgets which wallet you had connected, and you reconnect on the next visit.
• Blocking third-party storage or scripts is fine for the rest of the site, but the identity step will not work without Sumsub's widget.
• Your wallet extension keeps its own storage under its own policy, which nothing here can change.

Why there is no cookie banner

A consent banner asks permission for storage that is not needed to run the site. There is none here: no cookies at all, and one local entry that exists only because you connected a wallet. If that ever changes, this page changes before the code ships.

What happens to data that leaves your browser is covered in the Privacy Policy.