Privacy

Clear about the data that makes the service work.

Jacobi stores the account, workspace, target, and evidence information needed to run the audits you request and show the resulting record back to your workspace.

Privacy Policy v0.9Last reviewed Jun 26, 2026
01 ]Privacywe do not sell submitted URLs
Privacy at a glance

We collect the operational data required for an audit workspace.

Account access

Supabase authentication identifies the account that can access a workspace.

Workspace evidence

Watchlists, URLs, observations, findings, exports, and audit records support the review workflow.

Controlled sharing

External shares are optional, redacted when configured, time-limited, and revocable.

Data ledger

What we handle and why.

DataWhy it is usedWhere it comes from
Account and workspace identityAuthenticate access, associate workspaces, and apply role-based controls.Your sign-in through Supabase Auth.
Submitted URLs and watchlist detailsRun requested audits and retain the monitored record.Your workspace input.
Audit observations and findingsShow prices, coverage, extraction context, and policy results back to the workspace.Responses to the target URLs you submit.
Exports and share recordsProvide evidence packages and track controlled sharing or revocation.Actions taken by authorized workspace members.
Sharing and processors

Service providers operate the product — they do not resell your workspace.

Supabase provides authentication and Postgres-backed workspace storage. BrightData may be used for managed requests when a live audit is explicitly run. Stripe is configured in test mode; Jacobi does not store full card numbers.

We do not sell submitted URLs or audit results. We do not use them to train a product for resale. We do not publish a workspace's data unless an authorized member creates a share link.

About public shares: a redacted share converts exact URLs to domains and removes internal workspace identifiers, probe session identifiers, and extraction metadata. The creator can revoke it.

Your controls

Access is designed around the workspace.

  • Private workspace operations require sign-in and are checked against workspace membership and role permissions.
  • Production enterprise persistence fails closed when its database configuration is missing rather than silently serving an ephemeral workspace.
  • For a privacy question or a request concerning your account data, contact wearejacobi@outlook.com.
  • This pilot-era notice describes current service behavior. Jurisdiction-specific rights, retention periods, international-transfer terms, and any paid-service terms should be legally reviewed before a broader public launch.

See Terms of Service for acceptable use and service limitations.