Политика за поверителност

Тази политика е написана само на английски език.

Last updated 1 November 2026.

This policy explains what lite-type keeps about you, why, and what you can do about it. lite-type is run by a sole trader in the United Kingdom, who is the controller of your personal data; their name and postal address are on our contact page. You can reach us at info@mezlasoft.com.

In short

Google tells us an identifier for your Google account and nothing else: not your name, not your email address.
Your username is made up at random.
We keep your typing results so that you can see your progress and appear on the leaderboards.
The site shows ads from Google AdSense, which uses cookies. In the EEA, the UK and Switzerland they are personalised only if you consent, and you can change your choice at any time (Ads). Students and Ad-free accounts see no ads.
We count the visits our own ad links bring as totals, never per person (Links from our ads).
An educator's students are kept without names (Students, below).

Using lite-type without an account

You can use every page without signing in. Your lessons, results and daily goal are then kept in your browser's storage on your device, and never sent to us unless you sign in. The language you choose is kept in a cookie. On your first visit, our host uses the country your connection comes from to choose the site's language; it is not stored.

When you sign in

You sign in with Google, through Amazon Cognito. Google tells us a unique identifier for your Google account and nothing more. We then keep:

that identifier, a username we make up at random, and when the account was made;
your daily goal, if you set one;
your typing results: for each lesson its type, language and text, your speed, accuracy and time, and how you typed each key, with the statistics, best results and streaks worked out from them;
a session, so that you stay signed in, for up to 30 days.

When you sign in, the results kept on your device are moved to your account.

Ads pay for the free site. Google AdSense shows them on most pages; Settings, the Educator panel and students' pages have none. To choose, show and measure ads and to fight fraud, Google collects cookies or similar identifiers on your device, your IP address and the page you are on. Google is responsible for that data under its own privacy policy; we don't receive it. Google explains this on how Google uses information from sites that use its services.

In the EEA, the UK and Switzerland, Google asks on your first visit, before any ad cookie is set. "Consent" gives you personalised ads. "Do not consent" gives you non-personalised or limited ads, which Google chooses from the page and your rough location and which use fewer or no cookies.
In the US states with privacy laws that cover it, those laws count personalised ads as selling or sharing personal information. Google shows a "Do Not Sell or Share My Personal Information" link on the page; opting out there turns personalised ads off.
Elsewhere, Google may personalise ads. You can turn that off in Google's My Ad Center.

To change your choice, use "Privacy and cookie settings" at the bottom of any page with ads, or in the / menu. It shows wherever Google's consent message applies.

Students, Ad-free accounts and paying Educators see no ads, and for them the site loads nothing from Google: no ads, no cookies and no consent message.

Links from our ads

When we advertise lite-type elsewhere, the link in each ad carries a campaign tag in its address, such as ?ref=de-kids. The site reads the tag, takes it out of the address, and keeps it in the page's memory until you reload or close the page. Nothing is stored in your browser for it.

For each tag, each day and each language, we count the visits, the sign-ins (new and returning accounts), the Ad-free purchases, and the Educator trials and first payments it brought. These are totals: they name no one and keep no IP address, browser details or cookie. An account made during a visit from a tagged link keeps that tag, and an Educator subscription keeps the tag of the visit it was started from, so we can tell which ads bring people who stay. Students are never counted.

What other people can see

The leaderboards show your username next to your best scores, times, practice time and streaks. Nothing else about you is public.

Cookies and browser storage

Our own cookies and storage are only what the site needs to do what you ask of it, so we don't ask for consent to them:

__Host-session keeps you signed in, for 30 days or until you sign out.
__Host-oidc carries a sign-in from Google back to the site, for 10 minutes.
lang remembers the language you chose, for a year.
Your browser's storage keeps your results, lesson progress and daily goal while you are signed out, until you clear it.

Google's ad cookies are Google's own, set only on pages that show ads. Where the law requires consent, Google asks for it first (Ads).

Server logs and error reports

When your browser talks to our servers, our host records each request, including your IP address and your browser's details, in logs we keep for 30 days to keep the site secure and to find faults. When something goes wrong on our servers, an error report goes to GitLab, where we track and fix faults; it can include your account's identifier, but never what the request held or your IP address.

When something goes wrong in your browser, the site sends us an error report too, and it goes to GitLab in the same way. It holds the error's message and where in the site's code it happened, the address of the page without anything after a question mark, the page's language, the site's version and your browser's details. It holds nothing you typed and nothing about your account. GitLab keeps error reports for 90 days.

Purchases

Paid extras, such as Ad-free, are sold by Onelink, Stripe's merchant of record service. Onelink takes your payment details and handles them under its own privacy policy; we never see them. We keep only that your purchase was paid, when, and Stripe's reference for it, with your account. Stripe keeps its own record of the sale.

If you subscribe to Educator, we also keep with your account whether the subscription is paid, when it renews or ended, Stripe's references for it, your educator code, and which version of the Educator terms you agreed to and when.

Students

An educator who subscribes to Educator can make classes of student accounts. For the students' data, the educator, or the school they act for, is the controller, and we process it on their behalf as their processor: only to run their classes and only as they instruct us. For each student we keep:

their class, their seat's number, and an identifier we make for them, never a name;
their seat's password, if the class uses seat passwords;
an email address, only if the educator adds one, so the educator can send them their link, and whether an email to it bounced;
when they last signed in, and recent wrong passwords, to lock a seat after ten;
their typing results, daily goal and progress, as for any account, and their progress and results in each lesson the educator sets;
a session, so that they stay signed in, for up to 12 hours.

Students don't sign in with Google, never see ads and never appear on the leaderboards. Students may be under 13: their educator agrees to our Educator terms, which ask them to have the consent their school, the law or a parent requires. A student, or their parent or guardian, who wants to see, correct or delete their data should ask their educator; we help the educator answer, and pass on any request that reaches us.

Our Privacy for schools pages set this out for the educator's school in full, with the data processing agreement.

Removing a student's seat, or the educator deleting their account, deletes the student's data, usually within seconds. When an educator's subscription ends, their students can no longer sign in, and three months later their classes, students, emails and results are deleted.

Why we use your data

To give you the service you asked for (your account, results, leaderboards and purchases): this is necessary for our contract with you.
To keep the site secure, find faults, choose your language and learn which of our ads work: these are our legitimate interests, and they need very little about you.
To show ads that pay for the site: personalised ads in the EEA, the UK and Switzerland only with your consent, which you can withdraw at any time.
To keep records the law requires, such as tax records of purchases.

Who handles it for us

Amazon Web Services hosts the site, stores your data in Ireland and runs the sign-in.
Google signs you in; your Google account is covered by Google's own privacy policy.
Google AdSense shows the ads and asks for consent to them. For what it collects through them, Google is a controller in its own right (Ads, above).
GitLab receives the error reports.
Stripe and Onelink handle purchases.
Zoho hosts our email, if you write to us.

We share your data with no one else unless the law requires us to. Some of these providers process data outside the United Kingdom, for example in the United States; when they do, the transfer is covered by the UK's adequacy regulations or by the UK's approved data transfer agreements.

How long we keep it

Your account and results: until you delete your account. They are removed from our database at once, and from its backups within 35 days.
Students' data: until the educator removes the seat or deletes their account, or three months after their Educator subscription ends.
Server logs: 30 days.
Error reports: 90 days.
The totals counted per ad tag: they name no one, so we keep them. The tag an account or a subscription keeps goes with the account.
Emails you send us: as long as we need to answer them, and six years if they are about a purchase, for tax records.
What your browser keeps: until you clear it.

Deleting your account

Settings, then Delete account, removes your account, your results and your leaderboard entries. Results kept on your device stay there until you clear your browser's storage.

Your rights

You can ask for a copy of your data, to have it corrected or deleted, to restrict or object to how we use it, and to receive it in a form you can take elsewhere. Email info@mezlasoft.com; we answer within a month. Because we don't know your name or email address, we may ask you to show that the account is yours, for example by telling us the username Settings shows while you are signed in.

Complaints

If you are unhappy with how we use your data, tell us first at info@mezlasoft.com. We will acknowledge your complaint within 30 days, look into it and tell you the outcome. You can also complain to the Information Commissioner's Office at ico.org.uk or on 0303 123 1113.

Children

Anyone can use lite-type without an account. To make an account yourself you need to be 13 or older. Younger students can use lite-type in an educator's class, with the consent described in Students, above.

Changes to this policy

When this policy changes, the date at the top changes too. We will say so on the site before a change that matters takes effect, and ask for your consent first wherever the law requires it.