Cookies Policy
This page explains what cookies and similar technologies OpenBook uses, why we use them, and how you can manage them.
We've designed OpenBook to be cookie-light. We don't use advertising cookies, analytics cookies that profile you, or any third-party tracking. The cookies we do use are the ones that are necessary for the platform to actually work.
1. What are cookies?
Cookies are small text files that websites store on your device. Some are essential for the site to function (e.g. keeping you signed in). Others are used for tracking or advertising. Under EU rules (the ePrivacy Directive and GDPR), websites must obtain your consent before setting non-essential cookies.
Similar technologies — like local storage and session storage — work in similar ways. We treat them the same way as cookies for the purposes of this policy.
2. What we use, and why
On the marketing site (openbook.ie)
| Type | What it does | Consent needed? |
|---|---|---|
| Vercel infrastructure cookies | Session continuity, fraud prevention | No (strictly necessary) |
| Vercel Analytics (if enabled) | Anonymous page-view counts. Does not use cookies and does not identify individual visitors. | No (no cookies set, no tracking) |
| Vercel Speed Insights (if enabled) | Anonymous performance data. Does not use cookies. | No |
We do not use:
- Google Analytics
- Google Tag Manager
- Meta (Facebook) Pixel
- Hotjar, FullStory, or any session recording tool
- LinkedIn Insight Tag
- Any third-party advertising or remarketing pixels
On the app (app.openbook.ie and dash.openbook.ie)
| Type | What it does | Consent needed? |
|---|---|---|
Supabase Auth cookies (sb-*-auth-token) | Keeps you signed in across pages | No (strictly necessary) |
| Supabase session storage | Stores your auth state in the browser | No (strictly necessary) |
| Next.js framework cookies | Routing, prefetching, basic site function | No (strictly necessary) |
| Stripe cookies (only on checkout pages) | Fraud prevention, secure payment processing | No (strictly necessary for payment) |
All of these cookies are strictly necessary for the platform to do what it's there to do — sign you in, keep you signed in, take payments. Under EU law, consent is not required for strictly necessary cookies. We don't show a cookie banner because we have nothing to ask consent for.
3. Why no banner?
Cookie banners exist because most websites use cookies for tracking and advertising, and EU law requires consent for those. We've deliberately built OpenBook to avoid those cookies. Showing you a banner that says “we use strictly necessary cookies” with one button to click would be banner theatre — it adds friction without giving you any meaningful choice.
If we ever add tracking, analytics that use cookies, or any third-party advertising tag, we will add a banner before doing so, and we'll respect your choice.
4. How to manage cookies
You can disable cookies in your browser settings, but if you do, parts of the OpenBook app will stop working — most importantly, you won't be able to sign in. The marketing site (openbook.ie) will continue to work fine without cookies.
Most browsers let you:
- Block all third-party cookies
- Block all cookies from specific domains
- Delete cookies on a schedule
- Clear all cookies
For instructions, search your browser's help docs for “manage cookies”.
5. Mobile and PWA
When you save OpenBook to your phone's home screen as a PWA (progressive web app), the same cookies and storage apply. iOS and Android both isolate PWA storage from the regular Safari/Chrome storage, so it's separate from your normal browsing.
6. Changes
If we add, remove or change the cookies we use, we'll update this page and the effective date. Material additions (especially anything that would require a banner) will be communicated to existing users.
7. Contact
Cookie questions: sam@openhouseai.ie