Browser512

Privacy notice

Adapted from the project launch draft in docs/PRIVACY.md.

Draft — not final. Preview only. This counsel-review draft covers Zero-Exposure Credential Access Preview. It requires jurisdiction-specific legal review and counsel approval before any sale. Company identity, data controller, retention/deletion process, and related legal facts are not filled in here.

Security review status: internal QA completed for the stated build; independent security audit not completed. The planned first Early Access cohort is invitation-only and limited to Windows x64. Enrollment is not open until counsel approves the exact published documents and the exact Windows installer passes Authenticode and physical-device QA.

Local workspace data

Browser512 stores workspace cookies, local storage, cached web content and browsing history locally inside each workspace partition. These records are not sent to Browser512 by default.

Updates and network metadata

Account, Trial, licensing and update services receive standard request metadata. The public Cloudflare edge derives HMAC hashes for the exact IP and network prefix; the Browser512 Licensing database is designed not to store the raw IP. It may store those risk hashes, an OAuth identity hash, device public-key hash, request time and entitlement state to prevent repeated Trials and protect paid access. The application does not include analytics, advertising SDKs, account tracking, remote browser control or hidden telemetry.

Licensing storage

A device key and short signed entitlement lease are stored using the operating system secure-storage facility. The Trial begins at first device activation. The private device key is not sent to Browser512; the service receives its public key and hash. Paid access can continue offline only for the bounded signed lease period.

Automation and credential Preview

The local Automation Bridge requires a visible Trusted Session scoped to a controller, workspace, website origin and permissions. Passwords and OTP values are designed not to be returned through connector or audit output. Target websites necessarily receive credentials submitted to them. Credential use is blocked when a loaded extension can access the target origin. This Preview remains subject to cross-platform and independent security review.

Private workspaces and extensions

Private workspaces use a temporary browser partition. Their cookies, cache and website storage are discarded when Browser512 exits; they are not anonymous to websites, networks or device operators. Extensions run with the permissions declared in their own manifests, so users should install only extensions they trust.

Third-party websites

Website operators receive the data that users choose to submit to their websites. Their privacy notices and terms apply independently. Customers are responsible for obtaining authority to use each account and website.

Unresolved for counsel / owner: named data controller; retention/deletion schedule; lawful bases, subprocessors, data-subject rights, international transfers and jurisdiction-specific disclosures. Do not treat this page as an approved privacy policy.