Privacy, plainly stated.

First-party measurement with a clear choice.

The website records four anonymous events: a page was viewed, a download was clicked, a ScientFactory download redirect failed, or an external link was clicked. These events help us understand which pages and installers are useful and whether the download service is working.

With “Essential only,” each event receives a new event-specific identifier. The database stores the time, page path, and only the details needed for that event—for example, the installer type or destination website and path. Query strings are discarded. These counts describe events, not unique people or a person's journey through the site.

If you choose “Allow analytics cookies,” we set a random first-party visitor identifier for up to 180 days and create a temporary identifier for the current browser session. This lets us measure returning visits, sessions, and the path from page view to installer download. The identifiers are random: they are not derived from your name, email address, device fingerprint, IP address, or account with another service.

ScientFactory stores events and consent records first in its Cloudflare database. Pseudonymous copies may also be processed in ScientFactory's EU-hosted PostHog project so we can analyze usage and retention. You can change your choice at any time through “Cookie settings” in the footer; choosing “Essential only” removes the persistent visitor cookie.

ScientFactory does not use advertising trackers, browser fingerprinting, behavioral session recording, or cross-site tracking on this website. Research content is never included in website analytics events.

Standard infrastructure data may be processed to deliver the site.

The website is delivered through Cloudflare. Like other web infrastructure providers, Cloudflare may process standard request information such as an IP address, browser type, timestamp, and requested page to operate, secure, and troubleshoot the service.

Installer delivery is completed by GitHub.

The download page checks ScientFactory's release endpoint, which validates the public attested GitHub release handoff before locating an installer. Your browser does not bypass that validation by querying the GitHub API directly.

When you choose an installer, your browser first requests a ScientFactory download address. The website records the download click and redirects the browser to the official GitHub release file. A download_failed event means our website could not resolve or start that redirect; it cannot detect a later transfer failure after GitHub begins serving the file. GitHub processes the resulting file request under its own privacy terms.

Release details may be cached temporarily in your browser's session storage for up to 15 minutes. This avoids repeating the same release lookup and is cleared with the browser session.

Desktop measurement is controlled separately inside Scient.

Scient runs as a workspace layer on your computer. Builds with analytics available let you choose Off, Essential reliability, Product improvement, or Diagnostics in Privacy and analytics. The default is Off; making the feature available does not change your saved choice. Desktop events use a random installation identifier and never derive identity from a connected AI-provider account.

Normal product analytics exclude prompts, assistant responses, research documents, filenames, file paths, URLs, source text, generated scientific content, credentials, provider account identities, and raw error messages. Scient does not use desktop autocapture or session replay. When you use a connected AI provider, that provider receives the prompts and supporting context needed for the session under its own terms and privacy policy. This website notice does not replace those terms.

Shared desktop events go to ScientFactory's central Cloudflare storage. Diagnostic-only events stay there, with scheduled removal after 30 days; other raw events are scheduled for removal after 180 days. Product and reliability events may also be processed in our EU-hosted PostHog project under PostHog-managed retention. We do not promise those downstream copies are physically deleted within the same periods. Local unsent events are filtered by age before delivery, and cleanup runs while the app is running.

An enabled build lets you request deletion for the current installation. Scient clears its local analytics state after the first-party gateway accepts the request and replaces the random analytics identifier. Downstream removal of the matching PostHog profile and events is processed separately; acceptance does not mean every copy is already gone. A minimal deletion receipt and identifier-verification record remain to prevent delayed retries from recreating deleted history. They contain no usage events or research content.

We will update this page when the website changes.

If we add Scient accounts, forms, or additional identity links, this notice will be updated before those features are enabled for visitors.