KalbodyarOpen the app

فارسی

Kalbodyar Privacy Policy

Last updated: 24 Aban 1405 SH (15 November 2026)

This is an English translation of the Persian original, provided for convenience; if the two differ, the Persian version prevails.

This page states exactly what the site keeps. The principle is to collect as little as possible: no advertising, no third-party trackers, no external fonts or libraries (the fonts and the 3D library are loaded from the site itself).

1. If you do not create an account

  • Guest cookie (lp_guest): a signed stamp that records when the browser first visited, so that guest access and the trial period work correctly. It lasts about one year and contains no personal information.
  • Anonymous usage statistics: to improve the site, simple events are recorded, such as a page being opened, the device class (mobile/tablet/desktop), the screen-width range, the connection type, the tab opened, the ID of the selected structure, the question number and whether the answer was right or wrong, and the number of results and the length of a search query (not the text itself). IP addresses are not stored in the events table. The visitor ID is an irreversible digest (HMAC) of that same guest cookie, not a name or a number. If you are signed in, your account ID is also kept internally alongside the event, but it is not shown in reports. Raw events are deleted after a while (180 days by default).
  • Browser storage (localStorage): practice progress, spaced review, the tours you have seen and appearance settings stay in your own browser and are not sent to us, except for the part described below for accounts.

2. If you create an account

  • Account details: username, display name (optional), your password hashed with a salt (scrypt; the password itself is not stored), and, if you sign in by SMS or register a contact number, your mobile number. The time the account was created, the last sign-in and the subscription/trial status are also kept.
  • Sign-in sessions: to keep you signed in, a random token is placed in the lp_session cookie; only its hash is stored in the database, together with the creation time, expiry, last visit, IP address and browser details (User-Agent), for security and abuse control.
  • Logged attempts: failed sign-ins and sign-ups (username and IP) and SMS code requests (number, IP and a hash of the code) are kept to prevent password guessing and mass sending.
  • Study days: the list of days on which you practised is synced with your account, to show your streak and for reminders.
  • Learning data: your answers (question ID, correct / partly correct / wrong, time), the state of your review cards (box, memory prediction and next review time), points (XP), daily goal, estimated level in each pack, results of exams and of the daily challenge, and «active study time» (the seconds during which the page was in front of you and you were working with it, per day and per pack). These are needed for smart review, the dashboard and the study plan.
  • Onboarding questions and exam plan (optional): the role you choose (for example basic-sciences student or teacher), preferred packs, language, and, if you create a plan, the exam's name and date and its units.
  • League and leaderboards: in the weekly league, the daily/monthly leaderboards and the daily challenge, only your nickname and your points are shown to others (never your number or username). You change the nickname yourself, and you can leave the league and the leaderboards entirely.
  • Teacher's class (only if you join one yourself): the class teacher sees your display name (or nickname), weekly and total points, streak days, progress through the units, percentage of correct answers, general weak points and your study time for the week; they do not see your number or username. This same list is shown to you before you join, and you can leave the class whenever you want.
  • Error reports: the text of the report, its type, the page it was sent from and your account (if you are signed in). For guests, the IP address is kept only briefly, in the server's memory, to prevent mass sending.
  • Referrals and discount codes: the referral code you signed up with (so that both people receive their gift) and the discount codes you have used.
  • Telegram reminders (optional): if you link your account to the bot yourself, the Telegram chat ID and the reminder setting are kept. You can disconnect it whenever you want.
  • Payments (only when the paid section is active): the plan purchased, amount, status, times and the tracking code or payment-gateway ID. For card-to-card payments, the last four digits of the card and the receipt image you upload yourself may be kept. The full card number, CVV2 and card PIN are never entered or stored on the site. If SMS renewal reminders are enabled, one SMS is sent to your verified number near the end of your subscription; online payment takes place on the bank gateway's own page.
  • Payment receipt and contact number: for a card-to-card payment, the receipt image and the mobile number you enter in the payment form are stored with your username and, besides the admin panel, sent to the site owner in a Telegram message for review; they are used only to confirm that payment and to contact you about it.

3. Services that see data

  • The SMS service (only to send sign-in codes, when SMS sign-in is enabled) receives the mobile number and the text of the code.
  • The payment gateway (only when online payment is enabled) receives payment information directly from you.
  • If you talk to support through Telegram or Bale, those messengers have their own rules.
  • Server hosting and storage: the Liara cloud service (servers inside Iran). Database backups, if enabled, are kept in that same service's private storage or in the administrator's private channel and are used only for recovery in case of failure.

We do not sell data and do not give it to anyone for advertising. Only if ordered by a competent judicial authority may we be obliged to provide information.

4. Retention and your rights

Statistical events are deleted after the retention period. Sessions are invalid once they expire. Payment records may be kept for accounting and for handling complaints. You can ask for your account information to be corrected or deleted: send the request through the Contact page and, for identification, use the same method you created the account with. Payment records are kept for as long as accounting and tax laws require. When an account is deleted, its learning data, nickname and class memberships are deleted too.

5. Cookies

We only use essential, first-party cookies: lp_guest (guest), lp_session (sign-in) and, for administrators, lp_notrack (excludes their own device from the statistics). There are no advertising or cross-site tracking cookies. Your browser can block cookies; sign-in and guest access will then not work properly.

6. Children, security and changes

The site is intended for students and enthusiasts. Passwords are hashed and connections to the site should use HTTPS, but no system is perfectly secure; choose a unique password. If this policy changes, the new version will be published here. General terms: Terms of Use.