Cookie Policy
Last updated: May 13, 2026
1Who we are
This Cookie Policy explains how SocialLoopy B.V. ("SocialLoopy", "we", "us" or "our") uses cookies, local storage, session storage and similar technologies on socialloopy.com, the SocialLoopy dashboard and public Link-in-Bio pages.
For broader information about personal data, connected social media platforms, Google/YouTube API data, billing and retention, read our Privacy Policy.
2What cookies and similar technologies are
Cookies are small text files stored by a website in your browser. Local storage, session storage, service workers and cached files are similar browser technologies that can remember choices, keep a session secure, prevent draft loss or help a web app load faster.
First-party cookies are set by SocialLoopy. Third-party cookies are set by external providers, for example Google Analytics or an embedded media provider.
3Our consent approach
Required cookies and storage are used to provide the service you request, such as login sessions, account security, OAuth connection checks, dashboard preferences, checkout return handling and draft recovery. These are always active because parts of SocialLoopy would not work correctly without them.
Analytics cookies are optional. We do not load Google Analytics until you accept analytics in the cookie banner or cookie settings. You can withdraw that choice at any time.
4Cookies we use
| Category | Name | Provider | Purpose | Duration | Consent |
|---|---|---|---|---|---|
| Strictly necessary | socialloopy.* authentication cookies | SocialLoopy / Better Auth | Keeps you signed in, protects authentication requests and supports account security. | Up to 30 days, or shorter for security-specific cookies. | No |
| Strictly necessary | onboarding_done | SocialLoopy | Remembers that you completed onboarding so the dashboard does not show it again. | 1 year | No |
| Strictly necessary | twitter_code_verifier, tiktok_code_verifier | SocialLoopy | Temporarily stores OAuth PKCE verification data while you connect X/Twitter or TikTok. | 10 minutes | No |
| Strictly necessary | sl_google_calendar_oauth_state | SocialLoopy | Protects the Google Calendar OAuth connection flow against request forgery. | 10 minutes | No |
| Analytics | _ga, _ga_<container-id> | Google Analytics | Measures website usage, page views, sessions, device/browser information and approximate engagement trends. | Default GA4 duration is up to 2 years unless browser limits or settings shorten it. | Yes |
Google explains that GA4 uses first-party cookies such as _ga and _ga_<container-id> to distinguish users and preserve session state. You can read Google's explanation in its GA4 cookie usage documentation.
5Local and session storage we use
| Category | Name | Provider | Purpose | Duration | Consent |
|---|---|---|---|---|---|
| Consent | sl_cookie_consent_v1 | SocialLoopy | Stores your analytics cookie choice so we do not ask on every page. | Until you change your choice or clear browser storage. | No |
| Preferences | theme, language | SocialLoopy | Remembers display theme and language choices that you select in the interface. | Until changed or cleared. | No |
| Preferences | sl_active_workspace_id, sl_weekly_goal, sl_default_tone | SocialLoopy | Keeps dashboard workspace, planning goal and default writing tone preferences available between visits. | Until changed or cleared. | No |
| Functional | sl_composer_autosave_*, sl_snippets | SocialLoopy | Prevents draft loss and stores snippets you create for the composer. | Until the draft, snippet or browser storage is cleared. | No |
| Functional | sl_pending_payment, sl_pending_addon_payment | SocialLoopy | Temporarily remembers payment context when returning from checkout. | Browser session or until the payment flow is completed. | No |
| Functional | onboarding_dismissed, inbox canned replies, notification timestamps, daily briefing cache | SocialLoopy | Keeps small dashboard states and user-created quick replies available locally. | Until changed or cleared. | No |
This storage stays in your browser. It is not the same as the OAuth tokens we store on our servers when you connect a social media account; those server-side tokens are covered in the Privacy Policy.
6Public Bio pages and third parties
Public Link-in-Bio pages can count page views and link clicks without needing to set visitor cookies. When a page includes embedded videos, music players or customer-configured tracking pixels, external providers may set their own cookies or collect visitor information.
| Category | Name | Provider | Purpose | Duration | Consent |
|---|---|---|---|---|---|
| Embedded media | YouTube, TikTok, Vimeo, Spotify, SoundCloud, Apple Music embeds | External media providers | Public Link-in-Bio pages may include embedded videos or music. Those providers may set their own cookies or storage. | Controlled by the external provider. | Provider-dependent |
| Customer pixels | Meta/Facebook Pixel or TikTok Pixel when enabled by a Bio page owner | Meta, TikTok or another customer-selected provider | Some Bio page plans may allow page owners to measure visitor actions with their own tracking pixels. | Controlled by the pixel provider and page owner configuration. | Usually yes |
If you own a Bio page and enable third-party embeds or pixels, you are responsible for making sure your public page gives visitors the notices and consent choices required for your use case.
7Managing or deleting cookies
You can change SocialLoopy's analytics choice with the button on this page. You can also clear cookies, local storage and cached files in your browser settings. Clearing required cookies may sign you out, remove saved preferences, clear local drafts or interrupt an OAuth/payment flow.
8Changes and contact
We may update this Cookie Policy when our website, dashboard, integrations, analytics setup or legal obligations change. If we add new optional analytics or advertising cookies, we will update the policy and request consent where required.
Questions or privacy requests can be sent to privacy@socialloopy.com.