Privacy Policy
This policy describes the intended privacy model for Jawadpir Backup Manager, an administrator-only Google Drive backup integration currently under development.
1. Scope
The planned utility is intended for authorized administrators responsible for protecting application data. It is not designed as a consumer file-storage service, and it will not provide public backup access.
2. Google Drive permission
The planned integration will request Google Drive’s limited drive.file permission. This permission is intended to let the utility access files it creates and files or folders the administrator explicitly opens or selects for the application. It is not intended to provide unrestricted access to the administrator’s entire Drive.
If folder selection is enabled, the administrator will deliberately authorize the intended private backup location through Google’s supported selection and OAuth flow.
3. Backup contents
A planned snapshot may contain application database records, associated media, a manifest, checksums, and recovery metadata. Backup contents are intended to be encrypted before upload. The Drive account will store the encrypted archive rather than an intentionally readable copy of its protected contents.
4. OAuth credentials and tokens
OAuth client secrets, access tokens, refresh tokens, backup encryption keys, and application secrets must never be placed in public website files or exposed to visitors. The planned backend will store required authorization material server-side using restricted access and encryption appropriate to the deployment environment.
Access tokens may be refreshed when necessary for an administrator-authorized operation. Administrators may revoke the integration through their Google Account security settings. Revocation will prevent future Drive access until authorization is granted again.
5. Encryption and recovery keys
Backup archives are intended to use authenticated encryption before upload. The disaster-recovery key and any application key required to interpret restored data must be protected independently from the backups. Losing required keys may make encrypted backups permanently unreadable.
6. Retention
The current design target is to retain the latest two successfully uploaded and verified snapshots. An older verified snapshot would be considered for deletion only after a newer backup has completed and passed integrity verification. Failed or incomplete attempts must not trigger deletion of earlier successful backups.
Administrators remain responsible for any additional copies, legal retention requirements, Google Drive trash behavior, and removal of data when it is no longer required.
7. Data use and disclosure
Backup data and Google authorization are intended to be used solely to create, verify, retain, and restore administrator-authorized backups. The planned utility is not intended to sell personal data, use backup contents for advertising, or share them with unrelated third parties.
8. Security and limitations
The planned controls include administrator authentication, duplicate-job prevention, encryption, integrity checks, restricted secrets, and documented restore verification. No security measure eliminates all risk. Deployment should occur only after isolated testing, access review, recovery testing, and approval by the responsible administrator.
9. This website
These static pages use no backend, account system, analytics, advertising trackers, or external service integrations. Ordinary hosting infrastructure may process standard connection information such as timestamps and technical request data according to the hosting provider’s own practices.
10. Policy changes
This policy may be updated as the design, authorization scope, deployment status, or retention process changes. Material changes should be documented before the integration is used with real backup data.