Repository navigation
docs: disclose Safe Share data processing - #76
Merged
Merged
Conversation
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.
SeliaScan's privacy policy described OCR and barcode processing but omitted Safe Share's face detection. Disclose its on-device analysis, model download, SDK diagnostics, review limits, and the fact that redaction leaves originals and earlier shared copies intact. Add the same redaction limitation to the terms.
Verification: both edited diffs reviewed against the Safe Share implementation;
git diff --checkpasses. Isolated Chromium exercised all five website pages at 390px and 1280px, checked local links, UTF-8, image alternatives, keyboard skip links, no overflow or automatic external requests. Privacy body contrast is 6.58:1 light / 9.41:1 dark. Existing public pages return HTTP 200.Documentation only. No app/version/SDK/permission changes or Android release. Android tests were not run locally because the changed path is the static website; repository CI still applies. Existing operational support-retention rules remain subject to the publisher's actual procedure; this change does not certify all legal requirements.