Privacy Policy

Last updated: July 21, 2026

This policy explains what personal data Limva (“we”) collects on limva.io and related services, why we collect it, and how long we keep it. Limva is an early-stage service; the legal entity is in the process of being established. Until then, “Limva” refers to the operators of this website.

What we collect

Early access form: name, work email, company, role, and the project description you submit. We collect nothing else through the form — no hidden fields.

Checkout sessions (for studios integrating Limva): the item, the amount, the payment status, the wallet addresses involved, and any order metadata the studio chooses to send us — typically its own player or order identifier. That metadata is passed straight back to the studio’s server and is never written on-chain. Studios decide what to put in it and are the controller for that data; we process it on their behalf.

Technical logs: our hosting providers record standard server logs (IP address, user agent, request time) to operate and secure the service. We do not run advertising trackers or third-party analytics on this site.

Why we collect it

To reply to your early access request, evaluate fit, and onboard your studio. Legal basis: your consent (you submit the form) and our legitimate interest in responding to inbound requests. We do not sell personal data and we do not use it for advertising.

How long we keep it

Form submissions are kept while your request is active and for up to 12 months after our last contact, then deleted. You can ask us to delete your data earlier at any time.

Checkout session records are kept for as long as the studio’s integration is active, so that both sides can reconcile payments, and are deleted on the studio’s instruction.

Where it is processed

The website is hosted on Vercel, the API on Railway, and DNS is provided by Cloudflare. These providers process technical data on our behalf under their own data processing terms.

On-chain data

Payments made through Limva checkout happen on public networks. A transaction carries the payer’s wallet address, the recipient addresses, the amount, and a timestamp. Those records are public by the nature of the network, are not controlled by Limva, and cannot be edited or deleted by anyone, including us.

We keep personal data off the chain by design. No player identifier, email address, account ID, or other personal data is written into a transaction, into transaction metadata, or into a split contract. Order data a studio passes to us (for example a player ID used to credit an item) stays in our off-chain database and is delivered to that studio’s server by webhook. This follows the approach set out in EDPB Guidelines 02/2025 on personal data in blockchains: keep it off-chain in the first place, because on-chain records cannot be erased.

A wallet address is treated as personal data whenever it can be linked to an identifiable person — for example, when a studio associates it with a player account. Where such a link exists in our systems, erasure is carried out by deleting the off-chain link and the associated records; the public transaction itself remains on the network and stays outside anyone’s control.

Your rights

Under the GDPR you can request access to, correction of, or deletion of your personal data, and you can withdraw consent at any time. To exercise any of these rights, contact us via the contact form — mention “privacy request” in the message.