Legal
Cookie Policy
Last updated 7 October 2026 · Effective 7 October 2026
Which cookies and similar technologies run when you visit our website, who sets them, what they do, and how you can control them.
On this page
Plain-English summary: Our own domain sets no cookies and stores nothing in your browser. Our host, Framer, counts visits without cookies. The Cal.com booking calendar on our homepages loads as soon as a homepage opens, and Cal.com then sets its own cookies and stores a few items in your browser. Google receives your IP address when our fonts load. We have not added advertising, retargeting or cross-site tracking tools. This summary does not replace the full policy below.
1. About this policy
This Cookie Policy explains the cookies and similar technologies that run when you visit our website at wedesignlandingpages.com, including its translated pages, blog, shop and template previews (the “Site”). Read it together with our Privacy Policy, which explains how we handle personal information more broadly and the rights you have.
WeDesignLandingPages.com (“WDLP”, “we”, “us”, “our”) is a trading name of Hardik Dewra, a sole proprietor based in Bahadurgarh, Haryana, India.
2. What cookies and similar technologies are
Cookies are small text files that a website asks your browser to store. Your browser sends them back to the same website later. A first-party cookie belongs to the website you are visiting. A third-party cookie belongs to another company whose content is built into the page, such as a booking calendar. Session cookies are deleted when you close your browser. Persistent cookies stay until they expire or you delete them.
Websites and the services built into them can also use:
local storage and session storage, which are storage areas in your browser
scripts that send information from your browser to a server without storing anything, as analytics tools do
service workers, which are small scripts a website can register in your browser to handle tasks such as notifications
files loaded from another company’s servers, such as fonts, which send that company your IP address and browser details
This policy covers all of these.
3. What our own website sets
Our own domain, wedesignlandingpages.com, sets no cookies and writes nothing to your browser’s local storage or session storage. It does not register a service worker. We confirmed this with browser scans of our homepages, blog and shop pages on 7 October 2026.
Framer, which hosts the Site, includes code that looks for two settings in your browser’s local storage: __framer_force_showing_editorbar_since and framer-fetch-client-cache. For visitors, neither setting exists, and the code writes nothing. Framer creates the first one only for people who edit our Site in Framer, to show them its editing bar. The second one belongs to a Framer feature we do not use.
4. What runs on our pages
Our pages use services from other companies. The services in section 4.1 receive information from your browser but store nothing on your device. The booking calendar in section 4.2 stores cookies and other items. Section 4.3 explains what happens when you click a “Book a call” link. We do not ask for your consent before any of these services run. Section 6 explains how you can block them or remove what they store.
4.1 Services that store nothing on your device
Framer hosting
Provided by: Framer B.V. (Netherlands), our host and processor
When it runs: On every page.
What it does and what it receives: Delivers our pages, images, code and some of our fonts from Framer’s servers, which include Amazon Web Services in the United States and other regions. Framer receives your IP address, browser details, the page you request and the page you came from, and keeps server logs under its own retention practices.
Framer Analytics
Provided by: Framer B.V., as our processor
When it runs: On every page.
What it does and what it receives: Records page views, the links you click, performance and error data, and your time zone and language settings, so we can see aggregated statistics. Framer says it uses no cookies or persistent identifiers. To count daily unique visitors, it hashes (scrambles) your IP address and browser user agent (the browser and device details your browser sends) with a secret key that it changes and deletes every day.
Framer editor check
Provided by: Framer B.V., as part of its own platform
When it runs: On every page.
What it does and what it receives: A hidden frame from framer.com checks whether you are signed in to Framer as an editor of our Site. If you are signed in to Framer, your browser sends your framer.com sign-in cookies to Framer for this check. Nothing is stored for visitors who do not edit our Site.
Google Fonts
Provided by: Google
When it runs: On every page.
What it does and what it receives: Your browser downloads the fonts our pages use from Google’s servers (fonts.gstatic.com), so Google receives your IP address and browser details. Google set no cookies in our scans.
Sentry, through Cal.com
Provided by: Sentry, for Cal.com
When it runs: When any of our homepages opens, because the Cal.com calendar loads with the page. Also on cal.com.
What it does and what it receives: Cal.com’s calendar sends monitoring data, such as performance measurements, to Sentry’s servers in the United States. Sentry receives your IP address and browser details with it. Sentry set no cookies in our scans.
4.2 The Cal.com booking calendar
Our homepage, in every language, includes a booking calendar from Cal.com, Inc. (United States), so you can pick a time for a 20-minute call. The calendar loads automatically when the page opens, even if you never scroll down to it or use it. Our blog, shop and other pages do not include it.
When the calendar loads, Cal.com and Cloudflare, which protects Cal.com against bots, set the items below on Cal.com’s own domains. These are third-party items that belong to Cal.com. Cal.com handles booking details for us as our processor, and it uses this technical data for its own purposes, such as security and monitoring its service, under its own privacy policy. That policy says Cal.com uses its cookies for signing in, remembering preferences and security, and uses no third-party advertising cookies.
__cf_bm
Set by and type: Cloudflare, for Cal.com. Third-party cookie on cal.com.
When it is set: When any of our homepages opens. Also on cal.com.
Purpose and how long it lasts: Helps tell people from bots and protects Cal.com’s booking service. Lasts up to 30 minutes after your last activity.
__Secure-next-auth.csrf-token
Set by and type: Cal.com. Third-party cookie on cal.com.
When it is set: When any of our homepages opens. Also on cal.com.
Purpose and how long it lasts: Protects Cal.com’s forms against cross-site request forgery, a type of attack. Deleted when you close your browser.
__Secure-next-auth.callback-url
Set by and type: Cal.com. Third-party cookie on cal.com.
When it is set: When any of our homepages opens. Also on cal.com.
Purpose and how long it lasts: Remembers where Cal.com should send you after a sign-in step. Deleted when you close your browser.
reserverUid
Set by and type: Cal.com. Local storage in the Cal.com frame.
When it is set: When any of our homepages opens. Also on cal.com.
Purpose and how long it lasts: A random ID that stays the same across visits. Its name and Cal.com’s documentation indicate that it links temporary holds on time slots to your browser. Stays until you clear Cal.com’s site data.
nextauth.message
Set by and type: Cal.com. Local storage in the Cal.com frame.
When it is set: When any of our homepages opens. Also on cal.com.
Purpose and how long it lasts: Keeps Cal.com’s sign-in state in sync across your browser tabs. Stays until you clear Cal.com’s site data.
timeOption.is24hClock
Set by and type: Cal.com. Local storage in the Cal.com frame.
When it is set: When any of our homepages opens. Also on cal.com.
Purpose and how long it lasts: Stores whether to show times in 12-hour or 24-hour format. Stays until you clear Cal.com’s site data.
Cal.com service worker
Set by and type: Cal.com. Service worker for app.cal.com.
When it is set: When any of our homepages opens. Also on cal.com.
Purpose and how long it lasts: A small script that, in the version we checked, only handles push notifications. It shows nothing unless you allow Cal.com to send you notifications. Stays until you remove it in your browser settings.
The calendar’s code also writes a test item (nuqs-localStorage-test) and deletes it at once, to check that storage works. It also looks for display preferences, such as theme and time zone, that it may have saved on an earlier visit.
In our scans with Chrome’s default settings, all three cookies were set. Safari and Firefox block or isolate third-party cookies like these by default.
4.3 “Book a call” links
Our “Book a call” buttons and links open cal.com in a new tab. From that point you are on Cal.com’s own website, and Cal.com’s privacy policy and cookie notice apply. Cal.com sets its cookies there, stores items such as reserverUid on cal.com, and registers its service worker for cal.com. Framer Analytics records that you clicked the link.
If you book a call, Cal.com handles your booking details for us as our processor. Our Privacy Policy explains how we use them.
4.4 Providers’ privacy policies
These providers explain their own practices:
5. Our approach and what we do not use
Our own domain sets no cookies, we measure visits with cookieless analytics, and this policy lists what the services built into our pages do, including the Cal.com cookies on our homepages. We base it on our own browser scans and the providers’ documentation. We have not added advertising, retargeting or cross-site tracking tools. We do not use Google Analytics, Meta (Facebook) pixels, the LinkedIn Insight Tag, heatmaps or session recording. We do not sell personal information or share it for cross-context behavioral advertising.
6. How to control cookies and similar technologies
Use a content blocker. Privacy extensions and content blockers can stop requests to Framer Analytics (events.framer.com), Google Fonts or Cal.com. Parts of the Site may then look or work differently.
Delete cookies and site data. Your browser’s privacy settings let you see and delete cookies and stored site data. To remove the Cal.com items, including its service worker, clear the site data for cal.com and app.cal.com.
Book without the embedded calendar. Our blog and shop pages do not load the calendar. From there, use a “Book a call” link, which opens cal.com in a new tab under Cal.com’s own policies, or email us at admin@wedesignlandingpages.com to arrange a time.
Block third-party cookies. Safari blocks them by default, Firefox keeps them separate for each website by default, and Chrome lets you block them in its privacy settings. Blocking them stops Cal.com’s cookies from being set while you are on our pages, though the booking calendar may not work properly.
Our analytics. Framer Analytics stores nothing on your device and gives you no ID, so we cannot switch it off for one visitor. To stop it, block requests to events.framer.com with a content blocker or your browser’s privacy settings. If you have a question or an objection about it, email us with “Privacy” in the subject line.
Global Privacy Control and Do Not Track. Your browser can send these signals to websites. Global Privacy Control asks websites not to sell or share your personal information. Do Not Track asks them not to track you. We do not sell or share personal information for cross-context behavioral advertising, so there is no sale or sharing for a Global Privacy Control signal to stop. The Site does not currently change how it works when it receives either signal. For example, Framer Analytics still counts your visit, without cookies.
7. If we add tools that need your consent
We may later add cookies or similar technologies that need your consent under the law that applies to you, such as analytics that use cookies, advertising or retargeting pixels, or session recording. If we do, we will ask for your consent before they run. We will make refusing as easy as accepting, give you a way to change your choice at any time, and update this policy before the change goes live. Section 4 explains what runs on our pages today without a consent step.
8. Changes to this policy
We review this policy whenever we add, remove or change a tool on the Site. When we change it, we post the new version here with a new date. We keep previous versions of this policy. Ask us for a copy.
Last reviewed 7 October 2026. We last scanned the Site on 7 October 2026.
9. Contact us
For questions about this policy, email admin@wedesignlandingpages.com with “Privacy” in the subject line. Our Privacy Policy explains your privacy rights and how to use them.