Skip to content

docs: privacy policy for the extension and byte.vet sync - #75

Merged
SYM01 merged 1 commit into
mainfrom
develop
Oct 29, 2026
Merged

SYM01 merged 1 commit into
mainfrom
develop

Conversation

@SYM01

@SYM01 SYM01 commented Oct 29, 2026

Copy link
Copy Markdown
Collaborator

Summary

Adds PRIVACY.md. The Chrome Web Store requires a privacy policy now that sync sends user data to byte.vet. Once merged, the store listings (Chrome, Edge, Firefox) can link https://github.com/bytevet/proxyverse/blob/main/PRIVACY.md.

It covers:

  • what stays in the browser, and the extension's own network requests (PAC downloads, the proxy-credential warm-up, byte.vet when signed in);
  • what sync stores on byte.vet, how it's encrypted (contents per account; not end-to-end, metadata not encrypted by byte.vet), and how long it's kept;
  • processors (Cloudflare, GitHub or Google), deletion, and what each permission is for.

Docs only: no code changes, nothing to release.

Before relying on it

  • byte.vet offers account deletion online, as the policy says. As of bytevet/webapp 7b7cc3b there's no account or "delete all synced data" option.
  • admin@byte.vet receives mail.

🤖 Generated with Claude Code

Required by the Chrome Web Store now that sync sends user data to
byte.vet. Covers what stays in the browser, the extension's own network
requests, what sync stores and for how long, encryption, processors,
deletion and permissions.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@SYM01
SYM01 merged commit a2617df into main Oct 29, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant