GruView Beta Privacy Policy

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.

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.

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.

Project and comment data may be retained until a user deletes it or until beta operations require cleanup.

A user can delete their own account from inside the workspace. That action deletes owned projects together with the account, while comments left in other projects may be anonymized to preserve collaboration history.

Audit logs may be kept longer than project body data when needed for security and operational review. During beta, GruView targets ordinary operational log review and cleanup within about 90 days unless a security or investigation need requires longer retention.

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.

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.

Questions about privacy, beta operations, or requests to access, correct, or delete account data can be sent to ljh8779@gmail.com.

Basic account deletion can be handled through the in-product self-service flow. Other requests may still require account verification or manual handling during beta.

The current beta stack may rely on Google for sign-in, Render for API and database hosting, Vercel for frontend delivery, and Cloudflare for DNS and edge security configuration.

If external object storage is enabled, uploaded source bundles or document binaries may also be stored in an S3-compatible bucket while the database keeps metadata and access control records.

If the infrastructure or processing vendors change, this policy will be updated accordingly.