1. Scope
This policy applies to Linkrise pages and product experiences that we operate. It should be read together with the Privacy Policy, which explains how we collect, use, share, retain, and protect information.
Cookies are small files stored by your browser. Similar technologies include local storage, session storage, and other browser storage used to remember choices or keep the service working.
2. What Linkrise Uses Now
Linkrise currently uses essential and preference storage rather than advertising or cross-site marketing cookies.
- Authentication and security: to keep you signed in, protect sessions, support origin checks, prevent abuse, and maintain account security.
- Locale and product preferences: to remember interface language and similar choices, including the linkrise_locale cookie.
- Checkout and authentication providers: Paddle, OAuth providers, or other third-party services may set their own cookies on their own domains when you use their checkout or sign-in flows.
3. Non-Essential Cookies
We do not currently use advertising pixels, cross-site behavioral advertising cookies, or third-party marketing trackers on Linkrise.
If we introduce non-essential analytics, advertising, marketing, or session-replay cookies later, we will update this policy and provide consent or choice controls where required before setting those technologies.
4. Managing Cookies
You can control or delete cookies and browser storage through your browser settings. Blocking required cookies may prevent sign-in, Studio editing, checkout handoff, language preferences, or other requested features from working correctly.
5. Changes and Contact
We may update this Cookie Policy when Linkrise changes its product, providers, security controls, analytics approach, or legal requirements.
Questions about cookies or privacy can be sent to the support email listed below.
Current Cookie and Browser-Storage Inventory
Linkrise currently uses the items below for requested product functions. Cookie names used by the authentication library can vary between local and secure production environments. We review this inventory when providers or product behavior change.
- Authentication session and security cookies: first-party, HTTP-only where applicable, used to sign in, protect sessions, and complete OAuth security checks; retained for the session or the configured authentication lifetime.
- linkrise_locale: first-party preference cookie used to remember interface language for up to 1 year.
- linkrise-instagram-oauth-state: first-party, HTTP-only security cookie used only while connecting Instagram; expires after 10 minutes and is cleared on callback.
- linkrise:studio-chrome-mode and scoped Studio snapshot/signature keys: first-party local storage used for Studio appearance, recovery, and unsaved-work continuity; remains until overwritten, cleared in the product, account cleanup where supported, or browser storage is cleared.
- linkrise:studio-paywall-modal-shown: first-party session storage used to avoid repeatedly opening the same paywall during one browser-tab session; cleared when the tab session ends.
- Google, Paddle, or Meta may set their own cookies on their domains when you choose sign-in, checkout, portal, or connection flows. Their own policies control those third-party-domain cookies.