Cookie Policy
Last Updated: August 25, 2026
The short version: InviteWaale uses the cookies and local storage needed to keep you signed in, keep your invitation drafts safe, and process payments — plus one privacy-respecting analytics tool that tells us which parts of the product people get stuck on. We run no advertising or retargeting pixels, and nothing here follows you or your guests onto other websites.
1. What Are Cookies?
Cookies are small text files that are stored on your device (computer, smartphone, or tablet) when you visit a website. They let a website remember information between page loads — for example, that you are signed in.
This policy also covers similar technologies, in particular local storage: a browser feature that lets a site save small amounts of data on your device. Unlike cookies, local storage is never sent to our servers — it stays in your browser until it is cleared.
2. What We Do Not Use
We want to be specific about this, because many cookie policies claim more than the site actually does. InviteWaale does not use:
- Advertising, remarketing, or retargeting cookies of any kind
- Advertising pixels such as the Meta Pixel or the Google Ads tag — we advertise on Instagram, but we do not install Meta’s tracking code on this site
- Cookies that build an advertising or interest profile about you
- Third-party social media tracking pixels — our sharing features are plain links (for example to WhatsApp) that set nothing on your device
- Any tracking that follows you or your guests onto other websites
We do use one product analytics tool, described in section 3.2 below. It measures how this site is used and nothing else — it cannot see you on any other website, and we do not sell, share, or hand its data to advertisers.
3. Cookies We Do Use
3.1 Essential Authentication Cookies
These are strictly necessary: they are what keeps you signed in to your account as you move between pages. Without them, you would be logged out on every page load and could not use your dashboard at all.
They are set by Supabase, the authentication and database service that powers our accounts, and are issued on our own domain.
Purpose: Session management, keeping you signed in, and protecting requests against unauthorised use
Contains: An encrypted session token — not your password
Duration: Until the session expires or you sign out
Consent: Not required — strictly necessary for a service you asked for
If you only open an invitation someone shared with you and never sign in, no authentication cookie is set.
3.2 Product Analytics
We use PostHog to understand how people use InviteWaale — for example, how many people who start making an invite finish one, and where in that process they get stuck. This is how we decide what to fix next.
It sets a first-party cookie on our own domain containing a random identifier. That identifier means nothing outside this site: it is not shared with any other website, it is not matched against an advertising profile, and it is not sold. Analytics requests are served from our own domain rather than a third-party tracking domain.
Purpose: Measuring how the product is used so we can improve it
Contains: A random identifier, the pages you visit on this site, and which buttons you use
Duration: Up to 12 months
Provider: PostHog, acting as our data processor
We also record anonymised session replays of how pages are used. Everything typed into a form is masked before it leaves your browser — guest names, phone numbers, email addresses and the wording of your invitation are never captured.
If you would rather not be counted, turning on Do Not Track or Global Privacy Control in your browser, or using any standard content blocker, will stop it. Nothing on the site stops working if you do.
4. Local Storage We Use
These entries stay on your device and are never transmitted to us. They exist so the product does not lose your work or repeat itself.
Draft invitations
Saves an invitation you are composing so it survives a refresh or an accidentally closed tab before you have an account. Stored as inviteo-quick-draft.
Sign-in hint
A single flag recording that you were signed in recently, so we can show your dashboard immediately instead of flashing a login screen while we verify your session. It holds no identity information. Stored as invitewaale-auth-hint.
Host checklist cache
A local copy of your event checklist so it appears instantly and remains readable if your connection drops. Stored as host-checklist-… per invitation.
App install prompt
Remembers that you dismissed the “install InviteWaale” prompt, so we do not ask again. Stored as pwa-prompt-dismissed.
5. Third-Party Services
5.1 Razorpay (payments)
When — and only when — you choose to make a payment, we load Razorpay’s secure checkout. Razorpay is our payment processor and may set its own cookies to run the checkout and to detect fraud. This is necessary to complete a transaction you have initiated, and the checkout is not loaded anywhere else on the site.
Loaded: Only on the payment step, at the moment you start checkout
Their policy: Razorpay Privacy Policy
We never see or store your full card details.
5.2 Hosting and Infrastructure
Our hosting and database providers process technical request data — such as IP address and browser type — in ordinary server logs to serve pages, keep the service secure, and prevent abuse. These logs are not cookies and are not used to profile you. See our Privacy Policy for details.
6. Managing Cookies and Stored Data
You remain in control. Every browser lets you block or delete cookies and clear site data:
You can also sign out at any time, which clears your session cookie.
Note: Since we only use essential cookies and functional storage, blocking them has real consequences: you will not be able to stay signed in, and unsaved invitation drafts may be lost. InviteWaale is designed to degrade gracefully — if storage is unavailable, for example in private browsing, the site still works, but it will not remember drafts or preferences between visits.
7. Do Not Track
Some browsers send a “Do Not Track” (DNT) or Global Privacy Control signal. There is no universal standard for how sites should respond, but we honour it: if your browser sends one, our product analytics does not run at all and no analytics cookie is set. The essential sign-in cookie in section 3.1 still works, because without it you could not stay logged in.
Either way, we do not build advertising profiles or share data with advertisers.
8. If This Changes
We may update this Cookie Policy to reflect changes in our services, technology, or the law. If we ever introduce analytics or advertising cookies, we will update this page before doing so and — where the law requires it — ask for your consent first, rather than enabling them silently. Material changes will be reflected in the “Last Updated” date above.
9. Contact Us
If you have any questions about our use of cookies or this Cookie Policy, please contact us:
Email: privacy@invitewaale.com
Support: Contact Form