Privacy Policy

This Privacy Policy describes how Progress for Google Slides ("the Extension") handles information when you use our Chrome extension.

Summary

The Extension adds slide status labels inside Google Slides. By default, status data stays in your browser. If you choose to sign in with Google, status labels are stored on each slide as hidden marker shapes in the presentation so collaborators can see the same statuses. Status presets and collaborator emails are stored in Google Drive file metadata on that presentation. The Extension does not read slide text, images, or your browsing history, and it does not sell your data.

What Data We Collect

Data stored locally in your browser

• Slide statuses — Status labels (built-in or custom), internal slide identifiers, update timestamps, and a compact history of prior changes when signed in.
• Status preset configuration — Customized labels, colors, icons, order, and which statuses count as complete.
• Signed-in account — Your Google email and profile photo URL after sign-in, shown in the side panel Account view.
• Presentation identifiers — Google Slides presentation IDs for decks where you have used the Extension.
• Sync state — Sign-in status, last sync time, and recent sync error messages shown in the side panel.

This data is stored in chrome.storage.local and is used only to power the Extension UI (filmstrip chips, title-bar badge, and side panel).

Data sent to Google when you sign in

• Authentication — Google OAuth through Chrome's identity API with the drive.file, userinfo.email, and userinfo.profile scopes. After sign-in, Google asks you to confirm each presentation once. We do not receive your Google password.
• Slide status markers — Status labels stored on each slide as hidden marker shapes with alt-text metadata for presentations you can edit.
• Status presets and collaborator emails — Stored in Google Drive file metadata on the presentation. Profile photos stay in local cache and are not written to Drive.
• Presentation access — Marker and Drive metadata read/write only on presentations you open in Google Slides while using the Extension. Slides API requests are limited to slide page IDs and marker alt-text.

Data we do not collect

• Slide text, speaker notes, images, or other presentation content
• Browsing history or activity outside Google Slides
• Analytics, telemetry, crash reports, or advertising identifiers
• Financial, health, or location information

The Extension does collect email addresses as described above: your signed-in Google email, and collaborator emails stored in Drive file metadata for history attribution.

How We Use Data

We use data solely to provide Extension features: status chips, progress badges, local caching, optional collaborator sync, customizable presets, and the side panel (History, Statuses, and Account). We do not use your data for advertising, creditworthiness, or unrelated purposes.

How Data Is Stored

The Extension does not operate its own servers and does not store your data on developer-controlled infrastructure.

Data Protection

We take reasonable steps to protect Google user data and other information handled by the Extension.

Security procedures

Security procedures are in place to protect the confidentiality of your data. Because the Extension does not operate its own servers, protection focuses on secure local handling and least-privilege access to Google APIs.

Encryption and secure transport

We use encryption to protect your information in transit. All communication with Google services (OAuth, Google Slides API, Google Drive API, and Google userinfo API) uses HTTPS/TLS. No Google user data is transmitted over unencrypted connections.

Least-privilege access

The Extension requests the narrowest OAuth scopes needed for its features and accesses only the minimum data required:

• drive.file — After you confirm a presentation, reads slide page IDs, writes small hidden marker shapes, and reads/writes appProperties on that file only; does not list other Drive files or read slide text, images, or speaker notes.
• userinfo.email and userinfo.profile — Reads your signed-in email and profile photo URL for display and status history attribution.

API requests use field masks and scoped endpoints so only the data needed for sync is read or written.

Local storage and token handling

Cached Extension data is stored in chrome.storage.local, which is isolated to this Extension. OAuth access tokens are managed by Chrome's identity API and Google's OAuth infrastructure; we do not store OAuth tokens on developer-controlled servers.

Optional sign-in

Google user data is accessed only after you explicitly choose Sign in in the side panel. Without sign-in, status data stays in your browser and the Extension does not call Google APIs on your behalf.

Third-Party Services

When you sign in, the Extension uses:

• Google OAuth / Chrome Identity API
• Google userinfo API
• Google Slides API
• Google Drive API
• Google Picker API — used only to confirm the presentation you already have open

We do not share your data with any other third parties.

Data Sharing

We do not sell, rent, or trade your data. If you sign in and sync, status markers are stored inside the presentation, and status presets plus collaborator emails are stored in that file's Drive metadata. Collaborators with edit access can read this metadata through Google Slides, Google Drive, and this Extension.

Google User Data Retention and Deletion

This section describes how Google user data obtained through Google OAuth and Google APIs is retained and how you can delete it.

What counts as Google user data in this Extension

When you sign in, the Extension may access:

• Your Google account email and profile photo URL (userinfo scopes)
• Slide status markers stored on presentations you allow (drive.file scope)
• Status preset catalogs and collaborator email addresses stored in Drive file metadata on those presentations (drive.file scope)

We do not collect Google user data on developer-operated servers. Google user data persists only in your browser's local cache and in the Google Slides or Google Drive records for presentations you edit while signed in.

Retention

We retain Google user data only as long as needed to provide the Extension's features:

• Local cache — Stored while the Extension is installed and, for signed-in data, while you remain signed in or until you clear extension data.
• Slide status markers — Stored on each slide until you reset statuses, delete markers, or delete the presentation file.
• Drive file metadata — Status presets and collaborator emails remain in the presentation's Drive appProperties until overwritten by a later sync, removed through Google Drive, or deleted with the presentation file.
• OAuth tokens — Managed by Chrome and Google while you remain signed in; revoked when you sign out.

We do not retain Google user data on developer-controlled infrastructure after you uninstall the Extension or sign out, except where that data remains in Google's services under your control.

Deletion

You may delete Google user data handled by the Extension as follows:

Because we do not operate servers that store Google user data, there is no separate account or database from which we can delete data on your behalf. To request help locating or removing Extension-related Google user data, contact c.teerakit@gmail.com.

Permissions

• storage — Local cache of slide statuses, presets, and profile photos
• identity — Optional Google sign-in
• alarms — Periodic background sync for open presentations
• sidePanel — History, Statuses, and Account UI; opens when you click the toolbar icon
• https://docs.google.com/* — Find open Google Slides tabs so chips, presets, and the side panel stay in sync
• https://slides.googleapis.com/* — Read slide structure and write status marker shapes when signed in
• https://www.googleapis.com/drive/v3/* — Read and write status preset and collaborator email metadata when signed in
• https://www.googleapis.com/oauth2/v3/* — Fetch the signed-in user's email and profile photo

Children's Privacy

The Extension is not directed at children under 13, and we do not knowingly collect personal information from children.

Changes to This Policy

We may update this Privacy Policy when our data practices change. The date at the top of this page reflects the latest revision. Continued use of the Extension after an update means you accept the revised policy.