Legal
Cookie Policy
Effective date: May 31, 2026 Last updated: May 31, 2026
What this is
This policy explains the cookies and similar local-storage technologies The Date Post (https://thedatepost.com) uses, why we use them, and how you can control them.
If anything below is unclear, email hello@thedatepost.com.
What we use, in plain terms
The Date Post is built to work with the smallest possible amount of tracking. We do not use cookies for advertising, retargeting, or behavioural profiling. We do not embed third-party analytics, advertising pixels, or social-media trackers.
The cookies and local-storage entries we do use fall into three categories:
- Strictly necessary — the site won't work without them (sign-in sessions, fraud protection on payment pages).
- Functional — small preferences that improve your experience (your selected city, dismissed banners).
- Set by service providers we use — Clerk for authentication, Stripe for payments, Cloudflare for hosting and DDoS protection. These are described below.
Specific cookies and storage
First-party (set by The Date Post)
| Name | Type | Purpose | Lifetime |
|---|---|---|---|
pd_landing_city |
localStorage | Remembers which city you picked in the picker so you don't have to re-pick on return visits. | Until you clear browser data. |
Third-party (set by services we use)
| Set by | Cookies / storage | Purpose | More info |
|---|---|---|---|
| Clerk (authentication provider) | __session, __client_uat, __clerk_db_jwt |
Keeps you signed in. Without these, you'd have to sign in on every page load. | https://clerk.com/legal/cookies |
| Stripe (payment processor) | __stripe_mid, __stripe_sid |
Anti-fraud signals on pages where payment is involved. Only set on pages that load Stripe.js. | https://stripe.com/legal/cookies |
| Cloudflare (hosting / DDoS) | __cf_bm, cf_clearance |
Distinguishes humans from bots and confirms you've passed any security challenge. | https://www.cloudflare.com/cookie-policy/ |
We update this list when our stack changes. The current source-of-truth is whatever the deployed site actually sets — if you find something on the site that isn't in this list, email hello@thedatepost.com and we'll investigate.
What we do NOT use
We do not run, embed, or accept any of the following:
- Google Analytics, Google Ads, or any Google tracking script
- Facebook Pixel, Instagram Pixel, or Meta tracking of any kind
- TikTok Pixel
- Segment, Mixpanel, Amplitude, Heap, or any product-analytics SaaS
- Hotjar, FullStory, LogRocket, or any session-recording tool
- Advertising-network cookies, retargeting pixels, or data-management platforms
- Cross-site tracking of any kind
This is a deliberate product choice, not an oversight. If we add an analytics tool later, this policy will be updated and we will notify you before it takes effect.
How to control cookies
You can control or delete cookies in several ways:
In your browser - Chrome: Settings → Privacy and security → Cookies and other site data - Firefox: Settings → Privacy & Security → Cookies and Site Data - Safari: Settings → Privacy → Manage Website Data - Edge: Settings → Cookies and site permissions → Manage and delete cookies
On The Date Post specifically
- The "strictly necessary" cookies (Clerk auth, Cloudflare security)
cannot be disabled without breaking sign-in.
- The functional pd_landing_city value can be cleared by clearing
site data for thedatepost.com.
Do Not Track - We honour the browser-level "Do Not Track" signal where applicable. Because we don't run advertising or behavioural-tracking cookies in the first place, this primarily affects whether some optional functional cookies are set.
Changes to this policy
We will update this document if our cookie usage changes. Material changes (e.g., adding a new third-party cookie) will be flagged by an in-app notice the next time you sign in.
Contact
Questions, complaints, or "this list looks wrong" reports:
The Date Post Inc. 2416 Main St., Suite 398 Vancouver, BC V5T 3E2, Canada hello@thedatepost.com +1 (604) 720-0397 (Mon–Fri 9am–5pm Pacific)