Cookie Policy

Last Updated: September 8, 2026

This Cookie Policy explains how CertLynx uses cookies and similar technologies on the CertLynx website and how related storage technologies are used in the native iOS and Android applications. The technologies used on the website and in the native apps are different.

1. Cookies and Related Technologies

Cookies are small text files stored by a web browser. They can maintain a website login session, remember preferences, support security, and measure website usage. The CertLynx website may also use browser local storage, session storage, and website device-fingerprinting technology.

The native mobile apps may use protected device storage for authentication tokens and other app or operating-system security signals. These native technologies are not the website's cookies or website FingerprintJS visitor identifier.

2. Website Cookies and Browser Technologies

  • Authentication and security: website cookies support secure sessions, login, account actions, and protection against abuse. The website may use FingerprintJS or similar website device-fingerprinting technology at security-sensitive points.
  • Functional storage: website cookies or browser storage may remember interface choices and preferences.
  • Payments: Stripe may use cookies or similar web technologies when its web payment services are loaded to process transactions, detect fraud, and secure payments.
  • Analytics and measurement: the website uses Google Analytics and may use Google Ads conversion measurement to understand website traffic, registrations, conversions, feature usage, and performance.

Information generated through Google Analytics may be transmitted to and stored by Google on servers in the United States. Access from outside the United States may therefore involve an international transfer of information.

3. Native Mobile App Storage and Authentication

The native iOS and Android applications do not use CertLynx website next-auth cookies as the primary method for keeping you signed in, and native password login does not send the website FingerprintJS visitor identifier. Instead, the apps may store authentication or login tokens in protected device storage, such as SecureStore or comparable operating-system security storage.

The apps may use other security information made available by the app, operating system, authentication service, device, or server as needed to secure accounts and prevent abuse. CertLynx does not characterize these native security signals as website cookies or website device fingerprinting.

If an app opens a web page or third-party web payment experience, that web experience may use cookies according to the applicable provider's policies.

4. Examples of Website Cookies

Website cookie names and durations may change as CertLynx and its providers are updated. Examples include:

  • next-auth.session-token or a secure-prefixed equivalent: website authentication and session continuity; generally up to 30 days.
  • next-auth.csrf-token: website login and account-action security; generally session-based.
  • next-auth.callback-url: returns a website user to the appropriate page after sign-in; generally session-based.
  • sidebar:state: remembers a website interface preference; duration may vary.
  • cl_vid: first-party website visitor measurement; duration may vary.
  • Google Analytics cookies such as _ga, _gid, and _ga_*: website analytics and measurement; duration depends on configuration.
  • Stripe cookies such as __stripe_mid and __stripe_sid: payment security and fraud prevention when Stripe web technology is used.

Website device-fingerprinting identifiers may be stored in browser storage rather than as a named cookie. These website technologies do not describe native mobile password login.

5. Advertising and Conversion Measurement

CertLynx does not use cookies or native mobile tracking technologies to provide personal information to third-party ad networks for behavioral retargeting or third-party advertising profiles. Website conversion measurement may be used to understand whether a CertLynx advertising campaign led to actions such as registration; this measurement does not change the native app login mechanism.

6. Managing Cookies and App Storage

Website: You can restrict, block, or delete browser cookies through browser settings and any controls CertLynx makes available. Blocking necessary website cookies may prevent login or other website features from working.

Mobile apps: Browser cookie controls do not manage native app authentication tokens. You can manage device permissions the app actually requests through your operating-system settings. Signing out or deleting the app may remove some locally stored information; server-side account information remains subject to the Privacy Policy.

7. Changes and Contact

We may update this Cookie Policy as our website, mobile apps, providers, or technologies change. For questions, contact privacy@certlynx.com.