Privacy Policy

Effective April 15, 2026

This privacy policy describes how edpro.ai (operated by Educational Media Solutions / Chris Spence) handles data accessed through our internal productivity tools that connect to Google APIs.

What This Policy Covers

edpro.ai operates a set of internal productivity tools ("the App") that use Google OAuth to access the following Google services on behalf of the authenticated user:

Gmail (read, compose, and manage email)
Google Calendar (read and create events)
Google Drive (create and manage files)
Google Docs (create and edit documents)
Google Sheets (read and write spreadsheet data)
Google Slides (create and edit presentations)

Who Uses the App

The App is a private, internal tool used exclusively by the owner (Chris Spence / spencech@gmail.com) for personal and business productivity. It is not a public-facing product or service offered to third parties.

What Data We Access and Why

Gmail (gmail.modify)

Used to read incoming email for triage and classification, draft and send messages on behalf of the user, and mark messages as read after triage. This powers a daily email digest workflow and client communication drafting.

Google Calendar (calendar)

Used to create calendar events (reminders, meeting scheduling) and read calendar context for scheduling decisions.

Google Drive (drive)

Used to create and manage documents, spreadsheets, and files for business operations including proposals, invoices, and client deliverables.

Google Docs, Sheets, Slides (documents, spreadsheets, presentations)

Used to create, read, and edit documents and spreadsheets for business correspondence, invoice tracking, and project management.

How Data Is Stored

OAuth tokens (access and refresh tokens) are stored locally on the owner's machine in environment files that are excluded from version control via .gitignore.
Email metadata may be cached locally for short periods (typically less than 24 hours) to support the email digest workflow. Cached data is stored in a local .state/ directory that is excluded from version control.
No Google user data is stored on remote servers, databases, or cloud storage.
No Google user data is shared with any third party.

How Data Is Protected

All communication with Google APIs uses HTTPS/TLS encryption.
OAuth tokens are never committed to version control or shared in communications.
The App runs exclusively on the owner's local machine with full-disk encryption enabled.
Access is limited to a single authenticated Google account.

Data Retention and Deletion

Cached email metadata is automatically cleaned on each digest run (stale entries are removed).
No permanent copies of Google data are retained beyond what exists in the Google services themselves.
Revoking the App's access via Google Account Permissions immediately invalidates all tokens and stops all data access.

Your Rights

Since this is a private tool used by a single individual, the "user" and "operator" are the same person. The authenticated user can at any time:

Revoke the App's access at myaccount.google.com/permissions
Delete all locally cached data by removing the .state/ directory
Delete OAuth tokens by removing the relevant environment files

Contact

For questions about this privacy policy, contact:

Chris Spence
Educational Media Solutions
christopher.spence@educationalmediasolutions.com

Changes to This Policy

This policy may be updated from time to time. The effective date at the top of this page indicates when the most recent changes were made.