1. Scope and operator
Sabya Personal OS is a private productivity and personal knowledge system operated by Sabya Das for the operator and personal accounts the operator is authorized to use. It is not offered to the public. This documentation site contains no application interface, account login, analytics, advertising, or form-based data collection.
Questions or requests concerning this policy can be sent to sabya@sabya.co.
2. Google data the system accesses
The Google Cloud project declares permissions that may be used for the operator’s personal workflows. The current authorization flow requests the 42 scopes listed below. A particular connection receives only the permissions Google reports as granted after approval on its consent screen; configuring or requesting a scope does not by itself grant access.
| Service | Data or action | Purpose |
|---|---|---|
| Identity | Google account identity and primary email address | Confirm which authorized account is connected. |
| Gmail | Email metadata, messages, attachments, labels, drafts, sending, and account settings, depending on the scopes granted | Retrieve, organize, search, summarize, draft, send, and maintain email at the account holder’s direction. |
| Drive, Docs, Sheets, Slides, and Forms | Files, metadata, activity, documents, spreadsheets, presentations, forms, Drive apps, and supported Photos or Meet-created files; permissions can include reading, creating, editing, and deleting | Retrieve, organize, index, search, summarize, create, and update the account holder’s working materials. |
| Calendar | Calendars, access rules, settings, availability, and event details; permissions can include reading, creating, editing, sharing, and deleting | Provide schedule context, planning, availability, reminders, and account-holder-directed calendar actions. |
| Contacts and directory | Personal contacts, other contacts, and Workspace directory profiles; permissions can include reading, creating, editing, and deleting contacts | Find people, maintain contact records, and resolve collaborators for account-holder-directed workflows. |
| Tasks | Task lists and tasks; permissions can include reading, creating, editing, completing, moving, and deleting | Plan and maintain the account holder’s tasks and follow-ups. |
| Google Chat | Spaces, memberships, messages, reactions, availability, read state, and associated metadata; permissions can include creating, editing, sending, and deleting | Retrieve collaboration context and perform account-holder-directed Chat actions. |
| Google Meet | Meet spaces and settings, including spaces created by the system | Create and configure meetings and retrieve conference information. |
| Apps Script | Script projects, deployments, processes, and metrics | Inspect and maintain the account holder’s private Workspace automations. |
| Google Cloud | Cloud projects and data in services such as BigQuery, Cloud Storage, Dataplex, Datastore, Logging, Monitoring, Trace, and Service Management | Operate, inspect, and maintain the account holder’s private cloud workloads when a workflow requires it. |
| Other requested Google services | Google Play developer and games data, Maps tooling, Street View publishing, Drive app activity, and Generative Language models or retriever content | Support the operator’s specific developer, mapping, media, and AI-assisted workflows. |
Write or destructive actions are used only for an operator-requested workflow. The operator should review each Google consent screen because some requested scopes, if approved, permit creating, changing, sharing, sending, or deleting data.
Exact scopes in the current Google OAuth authorization request
As of September 1, 2026, the current authorization flow requests 42 scopes. Google determines and may revise each scope’s sensitivity classification. Full requested scope strings are listed below.
Requested scopes (42)
https://www.googleapis.com/auth/userinfo.emailhttps://www.googleapis.com/auth/userinfo.profileopenidhttps://www.googleapis.com/auth/androidpublisherhttps://www.googleapis.com/auth/calendarhttps://www.googleapis.com/auth/spreadsheetshttps://www.googleapis.com/auth/cloud-platformhttps://www.googleapis.com/auth/documentshttps://www.googleapis.com/auth/drivehttps://www.googleapis.com/auth/drive.meet.readonlyhttps://www.googleapis.com/auth/drive.appshttps://www.googleapis.com/auth/drive.apps.readonlyhttps://www.googleapis.com/auth/drive.activityhttps://www.googleapis.com/auth/drive.photos.readonlyhttps://www.googleapis.com/auth/drive.appdatahttps://www.googleapis.com/auth/drive.scriptshttps://www.googleapis.com/auth/generative-language.tuninghttps://www.googleapis.com/auth/generative-language.retrieverhttps://www.googleapis.com/auth/generative-language.peruserquotahttps://mail.google.com/https://www.googleapis.com/auth/gmail.settings.basichttps://www.googleapis.com/auth/gameshttps://www.googleapis.com/auth/maps-platform.mapstoolshttps://www.googleapis.com/auth/iam.testhttps://www.googleapis.com/auth/streetviewpublishhttps://www.googleapis.com/auth/contactshttps://www.googleapis.com/auth/contacts.other.readonlyhttps://www.googleapis.com/auth/directory.readonlyhttps://www.googleapis.com/auth/taskshttps://www.googleapis.com/auth/chat.spaceshttps://www.googleapis.com/auth/chat.membershipshttps://www.googleapis.com/auth/chat.messageshttps://www.googleapis.com/auth/chat.deletehttps://www.googleapis.com/auth/chat.users.availabilityhttps://www.googleapis.com/auth/chat.users.readstatehttps://www.googleapis.com/auth/meetings.space.createdhttps://www.googleapis.com/auth/meetings.space.readonlyhttps://www.googleapis.com/auth/meetings.space.settingshttps://www.googleapis.com/auth/script.projectshttps://www.googleapis.com/auth/script.deploymentshttps://www.googleapis.com/auth/script.metricshttps://www.googleapis.com/auth/script.processes
3. How Google user data is used
Authorized data is used to provide the account holder with private features such as:
- retrieving and normalizing messages, documents, attachments, and events;
- building private search indexes and contextual memory;
- finding information and relationships across authorized sources;
- summarizing content and answering the account holder’s questions;
- preparing personal briefs, reminders, drafts, and next actions; and
- sending email only when the account holder directs or approves the send action.
Google user data is not used by the operator for advertising, sold, or used to build a public user profile.
4. Storage and retention
The system can copy authorized Google content and derived text into private, operator-controlled working storage, search indexes, and backups. OAuth credentials are kept separately in access-restricted credential storage. Google user data is not stored on this public documentation site.
Stored content and derived indexes can be retained for the life of the operator’s personal archive or until the operator deletes them. There is currently no promised automatic deletion interval. Deleting an item in Google or revoking OAuth access stops or limits future access but does not automatically delete copies or derived data already stored by the system. Backup copies may remain until they are manually deleted or overwritten during ordinary backup maintenance.
5. AI-provider processing and other transfers
When an AI-assisted feature is used, the system may send selected Google content, extracted text, relevant search context, or a user-provided file to OpenAI and/or Anthropic. Those providers may perform functions such as embeddings, transcription, document or image analysis, summarization, and answer or draft generation. Transfers are limited to operating or improving the user-facing feature requested by the account holder; the operator does not transfer Google user data to those providers for advertising or data brokerage.
Google user data may otherwise be disclosed only:
- to service providers needed to operate the account holder’s requested feature;
- to a person the account holder specifically authorizes to assist with the private system;
- when reasonably necessary to investigate a security incident; or
- when required by applicable law.
6. Security
The operator uses scoped OAuth grants, access-restricted credentials, and private systems intended only for authorized personal use. The project includes some broad permissions; operational use is limited to the feature requested by the account holder. Reasonable steps are taken to reduce unauthorized access, disclosure, alteration, or loss. No system can guarantee absolute security, and this policy does not claim that all stored data is encrypted.
7. Account control, revocation, and deletion
An account holder can revoke the system’s future Google access from the Google Account connections page. The account holder can also request deletion of locally stored Google content and derived indexes by emailing sabya@sabya.co. The operator may verify the requesting identity and will identify the active data and backup copies covered by the request before deletion. Revocation alone does not delete previously stored copies.
8. Changes to this policy
This policy will be updated before Google user data is used for a materially different purpose. The effective date above will change when the policy is revised.