In short
Gridlap is a free fan project: the @gridlap_bot bot, a Mini App in Telegram, the gridlap.club website and the Gridlap app for iPhone and Android. This policy explains what we do with your data. You don’t have to accept it: the rules you accept are the terms of use.
- The controller of your data is Private Unitary Enterprise ‘Naladim-studiya’ (ChP ‘Naladim-studiya’), Republic of Belarus, UNP 194052034; registered office: ul. Leshchinskogo 33, korp. 2, kv. 69, 220140 Minsk, Belarus; email: owner@naladim.by. ChP ‘Naladim-studiya’ also develops Gridlap: it writes the software and runs the server.
- We keep what Gridlap can’t work without: who you are on Telegram (or, in the app, the phone’s guest account), your settings and what you do in games, predictions and ratings.
- We don’t sell data and there are no third-party ads; we only write to you about Gridlap itself if you switched on ‘News and announcements’ or ‘Back to the puzzles’ yourself. The server and its backups are in Belarus. We share data with Telegram (the bot and sign-in run through it), with Yandex – only if you switched on Metrica or Webvisor on the website – and with Apple, if you switched on the session card in the app. The AI assistant Claude (Anthropic) reviewing our log gets information without IP addresses, numbers, names, usernames or personal codes.
- We count website visits with our own counter without cookies: it stores neither your IP address nor your browser, and once the day is over its day fingerprint can’t be linked to anyone.
- To fend off attacks and tell people from robots, the server keeps a request log for 14 days – with the IP address minus its last number, not the full address. The web server’s failure records live for the same 14 days – also without the full IP address and without the browser.
- You have the right to know what we keep about you, to correct it, to delete it and to withdraw consent. You can delete your account at any time: in the app with a button, straight away; in the bot, the Mini App and on the website through support, within 15 days.
- Gridlap is for people aged 16 and over; if you’re younger – only with the permission of a parent or another legal guardian.
Who is responsible for your data
The controller (in Belarusian law, the operator) of Gridlap’s personal data is Private Unitary Enterprise ‘Naladim-studiya’ (ChP ‘Naladim-studiya’), Republic of Belarus, UNP 194052034; registered office: ul. Leshchinskogo 33, korp. 2, kv. 69, 220140 Minsk, Belarus; email: owner@naladim.by. The controller decides why and how the data is processed and is responsible for it by law. ChP ‘Naladim-studiya’ also develops Gridlap: it writes the software, ships it to the server and runs the server.
At ChP ‘Naladim-studiya’, the person responsible for internal oversight of personal data processing is its director. For questions about data, write to owner@naladim.by or use ‘Account → Report a problem’ in the Mini App, topic ‘Data’.
Until 26 October 2026 Gridlap was run by its owner as a private individual; now your contract is with ChP ‘Naladim-studiya’, and the new terms of use need to be accepted. If you don’t accept them by 25 December 2026, we’ll delete your account.
The Gridlap server and the database backups are in Belarus, with the hosting provider CloudVPS (Edinye resheniya LLC).
Why, on what legal basis and for how long
Each purpose has its own row: whose data it is, what data, on which legal basis we process it and how long we keep it. The bases come from Articles 6 and 5 of Law of the Republic of Belarus No. 99-Z ‘On Personal Data Protection’. Where the basis is the contract, we don’t ask for separate consent: this data is needed for Gridlap to work as the terms of use promise. People who open the website without an account have no contract with us – for them the row names its own basis.
Account and sign-in
- Whose data
- Users of the bot, the Mini App, the website and the app
- What data
- From Telegram: account number, first and last name, username, language. For an app guest – the installation number and the fingerprint of the device secret. Sign-in sessions: where you signed in (website, Mini App, app), browser or system, app version and build, time of the last sign-in. Which version of the terms you accepted and when
- Legal basis
- Contract – the Gridlap user agreement (Article 6, paragraph 15 of Law No. 99-Z)
- How long
- While the account exists. Website sign-in requests – 30 days. Website sessions – 30 days after they end
Profile, games, predictions, leagues, Laps, achievements
- Whose data
- Users
- What data
- Your own name, @username, helmet avatar and cosmetics; results of games and daily puzzles, predictions, bingo, prediction leagues, level, XP, streaks, achievements, Laps and what you bought with them, ‘My Season’; the days you visited and during which sessions Gridlap was open
- Legal basis
- Contract – the Gridlap user agreement (Article 6, paragraph 15 of Law No. 99-Z)
- How long
- While the account exists
Friends, communities, weekly leagues, ‘Nudge’
- Whose data
- Users and their friends
- What data
- Friend requests and friendships, shared streaks and tasks, ‘Nudge’ reminders; community membership, role and requests; your weekly league group and your XP in it
- Legal basis
- Contract – the Gridlap user agreement (Article 6, paragraph 15 of Law No. 99-Z)
- How long
- While both your and your friend’s accounts exist
The reward for inviting friends
- Whose data
- Users who invited a friend with their personal link, and new players who accepted it
- What data
- Who invited whom and when – a record appears only if you accepted someone’s friend link as a new player (an account no older than 3 days, signed in with Telegram, Apple or Google) and while Gridlap runs the reward. Whether the invited player has got going – how many days old their account is, how many daily puzzles they’ve finished, whether they’re banned or marked ‘cheater’ – the server works out from their account each time and doesn’t store separately. The Laps paid for an invited player are a row in the Laps log of the person who invited them. So that Laps aren’t paid twice for one person – for example, if they delete their account and create a new one – the record and that row keep, instead of the invited player’s number, a fingerprint of their sign-in: a tag computed from the Telegram number (or the Apple or Google sign-in) with the server’s secret key; it doesn’t reveal the number, it only shows that the same person came back
- Legal basis
- Contract – the Gridlap user agreement (Article 6, paragraph 15 of Law No. 99-Z)
- How long
- The ‘who invited whom’ record – while both accounts exist: if either is deleted, so is the record. The Laps for an invited player – while the inviter’s account exists; if the invited player deletes their account, that row keeps the amount, the date and the fingerprint of their sign-in, and 2 years after the payment we erase the fingerprint too
Race ratings and reviews, ‘Driver of the Day’, polls
- Whose data
- Users
- What data
- Rating of a round, review text, likes, votes
- Legal basis
- Contract – the Gridlap user agreement (Article 6, paragraph 15 of Law No. 99-Z)
- How long
- A review – until you remove its text (while ratings are open) or delete your account. A review hidden by moderation is shown to no one but is kept while the author’s account exists: moderation can put it back in the feed. Votes and likes – while the account exists; vote totals are kept without people
Reminders and notifications you switched on
- Whose data
- Users
- What data
- Time zone, language, how many minutes ahead to remind you, notification topics, session types, favourite drivers and team; which messages we sent and when; whether the bot is blocked
- Legal basis
- Contract – the Gridlap user agreement (Article 6, paragraph 15 of Law No. 99-Z)
- How long
- While the account exists
Calendar through a personal link
- Whose data
- Users who subscribed to the calendar
- What data
- A fingerprint of the personal link (the link itself isn’t stored), the chosen session groups, how far ahead to remind you
- Legal basis
- Contract – the Gridlap user agreement (Article 6, paragraph 15 of Law No. 99-Z)
- How long
- Until you change the link or delete your account
The ‘Session’ card on the iPhone lock screen (Live Activity)
- Whose data
- App users who switched it on
- What data
- Installation number, Apple tokens for pushes and the card, iOS version, language, time zone, the ‘follow every race’ choice
- Legal basis
- Contract – the Gridlap user agreement (Article 6, paragraph 15 of Law No. 99-Z)
- How long
- While the installation is linked to the account; signing out stops the token, deleting the account deletes it
Support
- Whose data
- Users; people who write by email; other people mentioned in a request
- What data
- Text and topic of the request, the technical note (app version, platform, time zone), our replies; in emails – the email address, name and text
- Legal basis
- For users – the contract (Article 6, paragraph 15). For requests about one’s own data – Law No. 99-Z itself, which obliges us to answer (Article 6, paragraph 20)
- How long
- Requests in the Mini App – while the account exists. Emails and data requests – 1 year after our reply
Moderation, reports, blocks, fair play
- Whose data
- Users and the people they report
- What data
- Who reported whom, the reason and the note; whom you blocked; moderation decisions and their reasons; the ‘cheater’ mark: for which days and by which rule it was set, its term and whether it was removed, and for it – your ‘Word’ games: the day, on which try it was solved, whether paid hints were used; for a banned person who deleted the account – the Telegram account number or, for an app guest, an encrypted fingerprint of the device key, and the reason for the ban
- Legal basis
- Contract – the Gridlap user agreement (Article 6, paragraph 15 of Law No. 99-Z)
- How long
- While the account exists. The ban memory after deletion – until the ban is lifted, but no longer than 3 years after deletion, then deleted: otherwise deleting the account would lift the ban
Protecting rights: messages with insults and threats
- Whose data
- Users who write insults to people, threats against people or Gridlap, or promises to attack the service to support or by email; threats of attacks – whoever they come from
- What data
- A copy of such messages and of our correspondence about them: the text, date, account number, name and @username in Gridlap and Telegram, the email address in emails. The director keeps it in Belarus, separately from the account; copies in the controller’s Telegram chat are deleted like other requests
- Legal basis
- For users – the contract (Article 6, paragraph 15): the terms, section ‘Support’, say that we keep such messages as evidence and pass them to a state authority on its lawful demand. Threats of attacks on the service, whoever they come from, – also the controller’s duty to protect the system where personal data is stored (Article 17 and Article 6, paragraph 20 of Law No. 99-Z)
- How long
- Messages received from 13 November 2026 – each for 3 years from the day it arrived, even if the account was deleted, then deleted. Messages received earlier – like other requests: in the Mini App – while the account exists, emails – 1 year after the reply
Protecting the service: request log and server records
- Whose data
- Everyone who opens the website, the Mini App and the app or writes to the bot
- What data
- Request log: time, page address, server response, browser string and hints, the site you came from, the IP address minus its last number and a fingerprint of the full address computed with the server’s secret key. Server records: events and errors, some with an account or chat number. Blocks of addresses that attack the service, the watchdog’s records of attacks and the counter of wrong admin passwords – with the address fingerprint and the address minus its last number
- Legal basis
- For users – the contract (Article 6, paragraph 15): the agreement says we protect the service and keep a log for that. For people who open the website without an account – the controller’s duty to protect personal data and the system it’s kept in against unauthorised access (Article 17 and Article 6, paragraph 20 of Law No. 99-Z)
- How long
- Request log – 14 days, server records – 60 days; neither goes into backups. An address block – for its term and 14 more days, the wrong-password counter – 14 days after the last attempt, a watchdog record of an attack – 60 days after the attack died down
Investigating failures and protecting the service: the web server’s failure records
- Whose data
- Everyone who opens the website, the Mini App and the app
- What data
- Only about requests the Caddy web server couldn’t complete (for example, while the Gridlap server restarts): time, page address without parameters, response code, what broke and the IP address minus its last number. The record has no browser string, no site you came from and no full IP address
- Legal basis
- The same as for the request log: for users – the contract (Article 6, paragraph 15), for people who open the website without an account – the controller’s duty to protect personal data and the system it’s kept in against unauthorised access (Article 17 and Article 6, paragraph 20 of Law No. 99-Z)
- How long
- 14 days – how long the server’s whole system log is kept; the records are not included in backups
Games on the website without signing in
- Whose data
- Website visitors who play without an account
- What data
- A random guest number – the number itself lives in your browser’s cookie, we keep only its fingerprint; daily puzzle games and the moves in them; for a short while – a fingerprint of the IP address computed with the server’s secret key
- Legal basis
- There is no contract with a guest. The address fingerprint protects the service against abuse, as with the log: so that thousands of guests aren’t created from one address (Article 17 and Article 6, paragraph 20 of Law No. 99-Z). The guest number is random, and once the fingerprint is wiped the games aren’t linked to anyone
- How long
- Games – 30 days after the last move; if you sign in, today’s games move to your account and the guest is deleted. The address fingerprint is wiped by the hourly clean-up – after about an hour, no longer than a day
Our own website visit counter: how many people open the website and how they differ from robots
- Whose data
- Website visitors
- What data
- Page address, referring site (name only), device type and a day fingerprint – your IP address and browser encrypted with a random key of the day. The key lives only in the server’s memory and is wiped the next day: after that the fingerprint can’t be linked to anyone, us included. The counter doesn’t store the IP address or the browser themselves
- Legal basis
- While the day key exists: for users – the contract (Article 6, paragraph 15), for others – the same protection of the service against robots as for the log (Article 17 and Article 6, paragraph 20). Once the day is over, the fingerprint is anonymous for good
- How long
- Day fingerprints – 35 days, then only totals without people remain
Where people came from (first touch)
- Whose data
- Users who came through one of our tagged links
- What data
- The link’s tag, where you arrived (bot or Mini App), when, and whether you were new
- Legal basis
- Contract – the Gridlap user agreement (Article 6, paragraph 15 of Law No. 99-Z)
- How long
- While the account exists
The ‘What should we improve in Gridlap?’ survey (gridlap.club/en/feedback)
- Whose data
- Everyone who sent the survey – with or without an account
- What data
- Answers to the survey questions (the options you picked, a score from 0 to 10 and texts), the page language, the date and a tag for where you came to the survey from (for example, ‘from a mailing’). The answer holds no account, IP address or browser. If you left a contact yourself – a Telegram @username or an email – it is kept with the answer and used only to follow up on it
- Legal basis
- Consent (Article 5 of Law No. 99-Z): you send the survey and the contact yourself, every field is optional, and the contact field says why it’s needed and how long it’s kept
- How long
- 2 years from the answer, then deleted. The answer isn’t linked to an account and isn’t deleted with one. We’ll delete an answer with a contact sooner if you ask and confirm the contact is yours; an answer without a contact isn’t linked to anyone, so it can’t be found to be deleted
Website statistics – Yandex Metrica
- Whose data
- Website visitors who pressed ‘Allow statistics’ or switched on ‘Statistics (Yandex Metrica)’
- What data
- _ym_* cookies, addresses of the pages you open, referrer, device and browser, IP address, website events as goals
- Legal basis
- Consent (Article 5 of Law No. 99-Z) – the ‘Allow statistics’ button or the ‘Statistics (Yandex Metrica)’ switch on the cookie banner
- How long
- Consent – 12 months, then we ask again. Cookie terms – in the cookie policy. Reports are in Gridlap’s Metrica account; Yandex doesn’t publish how long it keeps them there, so once Gridlap stops using Metrica we’ll delete the counter with all its data within 30 days
Webvisor – recording actions on a page
- Whose data
- Website visitors who separately switched on ‘Session recording (Webvisor)’
- What data
- Scrolling, clicks, mouse movement and taps on the page; input fields, names and usernames are masked
- Legal basis
- Separate consent (Article 5 of Law No. 99-Z) – only the separate ‘Session recording (Webvisor)’ switch on the cookie banner; the ‘Allow statistics’ button doesn’t switch it on
- How long
- Consent – 12 months, then we ask again. Recordings are in Gridlap’s Metrica account and are deleted together with the counter, like the statistics reports
Proving that consent to cookies was given
- Whose data
- Website visitors who made a choice on the cookie banner
- What data
- A receipt of the choice: a random number (also kept in your browser next to your choice), what was allowed, the banner version and when. It contains no name, IP address or browser
- Legal basis
- The controller’s duty to prove that consent was obtained (Article 5 and Article 6, paragraph 20 of Law No. 99-Z)
- How long
- 2 years from the choice, then deleted
Gridlap news and invitations to come back
- Whose data
- Users who switched these topics on themselves
- What data
- Telegram chat number, language, whether the ‘News and announcements’ and ‘Back to the puzzles’ topics are on; a consent log – when you switched a topic on or off, where and with which switch caption; which messages were sent
- Legal basis
- Consent (Article 5 of Law No. 99-Z): this is advertising for Gridlap, so only when you switch the topic on in the notification settings, and only from the age of 16
- How long
- Consent – 12 months from switching on: then the topic switches itself off, and you can switch it on again. Switch it off earlier and the messages stop straight away, no later than the next working day. The consent log – 2 years from each entry, deleted together with the account
Past Telegram Stars donations
- Whose data
- People who donated while Gridlap accepted donations
- What data
- Telegram account number, how many Stars, when, the Telegram payment number
- Legal basis
- A gift contract (Article 6, paragraph 15). We keep it to answer a claim or refund the Stars within the general limitation period (Article 197 of the Civil Code)
- How long
- 3 years from the payment date, then deleted. Gridlap doesn’t accept donations now
What we keep – in detail
This is about the bot, the Mini App and the website. What the iPhone and Android app keeps is in the next section.
- Your Telegram profile: account number, first and last name, username and language. Telegram passes them on when you open the bot or the Mini App and when you sign in on the website.
- Your Gridlap profile, if you filled it in: your own name, @username, helmet avatar, how long you’ve watched Formula 1, and which version of the terms you accepted and when.
- Settings: time zone, language, how many minutes ahead to remind you, time format, theme, favourite drivers and team, session types for reminders and which notification topics are on – session changes, session results, ‘Rate the race’, predictions, streak, achievements, ‘Back to the puzzles’, streaks with friends, leagues, the cup, communities and ‘News and announcements’. If you subscribed to the calendar – its settings and a fingerprint of the personal link.
- Who you blocked and who you reported – with the reason and the note, if you wrote one.
- What you do in Gridlap: game results, predictions and leagues, race ratings and reviews, votes for ‘Driver of the Day’ and in polls, achievements, friends, communities, Laps, ‘My Season’ cards.
- Support requests – what you wrote, the topic and the technical note the form attaches by itself: app version, platform and time zone.
- Past donations: how many Stars and when. Telegram handled the payment; we have no card details. Gridlap doesn’t accept money now.
- Service data: when you last visited (with the exact time), which messages we sent and whether the bot is blocked.
- If you first came to the bot or the Mini App through one of our tagged links – for example, from a Gridlap post on Threads or a button on gridlap.club – we note that first touch: the link’s tag (where it came from: which post or which place on the website – the footer, an article, a game and so on), where you arrived – the bot or the Mini App – when, and whether you were new to us. Signing in on the website through the bot also counts as such a touch – ‘from the sign-in page’ – but only if that was your first time in the bot. Only the first one: later links don’t change it. That’s how we learn which posts and pages bring people in.
- The days you opened the Mini App, visited the website signed in or wrote to the bot – just the day and where you were. Separately – during which sessions Gridlap was open while the session was running: the Mini App reports this every 5 minutes, with the exact time.
- If you accepted someone’s friend link as a new player – who invited you, when, and a fingerprint of your sign-in (it doesn’t reveal your Telegram number, but shows that Laps were already paid for you); if you invited a friend – whom and when, and how many Laps you got for them. Such a record appears only while Gridlap runs the reward for invited friends.
- The ‘What should we improve in Gridlap?’ survey (gridlap.club/en/feedback) is anonymous: the answer isn’t linked to your account, and neither your IP address nor your browser is written into it – only the answers, the page language, the date and a tag for where you came to the survey from. If you left a contact yourself (a Telegram @username or an email), it is kept with the answer for 2 years and used only to follow up on it. Sending the survey goes into the server’s technical log only as the time, the page address and the response code – without the answers, your IP address or your browser.
The iPhone and Android app
The Gridlap app has no sign-up and no Telegram sign-in: on first launch it creates a guest account for this phone by itself. Here’s what appears along the way:
- An installation number and a device secret – random, created by the app itself. Both live in the phone’s secure storage – on iPhone, the Keychain marked ‘this device only’ – so they don’t move to other phones. The secret is the key to the guest account: the server keeps only its encrypted fingerprint, from which the secret can’t be restored.
- The guest account on the server: its number, the installation number, the platform – iPhone or Android, the phone’s time zone (to show session times on your clock), the app version and build, the string the app introduces itself with, and when it last signed in.
- The days you opened the app – as with the Mini App: just the day and the platform.
- What you do in the app – the same as in the Mini App: username and helmet avatar, games and daily puzzles, predictions and leagues, friends, Laps and the cosmetics for them, level, achievements and streak, reports and blocks. Others see the same of it as described in ‘What others and your friends see’.
- Only on the phone, in the shared folder of the app and its widgets: favourite drivers and team, reminder settings and what the widgets show. None of it goes to the server.
- Reminders about sessions and daily puzzles are local notifications: the phone schedules them itself when you switch them on, without the server.
- The ‘Session’ card on the iPhone lock screen (Live Activity) – only if you switched it on. Then the app sends us Apple push tokens, the iOS version, language and time zone, and the server updates the card through Apple’s push service: it sends the session, time and phase. Switch the card off or sign out, and pushes to this phone stop.
- No tracking, no ads, no third-party SDKs: the app has no counters, analytics libraries or advertising identifiers, and we don’t track you in other apps or on websites. The app doesn’t ask for the camera, photos, contacts or location.
- The app shows the 3D track as a page of our website: opening it is counted by our own website visit counter like any other page, and Metrica doesn’t start there. The app’s requests to the server go into the same technical log as the website’s.
- You can delete your account in the app itself: ‘Account → Delete account’ – straight away (see ‘How to delete your data’). A guest account nobody has signed in to for 12 months we delete ourselves: its key lives only on the phone, and a lost account would otherwise be kept forever.
Formula 1 people in the reference
Gridlap has a Formula 1 reference and history since 1950. This is data about real people who don’t necessarily use Gridlap – and we are responsible for it as the controller too.
The Formula 1 reference and history: driver pages and tables since 1950, our biographies and articles, drawn portraits, games and race votes (‘Driver of the Day’, ratings)
- Whose data
- Formula 1 drivers – current and past, including those who have died; other Formula 1 people we write about
- What data
- First and last name (and the Russian spelling), code and number, sex, date of birth, for those who have died – date of death, place and country of birth, nationality, teams, results and statistics; our texts about the career; a drawn portrait in a closed helmet without a face; ‘Driver of the Day’ vote shares and fans’ average ratings
- Legal basis
- Previously published (publicly available) data – Article 6, paragraph 19 of Law No. 99-Z: career information that the drivers made public themselves or that was published with their consent. No consent is needed until the person asks us to stop
- Source
- The open f1db database (CC BY 4.0), Jolpica, OpenF1, official FIA and team publications, Wikidata (Russian spellings of names)
- Where we show it
- The gridlap.club website, the Mini App and the @gridlap_bot bot, the Gridlap app
- How long
- Until the person asks us to stop processing: after that we hide or delete their data within 15 days, and it leaves the backups within another 14 days
- About the health, injuries and illnesses of living people and about them being held legally liable, we write only what the person made public themselves. We don’t write about income; about family and where a person grew up or lives – only what they or their family made public themselves.
- How to ask us to hide data: a driver, their representative or a relative writes to owner@naladim.by – no Telegram account or electronic signature needed. Say who it’s about and what to hide; a representative also says how they confirm their authority. We reply within 15 days: we hide or delete the person’s data – the page, table rows, the portrait and mentions in our texts – and tell search engines about the removal, or explain why we refuse.
- We correct a mistake in data about a person within 15 days of being told about it.
Other people’s data in reviews, reports, requests and among friends
When someone writes about another person – in a review, a report, a support request or a ‘Nudge’ to a friend – we process that data too.
Race reviews, reports on players, support requests, friends and ‘Nudge’
- Whose data
- Gridlap players others write about; other people someone mentioned
- What data
- Username and name in Gridlap and what the author wrote about the person; among friends – the username and whether the friend solved the daily puzzle
- Legal basis
- For players – the user agreement (Article 6, paragraph 15). For others – Article 6, paragraph 19, only if the information is already lawfully public (for example, about drivers); anything else we delete as soon as we learn of it
- Source
- The author of the review, report or request
- How long
- A review – until the author removes it and while the author’s account exists; one hidden by moderation – not shown, for the same time; at the request of the person mentioned – deleted or hidden within 15 days. Reports and requests – while the author’s account exists; emails – 1 year after our reply; messages with insults and threats – from 13 November 2026, 3 years from the day the message arrived
- If someone wrote about you in Gridlap – even if you don’t use it – write to owner@naladim.by: we hide a disputed review straight away while we check and reply within 15 days. Untrue information that damages a person’s reputation we refute or delete no later than the day after the request, or explain the refusal in writing within 5 days.
What others and your friends see
Showing data to everyone is dissemination; showing it only to friends or members is provision. Both are part of how Gridlap works under the terms of use.
- Everyone: a race review – with your name (your own, if you set one, otherwise from Telegram), @username and avatar – in the Mini App, the app and on the website.
- Everyone signed in: name, @username, avatar and points in game tables, bingo and prediction leagues; in a league, members’ predictions become visible once entries close.
- Everyone signed in – a person’s card when they tap a name: name, @username, avatar, level, the badge, title and cover for Laps, and since which month you’ve been on Gridlap. It shows neither your Telegram account number nor your Telegram username.
- Everyone signed in – the ‘cheater’ badge next to the name while a mark for ‘Word’ lasts: 7 days from the moment the server set or extended it. A mark for games from 13 November 2026, while it lasts, also hides you from others in the game tables, the weekly league and the cup. The rule is in the terms: until 13 November 2026 – in the version of 26 October, section ‘Fair play’; from 13 November – section ‘The ‘cheater’ mark’.
- Everyone who opens a community: its name, motto, emblem and members with their roles.
- Everyone who has a link you shared yourself: an achievement card, ‘My Season’ and a friend invite (/f/<code>) – name, helmet and what you shared. These pages are closed to search engines.
- Friends only: name, @username, helmet, level, cosmetics, whether you solved today’s daily puzzle and your shared streak. ‘Nudge’ sends your friend a Telegram message with your name.
- Only the person who invited you – if you accepted their link as a new player, and while you’re friends: your name and how you’re getting going – how many of the daily puzzles the reward needs you’ve finished, whether the reward is waiting for your account’s age or for a ‘cheater’ mark to be lifted, and whether it has been paid. Remove them from your friends or block them, and you disappear from their list.
- Members of a weekly league group only: each other’s names, helmets and XP for the week. A community’s leader and helpers see your request to join and get a Telegram message about it.
- You can hide yourself from game tables in the Mini App settings – turn off ‘Show me on game leaderboards’.
- We don’t tell anyone that you blocked or reported them: a block only hides you from each other.
- Votes for ‘Driver of the Day’ and in polls are anonymous: only the overall shares are visible.
- There are no public profile pages for search engines.
Who sees your data inside Gridlap
In the admin panel the director of ChP ‘Naladim-studiya’ sees the list of Gridlap people: the Telegram and Gridlap profile, settings, activity days, games, ratings, requests, reports, who invited whom with a personal link and past donations, and for the app – installations, platforms, versions and builds; separately – survey answers, which aren’t linked to anyone. That’s needed to answer requests, handle reports and understand what people use. Nobody else has access to the admin panel.
A machine does three things by itself, without a person. First, it sets the ‘cheater’ mark for ‘Word’ for 7 days. It looks at on which days and on which try you solved it and whether you used paid hints. Until 13 November 2026 there is one rule – 3 game days in a row on the first try without paid hints – and during that time the mark is only a badge next to your name. From 13 November there is also a frequency rule: a mark if over a short period there are clearly more quick solves, on the first or second try without paid hints, than in fair play; games before 13 November don’t count for it. A mark for games from 13 November, while it lasts, also hides you from others in the game tables, the weekly league and the cup, and XP from the first of its days until its end doesn’t count towards leagues and your community; a mark for earlier games only stays a badge, XP earned before 13 November always counts, and your level and account don’t change. Second, it blocks, for a set term, an address the server is being attacked from. Third, it doesn’t save names, usernames, titles and reviews with swearing.
You can dispute any of these through support – then a person, the director, checks the decision. Until 13 November 2026 we hide the ‘cheater’ mark the day after your request and tell you the outcome of the check within 5 days. From 13 November the director checks the mark by hand against your games and within 5 days replies whether it is removed or kept and on which days and how many quick solves it was set for; the mark stays while it is checked – as in the terms, section ‘The ‘cheater’ mark’.
Our own website visit counter
We count how many people open the website ourselves – without cookies and without Yandex – so this counter works even if you didn’t switch on Metrica.
From each page you open we take its address, the site you came from (just its name, not the full address), the device type – phone, tablet or computer – and a fingerprint of the day: your IP address and browser encrypted together with a random key of the day. The key is kept only in the server’s memory and wiped the next day, so your visits on different days can’t be linked, and once the day is over the fingerprint can’t be linked to anyone – us included. This counter doesn’t store the IP address or the browser themselves. Robots are counted separately from people, and pages the browser preloads aren’t counted at all.
An open page also tells the counter – on our own site – that a browser opened it, and once the tab has been on screen for 15 seconds, that you stayed. The message carries only the page address: the counter marks the same day fingerprint with it and stores nothing in your browser. That’s how we tell people from programs that open pages without showing them to anyone.
Day fingerprints are kept for 35 days; after that only the totals remain: how many people and page views there were.
The same day fingerprint lets us count what people do on the website: tapping a link to the bot, a channel or the calendar or an article’s button into games or the calendar, starting a game from the games page, pressing ‘Open Telegram’ on the sign-in page; seeing a track in 3D, picking a view and staying in 3D for a minute; reading an article to the end; running a search – without the search text, only roughly how much was found: nothing, one to five, or more than five. Only the page, the event with its detail (where the button was, the track, the view, the article) and the number of people per day reach the database – no fingerprint, IP address or browser. That’s how we learn which articles and pages are useful.
If you opened the website through one of our links with a UTM tag – the address has utm_source and utm_campaign, as in a link from a Gridlap post on Threads – the counter remembers the tag until the end of the day and counts totals for it: how many people and visits it brought and how many of them went on to the bot or the Mini App. Only the tag and these daily totals reach the database – no fingerprint, IP address or browser.
The server’s technical log
Like any website, the Gridlap server keeps a request log: when a page was opened and which one, what the server answered and how fast, the browser string (every browser sends it to every site by itself), the browser’s short hints about its name and version (browsers send those to sites by themselves too) and the site you came from.
The IP address is never written to the log in full: we keep the address minus its last number (for example, 93.84.12.x) and a fingerprint of the full address computed with the server’s secret key – the watchdog uses it to block whoever attacks the site. Only the Gridlap server can restore the address from them, so this is personal data: it doesn’t leave the server, and Claude’s review doesn’t get it either.
The log is there to fend off attacks and password guessing, to tell people from robots and to investigate failures. It is kept for 14 days and is not included in backups. The controller sees it in the admin panel.
Separately, the server writes its own records – about jobs, mailings and errors; some of them carry an account or chat number so a failure for a specific person can be investigated. They are kept for 60 days and are not included in backups either.
In front of the Gridlap server runs the Caddy web server: it accepts secure connections and passes requests on to the server. Caddy keeps no separate log of visits to Gridlap, but when a request fails – for example, while the Gridlap server restarts – it notes that in the server’s system log: the time, the page address without parameters, the response code, what broke and the IP address minus its last number. The browser string, the site you came from and the full IP address are not in that record. These records are there to find the cause of a failure and to protect the service, on the same legal basis as the request log. The system log stays on the same server in Belarus and is kept for 14 days – a term that applies to the server’s whole system log; it is not included in backups and doesn’t leave the server, Claude’s review included.
Once a day the AI assistant Claude reviews the log for attacks and failures. It gets an extract without IP addresses or their fingerprints, without account numbers, names, usernames or email addresses, without personal codes in page addresses, without log row numbers and without the full browser string – only the browser’s name and version and the device type, with times rounded to the minute (see ‘Who we share data with’).
Yandex Metrica and Webvisor
The Yandex Metrica counter turns on only if you pressed ‘Allow statistics’ on the cookie banner or switched on ‘Statistics (Yandex Metrica)’, and Webvisor only if you separately switched on ‘Session recording (Webvisor)’: the ‘Allow statistics’ button doesn’t switch it on. If you pressed ‘Essential only’, the counter doesn’t start and nothing goes to Yandex.
If you allowed it, the counter sets its own cookies (_ym_uid, _ym_d and others) and collects statistics without names: which pages are opened, where people come from and on which devices.
Webvisor records how people use the pages – scrolling, clicks, mouse movement – so we can see where the site is awkward. It doesn’t record input fields, names or usernames on the page: they are masked.
The same events our own counter keeps (see the section above) – follow-through, signing in through the bot, 3D, finished articles, searches – go to Metrica as goals with the same details. A goal carries no search text, and Webvisor doesn’t record what you type into the search box; but the address of the search page, where the query is visible, reaches Metrica like the address of any page you open.
Yandex processes this data on our behalf; under its Metrica terms Yandex also uses aggregated data without people for its own purposes. Changed your mind? Press ‘Cookie settings’ at the bottom of the website’s pages and turn the switch off: the counter won’t start again and we’ll wipe its cookies on gridlap.club. Details are in the cookie policy.
There’s no Metrica in the bot or the Mini App. There we only note the days you visited – see ‘What we keep – in detail’.
Signing in on the website with the bot
When you sign in on the website, we note which browser the request came from (for example, ‘Chrome · Windows’), and not your IP address itself but its encrypted fingerprint – to limit the number of attempts. Sign-in requests are deleted after 30 days, and games without signing in once nobody has come back to them for 30 days.
You can sign out on the website in your account, and ‘Sign out everywhere’ is also in the Mini App settings and in the bot’s sign-in message.
Who processes data on our behalf
Processors handle data on our instructions and for our purposes. The controller is responsible to you for them.
- CloudVPS – Edinye resheniya LLC, Belarus: hosting of the Gridlap server, which holds the database and its backups. A data processing agreement under Article 7 of Law No. 99-Z – purposes, actions with the data, confidentiality and protection measures – has not been signed with CloudVPS yet: for now only the hosting contract applies.
- hb.by – TriInkom LLC, Belarus: mail hosting for the owner@naladim.by mailbox, which holds the emails you send us and our replies. As with CloudVPS, there is no data processing agreement under Article 7 of Law No. 99-Z with it yet.
- Yandex – Yandex LLC, 16 Lva Tolstogo St., Moscow 119021, Russia: Yandex Metrica and Webvisor, only if you switched them on. Yandex processes the data under its Metrica terms: they list the actions with the data, confidentiality and protection measures – under Russian law. For visitors to whom the GDPR applies, the party to these terms instead of Yandex LLC is Air Smart Advertising Solutions FZ-LLC (UAE).
Who we share data with and transfers abroad
The law allows transfers abroad to countries with an adequate level of personal data protection – the parties to Council of Europe Convention No. 108 and the countries of the Eurasian Economic Union. Russia is on this list; the USA and the UAE are not. We transfer data to countries outside the list only when it’s needed to perform the contract with you (Article 9 of Law No. 99-Z).
- Telegram – Telegram FZ-LLC, UAE; servers in different countries. The bot, the Mini App and website sign-in run through Telegram, so the server sends messages to you there – reminders, notifications, support replies, ‘Nudge’ with a friend’s name, community requests with the applicant’s name – and the bot forwards support requests from the Mini App and the app (name and text) to the controller’s chat; messages from the watchdog and Claude’s review arrive there without IP addresses. The basis is the contract: Gridlap works inside Telegram. The risk: it can’t be determined which country the data ends up in, and among the countries where Telegram has servers there are some where the law protects data less than in Belarus and there’s no authority to complain to. Telegram is an independent company and processes data under its own policy. Gridlap is also available without Telegram: the website without signing in, the Gridlap app with a guest account, and support by email.
- Yandex – Yandex LLC, Russia: website statistics and Webvisor, only if you switched them on. Russia is a country with adequate protection; the basis is your consent (see ‘Yandex Metrica and Webvisor’).
- Apple – Apple Inc., USA: only in the iPhone app, if you switched on the ‘Session’ card. The server sends Apple’s push service the device token and the card’s text – the session, time and phase. The basis is the contract: without it the feature you switched on doesn’t work. You install the app through the App Store or Google Play – what the stores collect themselves is under their own rules.
- A calendar you subscribed to yourself with a personal link – for example, Google Calendar (Google LLC, USA): it downloads the schedule of the chosen sessions and the reminders through the link by itself, with no name or number. The basis is the contract: you set up the subscription.
- Anthropic – once a day its AI assistant Claude reviews the server’s technical log (Anthropic PBC, USA) for attacks and failures. The extract contains times rounded to the minute, page addresses (with the personal codes of invitations and ‘Share’ links cut out, as well as people’s numbers and joining codes), server responses, the browser’s name and version, the device type and error records. That extract contains no Telegram account numbers or names, no IP addresses or their fingerprints and no full browser string, no usernames, email addresses or log row numbers. Anthropic doesn’t get the log itself and has nothing to link the extract to a person with.
- The error-reporting service (Sentry, Functional Software, Inc., USA) is not connected at the moment: error reports go nowhere. If we connect it, we’ll first add here exactly what is sent to it and how.
- Nobody else. The Formula 1 and weather data sources (OpenF1, f1db, Jolpica, MET Norway, OpenStreetMap) and search engines get only technical requests from our server and page addresses, with no data about you. We hand data to a state authority only on its lawful request.
Where and for how long
The data lives in a database on a server in Belarus (CloudVPS hosting). The database is backed up once a day, and the 14 latest copies are kept – also in Belarus.
The terms for each purpose are in the table ‘Why, on what legal basis and for how long’. In short: account data – while the account exists; an app guest account nobody has signed in to for 12 months we delete ourselves; sign-in requests – 30 days, games without signing in – 30 days after the last visit, the request log and the web server’s failure records – 14 days, server records – 60 days, address blocks – for their term and 14 more days, watchdog records of attacks – 60 days after the attack died down, day fingerprints of our own visit counter – 35 days, cookie banner receipts, the advertising consent log and survey answers – 2 years, the fingerprint of an invited friend who deleted their account in the Laps log – 2 years from the payment, records of past donations – 3 years from the payment date, the ban memory – no longer than 3 years after the account is deleted, a copy of messages with insults and threats – from 13 November 2026, each for 3 years from the day it arrived.
If Gridlap shuts down, we’ll delete all users’ data within 15 days of shutting down.
Your rights and how to use them
Under Law No. 99-Z (Articles 10–15) you have the right to:
- find out what data of yours we process, why, on what basis, who we share it with and how long we keep it – we reply within 5 working days, free of charge;
- correct inaccurate or outdated data – within 15 days; you can also change your name, username, avatar and settings yourself;
- find out who we shared your data with over the past year – within 15 days, free once per calendar year;
- demand that we stop processing and delete your data – within 15 days; if something can’t technically be deleted, we block that data and tell you within the same term;
- withdraw consent – where you gave it: Metrica and Webvisor in ‘Cookie settings’ at the bottom of the website’s pages, ‘News and announcements’ and ‘Back to the puzzles’ with the topic switch in the notification settings, a contact left in the survey with an email to owner@naladim.by; we stop processing based on consent within 15 days and messages no later than the next working day; what was done before the withdrawal remains lawful;
- complain about us to the National Personal Data Protection Center of the Republic of Belarus (cpd.by), and then to a court;
- if you are in the EU or the UK – also restrict processing, object to it and receive your data in a machine-readable form (we reply within a month), and complain to the supervisory authority of your country too.
How to submit a request
The law names two ways, and we accept both: a written request – a letter to the controller’s address in ‘Who is responsible for your data’ – or an electronic document with an electronic digital signature sent to owner@naladim.by. The request contains your full name, address, date of birth, what you demand and your signature; if we process your data without your consent (for example, you’re in the drivers’ reference), also your identification number or the number of your identity document. You can also withdraw consent the same way you gave it.
We also accept simpler requests – an email to owner@naladim.by or, in the Mini App, ‘Account → Report a problem’, topic ‘Data’. We handle them within the same terms. So that a stranger doesn’t get your data, we’ll ask you to confirm the account is yours – for example, by writing from that Telegram account.
How to delete your data
In the app: ‘Account → Delete account’. The account and everything linked to it are deleted straight away.
A Telegram account – the bot, the Mini App and the website – is deleted on request: open the @gridlap_bot Mini App – ‘Account → Report a problem’, topic ‘Data’; if your access is blocked, the same form is on the ‘Access blocked’ screen. Or write to owner@naladim.by. We’ll delete everything linked to your account within 15 days and reply when it’s done. Reviews are deleted together with the account.
What stays: records of past Stars donations – 3 years from the payment date, to answer a claim or refund the Stars; a record of the deletion itself with no name or number – it can’t identify a person; answers to the ‘What should we improve in Gridlap?’ survey – they aren’t linked to the account and are deleted after 2 years; if Laps were paid for you as an invited friend – the fingerprint of your sign-in in the Laps log of the person who invited you, for 2 years from the payment, so that Laps aren’t paid twice for one person; for an account blocked by moderation – the Telegram account number (for an app guest, a fingerprint of the device key) and the ban reason until the ban is lifted, but no longer than 3 years, so deleting doesn’t lift the ban; the bot’s messages in your Telegram chat – you delete those yourself; server records with an account or chat number – up to 60 days after they were written, the request log and the web server’s failure records – up to 14 days: they’re needed only to protect the service and investigate failures, and are deleted automatically; communities you created, if other members are in them – they live on with their name and motto, but without you. Copies of your requests that the bot forwarded to the controller’s Telegram chat are deleted by the controller within the same 15 days. A copy of messages with insults and threats stays: from 13 November 2026 the director keeps it in Belarus as evidence – each message for 3 years from the day it arrived (section ‘Why, on what legal basis and for how long’).
In backups the deleted data stays for up to 14 days: we use backups for nothing but restoring the database after a failure – that’s blocking under the law. After 14 days the backups are overwritten and the data is gone. If after a failure we ever have to restore the database from a backup made before your deletion, the deleted account comes back into the database: we’ll announce such a restore in the @gridlap channel and on the website, and the account will have to be deleted again – in the app with the button, otherwise through support. Details are on the ‘Account deletion’ page (gridlap.club/account-deletion).
You can turn reminders off in the settings, and if you block the bot, messages stop straight away.
Age
Gridlap is for people aged 16 and over. If you’re under 16, use Gridlap only with the permission of a parent or another legal guardian: by accepting the terms you confirm that you’re 16 or over or that a parent allowed it.
Consent to optional cookies (Metrica and Webvisor) and to the ‘News and announcements’ and ‘Back to the puzzles’ messages can only be given from the age of 16. If you’re younger, press ‘Essential only’ and don’t switch these topics on. In the app stores Gridlap is rated 13+ – that’s a content rating, not permission to use Gridlap without a parent.
How we protect data and what happens after a breach
The server and its backups are in Belarus; the website, the Mini App and the app use only secure connections (HTTPS). We keep the device secret, the calendar link and the IP addresses of website sign-ins as encrypted fingerprints, and in the request log and the web server’s failure records the address minus its last number. Only the director of ChP ‘Naladim-studiya’ signs in to the admin panel: every sign-in is confirmed in Telegram, or, if Telegram isn’t available, with a one-time code issued by the server itself.
If data leaks, is lost or is changed without our knowledge, we’ll report it to the National Personal Data Protection Center no later than 3 working days after we learn of it, and within the same term to the people whose data is affected: in the bot, in the app or by email.
If this policy changes
A new version means a new date at the top of the page. We’ll announce significant changes – new purposes, new recipients, transfers to new countries – in advance, at least 10 days ahead: in the bot with a service message, on the website and in the app. For new purposes based on consent we’ll ask for it separately.
We keep past versions: we’ll send any of them on request to owner@naladim.by.