docs(privacy): disclose runtime rule fetches + decoupling story#169
Merged
Conversation
The Network Requests table omitted three real egress paths:
- SIGMA rule manifest + per-rule YAML downloads (SigmaRuleFeed)
- Centralized IOC YAMLs from android-sigma-rules/rules/ioc-data/
(PublicRepoIocFeed)
- User-configured custom rule URLs (Settings → Custom Rule Sources)
The Open Source Transparency section also did not articulate that
detection logic lives in an independent public repo, decoupled from
the compiled app — a core trust property for high-risk users.
Adds three table rows + a "Detection rules live in a separate, public
repository" subsection. Re-renders cloudflare-worker.js so the PR-time
sync check passes.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
yasirhamza
pushed a commit
to yasirhamza/androdr-site
that referenced
this pull request
Apr 28, 2026
…closure) Sync of docs/PRIVACY_POLICY.md following yasirhamza/AndroDR#169: adds three rows to the Network Requests table (SIGMA rule downloads, centralized IOC data, optional custom rule URLs) and a new "Detection rules live in a separate, public repository" subsection. Co-Authored-By: Claude Opus 4.7 (1M context) <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.
Summary
The privacy page had two real gaps surfaced while discussing AndroDR's positioning vs. consumer adblockers:
SigmaRuleFeed.kt)android-sigma-rules/rules/ioc-data/(PublicRepoIocFeed.kt)Both are now disclosed:
### Detection rules live in a separate, public repositorysubsection under Open Source Transparency that explains the YAML-rules-as-data approach, the public 5-gate validation pipeline, and thevalidation/rule-schema.jsoncontract.cloudflare-worker.jsre-rendered viascripts/render_privacy.pyso the PR-time sync check (#167) passes.Test plan
Check privacy syncworkflow passes (worker is in sync with markdown).python3 scripts/render_privacy.py docs/PRIVACY_POLICY.md cloudflare-worker.jsa second time printsno change.##sections were added or removed (renderer'sEXPECTED_H2 = 18invariant unchanged).EXPECTED_TABLES = 3invariant unchanged — only rows added to the existing Network Requests table).docs/PRIVACY_POLICY.md(e.g., on the github.io page after merge) and confirm the new rows appear above the closing paragraph and the new subsection appears between the audit links and the "Google Play Data Safety Alignment" section.🤖 Generated with Claude Code