Skip to content

Privacy Policy

Last updated: 30 October 2026

This policy explains what personal data Linkee collects when you use this website, the Linkee app at app.linkee.live and the Linkee browser extension, what we use it for, and what you can do about it.

1. Who we are

Linkee is operated by a sole proprietor (FOP) registered in Ukraine; “Linkee” is the trading name under which they operate. The registered name, registration number and address are provided on request. Ukraine’s Law No. 2297-VI “On Personal Data Protection” applies to the processing. For users in the EU, the GDPR applies as well, under its Article 3(2). For any question about your data, write to info@linkee.live.

2. What we collect

  • Your account: name, login, email address and password. The password is stored only as a one-way hash. If you link Telegram for alerts, we store your Telegram chat ID.
  • Your work in Linkee: sites, projects, recorded links and their prices, marketplace listings and deals, the people you invite to your workspace.
  • Sign-in and security records: IP address, browser type, time of sign-in and failed sign-in attempts.
  • Google and Yandex accounts you connect — see section 3.
  • Pages you capture with the browser extension — see section 4.

There are no payments in Linkee, so we do not collect card or bank details.

3. Data from Google and Yandex

Connecting Google or Yandex is optional. A site owner does it to show the site’s search traffic on its card in Linkee — for their team and, if the site is listed on the marketplace, for buyers.

Access we ask for is read-only:

  • Google: Search Console (webmasters.readonly), Google Analytics (analytics.readonly) and your email address (openid, email).
  • Yandex: Webmaster (webmaster:verify), Metrica (metrika:read) and your login (login:info).

What we read:

  • Google Search Console: the list of your properties and, for the site you pick, total clicks and impressions for the last 28 days.
  • Google Analytics 4: the list of your properties and web data streams and, for the stream you pick, total sessions for the last 30 days.
  • Yandex Webmaster and Metrica: the list of your sites and counters and, for the site you pick, its quality index (SQI), pages in search, visits and visits from search for the last 30 days.
  • Your Google email or Yandex login — only to show which account a site is connected with.

We do not read search queries, individual pages or any other reports, and we never change anything in your Google or Yandex accounts.

How it is stored: access tokens are kept encrypted. The totals are saved once a week as a history of measurements; figures older than 21 days are no longer shown.

Who sees it: members of your workspace see the figures on the site card. If the site is listed on the marketplace, buyers see the weekly totals, without your account name or the names of your properties.

Disconnecting: when you remove a source from a site, its figures and their history are deleted at once. When you disconnect the last site that used a Google or Yandex account, we delete that account’s tokens and revoke our access at Google (and at Yandex, where Yandex allows it), unless the same account is still connected elsewhere in Linkee. You can also remove Linkee’s access yourself at any time on your Google Account permissions page or in your Yandex ID settings.

Linkee’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not sell this data, do not use it for advertising and do not use it to train AI or machine-learning models.

4. The browser extension

The extension reads a page only when you ask it to (a button in the extension) or on tabs it opened itself for a task you started, such as checking search results. From such a page it takes the address, title, links and SEO data (headings, meta tags, structured data) and sends them to your Linkee account. It does not read your cookies, browsing history or passwords. Its sign-in token and working data are stored in your browser.

5. Other websites we look at

To check links, Linkee opens public pages of websites. To describe a site, it looks up public information about the domain: the Internet Archive, domain registration records (WHOIS/RDAP) and Ahrefs Domain Rating. Only domain names are sent to these services, nothing about you.

6. Why we use your data

  • To run your account and the features you use — performance of our agreement with you (GDPR Art. 6(1)(b)).
  • To keep accounts secure and stop abuse — our legitimate interest (Art. 6(1)(f)).
  • Google and Yandex data — your consent (Art. 6(1)(a)), which you withdraw by disconnecting.

We send emails that the service needs: address confirmation, invitations, link alerts. We do not send marketing emails.

7. Who else gets your data

We do not sell personal data. It reaches others only in these cases:

  • Other Linkee users, as you decide: members of your workspace; marketplace buyers see a listing (domain, prices, site figures) but not your name or email; the other side of a deal sees that deal.
  • Our hosting: Linkee runs on servers in the European Union (France). Emails go out from our own mail server.
  • Telegram, if you link it: alerts are delivered to you through Telegram.
  • Authorities, when the law requires it.

8. Cookies

This website and the app use no analytics or advertising cookies. The app uses a session cookie to keep you signed in, a “remember me” cookie for 30 days if you tick that box, and a cookie with your language. Your light or dark theme choice is kept in your browser’s storage.

9. How long we keep data

Account data and security records are kept while your account exists. If you ask us to delete your account, we delete it and the data linked to it within 30 days, except what the law requires us to keep. When a workspace owner deletes a workspace, it disappears for everyone but can be restored on request; write to us if you want it erased for good.

10. How we protect your data

  • Encrypted connections: the website, the app and the extension talk to our servers only over HTTPS (TLS 1.2 or 1.3); plain HTTP is redirected to HTTPS.
  • Google and Yandex access tokens are encrypted with AES-256-GCM before they are saved. The encryption key is kept apart from the database, so a copy of the database alone does not reveal the tokens. They are decrypted only in memory, at the moment Linkee requests your figures from Google or Yandex.
  • We keep as little as we can: from Google and Yandex we store only the totals listed in section 3 and your account email or login, never raw reports.
  • Passwords are stored only as Argon2id hashes. The browser extension’s sign-in tokens are stored only as hashes, and you can revoke any of them on the Extensions page of the app.
  • Access inside Linkee: a workspace’s data is visible only to its members, according to their role. Automated tests check that one workspace cannot read another’s data.
  • Servers: the database accepts connections only from the server itself and is not reachable from the internet. Administrative access is by SSH key only, password log-in is disabled, and repeated failed log-in attempts are blocked automatically. Only the operator of Linkee has administrative access.
  • If something goes wrong: if a breach affects your personal data, we will notify you and the competent authority as the law requires (under the GDPR, the authority within 72 hours).

11. Your rights

You can ask for a copy of your data, correct it, have it deleted, restrict or object to its use, receive it in a portable format, and withdraw consent. Write to info@linkee.live from the email address of your account; we reply within 30 days. You can also complain to the Ukrainian Parliament Commissioner for Human Rights or, in the EU, to your local data protection authority.

12. Children

Linkee is a tool for professionals and is not meant for anyone under 16.

13. Changes

When this policy changes, we update the date at the top. If a change affects how we use data you already gave us, we will tell you by email before it takes effect. See also our Terms of Service.