LoginLlama checks logins for signs of account takeover. This page says what personal data we handle, why, who else sees it, how long we keep it, and how you can use your rights.

1. Who we are

LoginLlama is run by Turbo Technologies Limited (company number 13124266), registered in England and Wales at 24 Brookside Business Park, Stone, Staffordshire, ST15 0RZ. In this policy, "we" and "us" mean that company.

For anything about your data, write to [email protected]. We have not appointed a data protection officer.

2. Our two roles

We are the controller for data about people who visit our website or hold a LoginLlama account. We decide what to collect about you and why.

We are a processor for the login data our customers send to the API about their own users. Our customer is the controller of that data. We use it only to provide the service, on their instructions, under the data processing terms. If you are one of their users, contact that company first. If you write to us, we will pass your request to them.

3. What we collect, why, and on what basis

3.1 Account holders

Account details: your name, email address, a hash of your password, your team and its members, and your two-factor settings. If you sign in with GitHub, we also get your GitHub name, email address and profile picture from GitHub. We use these to run your account. Basis: contract.
Your sign-ins to the dashboard: we check our own sign-ins with LoginLlama, so we store the IP address, browser and rough location of each one. We use these to protect your account. Basis: legitimate interests (keeping accounts safe).
Billing: on a paid plan, your billing name, email address, address and payment details go to Stripe. We keep the plan, invoices and payment status. Basis: contract, and legal obligation for tax records.
Email we send you: account email and alerts, a weekly summary, and a short series of tips after you sign up. The weekly summary has an unsubscribe link. To stop the tips, write to us. Basis: contract for account email and alerts; legitimate interests for the summary and tips.
Usage: which steps of sign-up and billing you have done, linked to your account id. We use this to see where people get stuck. Basis: legitimate interests (improving the product).
Support: what you send us by email. Basis: legitimate interests (answering you).

3.2 Website visitors

Request data: your IP address, browser and the page you asked for pass through Cloudflare and our servers. We use them to serve the page and to block attacks. Basis: legitimate interests (running a secure website).
Analytics: Google Analytics counts page views and sets a cookie to tell visits apart. We also store where you first came from (for example a search engine or a link) in a cookie, and attach it to your account if you sign up. We use both only to count how people find and use the site so we can improve it. Google handles the analytics data for us and does not use it for advertising. UK law lets us set these cookies without asking first on that condition. Basis: legitimate interests. To opt out, use the button below, install Google's opt-out add-on or block cookies for this site in your browser.
Analytics is on for this browser.
Free tools: if you use the IP lookup tool, we look up the address you enter. We do not store it.

3.3 Our customers' users

When a customer checks a login, they send us data about one of their users. We act as their processor. We receive:

the IP address and user agent of the login
an identity key, which is whatever id the customer chooses (often a user id or an email address)
an email address, if the customer sends one for alerts
whether the login succeeded

From these we work out the rough location (country, region, city), the network owner, the browser and device, and whether the address is a known VPN, Tor exit or hosting network. We look up location and network in databases on our own servers, with no outside call. We store each check with a risk score and the time. If the customer turns on alerts, we email their user about a suspicious login. If the customer sets a webhook, we send each result to the address they choose.

We use this data only to check logins for that customer. We do not sell it, use it for marketing, or share one customer's data with another.

4. Who else handles the data

We do not sell personal data. We use the companies below to run the service. The same list is on our subprocessors page.

Company	What for	What it gets	Where
Cloudflare	DNS, the tunnel that carries traffic to our servers, and the firewall in front of them. Also forwards email sent to @loginllama.app addresses.	Every request to the site and the API passes through it, including IP addresses, request headers and request bodies. Email sent to us.	United StatesEU-US Data Privacy Framework and its UK extension, or Standard Contractual Clauses
Resend	Sends email: sign-in and account email, login alerts, and product email. Resend delivers through Amazon SES.	Recipient email address and the content of the email. A login alert includes the time, location, browser and a small map of the login.	United StatesEU-US Data Privacy Framework and its UK extension, or Standard Contractual Clauses
Stripe	Takes payments and runs subscriptions.Only for customers on a paid plan.	Billing name, email address, address and payment details. Stripe holds the card; we never see the full number.	United StatesEU-US Data Privacy Framework and its UK extension, or Standard Contractual Clauses
Sentry	Error reports from the server and the browser, so we can fix faults.	Error details, the URL, browser and device, and the account id where there is one. Session replays of 10% of dashboard sessions and of every dashboard session with an error, with all text masked and all images blocked. Public pages are not recorded.	United StatesEU-US Data Privacy Framework and its UK extension, or Standard Contractual Clauses
Google Analytics	Counts visits to the website and the steps from sign-up to payment.	Pages viewed, referrer, browser, device, approximate location and a cookie id. For sign-up and billing events sent from our server, the account id.	United StatesEU-US Data Privacy Framework and its UK extension, or Standard Contractual Clauses
Backblaze	Stores encrypted nightly backups of the database.	A copy of everything in the database, encrypted before it leaves our servers. Backblaze cannot read it. Backups are kept for up to 6 months.	NetherlandsAdequacy decision (UK to EEA)
CARTO	Serves the map tiles on the dashboard login map.	The dashboard user's IP address and browser, and the map area in view.	United StatesStandard Contractual Clauses
OpenStreetMap Foundation	Map tiles for the small map in login alert email.	Our server fetches tiles for the area around a login (about city level). No IP address, email address or identity goes with the request.	United KingdomAdequacy decision (UK to EEA and EEA to UK)
Team Cymru	Network owner lookup for the free IP lookup tool.Only when someone uses the IP lookup tool. API login checks use a local database and send nothing.	The IP address a visitor types into the tool, sent as a DNS query.	United StatesStandard Contractual Clauses

The code also supports these, but we do not switch them on. We will add one to the table above before we do: Ahrefs analytics; Crisp chat; LogSnag; PostHog.

If you choose to sign in with GitHub, GitHub handles that sign-in under its own privacy policy. We may also share data when the law requires it, or with a buyer if the business is sold. This policy keeps applying to your data if that happens.

5. Where the data is, and transfers

We run LoginLlama on our own servers in the United Kingdom. The database, the cache and every login check are stored there. We do not use a cloud host for them.

Most companies in the table above are in the United States. When data goes to them from the UK or the EEA, we rely on the EU-US Data Privacy Framework and its UK extension where the company is certified, or on Standard Contractual Clauses with the UK addendum. Ask us at [email protected] for a copy of the safeguards.

6. How long we keep data

This is what the service does today.

Login checks: nothing deletes these on a schedule yet. We keep them while the customer's account is open, because the risk score is built from past logins. A customer can ask us to delete them at any time, and we delete them when the account closes.
Accounts: kept until you ask us to close your account. There is no delete button in the dashboard yet, so write to [email protected]. When someone leaves a team, we delete their membership.
Sign-in sessions: a session ends after seven days. The two-factor step ends after ten minutes.
Billing records: kept for as long as tax law requires.
Data at the companies above: kept under each company's own rules.

We keep login checks while the customer's account is open, because each new score compares a login against that history. We have not set a fixed limit yet, and will update this policy when we do. A customer can ask [email protected] to delete their login checks, or the checks for one of their users.

7. Your rights

Under UK and EU data protection law, you can ask us to:

give you a copy of your data
correct it
delete it
limit how we use it
stop using it where we rely on legitimate interests
send it to you or another company in a common format

Where we rely on your consent, you can withdraw it at any time. Write to [email protected]. We may ask you to prove who you are. We reply within one month. You can also complain to the data protection authority where you live or work.

If you live in California, you can also ask to know about, delete and correct your data. We do not sell or share personal data for advertising.

8. Cookies

We set these cookies:

Sign-in (better-auth.*): keeps you signed in to the dashboard. Needed for the service.
Two-factor (two_factor): holds the second sign-in step for ten minutes. Needed for the service.
Test mode (llama_test_mode): remembers whether the dashboard shows test data. One year.
First visit (ll_attribution): where you first came from. 90 days. We keep a copy in your browser's local storage too.
Google Analytics (_ga, _ga_*): tells visits apart. Set by Google.

Sentry may keep an id in your browser's session storage while it records a session replay. Stripe sets its own cookies on its checkout page. We do not use advertising cookies.

9. Security

All traffic is encrypted in transit. Row-level security in the database keeps each customer's data apart, so a query for one team cannot read another's. Teams can require two-factor sign-in for every member. If a breach affects your data, we will tell you and the regulator as the law requires.

10. Children

LoginLlama is a service for businesses. It is not meant for anyone under 18, and we do not knowingly collect data about children.

11. Changes

When we change this policy, we update the date at the top. If a change matters, we email account owners before it takes effect.

Privacy Policy