skip to content
privacy · last updated 2026-05-19

Plainly: the engine never phones home.

Conifer runs locally. The model, the prompts, the generated tokens — none of it leaves your machine. This page covers the few places where data does cross the wire: the website, the account system, and the install download.

01
conifer (desktop / cli / library)

What the engine sends

Nothing. The native engine has no analytics, no error reporting, no model-usage telemetry, and no auto-update ping. Prompts and generations stay on your disk and your accelerator.

The desktop app does two network calls, both initiated by you: downloading models you ask for from huggingface.co and checking for updates when you click the button. Neither call sends us anything we couldn’t see in a server log we don’t run.

02
conifer.build

What the website logs

This site is a static export served by Cloudflare Pages. Cloudflare keeps an edge access log (IP, user agent, requested URL, response status) for fraud and abuse handling. We don’t run our own analytics; no Google Analytics, no Plausible, no Segment, no Mixpanel — and we’d like to keep it that way.

The Conifer site sets no cookies of its own. Your sign-in session lives in localStorage on your device and is never read by us. Cloudflare may set its own fraud-protection cookies on certain network paths; those are governed by Cloudflare’s privacy policy.

03
supabase

Account

An account is one row in a database:

email
The address you signed up with. Used only to send the magic link, contact you about your account, and key your download eligibility.
created_at
Timestamp of first sign-in.
last_sign_in
Timestamp of the most recent magic-link click.

We do not store passwords (the magic link replaces them). We do not store IP addresses against your account. We don’t profile your usage of the engine from your account row — there’s nothing to profile, since the engine never reports back.

Auth runs on Supabase. Their privacy policy: supabase.com/privacy.

04
stripe (when applicable)

Payments

Conifer is free during beta. When paid tiers launch, payments go through Stripe. We never see your card details — Stripe holds them. We receive a customer ID and a subscription state, which we store next to your account row. Stripe’s privacy policy: stripe.com/privacy.

05
/feedback

Feedback & waitlist forms

If you send us feedback, request a private build, or join the waitlist, we store what you sent (email + message + the form- specific fields you filled in) in the same Supabase project. We read it. We may reply. We don’t share it. We delete it on request — see your rights below.

06
/chat

Browser surface

The browser surface (/chat) is a WebLLM playground that runs entirely client-side. Model weights come down to your browser’s IndexedDB and stay there. Prompts are processed in a Web Worker on your machine. Nothing about your prompts or generations leaves the browser tab.

07
how to get your data out or deleted

Your rights

Write to [email protected] from the address tied to your account and ask for a copy, a correction, or a deletion. We’ll do it within 30 days and confirm when it’s done. EU/UK residents have the rights enumerated under GDPR; California residents have the rights enumerated under CCPA. Both reduce, in practice, to the email above.

08
under-13s

Children

Conifer isn’t intended for children under 13 and we don’t knowingly collect data from them. If you learn that a child has signed up, write to the address above and we’ll delete the account.

09
when this page updates

Changes

Material changes to this policy are announced on this page and, for active accounts, by email. The date at the top is the most recent revision.