This Cookie Policy explains how Bytech LLP (Товарищество с ограниченной ответственностью «Bytech») uses cookies and similar technologies on https://deplion.cc — our marketing website and the Deplion dashboard.
It supplements Section 7 of the Privacy Policy, which describes what we do with the data these technologies collect.
This policy does not cover websites published by our users. Those sites are delivered from our infrastructure, but the site owner decides what runs on them. If you are a visitor to a site published through Deplion and have a question about its cookies, contact that site's owner. See Section 6 below.
1. What cookies are
A cookie is a small text file a website asks your browser to store. Similar technologies — local storage, session storage — do the same job with a different mechanism. Throughout this policy, "cookies" covers all of them.
We group cookies into two categories:
- Strictly necessary — without these the Service cannot work. They are set because you asked for a service that requires them (signing in, submitting a form, remembering your cookie choice). They do not require your consent, and cannot be switched off.
- Analytics — these help us understand how the Service is used. They are not set until you agree, and you can withdraw that agreement at any time. Section 3 explains what our analytics provider does receive before you agree, which is deliberately not nothing.
We do not use advertising or cross-site tracking cookies, and we do not sell the data these cookies produce.
2. Strictly necessary cookies
| Cookie | Set by | Purpose | Retention |
|---|---|---|---|
deplion-session (name follows the application name) |
Bytech LLP | Keeps your browser session — signed-in state, flash messages, CSRF protection state | Session, extended on activity; expires after 120 minutes of inactivity by default |
XSRF-TOKEN |
Bytech LLP | Cross-site request forgery protection for forms and dashboard actions | Same as the session cookie |
remember_web_* |
Bytech LLP | Set only if you tick "Remember me" at sign-in, so you stay signed in between visits | Up to 5 years, or until you sign out |
cc_cookie |
Bytech LLP (via the vanilla-cookieconsent library, which runs entirely on our own infrastructure) |
Stores your cookie choice, the categories you accepted, the consent revision and a random consent identifier, so we do not ask again on every page | 182 days |
Refusing strictly necessary cookies is not possible within the Service. You can block them in your browser, but the Service will not function.
3. Analytics cookies
| Technology | Set by | Purpose | Retention |
|---|---|---|---|
| Google Tag Manager and the tags it loads (Google Analytics) | Google LLC | Measuring how visitors reach and use our marketing website and dashboard: pages viewed, referrer, approximate location, device and browser | Set by Google; typically up to 2 years, varying by cookie |
No analytics cookie is set until you accept. Enabling the Analytics category — through "Accept all" or the preferences dialog — is what permits Google to store or read anything on your device. If you refuse, or simply ignore the banner, no analytics cookie is set and no identifier held on your device is read.
The container itself does load before you choose, and we should be plain about that. We use Google's Consent Mode in its advanced form: the Google Tag Manager container is requested on every page, but it is told, before it runs, that consent for every storage purpose is denied. In that state it may send Google an anonymous, cookieless signal that a page was viewed. That signal carries your IP address, the page address, the referring page and your browser's user agent, because any request to a third-party server carries those. It does not carry a cookie, a device identifier, or anything joining this visit to another one.
We do this so that visitor numbers remain measurable when most visitors decline — and we tell you rather than describing the container as absent, because it is not.
If you would rather Google's servers were not contacted at all, block googletagmanager.com in your browser or an extension. Nothing in the Service depends on it.
Google acts as our processor for this analytics data and may transfer it outside the European Economic Area and the United Kingdom. See Sections 6 and 8 of the Privacy Policy and our Sub-processors page.
4. Giving, changing and withdrawing consent
4.1. The first time you visit, a banner asks for your choice. You can accept all categories, refuse everything that is not strictly necessary, or open the preferences dialog and choose per category.
4.2. Withdrawing consent is as easy as giving it. Select Cookie settings in the footer of any public page, in the Legal section of the dashboard sidebar, or in Settings → Privacy. The preferences dialog opens with your current choice; changing it takes effect immediately.
4.3. When you withdraw consent for analytics, the withdrawal is signalled to the container immediately, without waiting for a page reload, and it stops setting and reading cookies from that moment. It returns to the cookieless state described in Section 3. Cookies already placed by Google are not removed by us — clear them through your browser's cookie settings if you want them gone.
4.4. Withdrawing consent does not make our earlier processing unlawful. It applies from the moment you withdraw.
5. Record of your choice
5.1. When you make or change a choice, we record it: the categories you accepted, the consent revision in force, the time, your IP address, a keyed hash of your browser's user agent, and a keyed hash of the random consent identifier stored in the cc_cookie cookie. If you are signed in, the record is linked to your account.
5.2. We keep this record because Article 7(1) of the GDPR requires us to be able to demonstrate that consent was given. It is a record of a choice, not a profile: the consent identifier is stored only as a keyed hash, so the record cannot be used to follow you around the Service.
5.3. These records cannot be edited or deleted after the fact — they are stored append-only. If you delete your account, the link to your account is removed and the record is retained in anonymised form. See Section 9 of the Privacy Policy.
5.4. If you sign in, you can download your consent records together with the rest of your data from Settings → Privacy.
6. Consent revisions
6.1. Every consent is recorded against a revision number. If we materially change what we use cookies for — a new category, a new provider, a different purpose — we raise the revision and update this policy.
6.2. Raising the revision invalidates every consent given under the previous one. You will be asked again on your next visit, and the analytics category returns to "off" until you make a new choice.
7. Cookies on sites published by our users
7.1. Deplion lets users publish their own websites. Those sites may set their own cookies, including analytics or advertising cookies, using code the site owner (or their AI assistant) placed there.
7.2. We do not control those cookies and this policy does not cover them. The site owner is the controller for them and is responsible for any consent banner required on their own site.
7.3. We do inject a "Made with Deplion" badge into pages served on our free tier. The badge is a link and sets no cookies.
7.4. If a published site sets cookies without asking you and you cannot reach its owner, you can report it to [email protected].
8. Managing cookies in your browser
Every major browser lets you view, block and delete cookies. Blocking all cookies will break the Service, because the strictly necessary cookies in Section 2 will also be blocked. Browser-level controls are independent of the choice you make in our banner — if you clear cookies, our banner will ask again.
We do not currently act on the "Do Not Track" or "Global Privacy Control" browser signals. Analytics storage is denied by default here in any case; what those signals do not currently suppress is the cookieless request described in Section 3, which you can block at the browser level as described there.
9. Changes to this policy
We may update this policy. The version and effective date are shown at the end of this page. Where a change affects what we use cookies for, we also raise the consent revision described in Section 6, which means you will be asked for a fresh choice.
10. Contact
Bytech LLP (Товарищество с ограниченной ответственностью «Bytech») BIN 230740022607 29A microdistrict, building 90, office 202, Aktau, Mangystau region, 130000, Republic of Kazakhstan
- Cookie and privacy questions: [email protected]
- Abuse reports about a published site: [email protected]
Version 2026-07-29 — effective 2026-07-29.