Cookie Policy
There are three different places cookies can come up with DearConvert: this website, the app you log in to, and the pages our customers publish. The rules are different for each, so we have kept them separate. The short answer is that we set very few cookies and none of them are for advertising.
1. What cookies are
A cookie is a small file a website asks your browser to store, so that the site can recognise something on your next request. Cookies can be strictly necessary, which means the site cannot work without them. They can be functional, which means they remember a choice or a state to make the experience consistent. They can also be used for analytics or advertising, which is the category most people are worried about.
Similar technologies such as local storage do much the same job in a different place. Where we mention cookies below, treat it as covering those too.
2. Cookies on this website
The marketing site you are reading now, www.dearconvert.com, sets no analytics cookies and no advertising cookies at all. There are no third-party trackers, no pixels and no profiling here.
That means there is nothing on this site for you to consent to, accept or reject. You can read every page, including the pricing page, without us or anyone else building a record of it.
3. Cookies in the DearConvert app
Once you log in at app.dearconvert.com, the app uses strictly necessary cookies only. They keep you signed in and protect the app against a common class of attack. They are not used to study your behaviour, and there is nothing here for advertisers.
| Cookie | Purpose | Type | Duration |
|---|---|---|---|
dearconvert-session |
Keeps you signed in as you move between pages, so you are not asked for your password on every click. | Strictly necessary, first party | 120 minutes of inactivity |
XSRF-TOKEN |
Protects forms and actions in the app against cross-site request forgery, meaning another site trying to make your browser do something in your account. | Strictly necessary, first party | Same as the session above |
Both are needed for the app to function. If you block them, you will not be able to stay logged in.
4. Cookies on pages published with DearConvert
This is the section that matters most, because it is about pages our customers publish and the visitors who land on them.
Published pages are served as static HTML from a global edge network. Our edge worker sets at most two first-party cookies, and only when the page actually needs them. Both are functional. Neither is used for advertising, and neither follows anyone across sites.
| Cookie | Purpose | Type | Duration |
|---|---|---|---|
dc_v_{pageId} |
Remembers which A/B test variant a visitor was shown, so that if they come back they see the same version of the page rather than a different one. Set only when the page is running an A/B test. SameSite=Lax, path /. |
Functional, first party | 30 days |
dc_unlock_{pageId} |
Remembers that a password-protected page has already been unlocked, so the visitor does not have to type the password again on every view. Set only on password-protected pages. SameSite=Lax. |
Functional, first party | 24 hours |
| Cloudflare Turnstile cookies | Bot detection on forms, when the customer has switched Turnstile on for that form. These are set and controlled by Cloudflare, not by us. | Third party, set by Cloudflare | Set and named by Cloudflare, and documented in Cloudflare's own Turnstile documentation |
Two clarifications that people ask about:
- The honeypot is not a cookie. Every DearConvert form includes an always-on hidden field named
dc_website. Real people never see it or fill it in, so anything that does fill it in is almost certainly a bot. It sets nothing in your browser and stores nothing about you. - Anything else on the page belongs to the customer. If a published page has extra cookies, they come from tracking the customer chose to add. See the next section.
5. If you publish pages with DearConvert
Read this part as a customer rather than as a visitor, because responsibility sits with you.
The two functional cookies in the table above are the only cookies DearConvert sets on your published pages. You are welcome to copy that table straight into your own cookie notice.
Everything else you add is yours to disclose. In site settings you can add your own tracking to your own pages, including Google Analytics 4, Google Tag Manager, the Meta Pixel, the TikTok Pixel, the LinkedIn Insight Tag, and Meta Conversions API events sent server-side. When you switch any of those on:
- The cookies and identifiers they set are your responsibility, not ours.
- You need your own cookie notice covering them, and in places such as the EEA and the UK you need valid consent before the tracking loads.
- You also need to meet the terms of the platform you are sending data to, including for server-side Conversions API events, where there is no cookie banner in the visitor's way to make consent obvious.
Your obligations here are also covered in our Acceptable Use Policy and our Data Processing Agreement.
6. Custom fonts and Google
7. How to control cookies in your browser
You can see, delete and block cookies from your browser settings, usually under a privacy or site data section. Chrome, Safari, Firefox and Edge all let you clear cookies for a single site, block third-party cookies, or clear everything when you close the browser. Most also offer a private browsing mode that discards cookies at the end of the session.
Worth knowing before you block everything:
- Blocking cookies for
app.dearconvert.comwill stop you logging in, because the sign-in cookie is what keeps you signed in. - Blocking cookies on a published page is harmless. You may be shown a different A/B variant than last time, and you may have to re-enter the password on a protected page.
- Clearing cookies does not delete anything a business already collected from you through a form. For that, contact the business whose page you filled in, or see the routes in our Privacy Policy.
8. Why you do not see a consent banner here
Because we do not set advertising or analytics cookies on this website, there is nothing to ask you about. A banner that asked you to accept cookies we do not set would be theatre, so we have not added one.
Strictly necessary cookies in the app do not require consent under EU and UK rules, because the service you asked for cannot work without them.
If that ever changes, if we add analytics to this site or anything that is not strictly necessary to the app, we will add a proper consent banner with a real reject option, and we will update this page before we turn it on.
9. Changes to this policy
If we add, remove or change a cookie, we will update this page and the date at the top. For changes that affect published pages, we will also tell customers, since you may need to update your own cookie notice.
10. Contact
DearConvert is operated by Shiva Guru Balaji S, an independent software developer operating as a sole proprietor in India, from 43b/1 Poosari Thottam, Soolai, Erode 638004, Tamil Nadu, India.
- Questions about cookies or privacy: team@dearconvert.com
- General support: team@dearconvert.com
- Related documents: Privacy Policy, Terms of Service, Sub-processors, Security