Cookie Policy — Relm Pro

This Cookie Policy explains what cookies and similar technologies we use on the Relm Pro platform at relm.ai, what each category does, and how you can change your preferences at any time. It supplements our Privacy Policy.

1. What are cookies?

Cookies are small text files that a website saves on your device when you visit. They're widely used to make sites work efficiently and to provide reporting information to site owners. We also use related technologies such as local storage (browser-side key/value storage) and pixels (tiny images used to confirm an email was opened).

2. The categories we use

2.1 Strictly necessary

Required for the platform to work. We can't turn these off in our systems and they don't require your consent under applicable law because the service can't be delivered without them. Examples:

Authentication & session — Clerk session cookies (__session, __client_uat) that keep you signed in and prevent CSRF.
Anonymous browser id — relm_anon_id (a random UUID) so we can correlate consent events from the same browser.
Consent state — relm_consent_ack and the per-category preference cookies that record what you selected on the cookie banner.
Security — rate-limit and bot-detection cookies set by our hosting provider (Vercel) and authentication provider (Clerk).

2.2 Analytics

First-party product analytics that tell us which features are reliable, fast, and useful. We do not load any third-party analytics scripts that build cross-site profiles. Analytics cookies expire within 12 months.

2.3 AI training

Marks whether you've consented to letting us use de-identified usage data and AI chat interactions to evaluate and improve our research agents. We do not train models on your uploaded documents or on personally identifiable information without separate, explicit consent. Turning this off does not change product functionality.

2.4 Marketing

Reserved for personalized communications about new features and occasional newsletters. Off by default. We do not currently load third-party advertising pixels (Google Ads, Meta Pixel, LinkedIn Insight, etc.). If we ever start, we'll update this policy and re-prompt your consent.

3. Cookies we set

Name	Category	Purpose	Expires
__session	Necessary	Clerk authenticated session.	Session
__client_uat	Necessary	Clerk client-side auth state.	1 year
relm_anon_id	Necessary	Anonymous browser id for consent correlation.	1 year
relm_consent_ack	Necessary	Timestamp of your most recent consent decision.	1 year
relm_consent_analytics	Necessary	Whether you've allowed analytics cookies.	1 year
relm_consent_ai_training	Necessary	Whether you've allowed de-identified AI training use.	1 year
relm_consent_marketing	Necessary	Whether you've allowed marketing cookies.	1 year

4. Audit log of consent decisions

When you accept, reject, or change preferences on the cookie banner, we record the event server-side so we can demonstrate compliance if asked. Each row contains:

The anonymous browser id from relm_anon_id
Your signed-in user id, if any (otherwise null)
Which categories you accepted or rejected
A SHA-256 hash of your IP address (salted with a server-side secret) so we can detect spam without storing the raw IP
Your User-Agent string
The action (accept all, reject non-essential, customize, revoke)
A timestamp

We never sell or share these logs. They're retained for as long as necessary to demonstrate compliance — typically up to seven (7) years — and then deleted.

5. Changing or revoking your consent

You can change your cookie preferences at any time by clicking the button below. Revoking consent reopens the banner and writes a new audit row capturing the change.

You can also configure your browser to block or delete cookies entirely. Doing so will sign you out and may degrade some platform features (for example, the chat assistant won't be able to keep your session warm between page loads).

6. Third-party services

Several services we depend on may set their own cookies. We list the principal ones below; for the most current set, see each provider's policy directly.

Clerk — authentication and session management
Vercel — hosting, edge cache, and bot protection
Stripe — payments (only set on the checkout page)
Sentry — first-party error and trace telemetry
Resend — transactional and newsletter email delivery (no in-browser cookies; pixel tracking only on opt-in newsletter emails)

7. Do Not Track and Global Privacy Control

We currently do not respond to browser “Do Not Track” signals because the standard has been deprecated. We do plan to honor the Global Privacy Control (GPC) signal as adoption stabilizes. In the meantime, the cookie banner gives you direct per-category control.

8. Changes to this policy

We may update this Cookie Policy from time to time. When we do, we'll bump the “Last updated” date at the top of this page and, if the change is material, re-prompt your consent on your next visit.

9. Contact us

Questions about cookies or consent? Email legal@relm.ai.

Relm, Inc. — Cookie Policy