LARGUS

Privacy Policy

Effective 8 October 2026 · Version 2026-10-08.9

This policy covers the Clargus pre-beta website, applications, optional site analytics, and publisher referral program. It does not replace the terms or privacy information for a future live product.

1. Who is responsible

Clargus operates this website and is responsible for the personal information described here. Contact [email protected] for privacy requests.

2. Information we collect

Applications include your name, email, investor type, and the firm, publication/profile, research interests, and message you choose to provide. Please do not submit confidential positions, client information, financial account credentials, or sensitive personal information.

We keep the policy versions you acknowledged, the time and method of acknowledgement, and your cookie choices. With optional analytics enabled, we collect a random visitor/session identifier, page path, application audience, and events such as viewing, starting, or submitting a form. Our first-party analytics records and manual Google Analytics events omit form text, names, email addresses, full query strings and full referring URLs. Microsoft Clarity recordings have the separate safeguards and URL handling described below.

With referral attribution enabled, we associate a valid referral link with a publisher account, platform, and your application. Publisher records may include name, organization, business contact details, public profile/website links, platform accounts, and relationship notes. We may obtain those details directly or from public business and social profiles. Network requests also expose technical data such as IP addresses to our hosting and database providers; we do not intentionally copy IP addresses into our analytics tables.

3. How and why we use information

We use application details to review requests, prepare access, and communicate about your application. Where applicable, this is processing to take steps at your request before a possible service relationship. Our legitimate interests cover protecting the website, maintaining business contacts, and retaining proportionate records of acknowledgements and consent. Where local law requires a different basis, that law applies.

Optional analytics and persistent referral attribution rely on your separate choices. Declining or withdrawing them does not prevent an application. Acknowledging this Privacy Policy is not consent to advertising, optional analytics, or unrelated marketing. We do not add applicants to promotional mailing lists merely because they apply.

Applications are reviewed by people. We do not use the collected website data to make solely automated decisions with legal or similarly significant effects.

4. Security checks and short-lived prefill

Applications use Google reCAPTCHA v2 to help prevent automated abuse. This security check is separate from optional analytics and referral tracking; Google may process browser, device, and connection information to provide it. If the check is unavailable or inaccessible, contact us for application assistance.

If you enter an email in an insight preview, we carry it to the application using sessionStorage in that browser tab for up to ten minutes, then remove it when read. We do not place the email in the navigation URL or retain a full application draft. Refreshing a form may lose unsent entries.

5. Google Analytics 4

With analytics consent and a configured Google property, we use Google Analytics 4 for website and form measurement. Google receives pseudonymous browser identifiers, page and event information, and browser/device and connection metadata. Our manual events omit form contents, names, email addresses, full query strings, and URL fragments. Google signals and advertising personalization are disabled in our tag configuration.

Google processes analytics data under the arrangements applicable to the configured property. Its retention settings are separate from the prepared 90-day first-party analytics cleanup target described below and do not apply to all aggregated reports. Contact us about the applicable property settings and transfer arrangements. Google’s privacy information is at https://policies.google.com/privacy.

6. Microsoft Clarity session recordings

With a configured Clarity project and your optional analytics consent, Microsoft Clarity records page interactions and produces session recordings and heatmaps to help improve the website. Microsoft receives browser/device and connection information, pseudonymous identifiers and eligible page URLs. Approved referral and campaign parameters may appear in those URLs; we do not promise Clarity strips every query parameter.

We apply masking to the fields you type into. Recordings are tagged with the same random first-party visitor and session identifiers that our own analytics store, so that an administrator can review the recording behind a submitted application. We do not send names, email addresses, application IDs or form text through Clarity identification calls. Private administration and email-preference pages, URL fragments and unknown or sensitive query parameters prevent the tracker from starting. Masking and these exclusions require verification in the configured project; do not enter confidential information into public forms.

Clarity stays absent before analytics consent and while no project ID is configured. We signal analytics storage consent only and deny advertising storage. Withdrawal signals denial and stops further collection on this document; previously collected recordings are not automatically erased. If you grant consent again after a stop, collection waits for the next eligible page document. Microsoft controls its data retention and processing arrangements separately from our first-party cleanup; see https://learn.microsoft.com/en-us/clarity/setup-and-installation/data-retention and https://privacy.microsoft.com/privacystatement.

7. Application emails and product updates

We send an application acknowledgement through the Clargus backend email system and its email delivery provider, Resend. If you separately check the email opt-in box, you subscribe to product updates and launch news when your application is saved. No additional email confirmation is required. You can apply without subscribing, and unsubscribe from updates through any update email. The application acknowledgement is separate from optional marketing.

We record the text/version you were shown, your affirmative checkbox opt-in and withdrawal times. These choices are separate from cookie preferences and Terms/Privacy acknowledgement. The prepared cleanup configuration keeps subscribed contact details while the subscription is active and targets deletion of unsubscribe records after three years and delivery/outbox records after 90 days, except records still marked sending. Legacy pending subscriptions are targeted for removal after 30 days; new checkbox opt-ins subscribe immediately and do not enter a confirmation flow. These cleanup routines and their scheduling have not been verified in the deployed database. We do not put tracking pixels in these landing-page emails.

8. Who receives information

Authorized Clargus personnel and providers helping host the website, store data, and handle requests may process information for those purposes. Supabase stores application, consent, analytics, publisher, and email preference records. Microsoft processes optional Clarity interaction recordings and analytics; Google processes optional Google Analytics data. Resend processes recipient addresses and message contents to deliver email through the Clargus backend. The current database region is East US (North Virginia). Infrastructure providers may process data in other locations.

We do not sell application details or give creators access to applicants’ names, emails, or research interests. Private institutional applications are not published. Creator application details are also private; choosing to become a creator does not authorize us to publish your application.

We may disclose information when required by law, to protect rights and safety, or in a business transfer subject to applicable safeguards. Where legally required for international transfers, we must use a permitted transfer mechanism, such as appropriate contractual safeguards. Contact us for the applicable arrangement.

9. Retention

The prepared cleanup configuration targets deletion after 24 months for pre-beta applications and their linked policy acknowledgements, 90 days for raw optional analytics events, and three years for pseudonymous cookie-choice records. A daily database schedule is configured only when the required scheduling extension is available; deployed scheduling and cleanup results must be verified before public launch. A referral cookie lasts up to 30 days; the cookie-choice cookie lasts up to 180 days. Active publisher business records remain while the relationship is relevant. Review of inactive publisher records after 24 months is an intended manual operating step; no automatic publisher-erasure job is enabled.

We may retain necessary records longer to meet a legal obligation or handle a specific dispute. Backups and provider logs follow the providers’ retention arrangements and may take additional time to expire. You may request earlier deletion where applicable.

10. Your choices and rights

Use Cookie settings in the footer to decline or withdraw optional tracking. This stops our future optional analytics events on this browser and removes our optional cookies, including accessible first-party Google Analytics and Clarity cookies when configured. Microsoft-domain cookies are controlled by Microsoft and browser settings. Withdrawal does not erase earlier vendor records or reverse earlier lawful processing. For access, correction, deletion, restriction, portability, or objection where available, email [email protected]. We may need proportionate information to verify your identity.

You may complain to the data protection authority for your location. Rights and applicable deadlines depend on the law that applies to you. Necessary application information is required to review your request; optional research details and optional cookies are not.

11. Security, age, and changes

We use access controls and separate public submission from administrative access. No system is completely secure. The website and pre-beta program are intended for adults aged 18 or older. Contact us if you believe a child has provided information.

We will publish material policy changes here and update the version. If the purpose of optional tracking changes, we will request a new choice before enabling it.