1. Introduction
This Privacy Policy describes how MPLS Backup (the “Application”) accesses, uses, stores, and protects information obtained through the Google Drive API and the Google OAuth 2.0 authorization service.
MPLS Backup is a personal, owner-operated utility. It creates encrypted snapshots of a local database and stores them on the owner’s personal Google Drive account. The Application is used exclusively by its owner and operator; no external users, public accounts, or third-party data sharing are involved.
2. Who This Policy Applies To
This Application is a single-user personal tool. Only the owner and operator of this Application is authorized to use it or grant it access to a Google account. No other individuals create accounts, log in, or interact with this Application.
3. Information We Access via Google Drive API
Through the Google Drive API, this Application performs the following operations exclusively within a designated private backup folder in the owner’s Google Drive:
- Write: Upload encrypted backup files to the designated folder.
- Read (list): List files in the designated folder to manage backup retention.
- Read (download): Download encrypted backup files to the owner’s local machine for restore operations.
- Delete: Remove backup files from the designated folder per the backup retention policy, upon explicit owner action.
The Application does not:
- Access, read, modify, or delete any files outside the designated backup folder.
- Read decrypted content from Google Drive (all files are ciphertext on the server).
- Access Google account profile information, email address, contacts, calendar, or any other Google service data.
- Transmit any data from Google Drive to any server, service, or third party.
OAuth scope note: This Application uses the
drive OAuth scope, which technically permits access to all files
in the authorized Google Drive account. The Application is designed and operated
exclusively to access the designated backup folder. No other files are accessed.
4. How We Use Google Drive Data
Access to Google Drive is used solely to provide the core backup functionality of this Application:
- Storing encrypted backup files in the owner’s private Google Drive folder.
- Managing (listing and deleting) those backup files according to a retention schedule.
- Restoring backup files to the owner’s local machine when needed.
Google Drive data is not used for any other purpose, including: advertising, analytics, machine learning, profiling, or any commercial activity.
5. Encryption and Data Security
All data is encrypted on the owner’s local machine before being transmitted to Google Drive. Encryption is performed by the rclone crypt layer using the following configuration:
- Algorithm: AES-256-CTR (industry-standard symmetric encryption)
- Content encryption: All backup file contents are encrypted. Google Drive stores only ciphertext; the plaintext is never accessible from the cloud.
- Filename encryption: Enabled (Standard mode). All filenames stored on Google Drive are encrypted strings; the original filenames are not visible.
- Directory name encryption: Enabled. Folder names within the backup folder are also encrypted.
Key Storage
Encryption keys (password and salt) are stored exclusively in a restricted-access configuration file on the owner’s local machine. Keys are:
- Never transmitted to Google Drive.
- Never transmitted to any remote server or third-party service.
- Accessible only to the owner and the local system account that runs the backup process.
OAuth Credentials
The Google OAuth refresh token is stored locally in the same restricted-access configuration file. It is not shared with any third party and is used only to authenticate API requests to the owner’s Google Drive account.
6. Data Retention
Encrypted backup files stored on Google Drive are retained according to the following tiered rolling schedule:
- Safety floor: The most recent 3 backups are always retained, regardless of age.
- Daily tier: All backups are retained for 30 days.
- Weekly tier: One backup per week is retained for 12 weeks.
- Monthly tier: One backup per month is retained for 12 months.
Files outside the retention window are removed only upon explicit owner action using the backup pruning utility. No automatic deletion occurs without a deliberate owner-approved command.
The owner may delete any or all backup files from Google Drive at any time by removing them through the Google Drive web interface or by revoking this Application’s access entirely.
7. Data Sharing
We do not share, sell, transfer, license, or disclose any data obtained through the Google Drive API to any third party, for any purpose.
This Application does not use Google user data for:
- Advertising or marketing.
- Analytics or user profiling.
- Training machine learning models.
- Determining creditworthiness, insurance eligibility, or similar assessments.
- Any purpose beyond the encrypted backup functionality described in this policy.
8. Google API Services User Data Policy
This Application’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Specifically, information obtained through Google APIs is used only to provide the backup functionality described in this Privacy Policy, and is not transferred to any third party.
9. OAuth Access and Revocation
This Application uses Google OAuth 2.0 for authorization. The OAuth access grant is stored locally on the owner’s machine and is not transmitted to any external service.
To revoke this Application’s access to your Google Drive at any time:
- Go to myaccount.google.com/permissions.
- Locate the Application in the list of connected apps.
- Click Remove access and confirm.
Revoking access immediately prevents the Application from authenticating new API requests. Any existing locally stored backup files are unaffected.
10. Third-Party Services
This Application does not incorporate any third-party analytics, advertising networks, tracking scripts, or external content delivery networks.
The only external service used is the Google Drive API, described above. Interactions with Google are governed by Google’s Privacy Policy and Google’s Terms of Service.
11. Changes to This Policy
We may update this Privacy Policy from time to time, particularly as the Application moves from development into active use. Updated versions will be posted at this URL. The “Last updated” date at the top of this page reflects the most recent revision.
Material changes will be noted in the revision date. Continued use of the Application after a policy change constitutes acceptance of the updated terms.
12. Contact
For questions or concerns about this Privacy Policy or the Application’s data practices, please contact:
Owner/Operator: MPLS Backup
Email:
mpls.team001@gmail.com