Privacy Policy

When you sign in, Drive Audio uses Google's OAuth sign-in to request the drive.readonly permission — read-only access to your Google Drive. The app uses this access solely to:

• list your folders, shared folders, shared drives and starred items so you can browse them;
• read file metadata (name, size, modification date, and for shared items, who shared it and when) to display in the app;
• stream or download the audio files you choose to play.

Drive Audio never modifies, uploads, moves, shares or deletes anything in your Google Drive.

The sign-in tokens Google issues are stored only in the iOS Keychain on your device and are sent only to Google's own servers to access your files. We do not see them. You can revoke the app's access at any time from your Google Account permissions; the app will then ask you to sign in again.

Everything the app stores is kept in its private storage on your iPhone and is deleted when you delete the app. None of it is sent to us or to anyone other than Google.

Drive Audio handles Google Drive data — which Google classifies as sensitive — with the following safeguards. These apply to all Google user data the app touches: file metadata, file contents and OAuth tokens.

Encrypted in transit

Every connection the app makes — sign-in, file listings, streaming and downloads — goes directly to Google over HTTPS (TLS 1.2 or later) using Apple's system networking. The app never uses plain HTTP and never routes Google data through any other server.

Encrypted at rest

Sign-in tokens are stored in the iOS Keychain, which encrypts them with keys held in the device's Secure Enclave. They are marked device-only (not included in backups or iCloud Keychain) and become readable only after the device has been unlocked once since boot. Downloaded audio, cached tracks, notes and favorites are stored in the app's sandboxed container, which iOS Data Protection encrypts with the device passcode.

Isolated by the operating system

iOS app sandboxing prevents other apps from reading Drive Audio's storage. There is no shared container, app group, file-sharing entitlement or iTunes file exposure, so files and notes cannot be browsed from outside the app.

No copies anywhere else

Drive Audio has no backend, database, analytics or logging service. Google Drive data is never transmitted to the developer or to any third party, so there is no server-side copy to protect, breach or subpoena.

Least privilege

The app requests a single, read-only Google scope (drive.readonly). It has no ability to create, edit, share or delete Drive files, and tokens are used only for the Drive API calls needed to list and play audio.

Retention and deletion

Google data is retained only on your device and only for as long as you keep it: cached tracks are evicted automatically (least recently played first, capped at 1 GB), downloads and notes stay until you remove them or delete the app, and signing out immediately erases the stored tokens. Deleting the app removes everything. Revoking access in your Google Account invalidates the tokens on Google's side as well.

Human access

No person — including the developer — can access your Google Drive data through Drive Audio. There is no admin console, support tooling or remote access path.

Security incidents

Because no user data leaves the device, a breach of developer systems cannot expose your Drive data. If a vulnerability in the app itself were discovered, an update would be issued through the App Store and described at this address. Report concerns to ben.strohbeen@gmail.com.

Nothing. Drive Audio has no analytics, no crash reporting service, no advertising, and no servers of ours. We do not know who uses the app.

Apple may collect standard, anonymized diagnostics according to your device's settings and Apple's own privacy policy.

The only third party the app communicates with is Google (Google Drive API and Google sign-in), governed by Google's Privacy Policy.

Drive Audio is not directed at children under 13 and does not knowingly collect information from anyone.

If this policy changes, the updated version will be posted at this address with a new "last updated" date.

Questions about privacy: ben.strohbeen@gmail.com