Your learning data is designed to stay local.

Last updated: 2026-09-03. This page describes the behavior of the application contained in this repository. Hosting providers can still receive ordinary web-request metadata when they deliver the static site.

Local datasets and model training

CSV files selected in the application are parsed in the browser. The application does not require a server-side ML API to train the included models, and the production host is designed to serve static HTML, CSS, JavaScript, worker files, and assets.

Browser storage

Learning progress, experiments, workspace notes, and related state may be stored in browser storage on your device so the application can restore your work. You can remove this data using the application's reset controls where available or by clearing site data in your browser.

Hosting logs

Like most websites, the static hosting provider or reverse proxy may process connection information such as IP address, request path, timestamp, user agent, and security/error logs. That infrastructure data is separate from the contents of local CSV files and model calculations.

Optional community contributor data

When the Origen contributor wall is enabled, the browser can read approved public contributor records directly from Supabase. Published records are limited to public-facing credit such as a chosen display name, profile image URL, contribution summary, product/category, dates, and an optional public profile link. Model datasets and model-training calculations do not use this service.

The public Contribute shortcut can open a separately configured external form provider. Information submitted there is governed by the form shown to the contributor; private model datasets and sensitive security details should not be submitted through a public form.

Analytics, advertising, and accounts

The production build in this package does not include an advertising SDK, cross-site tracking script, cloud account system, or analytics service. If those are added later, this notice should be updated before deployment.

Permissions

The supplied production security policy disables camera, microphone, geolocation, payment, and USB permissions because the current application does not need them.

Questions and changes

This repository does not embed a public support email address. The site owner should add a verified contact method before collecting user enquiries or other personal information.