Blubber privacy policy

Effective 2026-10-31. This policy covers Blubber, a personal internship monitoring agent built and run by Aidan Chien (the owner) for the owner's own use. About Blubber.

Who uses Blubber

Only the owner. Blubber has no accounts and accepts no sign-ups. The only Google account it can be connected to is the owner's own.

What it accesses

How Gmail data is used

Message text is processed on the owner's computer to decide whether a message is a recruiter signal. Part of that processing may pass the text to an AI assistant (OpenAI Codex or Anthropic Claude) under the owner's own subscriptions, with the assistant's tools and web access disabled.

Full message contents are not stored in Blubber's cloud database and never appear on its dashboard. Only the minimal facts needed for an alert may be stored: the sender's domain, the subject, extracted dates, and a link back to the message in Gmail.

Gmail data is used only to produce alerts for the owner. Blubber does not sell it, share it with anyone, use it for advertising, or use it to train models.

Blubber's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Where data lives and for how long

Alerts and the derived records above live in a private database only the owner can read, and in Telegram messages to the owner. The Gmail access token is stored only on the owner's computer. The owner can delete any record at any time and can revoke Blubber's access at myaccount.google.com/permissions, which stops all Gmail reading at once.

Security

The database and this dashboard are private: the dashboard needs a password and reads through a database role that can only read. The access token never leaves the owner's computer.

Changes and contact

Changes are posted on this page with a new effective date. Questions go to the owner through aidanchien.com.