docs(privacy): correct privacy policy + README to match actual app behavior#218
Merged
Conversation
…havior Pre-Play-submission accuracy pass, two-reviewer cycle (fact-checker + adversarial Play-policy reviewer). Fixes: Privacy policy: - DNS Monitoring: retract false "resolved locally / no traffic to external servers" claim — blocked domains get a local NXDOMAIN, allowed queries are forwarded to Google Public DNS (8.8.8.8) over UDP/53; disclosed honestly incl. Data Safety in-transit line - Network table: add CISA KEV + OSV endpoints (CveRepository), add HaGeZi blocklist feed, drop stale MalwareBazaar direct-API row (descoped #146; cert feed is a network-silent stub), ioc-data 5→6 GETs (OEM prefixes) - Permissions: document PACKAGE_USAGE_STATS (optional usage-access for the forensic timeline) and FOREGROUND_SERVICE_SPECIAL_USE - Retention: DNS events AND forensic timeline events auto-prune at 30 days; scan history indefinite; report log 300→500 lines; integrity check best-effort wording; encrypted-at-rest Android 8-9 caveat; 5→six-gate pipeline description; last-updated 2026-06-12 README: - "No data transmitted to any server" → accurate feeds + optional-DNS wording - rules-repo URL yasirhamza/android-sigma-rules → android-sigma-rules/rules - privacy link → /privacy route Comment-only code changes: stale "not Play-Store-reviewed" wording in AndroidManifest.xml and DnsVpnService.kt KDoc. cloudflare-worker.js re-rendered via scripts/render_privacy.py (11/11 tests). Dormant ZimperiumIocFeed tracked separately as #217. Closes #15 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pre-Play-submission accuracy pass over docs/PRIVACY_POLICY.md, README.md, and the rendered worker page. Every claim verified against code by two review agents (fact-checker: APPROVE after verification; adversarial Play-policy reviewer: 3 blockers found and fixed, re-review verified all fixes byte-level against DnsVpnService/CveRepository/UsageStatsScanner).
Key corrections:
Verification: render_privacy.py invariants hold (18 H2 / 3 tables), 11/11 render tests, compileDebugKotlin clean (comment-only code changes). Follow-up: #217 (dormant ZimperiumIocFeed).
Closes #15
🤖 Generated with Claude Code