Cookie Policy

This Cookie Policy explains how blupdf ("blupdf", "we", "us" or "our") uses cookies and similar technologies on blupdf.com and in the blupdf application (together, the "Service"). It is part of our Privacy Policy. The short version: we set only the cookies that are strictly necessary to sign you in and process payments. We set no advertising cookies and no cross-site tracking cookies, and our analytics are cookieless.

1. What cookies are

A cookie is a small text file that a website stores in your browser. Cookies let a site remember something between page loads — for example, that you are signed in. "Session" cookies are deleted when you close your browser; "persistent" cookies stay until they expire or you delete them. Cookies set by the site you are visiting are "first-party"; cookies set by another domain are "third-party". Similar technologies, such as local storage, work in a comparable way and are covered by this policy.

2. Cookies we set

All of the cookies used by the Service are strictly necessary: without them you could not sign in, stay signed in, or pay.

Cookie	Set by	Purpose	Type	Lifetime
sb-* (for example sb-access-token, sb-refresh-token, chunked variants ending in .0, .1)	blupdf (via Supabase Auth)	Keeps you signed in after you continue with Google, and refreshes your session securely.	Essential, first-party	Session to 1 year, refreshed while you use the Service
__stripe_mid, __stripe_sid	Stripe	Fraud prevention and security on Stripe-hosted checkout and billing pages.	Essential, third-party (Stripe)	__stripe_sid 30 minutes; __stripe_mid 1 year
Load-balancing cookie (only if present)	Vercel	Routes your requests consistently to the same server during a visit.	Essential, first-party	Session

We do not read or write any other cookies. If you clear your cookies you will be signed out and will need to continue with Google again; nothing else is lost.

3. What we do not set

• No advertising cookies. We do not run advertising on the Service and we do not set cookies for ad networks.
• No cross-site tracking. We do not use pixels, beacons or cookies from social networks or data brokers, and we do not track you across other websites.
• No fingerprinting. We do not attempt to identify your device by combining browser characteristics.
• Cookieless analytics. We use Vercel Analytics and Vercel Speed Insights to understand page views and page performance. Both are cookieless: they store no cookies, no identifiers in local storage, and no personal data, and they cannot follow you between sites. Measurements are aggregated.

Because we set only essential cookies, we are not required to ask for consent and we do not show a cookie banner. If we ever introduce a non-essential cookie, we will update this policy and ask for your consent first where the law requires it.

4. Managing cookies

You can control cookies through your browser settings. Every major browser lets you view the cookies that are stored, delete some or all of them, and block cookies from specific sites or from all sites. Instructions are available from the browser makers:

• Chrome: Settings → Privacy and security → Cookies and other site data
• Safari: Preferences → Privacy → Manage Website Data
• Firefox: Settings → Privacy & Security → Cookies and Site Data
• Edge: Settings → Cookies and site permissions

Please note that blocking or deleting the sb-* cookies means you cannot stay signed in to blupdf, and blocking Stripe's cookies may prevent checkout from completing. The rest of the website — pricing, documentation, blog and legal pages — works without any cookies at all.

5. Changes to this policy

We may update this Cookie Policy when we change the cookies we use or when the law changes. The "Last updated" date at the top of this page shows the most recent revision. Material changes will be announced in the Service or by email.

6. Contact

Questions about cookies or about this policy: support@blupdf.com.