Personal Scripts · matsby.org · Effective October 23, 2026
"Personal Scripts" is a set of small automation programs written and run by Matthew Stepka for his own use. They are not offered to the public, and nobody other than Matthew Stepka signs in to them. This policy explains what Google account data the scripts access and how it is handled.
Only the owner, Matthew Stepka, using his own Google account. The scripts run on his personal computer. There are no other users, no sign-up, and no public service.
With the owner's permission, granted through Google's sign-in screen, the scripts may access the following data in the owner's own Google account:
Gmail: reading delivery-failure (bounce) notices and the original messages they refer to, and creating draft emails. Drafts are never sent automatically.
Google Contacts: reading contacts and updating them, for example labeling an email address that bounced, tidying notes, merging duplicates, and managing contact labels.
Google Sheets and Google Drive: creating and updating spreadsheets that log the scripts' activity, such as a list of bounced email addresses or archived tasks.
Google Tasks: reading tasks so they can be archived to a spreadsheet, and deleting them from the default list afterwards.
The data is used only to perform these tasks for the owner. It is not used for advertising, profiling, analytics, or training machine-learning models, and it is not sold.
Results are written back into the owner's own Google account (contacts, drafts, spreadsheets). The sign-in tokens and short run logs are stored only on the owner's computer. No data is copied to any server operated by the scripts or by anyone else.
Data obtained from Google is not shared with or transferred to any third party.
The use and transfer of information received from Google APIs by these scripts adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Access can be withdrawn at any time from the Google Account's Third-party apps & services page. Deleting the locally stored sign-in token also stops the scripts from accessing the account.
If the scripts start using data in a new way, this page will be updated and the effective date changed.
Questions about this policy: matthew.stepka@gmail.com