VYNDI OS Backup Privacy Policy

1. Who operates this service and what it covers

Vāyú Shastr operates the VYNDI OS Backup integration as part of the VYNDI OS enterprise software project. The integration is intended for authorized account owners or administrators who choose to back up the VYNDI OS database to their Google Drive. This policy covers that Google OAuth integration and its backup and restoration workflows. Other parts of our public website are covered by the corporate website privacy notice.

2. Google Drive information and permissions

If you authorize the connector, it obtains an OAuth token enabling access to Google Drive using the Google Drive API. The current connector configuration requests the scope https://www.googleapis.com/auth/drive.file. This is a per-file permission that permits this OAuth application to create files and access files and folders created by or explicitly opened with it. Other Google Drive files and folders are not accessible through this OAuth client merely because you grant this scope.

The configured backup and restoration workflows operate only within a dedicated VYNDI OS encrypted-backup folder created by this OAuth application: checking connectivity, uploading encrypted backup archives, reading back those archives to validate integrity, and downloading an explicitly selected archive for an authorized restoration test. You cannot use the connector to browse unrelated Drive documents or photographs with this per-file grant. We do not intentionally share, remove, or synchronize unrelated Drive files. An existing folder created by another app is not automatically accessible using this permission; the setup process uses a new folder created with the same Google OAuth client.

For these operations, Google provides file or folder identifiers, filenames, object sizes, timestamps and other metadata needed to manage and verify the backup. The connector does not require your Google account password and does not obtain access to Gmail, Google Photos or Google Contacts APIs as part of this backup workflow.

3. Accounting and other data included in a backup

When activated, the workflow reads VYNDI OS's PostgreSQL database through a designated backup database account. The exported archive may contain journals, invoices, vouchers, receipts, financial balances, business contacts, employee or supplier records, supporting documents stored inside the database, and audit-log entries. Such records may contain personal and commercially sensitive information. These records originate in VYNDI OS; they are not copied from unrelated Google Drive files.

Files held outside the PostgreSQL database are not automatically covered by the current database-archive workflow unless a separate, documented export process is added.

4. Why we use the information

• Create an encrypted recovery copy of the VYNDI OS database in the authorized Drive folder.
• Check that the uploaded encrypted backup can be retrieved unchanged using a cryptographic checksum.
• Perform an administrator-initiated recovery test on an isolated, disposable database, or support a separately authorized recovery operation.
• Produce minimal technical records of backup success, failure, file identifiers, timestamps and verification results; detect and investigate backup-security issues.

We do not sell Google user data, use it for targeted advertising, build advertising profiles, provide it to data brokers, or use it to train generalized artificial-intelligence models. Access to Google user data is limited to the disclosed backup, restore and security functions and the permitted exceptions below.

VYNDI OS Backup's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

5. Encryption, credentials and security

The prepared backup workflow uses a TLS-protected database connection and encrypts the database export with the age public-key encryption format before uploading it to Google Drive. The uploaded file is ciphertext. A SHA-256 digest of the encrypted file is checked against a separate download or readback. The corresponding private decryption identity is intended to remain in a separately protected restoration environment and an offline recovery location controlled by the operator.

When configured, Google OAuth credentials and the database connection credential are stored as restricted GitHub Actions secrets. A temporary GitHub-hosted runner processes the database stream during backup and decrypts an authorized archive only as part of an isolated restore drill. Google Drive stores the encrypted files, but Google may still process storage metadata such as names, sizes and timestamps. Cloud services cannot be guaranteed free from all security risks. The private decryption identity must never be supplied to Google Drive or placed in a public repository.

Operational controls described here are design and configuration requirements; until the relevant workflows have passed live commissioning tests, this policy does not claim that scheduled backups or restoration have already occurred.

6. Service providers and disclosure

The backup process uses Google Drive to store encrypted archives, GitHub Actions to execute authorized jobs, and the database hosting provider to read the source database. These providers process information only as necessary to deliver the service under their own applicable terms. Authorized VYNDI OS operators or reviewers may access limited backup metadata and may use the decryption identity for an approved recovery test. We do not give third parties plaintext accounting records for advertising, profiling or unrelated commercial purposes.

We may disclose information when required by applicable law, to protect against fraud or a security incident, or when you explicitly authorize a separate transfer consistent with Google's Limited Use requirements.

7. Retention and deletion

Encrypted backup files remain in the authorized Google Drive folder until the account owner or an authorized administrator deletes them under the applicable business-record retention policy. The current workflow does not automatically purge old backup files. Audit, legal and accounting record-retention obligations may require preserving the underlying books independently of the Google Drive integration. Google Drive is not represented as an immutable archive or as a guarantee of storage in India.

Temporary backup files are scheduled for deletion from the GitHub runner when a job finishes, subject to runner and provider handling. Workflow summaries and execution metadata may remain in GitHub under the organization's retention settings. Deleting an encrypted backup from Google Drive is a separate action from removing the production accounting records or statutory audit logs.

8. Your choices, access and revocation

You decide whether to authorize the connector. You can withdraw its Google account access at any time from Google Account → Third-party access. Revocation prevents new authorized Google API access, subject to already-running sessions and Google's revocation process, but does not itself erase previously uploaded backup files. To stop automated jobs completely, an administrator must also disable the VYNDI OS backup schedule and remove the stored OAuth token from the integration.

You may contact us to ask about access, correction or deletion of information processed through this integration, subject to applicable security and statutory accounting-record retention obligations. Where the Google Drive folder is in your account, you can inspect and manage its encrypted files directly; recovering their contents requires the corresponding authorized private decryption identity.

9. Storage location and compliance limitations

Google Drive account storage and supporting infrastructure can be outside India. We do not claim that using this integration fulfills Indian company-law requirements for daily physical backup storage in India, that it replaces an independently tested statutory backup, or that it constitutes a Chartered Accountant's audit opinion. Financial-record compliance must be assessed separately for the applicable legal entity and regulatory duties.

10. Children and unrelated processing

The backup connector is intended for authorized business administrators and is not designed or marketed for children. It is not a consumer social product, advertising product or general-purpose Google Drive file-search service.

11. Changes to this policy

We may update this notice when the connector's permissions, providers, features or data-handling practices change. Material changes affecting Google user data will be disclosed before new uses begin; additional authorization will be requested where required. The effective date at the top identifies the published version.

12. Privacy contact

Questions, access requests, concerns and revocation or deletion assistance may be directed to info@vayushastr.com. Postal correspondence: Vāyú Shastr, Bilichi, Coimbatore 641019, Tamil Nadu, India.

The conditions for choosing to authorize or use this optional connector are described in the VYNDI OS Backup Terms of Service.

VYNDI OS Backup is an independent Vāyú Shastr integration and is not a product of, or endorsed by, Google.