Privacy Policy

Last updated: April 12, 2026

This policy describes how VoiceMatrix Studio handles Google user data. It applies only to the VoiceMatrix Studio web application.

Google User Data Access

VoiceMatrix Studio requests Google OAuth scope https://www.googleapis.com/auth/drive.readonly.

With that read-only scope, the app can access Google Drive data needed to browse and load choir rehearsal materials, including:

• Selected folder identifiers and folder names.
• Song subfolder names and modified timestamps.
• File metadata in selected song folders (file ID, file name, MIME type, size, modified time, and other metadata fields when available).
• File contents for downloaded rehearsal files (for example, MP3 and LRC files).
• Basic account hint data from Google Drive after successful sign-in, such as the Google account email address and related account metadata returned by the API.

The app does not create, edit, move, delete, or share Google Drive files.

How Google User Data Is Used

VoiceMatrix Studio uses this data to:

• Let a user connect their Google account and pick a Drive folder as a song library.
• List song folders and available rehearsal files.
• Download selected rehearsal files so they can be played offline in the browser.
• Check for updates by comparing stored metadata with current Drive metadata.

Data Sharing / Disclosure

Based on the current implementation, VoiceMatrix Studio sends Google user data directly from the browser to Google services only (Google Identity Services, Google Picker, and Google Drive API over HTTPS).

VoiceMatrix Studio does not share Google user data with third parties, except where necessary to operate the application, comply with applicable law, or protect the rights, safety, and integrity of users or the service.

The application code does not send Google Drive file data or Google account hint data to a separate VoiceMatrix Studio backend API. The codebase also does not include third-party analytics, telemetry, crash reporting, ad SDKs, or external data processors.

Data Protection

Access tokens are kept in in-memory runtime state and are not written to persistent browser storage. A full page refresh clears the in-memory token.

Communication with Google APIs and scripts uses HTTPS endpoints.

Downloaded files and related metadata are stored locally in the user's browser (IndexedDB) to support offline playback. The current implementation does not add separate application-level encryption for that local IndexedDB content.

Data Retention and Deletion

VoiceMatrix Studio stores Google-derived data locally in the browser until it is removed by user action or browser data clearing. There is no automatic time-based retention expiry currently implemented.

Stored data can include downloaded file blobs, file metadata, song and library caches, and a small localStorage session hint indicating a previously connected Google account (email/ID hint and timestamp).

Users can remove local downloaded content for a song in the app UI (Delete downloaded files), which deletes that song's downloaded blobs and associated metadata from IndexedDB. Users can also disconnect Google in the app, which clears the local Google session hint used by the app. Users may additionally clear all browser site data to remove all locally stored app data.

User Control / Revoking Access

You can control access in these ways:

• Disconnect Google inside the app.
• Revoke VoiceMatrix Studio access via your Google Account permissions.
• Delete downloaded content in the app.
• Clear browser site data to remove all stored app data.

Contact: magnus@magnus.se

← Back to VoiceMatrix Studio