Pending legal review. This text describes how InviteKeep works today in plain English; highlighted items in [brackets] are still to be filled in.
Cookie policy
Last updated 23 October 2026
InviteKeep uses no advertising, analytics or social-media cookies, and invitation pages load no third-party scripts. Everything below is strictly necessary for a feature you use, so no consent banner is needed; you can still clear these at any time in your browser.
Cookies
| Name | Purpose | Where | Lasts |
|---|---|---|---|
sb-…-auth-token | Keeps you signed in (including the temporary session that saves a draft before you sign up) | Host app, studio, sign-in | Until you sign out; refreshed while in use |
ik-claim | Moves the draft you designed before signing up into your new account | Sign-in | 24 hours |
ik-pc-<event> | Remembers that you entered an event’s passcode | Invitation pages | 90 days |
Browser storage
| Name | Purpose | Lasts |
|---|---|---|
ik-seen-… | Skips the opening animation on your next visit | Until cleared |
ik-uploader-name | Remembers the name you put on album uploads | Until cleared |
| Check-in queue | Lets venue staff keep checking guests in when the network drops | Until synced |
| Entry pass cache | Lets your QR entry pass open without signal at the venue | Until cleared |
Third parties
Checkout happens on Dodo Payments’ hosted page, and “Continue with Google/Apple” opens their sign-in pages; those sites set their own cookies under their own policies. Cloudflare may set a strictly necessary security cookie (such as __cf_bm) to tell people from bots.
If we ever add optional cookies (for example analytics), we will ask for your consent first where the law requires it and update this page.