Repository navigation
docs: privacy and data-flow map (audited refs, backend-default decision) - #20
Draft
obvious-autobuild[bot] wants to merge 1 commit into
Draft
obvious-autobuild[bot] wants to merge 1 commit into
obvious-autobuild[bot] wants to merge 1 commit into
Conversation
Maps every outbound data flow (recipe generation, direct Gemini fallback, reverse-scan re-ranking, live assistant, notification sync, HealthKit), backend retention and logging, local-only storage, user controls and their gaps, and the open PR heads that touch data-flow surfaces. Includes the backend-default keep/opt-in/remove analysis with a recommendation. docs/check_refs.py re-verifies all 119 file:line refs (113 on main, 6 on PR heads); pass as of this commit.
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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
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.
What
Privacy and data-flow map for the iOS app and the gemini-agent backend, audited at
main@1151588d6bc6f5dcc3e848b6115813ff36ffbf0d, plus the still-open backend-default decision (keep cloud on by default / opt-in / remove) with a recommendation and what would reverse it.Covers
latestCameraFrame,lastUserMessage, mutation audit), tool-argument tracing, webhook body logging, no auth on/v1routes.Every factual claim carries a
file:lineref.docs/check_refs.pyre-verifies all 119 refs (113 on the audited main SHA, 6 on PR heads viagit show):Not included
No behavior changes. The keep/opt-in/remove analysis is documentation only; the recommended follow-ups (redact tool-arg/webhook logs, TTL for the live-session store) are named in the doc and deliberately not implemented here.
Verification
python3 docs/check_refs.pypasses on this branch (working tree at the audited main SHA).git show <head-sha>:<path>for fix(ios): save failed scans and show them in the scan report #133e6d321f, fix(ios): stop camera labels resolving to unrelated foods and record failed Vision requests #8a9df6aa3, feat(ios): let meal-photo confidence set how much the user confirms #530f34184, fix(ios): make the scan-to-meal loop work and log what was confirmed #48c9c88fe.