This Cookies Policy explains how FILATOR DIGITAL TECHNOLOGIES, trading as Deepage ("Deepage," "we," "us") uses cookies and similar technologies on deepage.io and in the Deepage app. It should be read together with our Privacy Policy.
01 What cookies are
Cookies are small text files placed on your device when you visit a website. They help the site work and remember your choices. This Policy also covers similar technologies we use, such as your browser's local storage.
02 The cookies we use
Essential cookies (always on)
Required for the site and app to work. They are set without asking, and they are not used for analytics or advertising.
| Cookie | What it does | Duration |
|---|---|---|
authjs.session-token | Keeps you signed in to your account | Up to 30 days |
authjs.csrf-token, authjs.callback-url | Protect sign-in against forged requests and return you to the right page | Session |
dp_human | Records that you passed the security check before signing up or signing in with Google or GitHub | 30 minutes |
dp_consent | Remembers your cookie choice | 12 months |
dp_cr | Remembers whether your location needs a cookie choice before anything optional runs. We read your country from your IP address to decide; we do not store the country | 24 hours |
dp_project | In the app: remembers which of your websites you last opened | 12 months |
dp_tz | In the app: your time zone, so times show in it | 12 months |
On HTTPS the sign-in cookies carry a __Secure- or __Host-prefix. The security check on sign-up and sign-in is Cloudflare Turnstile; it runs in Cloudflare's own frame, under Cloudflare's privacy policy.
Analytics cookies (Google Analytics)
We use Google Analytics on our public pages to understand how the site is used: which pages are viewed, how visitors move between them, and where they came from. It sets cookies that give your browser a pseudonymous identifier. In the EU/EEA, the UK and Switzerland it runs only if you accept analytics in the cookie banner; until then no Google script is loaded. Elsewhere it runs unless you turn it off in Cookie settings. It never runs inside the app.
| Cookie | Provider | Purpose | Duration |
|---|---|---|---|
_ga | Distinguishes visitors | Up to 24 months | |
_ga_* | Maintains session state | Up to 24 months |
Advertising (Google Ads)
We use Google Ads to see whether our ads lead people to set up Deepage, and to show our ads to people who have visited deepage.io (remarketing). In the EU/EEA, the UK and Switzerland this runs only if you accept advertising in the cookie banner; elsewhere it runs unless you turn it off in Cookie settings, and never if your browser sends a Global Privacy Control signal. On our public pages, Google's tag reads the ad click identifier when you arrive from one of our Google ads and keeps it in a cookie. When you finish setting up your first website, your browser sends Google Ads one event: the conversion it belongs to, a random identifier we create for that event, and the page address without any of its details. We do not send your name, your email address, your website or anything you typed, and we do not use Google's enhanced conversions. A copy of that random identifier is kept in your browser's local storage (dp_ads_onboarding_conversion) so the same event is never sent twice.
Remarketing: when advertising is on, Google's tag records your visits to our public pages so we can show our ads to people who have visited deepage.io, on Google and on other sites that show Google ads, and so Google can build audiences from those visits for our campaigns. Google uses its own cookies for this, under Google's policies. When advertising is off, nothing is used for remarketing.
When both categories are off, no Google script is loaded and nothing is sent to Google. When analytics is on and advertising is off, nothing is sent to Google Ads and no advertising cookie is set.
| Cookie | Provider | Purpose | Duration |
|---|---|---|---|
_gcl_au | Measures ad conversions and supports remarketing | 90 days | |
_gcl_aw | Keeps the ad click identifier after you arrive from a Google ad | 90 days |
When Google's tag runs, Google may also set or read cookies on its own domains. Those are governed by Google's policies; you can learn how Google uses data at google.com/policies/privacy/partners.
03 Your choices
- The cookie banner (EU/EEA, UK and Switzerland): on your first visit, a banner offers Accept all, Reject all and Manage preferences. Nothing optional runs until you choose, and rejecting is as easy as accepting. We ask again after 12 months, or if what the categories cover changes. If we cannot tell where you are, we show the banner.
- Everywhere else: no banner is shown; analytics and advertising (including remarketing) are on until you turn them off in Cookie settings.
- Changing or withdrawing your choice: use Cookie settings at the bottom of every page of our site, or the button on this page. Turning a category off deletes its cookies on deepage.io and reloads the page so Google's script stops. Cookies Google keeps on its own domains are removed through your browser or Google's settings.
- Global Privacy Control: if your browser sends a GPC signal, advertising, including remarketing, stays off, wherever you are and whatever you choose.
- Browser controls: most browsers let you block or delete cookies in settings. Blocking essential cookies may stop parts of the Service, such as signing in, from working.
- Google Analytics opt-out: available at tools.google.com/dlpage/gaoptout.
04 Changes to this Policy
We may update this Policy as our use of cookies changes. The "Last updated" date reflects the current version; material changes will be announced on the site.
05 Contact
Questions about this Policy: hasan@deepage.io.