Odoo Backups

Privacy policy

Effective date and last updated: October 18, 2026

This policy explains how Code Wave Agency ("we", "us") handles information when operating Odoo Backups, our managed tool for creating Odoo database and attachment backups, storing archives in an authorized Google Drive account, and reporting backup status.

We use Google Drive access to store and manage backup archives. We do not sell Google user data, use it for advertising, or use it to train general-purpose AI models.

1. Information we handle

Database and attachment archives: selected Odoo databases and their filestores. Depending on the customer's database, these may contain business records, contact details, accounting or payroll information, and uploaded documents or recordings.
Google Drive information: backup files and folders the app is authorized to access, including their names, identifiers, sizes, timestamps, and checksums used to organize and verify backups.
Authorization credentials: OAuth access and refresh tokens that allow the backup server to communicate with Google Drive. The app does not receive your Google password.
Operational records: database names, backup timestamps, archive paths and sizes, and success or error details used for monitoring and troubleshooting.

2. Google Drive permissions and purpose

The Google connection requests https://www.googleapis.com/auth/drive.file. This permits access to files created by the app or explicitly made available to it. It does not grant general access to unrelated files in your Drive.

We use this access to create backup folders, upload archives, inspect file metadata and checksums, retrieve authorized archives for recovery when requested, and remove older archives according to the configured retention policy. Authorization applies to the selected Google account and can be revoked.

3. How information is used and accessed

We process this information to provide backups, recovery, retention cleanup, maintenance, and support. Authorized administrators may access archives when needed for these tasks and according to the customer's instructions. Google user data is not used for advertising, profiling, credit decisions, or training general-purpose AI models.

Our use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

4. Service providers and notifications

Backup archives are stored on the configured server infrastructure and in the Google Drive account authorized for the service. Google and the server hosting provider process information as necessary to provide those services under their own applicable terms and policies. Access may also be disclosed where required by applicable law.

When Telegram notifications are enabled, status messages may include database names, timestamps, results, and diagnostic details. In the current notifications-only configuration, backup archives and Google OAuth tokens are not sent to Telegram. Enabling archive delivery through another channel requires separate configuration and appropriate authorization.

5. Storage, retention, and deletion

The current default configuration keeps local archives for seven days and Google Drive archives for thirty days. Retention can be changed for each deployment. Cleanup runs with the backup job, so removal depends on that job completing successfully.

Google Drive deletion may move files to Trash instead of immediately erasing them. Google's Trash retention rules and any account or organizational retention settings still apply. Copies downloaded, restored, or exported elsewhere must be managed separately. Operational logs are maintained separately from archive retention and may be kept for troubleshooting; contact us to request their deletion where applicable.

6. Security

Google Drive API connections use HTTPS. Server-side credential files use restricted permissions, and access is limited to authorized operators. Backup archives contain sensitive information and must be protected by the server and Google account access controls; this service does not itself add password encryption to every ZIP archive. No storage or transmission method can eliminate all security risks.

7. Your controls and requests

You can revoke Google access in your Google Account connections, remove archives from your Drive, or ask us to stop scheduled uploads or delete retained copies. Revoking access stops future authorized Drive operations but does not automatically remove existing backups or restore copies. We may need to verify your authority before processing a request involving a customer's database.

For access, correction, deletion, or other privacy requests, contact mka2010asd@gmail.com. Rights and any applicable exceptions depend on the relevant law and service agreement.

8. This website and policy changes

These legal pages do not include analytics scripts or set application cookies. The website hosting provider may process technical request data, such as IP addresses and browser information, to deliver and secure the pages. This policy describes Odoo Backups; other Code Wave Agency services may have separate disclosures.

We will update this page when these practices change and revise the date above. Material changes to Google data access or use will be disclosed and, where required, require renewed consent before taking effect.

9. Contact

Odoo Backups is operated by Code Wave Agency. Contact: mka2010asd@gmail.com. Website: code-wave-agency.com.