Fadila Privacy Policy

Last updated 9 September 2026.

Fadila is a music player that runs entirely in your browser. It has no user accounts and no backend database. Your music library, playlists and settings are stored in your own cloud drive, in a folder that belongs to this app, and nowhere else.

Google data Fadila asks for, and why

Fadila requests the narrowest permissions that let it do its job. You are asked for each one separately, at the point you first use the feature that needs it, and you can decline any of them and still use the rest of the app.

• See your YouTube account (youtube.readonly) — used to list your own YouTube playlists and the videos in them, so that music videos from your private playlists can be added to a Fadila playlist and played. Fadila does not post, modify or delete anything on your YouTube account.
• See, create and delete its own configuration data in your Google Drive (drive.appdata) — used to store your Fadila library, playlists and settings as three compressed JSON files in Google Drive's hidden application data folder. This permission cannot read any other file in your Drive. It is how your library follows you between devices without Fadila running a server.
• See and download all your Google Drive files (drive.readonly) — used to browse the folders in your Drive, list the audio files in them, read their track metadata, and stream the audio to the player when you press play. Files are read on demand for playback; Fadila does not copy your Drive files anywhere, and never writes to or deletes them. This is a read-only permission. Fadila asks for it rather than the narrower per-file permission because music collections are organised as folder trees — often thousands of folders — and the per-file permission cannot see inside a folder, which would mean selecting every track individually.

How your data is stored and used

Google user data is used only to provide the playback and library features described above. It is not used for advertising, profiling, training machine learning models, or any purpose you have not asked for.

Access tokens are kept in your browser and are never transmitted to us. Your library, playlists and settings are written to your own cloud drive and cached in your browser's local storage so the app can start offline. Audio and video are streamed directly from Google to your browser — it does not pass through any server we operate.

How your data is protected

Fadila is built so that the sensitive data it handles — your Google access token and the contents of your Drive — stays between your browser and Google. The measures below are in place to keep it that way.

• Encryption in transit. The app is served only over HTTPS, and every request it makes to Google's APIs uses TLS. There is no unencrypted path for your data.
• No server-side copy. We operate no database and no server that receives, stores or processes Google user data. At rest, your files, library and settings exist only in your own Google Drive, under Google's own security controls, and in your browser's storage on your device.
• Short-lived, tightly scoped access tokens. Google issues Fadila a token that expires after about an hour, with no long-lived refresh token behind it. The token is stored only in your browser — in memory and in the browser's local storage, so that a page reload does not sign you out — and is deleted when it expires or when you sign out. It is sent only to Google's own API endpoints and never to us or to any third party. The background worker that streams audio attaches the token solely to requests for www.googleapis.com.
• Least privilege. Fadila asks for each permission separately, at the moment the feature that needs it is first used, and the Drive permission it uses is read-only. It cannot modify or delete your files.
• Scrubbed diagnostics. Error reports are filtered in your browser before they leave it, removing access tokens, file identifiers, file names, paths and file contents, so diagnostics never carry Google user data.
• No human access. Because we hold no copy of your data, no employee, contractor or automated process of ours can read it. There are no accounts, administrators or support tooling with access to Google user data.
• Open, auditable code. Fadila's source code is published at github.com/gunnim/fadila, so the handling described here can be verified by anyone.
• Incident response. If we become aware of a security incident that affects Google user data, we will notify affected users without undue delay, and notify Google as required by the Google API Services User Data Policy.

Limited Use disclosure

Fadila's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Third parties

Fadila does not sell, rent or share your Google user data with anyone. Three third-party services are involved in running the app, and none of them receive your Google data:

• Sentry — receives crash and error reports (an error message, a stack trace, and your browser and operating system version) so that faults can be diagnosed. Reports are scrubbed in your browser before they are sent: they do not include your Google data, access tokens, file contents, file names or file identifiers.
• Google Analytics for Firebase — records anonymous usage statistics such as page views, so we can tell which parts of the app are used. It does not receive your Google data.
• Fadila's podcast proxy — a small serverless function we operate that fetches public podcast RSS feeds on the app's behalf, because browsers block those requests directly. It sees only the address of the public podcast feed you subscribed to. It is never used for Google Drive or YouTube data.

Other storage providers

Fadila can use Microsoft OneDrive or Dropbox in place of Google Drive. The arrangement is identical: your library, playlists and settings are stored in an app-specific folder in your own account, and audio is streamed from there to your browser.

Retention, and how to revoke access

We hold no copy of your data, so there is nothing on our side to delete. To remove Fadila's access to your Google account, visit your Google account permissions page and remove Fadila. To delete the data Fadila has stored, delete the Fadila folder from your cloud drive, and clear this site's data in your browser. Revoking access stops all further access immediately.

Changes and contact

If this policy changes, the date at the top of this page changes with it. Questions about privacy, or about this policy, can be sent to gunni@starcraft.is.