Cookie Policy
This Cookie Policy explains how the website at dynotable.com ("the Site") uses cookies and similar technologies. It complements our Privacy Policy and Legal Notice. The Site is operated by Dmitrii Nevzorov, trading as DynoTable (NIF Y4075577Z) — see the Legal Notice for full provider details.
What cookies are
A cookie is a small file a website stores on your device to make the site work or to remember information about your visit. Similar technologies — browser local storage and session storage — serve comparable purposes, so this policy covers those as well and calls them all "storage".
Our position: three categories, two of them your choice
The Site uses three categories of storage:
- Strictly necessary — needed for the Site to work, to keep you securely signed in, and to remember the choice you make below. Under Spanish AEPD guidance and the ePrivacy rules these are exempt from consent, so they are used whatever you decide.
- Analytics — lets us recognise the same browser across tabs and visits so that page views group into a journey. Off unless you accept it.
- Advertising — lets us measure whether a click on one of our ads led to a sign-up or a subscription. Off unless you accept it.
The first time you visit, a banner asks you to accept or reject. Reject is one click, exactly as prominent as Accept, nothing is pre-ticked, and the Site behaves identically whichever you choose — there is no cookie wall. Until you decide, analytics and advertising are treated as refused.
Your decision is stored in a first-party dt_consent cookie and you can change
or withdraw it at any time through Cookie settings, in the footer of every
page and on the sign-in page (which has no footer).
Strictly-necessary storage
Used whatever you decide. It carries no advertising identifier and is not shared for advertising.
| Name | Purpose | Type | Lifetime |
|---|---|---|---|
| Session cookies (our sign-in provider) | Keep you securely signed in to your account | Cookie | Session / provider's own |
| CSRF token | Protects form and request submissions from forgery | Cookie | Session |
locale | Remembers the language you picked | Cookie | 12 months |
dt_consent | Records this very choice: which categories you accepted, a random consent id, and the version of this notice you answered | Cookie | 12 months |
dt:consent:sync | A random value written when you decide, so other open tabs know to re-read the consent cookie. It carries no consent data itself | Local storage | Until you clear it |
dt-theme | Remembers light or dark mode | Local storage | Until you clear it |
dt:learn:*, tool:* | Your place in the learning material and the inputs you typed into the free tools, kept on your device | Local storage | Until you clear it |
Analytics storage — only if you accept
If you accept analytics, our analytics provider (PostHog, EU hosting) stores an identifier so repeat visits and separate tabs can be recognised as the same browser. Nothing in this category is set before you accept it.
| Name | Purpose | Type | Lifetime |
|---|---|---|---|
ph_* (analytics provider) | Recognises the same browser across tabs and visits so page views group into a journey | Cookie and local storage | 12 months |
__ph_opt_in_out_<id> | The analytics library's own record that you opted in, read by it on every page | Local storage | 12 months |
If you reject, or have not decided yet
We still count the visit, but without any stored identifier: no cookie is written, nothing is kept on your device, and the visit is counted using a temporary non-reversible value our analytics provider derives on the fly. It is not stored on your device, it changes over time, and it cannot be used to recognise you on a later day or on another website.
Advertising — only if you accept
This category sets no cookie of its own and loads no third-party ad tag. The Site makes no request to Google, to an ad network, or to a tag manager — not before your decision and not after it.
What it does control is one transmission. If you arrived by clicking one of our
ads, the ad click carries a Google click ID (gclid) in the link, which we hold
in the acquisition record described below. When you then start a trial or a
subscription, and only if you accepted advertising, that click ID is sent to
Google Ads together with the fact that a conversion happened, so we can tell
which ads work. Your advertising decision travels with it as an explicit consent
signal. If you rejected, or have not decided, nothing is sent to Google.
How you arrived
On the first page of a visit the Site records how you got there — campaign parameters in the link, the site that referred you, the page you landed on. This happens before you have decided anything, so it is deliberately kept narrow: it holds no identifier, it describes the arrival rather than the person, it is first-party, and it leaves your browser only as part of an action you take yourself — creating an account or starting a subscription.
Where it is kept follows your decision. Until you accept analytics it lives in session storage, which is per-tab and disappears when you close the tab. Once you accept, it is copied to local storage for up to 90 days so that the desktop app's sign-in tab can still see it; that copy is deleted when you withdraw.
| Name | Purpose | Type | Lifetime |
|---|---|---|---|
dt_first_touch | Campaign parameters, referring site and landing page of your first page view | Session storage | Until the tab closes |
dt_first_touch | The same record, promoted so a second tab can read it — analytics consent only | Local storage | 90 days |
What we do not do
- We do not record your screen. Session recording and replay are switched off in every state, accepted or not, and no keystroke, mouse path or form input is captured.
- We do not build advertising audiences. Nothing here feeds a remarketing list, an interest profile or a lookalike audience, and the personalisation signal we send Google is always "denied".
- We do not sell or share personal data for cross-site advertising.
- We load no third-party advertising or tag-manager script.
The consent record we keep
When you decide, your choice is also written to our own database as an audit
row: the random consent id from the dt_consent cookie, the time, which
categories you chose, and the version of this notice. That row holds no IP
address, no account id and nothing else about you — it exists so a consent
decision can be evidenced, as the GDPR requires, without turning the record into
personal data.
Changing your mind
Cookie settings in the footer (and on the sign-in page) reopens the choice at any time. Withdrawing is one click and takes effect immediately.
Withdrawal clears what consent created: the analytics identifier and the cookies and local storage it lived in, and the persistent copy of the acquisition record. The analytics library's own record is switched from opted-in to opted-out, and counting returns to the identifier-free mode described above. Your decision itself is kept — as a record with every category switched off — so that the banner does not ask you again. Withdrawal stops any further transmission to Google Ads; it cannot recall a conversion that was already reported.
You can also block or delete storage in your browser settings. Blocking strictly-necessary cookies may stop you from signing in or using account features, but does not otherwise affect the public pages.
Changes
If we add a category, change what a category does, or otherwise change this notice materially, we increase its version. A decision made under an earlier version stops counting, the banner asks again, and nothing in the analytics or advertising categories runs in the meantime.
Contact
Questions about cookies: support@dynotable.com.