Last updated: 17 September 2026
The short version. Trackly sets one cookie of its own, and it exists only to keep you signed in. We also run three third-party tools that load together with the page: the Meta pixel, which measures our advertising, and Yandex Metrica and Google Analytics, which measure how the site itself is used — Metrica includes a session recorder. There is no consent banner today, so if you would rather they did not run, sections 4 and 5 explain how to block them in half a minute.
A cookie is a small text file a website asks your browser to store and send back on the next request. It is how a site remembers that the person loading this page is the same person who signed in a minute ago. The same rules in this policy apply to anything that works the same way — local storage, session storage, pixels, web beacons and device fingerprinting.
| Name | Set by | Purpose | Lifetime | Category |
|---|---|---|---|---|
trackly_sid |
inst.trackly.one (first party) | Holds the identifier of your signed-in session. Without it you would be signed out on every page load and could not reach your dashboard. It contains a random identifier and nothing else — no email, no name, no advertising ID. | 30 days, or until you sign out | Strictly necessary |
The cookie is marked Secure (it is only ever sent over HTTPS), HttpOnly
(scripts on the page cannot read it, which blunts cross-site scripting attacks) and
SameSite=Lax (other sites cannot cause your browser to send it).
Your dashboard filters — niche, source platforms, budget range — are stored on our server against your account, not in a cookie.
We advertise on Facebook and Instagram, and we need to know whether that advertising brings people who
actually sign up. For that we use the Meta pixel (id 28141176198867446), a script from
Meta Platforms, Inc.
| What | Who | What it collects | When it runs |
|---|---|---|---|
Meta pixel_fbp, _fbc and Meta’s own cookies |
Meta Platforms, Inc. (third party) | That a browser opened a page of ours, the page address, your IP address, browser and device details, and the Meta cookies already in your browser | On every page, as soon as the page loads |
There is no consent banner on this site today, so the pixel is on by default. We would rather say that plainly than publish a policy describing a switch that does not exist.
How to turn it off. Any of these works, and the site behaves identically either way:
connect.facebook.net from loading. Then nothing about your visit
reaches Meta at all.A switch on the site itself is planned, so that this stops depending on your browser. When it ships, this page will say so.
To see which pages people open, where they stop and what breaks, we use Yandex Metrica
(counter 112428127), a service of Yandex. It loads with the page, on the public pages and in
your signed-in dashboard alike.
| What | Who | What it collects | When it runs |
|---|---|---|---|
Yandex Metrica_ym_uid, _ym_d, _ym_isad,
_ym_visorc and related cookies |
Yandex (third party) | Pages you open and in what order, the address you came from, your IP address, browser, device and screen size, and how long you stay. Session recording (Webvisor) is switched on, so it also records mouse movement, scrolling, clicks and keystrokes as you move around the site. | On every page, as soon as the page loads |
About the session recording. This is the most intrusive thing on the site and we would rather name it plainly than bury it. Webvisor replays a visit like a video: mouse, scrolling, clicks.
What it is not allowed to see. Every field you can type into — the email and password boxes on the sign-up and log-in forms — is marked so that Yandex records asterisks instead of the characters. The places where your address is printed back to you, in the dashboard header, the side menu, the confirmation banner and the payment receipt, are excluded from the recording entirely. So a replay shows us that someone filled the form, not what they filled it with. The only other controls on the site are the two price sliders, which hold no personal data.
We use the recordings to find broken layouts and dead ends, not to identify people.
How to turn it off. Any of these works:
mc.yandex.ru from loading.We also run Google Analytics 4 (measurement ID G-X3SDLHML3T), a service of
Google. It tells us which pages people open, where they arrive from and where they leave. It loads with
the page, on the public pages and in your signed-in dashboard alike.
| What | Who | What it collects | When it runs |
|---|---|---|---|
Google Analytics_ga, _ga_X3SDLHML3T |
Google (third party) | Pages you open and in what order, the address you came from, your browser, device and screen size, your approximate location, and how long you stay. Your IP address is used to work out that location and is not stored by Google Analytics. There is no session recording here — that is Metrica only. | On every page, as soon as the page loads |
The two _ga cookies last two years and hold a random identifier that lets Google tell a
returning browser from a new one. We have not switched on Google Signals, so Google Analytics is not
joining your visit to a signed-in Google account for our benefit. What Google does with the data on its
own account is governed by its privacy
policy.
How to turn it off. Any of these works:
googletagmanager.com from loading.United States law does not require a blanket consent banner. What it requires is that you not be tracked for someone else’s purposes without a way to say no, and that we describe honestly what we do. That is what this page is for.
Note that both analytics tools — Yandex Metrica with its session recording, and Google Analytics — would need explicit consent before loading under the GDPR. If you are in the EEA or the UK, block them as described in sections 4 and 5 until we ship the switch.
We are not pretending the question is settled. Under the California Invasion of Privacy Act, sites that load an advertising pixel before the visitor has agreed to it have been sued in the thousands — the argument being that a third party learns of the visit at the same instant the page opens. We treat that as a real risk: a site-side switch is planned, and this page will be updated the day it ships.
These apply to the Meta pixel today and to any tag we might add later:
Every browser lets you see, block and delete cookies — usually under Settings → Privacy. You can block
ours, including trackly_sid. If you do, the site will still show you the public pages and the
live feed, but you will not be able to stay signed in to a dashboard.
Write to pravdalife777@gmail.com or message @trackly_support. What we do with the data behind these cookies is described in the Privacy Policy.