Add privacy policy page - #66
Closed
sn0wm1ku wants to merge 1 commit into
Closed
Conversation
Add OSBR privacy policy covering authentication, data handling, third-party services, and user rights. Update sidebar config to include the new page under Policies. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
github-actions
Bot
added
the
ci-testing
Contributor
There was a problem hiding this comment.
Pull request overview
Adds an OSBR Privacy Policy page to the VitePress handbook documentation and links it from the sidebar so it’s discoverable alongside other policy documents.
Changes:
- Add new
doc/privacy-policy.mdcovering authentication, data handling, third-party services, and user rights. - Update VitePress sidebar config to include a “Privacy Policy” link under “Policies”.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
doc/privacy-policy.md |
Introduces a new privacy policy document page for the handbook site. |
doc/.vitepress/config.mts |
Adds the Privacy Policy entry to the “Policies” sidebar section. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+58
to
+61
| - We only use Google API data to provide and improve the user-facing features you interact with. | ||
| - We do not transfer Google API data to third parties unless necessary to provide the service, required by law, or with your explicit consent. | ||
| - We do not use Google API data for advertising or to build user profiles. | ||
| - We do not allow humans to read Google API data except with your consent, for security purposes, to comply with the law, or when data has been aggregated and anonymized for internal operations. |
There was a problem hiding this comment.
In Section 6, the bullet "We only use Google API data to provide and improve the user-facing features you interact with" can be read as using Google API data beyond passthrough (e.g., analysis/training), which conflicts with Section 3’s statement that API responses are “not stored, processed, or analyzed” on OSBR servers. Consider rewording to make these statements consistent (e.g., clarify whether any processing occurs and, if not, remove/qualify “improve”).
Suggested change
| - We only use Google API data to provide and improve the user-facing features you interact with. | |
| - We do not transfer Google API data to third parties unless necessary to provide the service, required by law, or with your explicit consent. | |
| - We do not use Google API data for advertising or to build user profiles. | |
| - We do not allow humans to read Google API data except with your consent, for security purposes, to comply with the law, or when data has been aggregated and anonymized for internal operations. | |
| - We only use Google API data to provide the user-facing features you request. Consistent with Section 3, Google API responses are passed directly to the requesting client and are not stored, processed, or analyzed on our servers. | |
| - We do not transfer Google API data to third parties unless necessary to provide the service, required by law, or with your explicit consent. | |
| - We do not use Google API data for advertising or to build user profiles. | |
| - We do not allow humans to read Google API data except with your consent, for security purposes, or to comply with the law. |
Member
Author
|
Migrated to #65 |
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.
Summary
doc/privacy-policy.md) covering authentication, data handling, third-party services, and user rightsTest plan
privacy-policy.htmlpresent in build output🤖 Generated with Claude Code