PersonalWork
A personal, single-user automation application that connects one Google Account to its owner's own AI agent, so routine work can be carried out on the owner's behalf.
- No login to read this page
- Single user — the owner
- Google API Limited Use
- Not a public service
What PersonalWork is Privacy policy Terms of use
This page is the home page of the OAuth application PersonalWork. Everything below is readable without signing in. The application name is the same everywhere it appears — here, in the page title, in the structured data on this page, and on Google's authorization screen.
Purpose of the application
PersonalWork exists for one reason: to let its owner's AI agent perform everyday personal and work chores through Google's APIs, instead of the owner clicking through each one by hand.
Who uses it
One person — the owner of the application and of the single Google Account that authorizes it. PersonalWork is not offered to the public. It has no sign-up, no user list, and no way for a second person to obtain an account.
What problem it solves
Keeping a mailbox, a calendar, a drive of documents and a task list tidy is a lot of small repetitive steps. PersonalWork turns those steps into work the owner's own agent can carry out, so the owner reviews results instead of doing the filing.
How the owner reaches it
There is no public front door to log into. The application runs on the owner's own infrastructure and is driven by the owner's agent. This website only publishes the application's description, privacy policy and terms.
Why it needs Google
The work it does is reading and organizing the owner's own Google content. It therefore asks Google for permission to work on the owner's Drive, Gmail, Calendar, Contacts, Tasks and related surfaces, and does nothing there that the owner did not ask for.
What PersonalWork does
Every capability below acts only on the owner's own account, and only when the owner — or the owner's agent, on the owner's instruction — asks for it.
Documents & files
Reads, creates, updates and organizes the owner's own files and documents in Google Drive, including Docs, Sheets, Slides and Forms content.
Reads, labels, files, drafts and sends mail from the owner's own mailbox, and keeps the owner's own filters and mailbox settings in order.
Calendar & meetings
Reads and edits the owner's own calendar entries and works with the owner's own meeting spaces.
Contacts & directory
Looks up and maintains the owner's own contacts, and reads the directory information the owner is already entitled to see.
Tasks, notes & chat
Maintains the owner's own task lists and keeps the owner's own team-chat spaces and messages in order.
Reporting
Compiles the owner's own Analytics, Search Console and advertising figures into summaries the owner reads.
What PersonalWork does not do
- It is not a product, service or platform offered to other people.
- It does not sell, rent, trade or share Google user data with anyone.
- It does not use Google user data for advertising, profiling, creditworthiness or any similar purpose.
- It does not use Google user data to train or improve generalized artificial-intelligence or machine-learning models.
- It does not create, request or distribute AI-generated non-consensual intimate imagery (AI NCII), or any sexual or intimate content of real people — this is an outright prohibition, not a limitation.
- It does not send bulk or unsolicited messages, harass anyone, or use Google APIs for any unlawful purpose.
- It runs no advertising, and transfers no Google user data to third parties for advertising or resale.
- It lets no human other than the owner read the owner's Google content.
Where a task needs an AI model's help, the model acts only on the owner's own content, only for that task, under terms that prohibit using the content to train general models. PersonalWork itself never uses Google user data for model training.
How it works
The owner authorizes once
The owner grants PersonalWork access with their own Google Account, on Google's own consent screen. No credentials pass through this website.
Google issues an access grant
Google returns OAuth tokens. They are stored encrypted on the owner's own machine and stop working the moment the owner revokes access.
The owner's agent asks for work
The agent decides what needs doing — file this mail, update that document, summarize these numbers — and calls Google's APIs for that one task.
The owner sees the result
Changes land in the owner's own Google account. Nothing is published, forwarded to a third party, or kept beyond what the task needs.
This website is static: it hosts no application code, collects no data, sets no cookies, and has no forms, accounts or analytics.
Google user data and why it is requested
PersonalWork asks for the permissions its tasks need. Each row is a group of Google API scopes with the reason that group is requested. All of them act on the owner's own account only.
| Area | Google scopes | Why it is requested |
|---|---|---|
| Identity | openid, profile, email, userinfo.email |
To know which Google Account a task applies to, so the owner's own content is the only content touched. |
| Drive and documents | drive, drive.activity.readonly, drive.labels.readonly, documents, spreadsheets, presentations, forms.body, forms.responses.readonly |
To find, read, write, reorganize and summarize the owner's own files and documents. |
| Apps Script | script.projects, script.deployments, script.processes |
To manage the owner's own small automation scripts and read their execution history when a task fails. |
| Gmail | gmail.modify, gmail.settings.basic, gmail.settings.sharing |
To read, label, file, draft and send the owner's own mail, and to keep the owner's own filters and mailbox settings in order. |
| Calendar and Meet | calendar, meetings.space.created, meetings.space.readonly, meetings.space.settings |
To read and update the owner's own calendar entries and meeting spaces. |
| Contacts and directory | contacts, contacts.other.readonly, directory.readonly |
To look up and maintain the owner's own contacts, and to read directory information the owner is already entitled to see. |
| Tasks | tasks |
To maintain the owner's own task lists. |
| Team chat | chat.spaces, chat.memberships, chat.messages, chat.messages.reactions.readonly, chat.messages.reactions.create, chat.users.readstate.readonly |
To read and post in the owner's own chat spaces and to keep the owner's own read state in sync. |
| Classroom | classroom.courses, classroom.announcements, classroom.coursework.me, classroom.coursework.students, classroom.courseworkmaterials, classroom.guardianlinks.students, classroom.profile.emails, classroom.profile.photos, classroom.rosters, classroom.topics |
To keep the owner's own course material and rosters in order. |
| Photos | photoslibrary.readonly.appcreateddata |
Read-only access, limited to media this application itself created. |
| Reporting | analytics.readonly, webmasters, adwords |
To pull the owner's own traffic and advertising figures into summaries the owner reads. |
| YouTube | youtube.readonly |
Read-only access to the owner's own YouTube data. |
Google API Services User Data Policy — Limited Use
PersonalWork'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.
Google user data is used only to provide or improve user-facing features that are visible in the application, is transferred only if necessary to provide or improve those features, and is never used for advertising or sold to third parties. No human reads the owner's Google user data, except where the owner has given explicit consent, where it is necessary for security purposes, to comply with applicable law, or where the data has been aggregated and anonymized for internal operations.
The full statement of what is collected, why, and for how long is in the privacy policy.
Data and security
Least privilege
Scopes are requested for the surfaces a task actually uses. Where a read-only scope is enough, a read-only scope is used.
Tokens under the owner's control
OAuth tokens live on the owner's own machine with restrictive permissions, are excluded from backups and source control, and stop working the moment the owner revokes access in their Google Account.
Encryption in transit
Every hop — browser to this site, application to Google, application to its providers — uses TLS.
Minimal retention
Working copies of content are removed when a task ends. Logs are kept 30 days and contain no message bodies or document text.
No third-party readers
No human other than the owner reads the owner's Google content. Support is provided by the operator, who is the owner.
Breach response
If a breach affecting personal data occurs, the operator revokes the affected credentials, notifies the owner without undue delay, and reports to the competent authority where the law requires it.
Support and contact
PersonalWork is a one-person project. Questions about the application, its privacy policy or its terms — and any request to access, correct or delete data — go to the same place.
Data requests
Ask by email for access, correction, portability or deletion.
Deletion of tokens and task data: within 7 days. Logs: within 30 days.
Revoke access yourself
Google Account → Security → Third-party apps
Removing PersonalWork there takes effect immediately.
Documents on this site: privacy policy · terms of use · Google user data.