Legal · databasus

Privacy Policy

What databasus, a personal Google Drive backup client, accesses and how it's used.

app
databasus
role
personal database‑backup client, reads/writes its own files in Google Drive
scope
drive.file — app‑created files only, no access to the rest of your Drive
contact
mririamine93@gmail.com
updated
2026‑09‑07

On this page

  1. Overview
  2. Data we access
  3. How it's used
  4. Storage & retention
  5. Sharing
  6. Security
  7. Children's privacy
  8. Changes
  9. Contact

1. Overview

Databasus is a personal‑use application built to back up databases to a user's own Google Drive. It authenticates with Google via OAuth 2.0 and, once authorized, creates and manages backup archives (for example .sql.gz or .dump files) inside that same Drive account.

Databasus does not operate as a public service with third‑party accounts — each installation acts only on the Google account that authorized it.

2. Data we access

Databasus requests the Google Drive drive.file scope. Under this scope, it can only see and manage files that it itself creates, or files a user explicitly opens with it — it cannot browse, read, or modify the rest of a Drive account.

3. How it's used

Data accessed through the Drive API is used solely to perform backup and restore operations: uploading new backup archives, listing existing ones, and retrieving or deleting them on request. Databasus does not run analytics on backup contents, does not serve ads, and does not use this data to build profiles.

4. Storage & retention

Backup archives live in the user's own Google Drive, under the user's own storage quota — databasus does not maintain a separate copy on external servers beyond what is needed in transit to complete a backup or restore. Archives remain until deleted by the user, either from within databasus or directly in Drive.

5. Sharing

Backup data is never sold, rented, or shared with third parties. Nothing accessed through the Drive API leaves the direct path between databasus and the authorizing user's own Google Drive.

6. Security

Access tokens are obtained through Google's standard OAuth 2.0 flow, transmitted over TLS, and stored only long enough to perform authorized operations. Access can be revoked at any time from a Google Account's third‑party access settings, which immediately stops databasus from reaching that Drive.

7. Children's privacy

Databasus is a systems‑administration tool and is not directed at, or knowingly used by, children under 13.

8. Changes to this policy

If databasus's data handling changes, this page will be updated and the date in the manifest above revised accordingly.

9. Contact

Questions about this policy can be sent to mririamine93@gmail.com.