docs(device-admin): normalize contact references to role placeholders - #66
Merged
Conversation
verlyn13
changed the title
This repository is public. Six tracked files under docs/device-admin/ carried five third-party personal Google identities, three of them belonging to minors and correlated by given name with specific devices. Commit c0de37c redacted only the operator's own address and left these in place, in several cases within the same paragraph. Replace each address with a stable role placeholder, following the REDACTED-operator-google-account convention that commit already established: Ahnie -> REDACTED-ahnie-google-account (5 occurrences) Axel -> REDACTED-axel-google-account (5) Ila -> REDACTED-ila-google-account (4) Wyn -> REDACTED-wyn-google-account (17) (2nd adult, unnamed in the docs) -> REDACTED-adult-2-google-account (1) The placeholders preserve the identity-to-device mapping the profile design depends on while removing the contactable addresses. Given names were already present in these tables independently and are unchanged. Scope notes: - The five addresses appear only under docs/. policies/host-capability- substrate/tiers.yaml is byte-pinned by a sibling repo and contains only the operator's own address; it is deliberately untouched. - The addresses remain reachable in git history on the public remote. Closing that requires a separate history-rewrite decision.
… pass The initial sweep matched only @gmail.com and stepped over an @alaska.edu address sitting on the same line as a value it had already redacted -- the same failure mode as c0de37c, which is what an unautomated control looks like. This one is worth closing specifically: unlike the operator's gmail, the academic address is not exposed through commit metadata, so removing it from file content actually reduces a surface rather than being theater. The Happy Patterns business address on the same line is left in place -- that is the operator's own published business identity, not a personal identifier, and removing it is their call rather than a compliance fix.
verlyn13
force-pushed
the
fix/redact-third-party-pii
branch
from
August 29, 2026 07:16
e317340 to
17b6ea8
Compare
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
Remove personal contact information from six tracked device-administration documents.
Validation
main.docs/device-admin/files.Scope
This reduces exposure in the current repository tree. Existing Git history remains unchanged and is not rewritten by this PR.