gruview.com
GruView Beta Privacy Policy
This page describes the data GruView currently collects and processes in the beta product. If the processing scope changes, this policy will be updated before the feature is expanded.
Last updated: March 25, 2026
1. Data we collect
When you sign in with Google, GruView stores the basic profile data needed to operate the account: your name, email address, and profile image. GruView does not access Gmail, Drive, Calendar, or other separate Google data.
When you upload or collaborate on a project, GruView stores project names, file trees, text file contents, comments, invitation records, and access role assignments.
For security and operations, GruView may store audit events for actions such as sign-in, project creation, sharing, downloads, and deletion. These records can include IP address, user agent, and event timestamps.
2. How we use data
Collected data is used to authenticate accounts, decide project access, preserve collaboration history, diagnose issues, and keep the service operational.
The current beta Summary feature does not send project content to an external LLM. It organizes comments inside the service. If that processing model changes, this policy will be updated first.
3. Sharing with other users
If a project owner invites another user, that invited user can view the project name, files, comments, summaries, and activity records needed for collaboration. The exact scope depends on whether the user is an owner, editor, or viewer.
Invite links are used to connect access to a specific project. A recipient still needs to sign in with the invited Google account before the permission is activated.
4. Retention and deletion
Project and comment data may be retained until a user deletes it or until beta operations require cleanup.
Audit logs may be kept longer than project body data when needed for security and operational review. During beta, GruView aims to avoid retaining data longer than necessary.
5. Security and beta limitations
GruView uses private projects and role-based access control, but as a beta service it does not guarantee uninterrupted availability or complete protection against every possible security threat.
Before uploading sensitive or regulated source code, users should evaluate whether a public beta collaboration environment is appropriate for that material.
6. Policy changes
This policy will be updated when the product structure or data handling changes. Material changes may be announced through the sign-in experience, product notices, or release updates.