Browser512

Privacy notice

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

Draft — not final. This notice is a launch draft. 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.

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

If automatic updates are configured, the app contacts the vendor update endpoint to check for a newer version. The endpoint may receive standard network metadata such as IP address and request time. The application does not include analytics, advertising SDKs, account tracking, remote browser control or hidden telemetry.

Licensing storage

License envelopes are stored using the operating system secure-storage facility. A licence includes only the fields the vendor issues, such as licence ID, customer name, tier and expiry; do not put passwords or personal data not needed for licensing into a license file.

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; support and privacy contact roles beyond the public mailbox below; retention and deletion process; jurisdiction- specific disclosures. Do not treat this page as an approved privacy policy.