Reline が使用するブラウザストレージと、それぞれの役割。

This page covers cookies, localStorage, sessionStorage, IndexedDB, and any other browser storage Reline uses, both on the marketing website (reline.so) and inside the app. Most of what we set is strictly necessary for the app to work and is used whether or not you accept analytics. A separate, optional set is used for product analytics and, on the website only, for one marketing tag; both load only after you consent.

These are required for Reline to function and do not need consent. Disabling them in your browser will break sign-in.

• Authentication cookies (e.g. session and refresh tokens) — keep you signed in. Set on sign-in.
• Locale preference (NEXT_LOCALE) — remembers your selected language.
• Consent choice (reline_analytics_consent) — stores whether you accepted or declined analytics, so we don't ask again.
• Theme & layout (localStorage) — your light/dark theme and sidebar/chat layout.
• Sidebar state (sidebar_state cookie) — whether the sidebar is collapsed, so the page renders in the right layout before any script runs.
• Offline cache (IndexedDB) — a local copy of the notes, folders and settings you opened, so the app loads instantly and keeps working without a connection. It lives only in your browser and is cleared when you sign out.

When you accept analytics, we use PostHog, a first-party product-analytics tool, to measure which features are used and where errors happen so we can plan capacity and fix bugs. It sets a PostHog cookie (e.g. ph_…_posthog) holding a pseudonymous identifier. When you are signed in, these events are associated with your account (user ID, email, and name) so we can support you and understand real usage.

Our product-usage events don't include note, transcript, or recording content. Session recordings, however, capture your on-screen activity — including note and transcript content that's visible while you use Reline — so we can reproduce and fix issues; password fields are always masked and network request/response bodies are not recorded. We do not use cross-site advertising trackers inside the app; the only marketing tag we use runs on the public website, after consent, and is listed below. If you do not consent (or your browser sends a Do Not Track / Global Privacy Control signal), analytics — including session recording — does not load at all.

• Vercel Web Analytics — counts page views on the marketing website using a hash that changes daily and cannot be used to recognise you across days. No cookie, no cross-site identifier.
• Vercel Speed Insights — collects Core Web Vitals timings (how fast pages load and respond) from a sample of visits. No cookie and no personal identifier.

Because these store nothing on your device and cannot identify you, they run without a consent prompt; they are listed here for completeness.

• LinkedIn Insight Tag — loads on the marketing website only, and only after you accept analytics in the consent banner. It lets us measure whether visitors who arrived from a LinkedIn campaign signed up, and sets LinkedIn's own cookies (e.g. li_fat_id, bcookie) which are governed by LinkedIn's cookie policy. It never loads inside the app.
• Lemon Squeezy affiliate cookie — if you arrive through an affiliate link (?aff=), our merchant of record's affiliate script loads and sets its own cookie for 90 days so the referring affiliate is credited if you buy a plan. The script loads only after such a link; on any other visit nothing is set. Reline also keeps the affiliate code in localStorage (reline:affiliate-ref) for 90 days so the credit survives a free trial.
• First-touch attribution (localStorage) — the campaign parameters on the first page you landed on (utm tags, gclid, li_fat_id) and the referring site, stored in your browser so we can record which channel brought you here if you later sign up. It is copied to your account once at sign-up, deleted with the account, and you can object by emailing privacy@reline.so.

Google Sign-In — the Google Identity script loads on marketing pages and the sign-in page so you can sign in with one tap. Google may read or set its own cookies on its domains to know whether you are signed in to a Google account; that is governed by Google's privacy policy. Reline receives nothing until you choose to sign in.

When you first visit, a banner lets you accept or decline analytics. You can change your choice at any time from Settings → Preferences → Analytics inside the app, and we honor browser Do Not Track and Global Privacy Control signals automatically.

You can also clear cookies and localStorage from your browser at any time — doing so signs you out and resets your preferences. See our privacy policy for how we handle personal data.