Privacy

Last updated 8 November 2026

Railvo is payment software for merchants. It creates payment requests and checkout pages, watches the merchant’s own provider accounts for incoming payments and keeps an exact record of them. It never holds anyone’s money. Railvo is in a closed pilot: only invited merchants can sign in. It has no ads, no analytics and no tracking.

Who is responsible

Mitil runs Railvo and decides how merchants’ account data is used (the GDPR “controller”). Contact: info@mitil.ai; website: mitil.ai.

When you pay a merchant through Railvo, that merchant is responsible for your data, and Railvo processes it for them, on their instructions (as their “processor”). Questions about a payment are best sent to the merchant first.

Merchants

When you use Railvo as a merchant, it keeps:

• Sign-in details. Your email address. If you sign in with Google, Google gives Railvo your Google account ID, email address and name. Railvo emails you one-time sign-in codes and links, and keeps only a one-way fingerprint of each. To limit abuse, it keeps the network address each sign-in email was requested from (for IPv6, only its /64 network).
• Your sessions. When each one started and was last used, and a rough description of its browser, such as “Firefox on Linux”, so you can see your sessions and end them.
• Your merchant profile and stores. Whether you sell as an individual or a business, your stores’ names and branding, and your payment settings.
• Provider connections. The API keys you give Railvo for your accounts at providers such as Bitfinex, Binance, Narvi and Checkout.com. They are stored encrypted and never shown again. Railvo uses them only to read your balances and transactions, to start card payments and, if you turn conversion on, to place orders on your exchange account. Railvo never asks for permission to withdraw.
• Railvo API keys. Railvo shows a new key once and then keeps only a one-way fingerprint of it.
• An audit record of sensitive actions in your account: what was done, by whom and when.

Customers who pay a merchant

For each payment, Railvo keeps:

• The payment request the merchant created: amount, description, expiry, and any customer name or reference the merchant added.
• Evidence of the payment from the merchant’s own accounts. For Lightning, the invoice and its payment hash. For bitcoin, the address and the transaction ID, which are public on the blockchain. For bank transfers, the payer’s name, account number and payment reference as the bank reports them. For cards, the payment’s status and reference from Checkout.com.

Card numbers are typed into Checkout.com’s own payment form, which runs inside the checkout page; Railvo never sees them. That form belongs to Checkout.com, and it may collect information about your device to prevent fraud.

Cookies and your device

When you start to sign in, Railvo’s merchant app sets a session cookie, so that the sign-in can only be finished in the same browser. Until you are signed in, the cookie lasts until you close the browser; after that, for up to 7 days. If you sign in with Google, a second cookie protects that sign-in for 10 minutes. Both names start with __Host-, and page scripts can’t read them. A session ends after 12 hours without use, after 7 days at most, or when you sign out. The checkout page sets no cookies of its own. These pages on railvo.app set no cookies and load nothing from other sites.

On our servers

Railvo runs on its operator’s own server in the Czech Republic, behind Cloudflare. Like any website, it receives your IP address with each request, and uses it to answer the request and to limit abuse. Its logs record technical events, such as each request’s type, result and timing, and never contain secrets or card numbers.

Who else processes data

• Cloudflare carries all traffic to Railvo and sends its emails.
• Google handles sign-in if you choose it, under its own privacy policy.
• Checkout.com processes card payments.
• The merchant’s providers, such as Bitfinex, Binance, Narvi and Checkout.com, hold the merchant’s money and records under the merchant’s own agreements with them. Railvo reads from them and acts on them for the merchant.

Cloudflare and Google are US companies and Checkout.com is based in the UK, so data they handle may be processed outside the EU, under the safeguards in their data-protection terms.

How long data is kept

• Sign-in attempts, with the fingerprints of their codes and links: a day after they are used or expire.
• Google sign-in attempts: a day.
• Network addresses of sign-in email requests: a day.
• Sessions: a session ends when you sign out, after 12 hours without use, or after 7 days, and its record is deleted 7 days after it ends.
• Logs: 30 days.
• Raw responses from providers: 90 days. The payment facts Railvo takes from them stay with the financial records.
• Exports you download: 7 days.
• Merchant accounts and financial records (payment requests, payments, the ledger and the audit record): until the merchant asks Railvo to delete them, except for what the law requires to be kept longer.

Deletion runs every hour, so data can stay a little longer than listed here, and longer while the service is down.

Why we may use it

Railvo keeps merchants’ accounts, connections and records to provide the service they signed up for. It processes customers’ payment data on the merchant’s instructions. Logs, abuse limits and the audit record rely on our legitimate interest in a secure, working service. Some financial records may have to be kept by law.

Your rights

You can ask for access to your data, for its correction or deletion, or for a copy to take elsewhere, and you can object to or restrict its use. Write to info@mitil.ai and we’ll reply within a month. If you paid a merchant, we’ll handle your request together with that merchant. You can also complain to the Czech data protection authority, Úřad pro ochranu osobních údajů (uoou.gov.cz).

Changes

We’ll update this page and its date when anything here changes, and email merchants about changes that affect them.