eRassen Backup & Recovery Privacy Notice

This notice concerns the internal utility. It does not replace the public-website Demo privacy notice or define the complete contractual treatment of customer ERP data.

The documented Google Drive OAuth scope is https://www.googleapis.com/auth/drive.file. It allows access to files created or specifically authorized for the utility, rather than blanket access to other Drive content.

Within the authorized backup workflow, the utility may process object identifiers, filenames or paths, sizes, timestamps, status and integrity-related metadata, and upload or retrieve authorized backup objects. OAuth credentials are used to perform authorized Drive operations.

Google Drive data is used for the backup and recovery workflow: storing backup copies that were encrypted locally in Google Drive, checking authorized objects and metadata, retrieving copies for verification or recovery, and managing or removing eligible old copies under operational rules. Google API data is not used to advertise, profile visitors or market the public eRassen website.

Depending on the configured backup set, uploaded objects can contain encrypted operational database backups and supported recovery assets. Supported payloads are encrypted locally using age before upload; this does not conceal all Drive-visible metadata. Backup operations also use local server storage.

Credentials and operational access are restricted to authorized operators. Security controls reduce risk, but no storage or recovery mechanism is guaranteed to be infallible.

Google Drive provides external storage for authorized encrypted backup copies and associated remote-file metadata. Authorized eRassen operators access this information for operational needs.

Operational monitoring also uses Telegram to deliver backup status alerts to operators.

Retention, verification and deletion depend on the backup category and current operational safeguards. No universal guaranteed retention period is stated here. Eligible older objects may be removed under applicable procedures; this does not promise immediate deletion from all systems.

This notice does not promise that every historical database point or product-image copy is recoverable. Recovery checks and retention safeguards differ between backup categories.

The Google account holder may revoke OAuth authorization through Google account permissions. Revocation can interrupt future authorized backup operations; it does not automatically delete previously uploaded objects. Operators must follow separate recovery and deletion processes where appropriate.

This notice will be updated when actual Google API access, storage, retention or related processes change. Contact eRassen with privacy or data-handling questions.