MarkerloopВойти
← Все правила

Markerloop Privacy Policy

Редакция 3 · действует с 19 ноября 2026 г.

Version: 0.5 · Effective date: 19 November 2026

1. Who is responsible for your data

Alisher Toleberdyyev, a sole proprietor (individual entrepreneur) registered in the Republic of Kazakhstan under the business name "Markerloop", individual identification number (IIN) 971104350124, registered on 8 October 2026, contact support@markerloop.com ("Markerloop", "we") is the controller of the personal data described in sections 3–9.

Privacy contact: support@markerloop.com.

2. Two different roles

  • Your account and your use of Markerloop. We decide why and how this data is used. We are the controller. Most of this policy is about this data.
  • Data that Markerloop users collect on their own Sites. When someone builds a Site on Markerloop and a Visitor sends data through it — for example a contact form — the owner of that Site is the controller and we only store the data on their behalf. If you sent data through such a Site, ask its owner first. Section 10 explains more.

3. What we collect

3.1 You give it to us

DataWhenNotes
Usernameregistrationrequired
Email addressregistrationoptional at registration; needed for password reset and invitations
Passwordregistrationstored only as a bcrypt hash; we cannot read it
Email verified flag and timewhen you confirm your email
Accepted version of the Terms, the time of acceptance, and your IP address and browser user agent at that momentregistration and each new versionkept as proof of consent in a log that is never overwritten; erased together with your account
Content you create: records, files (with original file name, size, type, image dimensions), pagesusing the Servicemay contain personal data if you put it there
Email addresses of people you invite to a workspacesending an invitationwe also keep a log of who sent an invitation to which address and when

3.2 From a sign-in provider, if you use one

ProviderWhat we receive and store
GoogleGoogle account ID, email, name, profile picture address
Telegram (sign-in switched off in October 2026; data from earlier sign-ins is kept until the account is deleted)Telegram ID, username, first and last name, language code, profile photo address

3.3 Created automatically

DataWhereKept for
IP address, browser user agent, request method, path, statusservice request logs30 days
Email address and username in sign-in events; recipient address and subject of service emailsservice logs30 days
IP address together with email, for limiting repeated sign-in attemptsshort-lived cacheminutes to hours
Session tokens: only a hash of the refresh token with your user ID, username and emailshort-lived cache24 hours after the last renewal
Who changed access rights, keys or members, and whenworkspace audit logwhile the workspace exists
Author of each page revision (user ID)page historywhile the page exists; for published versions, until the workspace is erased
Access keys you create: name, creator, last time useddatabaseuntil revoked and removed
Error reports: technical details of a failure; default sending of personal data is switched offSentry (EU region)30 days
Page address, referring site, browser, operating system, device type, screen size, language, approximate location (country, region, city), anonymous visitor number (changes daily)visit statistics of our own public pages (self-hosted Umami)12 months

3.4 If you use the Telegram bot

We store your Telegram ID, username and display name, and keep a bot session for 7 days after your last use. The text of messages you send to the bot is not written to our logs.

3.5 Paid plans

There are no paid plans at the date of this version, and we do not process any payment data. If we introduce paid plans through a reseller, we will update this policy before anyone is charged.

3.6 What we do not do

  • We do not sell personal data and do not share it for advertising.
  • We do not use advertising or cross-site tracking cookies.
  • We do not make decisions about you by automated means that have legal or similarly significant effects.
  • We do not run visitor analytics on Sites built by our users.
  • We count visits to our own public pages — markerloop.com, tynda.markerloop.com and showroom.markerloop.com — with Umami, an open-source tool that runs on our own servers in Helsinki. It sets no cookies and stores nothing in your browser. Your IP address is used for a moment to work out an approximate location and, together with a salt that changes every day, to compute an anonymous visitor number; the address itself is not stored. We do not use it in the application after you sign in, and not on Sites built by our users. If your browser sends a "Do Not Track" signal, the visit is not counted.

4. Why we use your data and on what legal basis

PurposeDataLegal basis (GDPR Art. 6)
Create your account, sign you in, provide the Serviceaccount data, sign-in provider data, Content, session tokens, accepted Terms versioncontract — 6(1)(b)
Send service emails: verification, password reset, invitationsemail addresscontract — 6(1)(b)
Keep the Service secure: rate limiting, logs, audit log, error reportsIP address, user agent, log datalegitimate interests in security and reliability — 6(1)(f)
Understand how our public pages are usedvisit statistics of our own public pages (section 3.3)legitimate interests — 6(1)(f)
Respond to legal requests and enforce our Termsany data relevant to the requestlegal obligation — 6(1)(c); legitimate interests — 6(1)(f)
Product announcements by email — only if we start sending them and you opt in; we do not send them todayemail addressconsent — 6(1)(a); you can withdraw at any time

You are not required to give us data, but without a username and password we cannot create an account.

5. Cookies and similar storage

We use only what is needed for the application to work.

NamePurposeTypeLifetime
__Host-access_tokenkeeps you signed incookie, HttpOnly, SameSite=Strict1 hour
__Host-refresh_tokenrenews your sessioncookie, HttpOnly, SameSite=Strict24 hours
__Host-NEXT_LOCALEremembers interface languagecookie, SameSite=Lax1 year
__Host-ml_welcome_skippedremembers that you chose "Skip for now" on the welcome screen; holds your account IDcookie, SameSite=Laxuntil you close the browser
locale, editor layout stateinterface preferencesbrowser local storageuntil you clear it
markerloop:product-notice:hidden:…remembers that you chose "Hide" on an announcement; a new announcement has a new keybrowser local storageuntil you clear it
ml.invite.tokenkeeps an invitation link while you sign in or register to accept itbrowser session storage (this tab only)until it is used or you close the tab
ml.oauth.redirectthe page to return to after signing in with Googlebrowser session storage (this tab only)until it is used or you close the tab
markerloop:billing:paid:…the payment transaction ID right after a checkout, so a reload of the plan page does not lose itbrowser session storage (this tab only)until it is used or you close the tab

Sites published by our users are served without cookies from Markerloop. If you open the Markerloop mini-app inside Telegram, a script from telegram.org is loaded.

The visit counter on our own public pages (section 3.6) sets no cookies and stores nothing in your browser.

6. Who receives your data

Service providers that process data on our instructions (processors) are listed in the table below. We update this section and tell you by email or in the application at least 15 days before a new provider starts processing your data.

ProviderWhat forWhere
Hetzner Online GmbH (Gunzenhausen, Germany), under a data processing agreement under Article 28 GDPR concluded on 12 October 2026servers, databases, file storage, backupsHelsinki, Finland (EU)
Google (Google Workspace), the Google entity named in our Google Workspace agreementdelivery of service emailsGoogle may process this data in any country where Google or its subprocessors maintain facilities; transfers are covered by Google's Cloud Data Processing Addendum (an alternative transfer solution or, failing that, Standard Contractual Clauses)
Functional Software, Inc. d/b/a Sentry (San Francisco, USA)error monitoring; default sending of personal data is switched offSentry's EU data region (Germany). Any transfer to the United States is covered by Sentry's certification under the EU–U.S. Data Privacy Framework, with Standard Contractual Clauses as fallback (Sentry Data Processing Addendum v5.1.0, 29 May 2024)

Providers in the United States receive data only under a transfer mechanism recognised by Chapter V of the GDPR, as stated in each provider's data processing terms listed above.

Separate controllers:

  • Google or Telegram, if you choose to sign in with them: that provider learns that you use Markerloop.

Other recipients:

  • Members of your workspace see your username and what you did in the workspace.
  • Anyone on the internet sees what you publish on a Site and files you mark as public.
  • Authorities, when the law requires it. We check each request and give only what is required.
  • A company that continues the Service, if Markerloop is transferred to a company, merged or sold. We will tell you before your data moves under a different privacy policy.

7. Where your data is stored and international transfers

Your account data, Content, files and backups are stored in Hetzner's data centre in Helsinki, Finland (EU).

Markerloop's operator works from Kazakhstan and accesses the data from there for support and maintenance. The European Commission has issued no adequacy decision for Kazakhstan. Markerloop is directly subject to the GDPR for this processing (Article 3(2)), and we apply the GDPR to it in full — the same rules on purposes, security, retention and your rights as if we were in the EU. The standard contractual clauses adopted by the Commission in 2021 are not designed for this situation (Decision (EU) 2021/914, recital 7); when the Commission adopts clauses for operators outside the EU that are subject to the GDPR, we will adopt them. Until then, the safeguards are: data stays on servers in the EU; access from Kazakhstan is limited to the operator and protected by personal credentials with two-factor authentication on every account that gives access to production data. You can ask us for details.

If you are in Kazakhstan: your data is stored outside Kazakhstan, in Finland. Section 13 explains what this means under Kazakhstan law.

8. How long we keep data

DataKept until
Account datayou delete your account; then erased from live systems within 24 hours
Content in a workspaceyou delete it; a deleted workspace is kept for 30 days for restoration, then erased within 24 hours
A single page, record or filea record is erased when you delete it. A page or a file disappears from the workspace at once and cannot be restored, and the contents of the file are removed from live storage; the snapshots of the page's published versions and the record of the file (its name, size and type) stay until the workspace itself is erased
Backups and earlier file versions30 days; erased data, including the contents of deleted files, can remain in backup storage for up to 45 days
Logs30 days
Visit statistics of our own public pages12 months
Sign-in sessions24 hours after the last renewal
Invitation links7 days
Log of sent invitations30 days

9. Your rights

You can:

  • see the data we hold about you and get a copy;
  • correct data that is wrong;
  • delete your account and data — yourself in Settings → Account, or by writing to us;
  • restrict or object to processing based on our legitimate interests;
  • move your data — receive it in a common machine-readable format; there is no self-service export yet, so we provide the copy on request within 30 days;
  • withdraw consent where we rely on it, without affecting earlier processing.

Write to support@markerloop.com. We answer within one month; in complex cases we may take up to two further months and will tell you within the first month if so. We may ask you to confirm your identity. Using these rights is free.

If you are in the EEA, the UK or Switzerland you may also complain to the data protection authority of the country where you live or work. If you are in Kazakhstan, you may complain to the Committee for Information Security of the Ministry of Artificial Intelligence and Digital Development of the Republic of Kazakhstan (section 13).

We do not treat you differently for using your rights.

10. If you sent data through a Site built on Markerloop

The owner of that Site decides what happens with your data and must tell you about it in their own privacy notice. We store the data for them and do not use it for our own purposes.

What Markerloop itself processes when you visit such a Site: your IP address and browser user agent in request logs and for limiting abuse (section 3.3). We set no cookies and build no profile of you.

If the Site owner does not answer your request, write to us at support@markerloop.com and we will pass it on and help where we can.

For Site owners: the Data Processing Addendum in Annex B of the Terms applies to this data.

11. Security

  • Connections to the Service are encrypted with TLS.
  • Passwords are stored as bcrypt hashes. Session refresh tokens are stored only as hashes.
  • Private files are reachable only through links that expire after 15 minutes.
  • Production changes are made only through a version-controlled deployment process; superuser access to the production database is switched off.
  • Production data is accessed only by the operator, for support and maintenance.

If a breach is likely to put your rights at risk, we will notify the competent authority within 72 hours of becoming aware of it and will tell you without undue delay where the risk is high.

12. Children

The Service is for people aged 18 and over. We do not knowingly collect data from children. If you believe a child has given us data, write to us and we will delete it.

13. Additional information for some regions

Kazakhstan

Markerloop is operated by an individual entrepreneur registered in Kazakhstan, so the Law of the Republic of Kazakhstan "On Personal Data and Their Protection" No. 94-V applies to our processing in addition to the GDPR. Your data is stored in Finland (EU), as described in section 7; Kazakhstan law expects personal data to be stored in Kazakhstan (Article 12), and we are working on a copy of the data in a Kazakhstan data centre. Until then we apply the protection measures required of a small operator under the rules of the authorised body (order No. 179/НҚ) and the GDPR safeguards described in this policy.

By creating an account you give consent to the collection and processing of your personal data in the sense of Articles 7 and 8 of the Law: operator — Alisher Toleberdyyev, individual entrepreneur "Markerloop", IIN 971104350124; data — section 3; purposes — section 4; transfer to the providers in section 6 and cross-border storage in Finland — yes; publication in public sources — no, except Content you publish yourself; term — until you delete your account or withdraw consent. You may withdraw consent by deleting your account or writing to support@markerloop.com; we stop processing within 15 working days unless the law requires us to keep the data (Article 8(7)).

You may complain to the authorised body: the Committee for Information Security of the Ministry of Artificial Intelligence and Digital Development of the Republic of Kazakhstan. If a personal data breach occurs, we notify the authorised body within one working day of discovering it (Article 25(2)(8)) and you as described in section 11.

14. Changes to this policy

We will publish a new version with its effective date. If a change is significant we will tell you by email or in the application at least 15 days before it takes effect.

15. Contact

Alisher Toleberdyyev, individual entrepreneur "Markerloop", Republic of Kazakhstan, IIN 971104350124. Email: support@markerloop.com.