Cookie Policy
What Are Cookies?
Cookies are small text files placed on your device (computer, phone, or tablet) when you visit a website. They are widely used to make websites work properly, remember your preferences, and provide basic analytics to site owners.
ScieBeta uses cookies and similar technologies — such as browser localStorage and session tokens — to operate the platform. This policy explains what we use, why, and how you can control them.
Types of Cookies We Use
2.1 Strictly Necessary Cookies
These cookies are essential for ScieBeta to function. Without them, you cannot log in, publish content, or use authenticated features.
| Cookie name | Purpose | Duration |
|---|---|---|
| sb-access-token | Supabase authentication — keeps you logged in | Session / up to 1 hour |
| sb-refresh-token | Renews your session without re-login | Up to 7 days |
| sb-* (Supabase cookies) | Session state management via @supabase/ssr | Session |
2.2 Functional Cookies
These cookies remember your choices. Disabling them may affect non-essential features.
| Cookie / storage key | Purpose | Duration |
|---|---|---|
| theme-preference | Remember light/dark mode | 1 year |
| last-category | Resume browsing where you left off | 30 days |
| digest-read-state | Track read/unread status locally | 30 days |
2.3 Analytics Cookies
We may use basic, privacy-respecting analytics to understand how the platform is used — such as which pages are visited most and where users come from. When used, analytics are configured to:
- →Not track individual users across sessions.
- →Not share data with advertising networks.
- →Anonymise IP addresses before storage.
We do not currently use Google Analytics. If this changes, this policy will be updated with full details.
2.4 Third-Party Cookies
ScieBeta integrates with third-party services that may set their own cookies:
| Third party | Why it appears | Privacy policy |
|---|---|---|
| Supabase | Database and authentication | supabase.com/privacy |
| Vercel | Hosting and CDN | vercel.com/legal/privacy-policy |
| Google (Gemini API) | AI features in Studio | policies.google.com/privacy |
| Google Favicons API | Displaying source site icons in the feed | policies.google.com/privacy |
What We Do NOT Use Cookies For
- ✕We do not use cookies to track you across other websites.
- ✕We do not sell cookie data to advertisers or data brokers.
- ✕We do not build advertising profiles.
- ✕We do not use fingerprinting or supercookies.
- ✕We do not display advertisements anywhere on the platform.
Session Storage and localStorage
In addition to cookies, ScieBeta may use browser localStorage and sessionStorage for:
- →Temporarily caching digest content for faster loading.
- →Storing UI state (e.g. expanded/collapsed sidebar) during a session.
- →Draft autosave in the Studio editor — local only, not synced until you explicitly save.
This data stays on your device and is not transmitted to our servers unless you explicitly save or publish.
How to Control Cookies
Browser Settings
You can control or delete cookies through your browser settings. Common instructions:
| Browser | Where to look |
|---|---|
| Chrome | Settings → Privacy and security → Cookies and other site data |
| Firefox | Settings → Privacy & Security → Cookies and Site Data |
| Safari | Preferences → Privacy → Manage Website Data |
| Edge | Settings → Cookies and site permissions |
Opt-Out of Analytics
If we introduce analytics tools in future, we will provide an opt-out mechanism directly on the platform before activating them.
Do Not Track
ScieBeta respects the Do Not Track (DNT) browser signal where technically feasible. When DNT is enabled, we will not load any non-essential analytics scripts.
Changes to This Policy
We may update this Cookie Policy as our technology stack evolves. The effective date above will be updated accordingly. For material changes — such as adding new analytics or third-party tools — we will notify registered users by email before the changes take effect.
Contact
If you have questions about our use of cookies or would like to request changes to your cookie preferences: