Alobert Connect Privacy Policy#

Effective date: 29 October 2026

This Privacy Policy explains how Alobert Connect (the “Service”), operated by the owner of alobert.com (“I”, “me”), accesses, uses, stores, shares and deletes data, including data received from Google APIs. It also covers the alobert.com website.

1. Who the Service is for#

Alobert Connect is a private, self-hosted tool. It is used only by me and only connects Google accounts that I own. It is not offered to the public, has no sign-up, and cannot be connected by other people: the OAuth flow can only be started from an admin console that is not publicly accessible and requires my admin credentials.

2. Data collected and how each permission is used#

Alobert Connect collects Google user data only from my own Google accounts, only after I grant access on Google’s consent screen, and only for the purpose listed next to each permission. “Kept” means kept on my server after the request finishes.

Permission (OAuth scope)Google user data accessedWhy it is usedKept?
openid, email, profileAccount ID, email address, name and profile picture URLShow which of my accounts is connectedAccount ID and display name, as the connection label
drive, drive.fileFiles and folders in Google DriveUpload, list, download, verify and delete the encrypted backup files the Service writes; open files I ask forAction log only. Backups are encrypted before upload
drive.readonly, drive.metadata.readonlyFile contents and metadata (name, size, dates, folder)Find backup files and check their size and integrity; locate files I ask forAction log only
gmail.readonlyEmail messages, threads and attachmentsSearch and read my email to produce the summaries and notifications I ask forAction log only
gmail.modify, gmail.labelsMessage labels and read/archived state; label listApply labels, mark as read and archive messages when I askAction log only
gmail.compose, gmail.sendDrafts; outgoing messagesCreate a draft or send an email only when I explicitly askAction log only
gmail.settings.basicBasic mail settings such as filters and labels settingsRead or adjust my filters when I askAction log only
documents, documents.readonlyGoogle Docs contentRead, create and update documents I ask for, such as reports and work logsAction log only
spreadsheets, spreadsheets.readonlyGoogle Sheets contentRead, create and update spreadsheets I ask forAction log only
presentations, presentations.readonlyGoogle Slides contentRead, create and update presentations I ask forAction log only
forms.body, forms.body.readonly, forms.responses.readonlyForm content and form responsesRead my forms and their responses and edit forms I ask forAction log only
calendar and related calendar.* scopesCalendars, events, free/busy, calendar settings and sharingRead my agenda and create or update events and calendars I ask forAction log only
tasks, tasks.readonlyTask lists and tasksRead, create and complete tasks I ask forAction log only

Besides the connection label, the Service keeps only:

  • the encrypted OAuth access and refresh tokens needed to call Google APIs;
  • the action log described in section 4, which holds short, size-limited excerpts of each request and result.

The Service does not collect payment data, location, contacts, device identifiers, browsing activity or any data about people other than me. The full scope URLs are listed on the Alobert Connect page.

3. How the data is used#

Google user data is used only to provide features that I request:

  • creating, verifying and restoring encrypted backups of my servers in my Google Drive;
  • summarizing, searching, labelling and archiving my email, and drafting or sending a message only when I explicitly ask;
  • reading, creating and updating my documents, spreadsheets, presentations, forms, calendar events and tasks on request.

Google user data is not used for advertising, is not sold, is not used to build user profiles, and is not used to develop, improve or train generalized artificial intelligence or machine learning models.

4. Storage and security#

  • The Service runs on hardware that I own. Its admin console and API require authentication and are not open to the public; only the OAuth callback address that Google redirects to is reachable from the internet.
  • OAuth access and refresh tokens are encrypted with AES-256-GCM before they are stored on that server.
  • Google data is fetched on demand and returned to the requesting automation. Apart from the action log below, it is not kept.
  • Server backups stored in Google Drive are encrypted on my server before upload; Google Drive only receives ciphertext.
  • For troubleshooting, the Service keeps an action log of the most recent 5,000 actions. Each entry has the action name, time, outcome and a size-limited summary of the request and the result: every text value is cut to 256 characters, each entry is capped at 16 KB, and credentials such as tokens and passwords are removed. For email or document actions the summary can include short excerpts such as subjects, addresses or snippets. When the limit is reached the oldest entries are deleted.
  • All traffic between the Service and Google uses HTTPS.

5. Sharing and transfer#

I do not share, sell or transfer Google user data to third parties, with these limited exceptions:

  • AI processing at my request. When I ask my personal AI assistant to work with my Google data (for example “summarize today’s email”), the content needed for that request is sent to the AI model API that processes it, only to produce the answer I asked for. It is not used to train generalized models.
  • Legal requirements. If required by applicable law.

No human other than me reads Google user data processed by the Service.

6. Google API Services User Data Policy#

Alobert Connect’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

7. Retention and deletion#

  • OAuth tokens are kept until the connection is removed. Removing a connection in the admin console deletes its stored tokens.
  • Access can also be revoked at any time at https://myaccount.google.com/permissions.
  • Backup files remain in my Google Drive until I delete them or the backup retention policy prunes old snapshots.
  • Action logs are rotated automatically as described above.
  • The Service only holds data from my own Google accounts and collects no data about other people, so deletion is done directly by me using the steps above.

8. The alobert.com website#

The blog does not use accounts, analytics trackers or advertising cookies. It stores only your colour-theme preferences in your browser’s local storage. The site is served through Cloudflare, which processes standard request data (such as IP address) to deliver and protect the site.

9. Changes#

If this policy changes, the updated version will be posted on this page with a new effective date.


隐私政策(中文)#

生效日期:2026 年 10 月 29 日

本政策说明 Alobert Connect(以下简称”本服务”,由 alobert.com 站长运营)如何访问、使用、存储、共享和删除数据,包括通过 Google API 获得的数据,同时适用于 alobert.com 网站。若中英文版本不一致,以英文版本为准。

1. 服务对象#

本服务是私有的自建工具,只供我本人使用,只连接属于我的 Google 账号。不对外开放、没有注册入口,其他人无法接入:OAuth 授权只能从需要管理员凭据、不对公众开放的管理后台发起。

2. 收集的数据与各项权限的用途#

Alobert Connect 只从我本人的 Google 账号获取数据,只在我于 Google 授权页面同意后获取,并且只用于下表中每项权限对应的用途。“是否保留”指请求结束后是否仍保留在我的服务器上。

权限(OAuth scope)访问的 Google 用户数据用途是否保留
openid、email、profile账号 ID、邮箱、姓名和头像链接显示已连接的是哪个账号保留账号 ID 和显示名称,作为连接标签
drive、drive.fileGoogle Drive 中的文件和文件夹上传、列出、下载、校验和删除本服务写入的加密备份;打开我指定的文件仅在操作日志中;备份在上传前已加密
drive.readonly、drive.metadata.readonly文件内容和元数据(名称、大小、日期、所在文件夹)查找备份文件并检查大小和完整性;查找我指定的文件仅在操作日志中
gmail.readonly邮件、会话和附件搜索和读取邮件,生成我要求的摘要和提醒仅在操作日志中
gmail.modify、gmail.labels邮件标签、已读/归档状态;标签列表按我的要求加标签、标记已读和归档仅在操作日志中
gmail.compose、gmail.send草稿;发出的邮件只有在我明确要求时才起草或发送邮件仅在操作日志中
gmail.settings.basic过滤器、标签设置等基本邮件设置按我的要求查看或调整过滤器仅在操作日志中
documents、documents.readonlyGoogle 文档内容读取、创建和更新我指定的文档,例如报告和工作日志仅在操作日志中
spreadsheets、spreadsheets.readonlyGoogle 表格内容读取、创建和更新我指定的表格仅在操作日志中
presentations、presentations.readonlyGoogle 幻灯片内容读取、创建和更新我指定的演示文稿仅在操作日志中
forms.body、forms.body.readonly、forms.responses.readonly表单内容和回复读取我的表单及回复,按要求编辑表单仅在操作日志中
calendar 及相关 calendar.* 权限日历、日程、空闲状态、日历设置和共享设置读取日程,按要求创建或修改日程和日历仅在操作日志中
tasks、tasks.readonly任务列表和任务按要求读取、创建和完成任务仅在操作日志中

除连接标签外,本服务只保留:调用 Google API 所需的加密 OAuth 令牌;第 4 节所述的操作日志,其中只有每次请求和结果的简短、限长摘录。

本服务不收集支付信息、位置、联系人、设备标识、浏览记录,也不收集除我以外任何人的数据。完整的权限地址见 Alobert Connect 页面。

3. 数据用途#

Google 用户数据只用于提供我本人要求的功能:在我的 Google Drive 中创建、校验和恢复服务器加密备份;对我的邮件做摘要、搜索、加标签和归档,只有在我明确要求时才起草或发送邮件;按要求读取、创建和更新我的文档、表格、演示文稿、表单、日程和待办。

Google 用户数据不会用于广告,不会出售,不会用于建立用户画像,也不会用于开发、改进或训练通用人工智能或机器学习模型。

4. 存储与安全#

  • 本服务运行在我自己的硬件上,管理后台和 API 需要身份验证、不对公众开放;只有 Google 授权完成后跳转回来的回调地址可以从公网访问。
  • OAuth 访问令牌和刷新令牌先用 AES-256-GCM 加密,再保存到该服务器。
  • Google 数据按需获取,只返回给发起请求的自动化流程;除下述操作日志外不另行保留。
  • 存到 Google Drive 的服务器备份在本机加密后才上传,Google Drive 只收到密文。
  • 为排查问题,本服务保留最近 5,000 次操作的日志。每条记录包含操作名称、时间、结果,以及请求和结果的限长摘要:每段文本最多 256 个字符,每条记录最多 16 KB,令牌、密码等凭据会被移除。对于邮件或文档操作,摘要中可能包含主题、地址或片段等简短摘录。达到上限时最早的记录会被自动删除。
  • 本服务与 Google 之间的通信全部使用 HTTPS。

5. 共享与传输#

我不会向第三方共享、出售或传输 Google 用户数据,以下有限情形除外:

  • 应我要求的 AI 处理:当我让个人 AI 助手处理我的 Google 数据时(例如”总结今天的邮件”),完成该请求所需的内容会发送给处理它的 AI 模型 API,仅用于生成我要的结果,不用于训练通用模型。
  • 法律要求:适用法律要求时。

除我本人外,没有任何人会阅读本服务处理的 Google 用户数据。

6. Google API 服务用户数据政策#

Alobert Connect 对从 Google API 获得的信息的使用,以及向任何其他应用的传输,都将遵守 Google API 服务用户数据政策,包括其中的”有限使用”(Limited Use)要求。

7. 保留与删除#

  • OAuth 令牌保留到连接被移除为止;在管理后台移除连接会删除对应的已存令牌。
  • 也可以随时在 https://myaccount.google.com/permissions 撤销授权。
  • 备份文件保留在我的 Google Drive 中,直到我删除,或备份保留策略清理旧快照。
  • 操作日志按上述方式自动轮换。
  • 本服务只保存我本人 Google 账号的数据,不收集其他任何人的数据,删除由我按上述方式直接完成。

8. alobert.com 网站#

博客没有账号系统,不使用统计追踪或广告 Cookie,只在浏览器本地存储中保存你选择的配色偏好。网站通过 Cloudflare 提供服务,Cloudflare 会处理 IP 地址等标准请求数据,用于交付和保护网站。

9. 政策变更#

本政策如有变更,会在本页发布新版本并更新生效日期。