Lanitor

Privacy

Last updated 22 October 2026.

Lanitor is run from Lithuania. Write to hello@lanitor.dev about anything on this page. A person answers.

There are two kinds of people this page is about: customers, the teams that sign up and use the dashboard, and end users, the people our customers' apps ask us about before granting a free trial or credits. The rules differ, so they get separate sections.

If you are a customer

What we collect

Your email address, used to sign you in with a one-time link; we never see a password. The name of your workspace, which starts as your email's domain, or as the name part of your address on a personal mailbox, and which you can change. Which button on our site you signed up from and the ad campaign it came from, if any. The API keys you create, which we store only as hashes. Your entitlements and their settings. A count of decisions, for billing.

Billing is handled by Stripe. Stripe collects your card, billing address and VAT ID under its own privacy policy. We keep your Stripe customer and subscription identifiers, the subscription's status and period dates, and a short note about refunds, disputes or fraud warnings Stripe sends us.

Cookies on lanitor.dev

Signing in sets the session cookies the dashboard needs to know who you are. A small flag cookie remembers for 30 days that you have an account, so the front page offers your dashboard instead of a sign-up form. For ten minutes after you ask for a sign-in link, a cookie holds the address you typed so the next page can show it; it is never put in a URL. The code that connects your project to Lanitor is a one-time code that expires within an hour.

What we use it for

Running your account, billing you, and emailing you about your account: sign-in links, invoices and payment problems, and changes to the service or this page. There is no newsletter. We do not sell or share your details for advertising.

If you are an end user

You are reading this because an app you signed up for uses Lanitor to decide who gets its free trial or credits. That app is responsible for your data and should describe this in its own privacy policy. We process the data on its behalf and on its instructions, and we use it only to make decisions for that app. Apps' data is never combined to make decisions for another app.

What the app sends us

On the app's signup page, a small script creates a random visitor ID and keeps it in your browser's storage and in a cookie named lnt_vid for two years. It also computes a hash of a few stable browser traits: screen size, language, time zone and how your browser draws a short piece of text. The hash cannot be turned back into those traits, and it excludes your browser version so it does not change with updates. The script notes whether the browser is automated. We record your IP address when the script talks to us.

When the app asks for a decision, it sends the user ID it gave you and, usually, your email address. If the app uses it, it can also send a fingerprint of your payment method, which is an identifier Stripe or a similar provider derives from a card, never the card number itself. Later the app can tell us that you paid, or that it found abuse or confirmed you are fine.

What we do with it

We link your account to the device and network it came from and compare them with earlier signups at the same app: other accounts on the same device, email aliases of the same inbox, disposable email providers, how many accounts came from the same network recently, and whether a related account was marked as abuse. The result is a decision with reason codes, which the app sees in its dashboard. We send your IP address, and nothing else, to IPinfo to learn whether it belongs to a data centre or VPN; we cache that answer for 30 days.

We do not use your data to build profiles for anyone else, to advertise, or to train anything.

Your rights

Ask the app first; it can see and remove your records and tell us to do the same. You can also write to us directly and we will pass the request to the app and act on its instructions. Blocking the lnt_vid cookie or clearing your storage does not break the app's signup; the app simply gets a decision with less information.

Where everything is kept

The site and API run on Vercel. The database and sign-in service are hosted by Supabase in Frankfurt, Germany (EU). Sign-in and account emails are delivered through Resend. Billing data is at Stripe. Each of these processes data under a data processing agreement with us.

How long

Customer data stays for as long as the workspace exists, and is deleted within 30 days of the workspace being closed, except invoices and payment records, which tax law requires us to keep for 10 years. End-user data stays for as long as the customer's workspace exists, because decisions depend on history, or until the customer deletes it. Cached network lookups expire after 30 days. Records of unsuccessful sign-in attempts are not kept.

Analytics on this site

The front page and the sign-in page count visitors with Vercel Web Analytics, which uses no cookies. The front page also uses PostHog, hosted in the EU, to count page views and clicks. There is no session recording. Neither tool receives your email address or anything from the dashboard. If you would rather not be counted, a content blocker stops both.

The earlier waiting list

Before launch, the front page had a form to reserve a spot. Those addresses are in a database we run ourselves, are used for one email when access opens, and are deleted after that.

Removing your details

Customers: write to hello@lanitor.dev from your account's address and we close the workspace and delete it, along with its end-user data. You can also ask for a copy of what we hold. We answer within a month. If you are in the EU and think we have got something wrong, you can complain to the Lithuanian data protection authority, the State Data Protection Inspectorate.

Changes

When this page changes in a way that matters, we email customers and update the date at the top.