Cookie policy

This Cookie Policy explains how Riskline ("we", "us", or "our") uses cookies and similar technologies when you visit our website and use our application (riskline.co). Our philosophy on cookies is simple: we strictly limit data collection to what is necessary to make our platform work and to understand basic usage so we can improve it.

We do not use third-party advertising cookies, retargeting pixels, or cross-site tracking technologies (such as Facebook Pixels or Google AdSense).

Because we do not run advertising or sell your data to data brokers, our cookie footprint is minimal. We use exactly two kinds of cookie: ones that keep your account secure (strictly necessary, no consent required, processed on the basis of Article 6(1)(b) GDPR as necessary to provide the Service you requested), and one first-party analytics cookie (processed only on the basis of your consent, Article 6(1)(a) GDPR).

Analytics cookies are off by default. Our analytics provider is not loaded, and sets nothing on your device, unless you actively choose "Accept" in our cookie banner. Declining, or simply never answering, means no analytics cookie is ever placed. If you have an account, you can change your mind at any time in your account settings. If you don't (for example, you're just browsing the marketing site), you can withdraw consent by clearing your browser's cookies for riskline.co, which resets the banner and stops any previously accepted analytics cookie from being sent. We keep a timestamped record of your consent choice so we can demonstrate compliance if asked, as required by Article 7(1) GDPR.

We divide the cookies we use into two categories.

A. Strictly necessary (essential) cookies

These cookies are critical to the operation of the Riskline platform. Without them, you would not be able to log in, maintain a secure session, or use our security scanning features. Because they are essential to providing the service you requested, they cannot be disabled in our systems.

• Provider: Supabase
• Cookie names: Supabase auth cookies (for example, access and refresh tokens used in server-side rendering)
• Purpose: Authenticates your user session, keeps you securely logged in as you navigate between pages, and prevents unauthorized access to your account or scan reports.
• Type: First-party, session and persistent.
• Duration: Kept for the duration of your session and refreshed automatically while you remain logged in; cleared on logout or when your session expires.

B. First-party analytics cookies

We use first-party product analytics to measure feature usage, diagnose performance issues, and understand how users interact with our platform. This data helps us decide which features to build next and ensures the app runs smoothly. These cookies are set only after you opt in.

• Provider: PostHog
• Cookie prefix: ph_*
• Purpose: Distinguishes unique visitors and active sessions, and attributes specific in-app events (like clicking "Upgrade" or "Submit Feedback") to help us understand product adoption.
• Type: First-party, persistent.
• Duration: Up to 12 months from your last visit (our analytics provider's standard default), or until you withdraw consent, whichever is sooner.
• Consent: Opt-in. Not loaded until you accept, and revocable at any time from your account settings.

Although we only use essential and first-party analytics cookies, you always have the right and ability to manage, clear, or completely block cookies globally through your web browser settings.

Please note that if you block all cookies (including strictly necessary cookies), you will not be able to log into Riskline or use the scanning application.

Here is how you can manage cookie settings in major web browsers:

• Google Chrome: Click the three dots in the top right corner → Settings → Privacy and security → Third-party cookies (or Site Settings → Cookies). From here, you can clear cookies or block them entirely.
• Mozilla Firefox: Click the three lines in the top right corner → Settings → Privacy & Security. Under Enhanced Tracking Protection, you can choose your strictness level or manage exceptions.
• Apple Safari: Go to Safari in the top menu → Settings (or Preferences) → Privacy. You can choose to "Block all cookies" or click "Manage Website Data" to clear existing ones.
• Microsoft Edge: Click the three dots in the top right corner → Settings → Cookies and site permissions → Manage and delete cookies and site data.

For other browsers, please consult the official support documentation provided by your browser's manufacturer.

If we add new features or integrate new sub-processors that require different types of cookies, we will update this policy and, where required by the ePrivacy Directive and GDPR, implement the appropriate consent mechanisms before those cookies are placed on your device.