Website privacy
Privacy.
We store your email, and your answer to “How do you share your screen?” if you give one, only to confirm your signup and tell you when the Curtainly beta is ready, and for nothing else. Cloudflare runs the spam check on the signup form and stores the list. Resend, in the US, sends our emails: your welcome email, and a note to us about each signup with your email and your answer. To be removed, reply to any of our emails or write to [email protected]. Curtainly is run by BarterX Tech Private Limited.
What we count
We use PostHog, in its EU cloud (Frankfurt), to see how people find and use this site. On www.curtainly.tech these requests go through our own address, /ingest, on their way to PostHog. Before you answer or after Allow, your IP address reaches PostHog with each request; PostHog uses it to look up roughly where you are (country and city) and then discards it, so your IP address is not stored. A banner asks whether you allow more; what we collect depends on your answer.
Before you answer
We count visits without cookies. PostHog’s script isn’t loaded, and nothing is stored in your browser, neither cookies nor local or session storage, except your answer once you give one (and your light or dark theme, if you change it, and a temporary flag recording whether the opening curtain has played in this tab). Only these events are sent:
- Page view (
$pageview): when each page you open, including moves within the site. With:page_type, the kind of page: home, waitlist, blog, compare, privacy or other. - Your choice (
consent_accepted): when you choose Allow.
Before you answer, each event also carries:
utm_source: landing-link campaign source, when present (kept in memory for this page load);utm_medium: landing-link campaign medium, when present;utm_campaign: landing-link campaign name, when present;utm_content: landing-link campaign content, when present;utm_term: landing-link campaign term, when present;consent_state: your analytics choice when the event happened: unset, allowed or declined;content_view_id: a temporary random key for a content page opened with Allow, held only in memory to count reading and clicks once per page view; empty otherwise;content_slug: the blog or comparison the event happened on (its folder slug; index for the comparison overview), such as the article you were reading or the one a click came from; empty on other pages;platform: that it came from the website;traffic_channel: where the visit came from: search, an AI assistant, social media, another site, direct or an explicitly marked test run;landing_page: the first page you opened on this visit;referrer_domain: the domain of the site that sent you to that first page, such as google.com (or none);page_type: the kind of page the event happened on;
- the page's address, cut to its path and campaign tags (utm_source, utm_medium, utm_campaign, utm_content, utm_term); anything else in the address is removed;
- the address of the page you came from, cut the same way, and its domain;
- your browser's user agent, and from it your browser, operating system and device type (desktop, mobile or tablet);
- screen and window size, language and time zone;
- the library name and version (web, posthog-js) and the time;
- a marker that the event is cookieless, with no visitor ID: PostHog tells visitors apart with a hash of your IP address and browser details that changes every day (the IP address itself is discarded, not stored);
After No thanks
We send your choice (consent_declined) and subsequent page views ($pageview) as unlinked counts. PostHog’s script stays off. These events have exactly four browser event properties:
- page_type: the kind of page;
- consent_state: declined;
- traffic_channel: the broad source of the visit, such as search, direct or an explicitly marked test run;
- $pathname: the page path without query parameters or a fragment;
each event has a fresh transport nonce, never stored or reused; no visitor or session ID and no daily visitor hash; person-profile processing is disabled. PostHog adds its own processing flags, library metadata and timestamps during ingestion; these are not extra browser or campaign details.
We do not send campaign tags, referrers, screen or window sizes, language, time zone, or browser details in these events. On the production /ingest route, our proxy also removes the referring address and replaces your user agent, and does not forward your IP address for these counts. Normal HTTP connection information reaches the services handling each request. Counts cannot tell whether two declined page views came from the same visitor.
If you choose Allow
Only if you choose Allow, PostHog’s script is loaded and we send every event below. PostHog also records a replay of the pages as you see them, with every form field hidden and the address you signed up with left out, where you click and move the pointer (heatmaps), and the buttons and links you click, with their text.
- Website performance (
web_vital): when a document loaded with a saved Allow has a measured LCP, INP or CLS; updates count once. With:metric, LCP, INP or CLS;value, numeric score (milliseconds for LCP and INP);document_route, approved original document path;device, desktop, mobile or tablet;browser, coarse browser family;release, deployed website commit;navigation_type, document navigation kind;metric_key, temporary metric key used to count updates once; never stored in your browser. - Page view (
$pageview): when each page you open, including moves within the site. With:page_type, the kind of page: home, waitlist, blog, compare, privacy or other. - Your choice (
consent_accepted): when you choose Allow. - Your choice (
consent_declined): when you choose No thanks. - Waitlist form (
waitlist_form_viewed): when the form is shown. - Waitlist form (
waitlist_form_started): when you first click or type in it (never what you typed). - Waitlist form (
waitlist_submit_clicked): when you press the button. - Waitlist form (
waitlist_signup_succeeded): when the signup worked. With:first_content_slug, the first blog or comparison opened during this page load, kept only in memory; empty if none;first_content_type, whether that first page was a blog post or a comparison, kept only in memory with it; absent if none;traffic_channel, where the visit came from: search, an AI assistant, social media, another site, direct or an explicitly marked test run;landing_page, the first page you opened on this visit;utm_source, campaign tag in the link you followed, if any: who shared it (x, a newsletter…);utm_medium, campaign tag: the kind of link (social, email, referral…);utm_campaign, campaign tag: the campaign's name;utm_content, campaign tag: which link of the campaign;utm_term, campaign tag: the search term of an ad. - Waitlist form (
waitlist_signup_failed): when the signup didn't work. With:reason, why: the address looked incomplete, the human check failed, too many tries, a server error, or no connection. - Teaser film (
video_played): when it starts playing. With:video_id, which film;section, where it sits on the page. - Teaser film (
video_progress): when it reaches ten seconds, a quarter, half or three quarters. With:video_id, which film;section, where it sits on the page;percent, 25, 50 or 75 for a percentage milestone;seconds, 10 when playback reaches ten seconds, including by skipping ahead. - Teaser film (
video_completed): when it finishes. With:video_id, which film;section, where it sits on the page. - Teaser film (
video_unmuted): when you turn the sound back on. With:video_id, which film;section, where it sits on the page. - Buttons and links (
cta_clicked): when you use one of our sign-up or navigation buttons or links. With:cta_id, which button or link you used;location, where it sits on the page. - Article reading (
scroll_depth): when 25, 50, 75 or 90 percent of the article body has reached the bottom of your window. With:percent, 25, 50, 75 or 90. - Links to other sites (
outbound_clicked): when you follow one. With:url_domain, the other site's domain, not the full address.
Website performance events carry only their listed fields, the existing visitor ID, transport authentication and a flag that prevents person-profile updates. Other events carry the details listed above for page views, and PostHog adds:
- website performance events are stricter: only the listed numeric metric and coarse dimensions, the existing visitor ID, transport authentication and a false person-profile-processing flag; no automatic page address, campaign, referrer or replay details;
- a random visitor ID, kept in your browser's local storage and a cookie on www.curtainly.tech, so visits can be joined up;
- a session ID, a window (tab) ID and a page view ID;
- the library name and version;
- your browser, operating system and device type, screen and window size, language and time zone;
- the page's address (path and campaign tags only), host and title, and the page you came from;
- the campaign tags (utm_*) of this visit and of your first visit, and the first page and referrer PostHog saw for you;
Addresses are cut to their path and campaign tags before they leave your browser, and any text that looks like an email address is removed. No event carries your email, name or anything you type.
Keeping and changing your choice
PostHog keeps analytics events for up to seven years and session replays for 30 days. We keep your choice in your browser for 12 months, then ask again. To change it, use Privacy settings at the bottom of any page. Choosing No thanks after Allow stops the replay and deletes what PostHog stored in your browser. The curtain preference contains only “already played”, has no visitor identifier, is separate from analytics, and lasts for this tab session.