01. Who operates this service
Marrow ERP Private Backups is intended as an internal business recovery tool operated by Marrow Industries Private Limited (Cossy Seating), for its authorized owner. The operator name and support contact have been confirmed by the owner.
Contact: cossyseating@gmail.com. This policy covers the backup service and these information pages, not every activity of the ERP, Google, GitHub or other providers.
02. Information involved
- Business database contents
- The authorized export may include customer, vendor and staff information; contact details; and orders, payments, purchases, stock and other operational records present in the database. It may also include database security and application metadata included in the approved export scope.
- Google connection information
- OAuth credentials and an access/refresh token would allow the job to act with the owner’s approved file permission. The service would not ask for or store the owner’s Google password.
- Backup files and file metadata
- Encrypted archives, file and folder identifiers, names, creation times, sizes, checksums, and ownership or permission metadata needed to store, check and manage the app’s files. Encryption of archive contents does not hide all file metadata.
- Operational information
- Run identifiers, timestamps, success/failure status, sanitized error categories and backup inventory. Logs and alerts are intended to exclude record contents, passwords, tokens and recovery keys.
03. Google Drive permission
The intended scope is https://www.googleapis.com/auth/drive.file. It permits access to files created by the app or explicitly selected for the app. The intended tasks are to create a dedicated backup folder and encrypted files, read back its uploaded files for checks, and manage only its own eligible backup copies.
This is not full-Drive, Gmail, Google Contacts or Calendar access. The declared scope and the actual authorization request must match before access is granted. Merely creating an OAuth client does not grant access to any Drive files.
Google describes this permission in its Drive authorization guide.
04. Purpose, processing and providers
The proposed purpose is to create recovery copies, verify them, apply approved retention, and notify the owner of failures or missed backups. Data would not be sold, used for advertising, unrelated profiling or AI-model training.
- Supabase holds the source database that the approved backup job would read.
- GitHub Actions would temporarily process unencrypted database contents during export, then encrypt the archive before upload. A private repository does not remove GitHub from this processing path.
- Google Drive would store encrypted archives and the file metadata needed for storage and verification.
- Monitoring and email providers are intended to receive limited run-status information and an owner alert address, not database contents or recovery keys. Independent monitoring is planned using Cloudflare; the final alert path is not yet enabled and must be documented before activation.
Provider processing and infrastructure locations depend on the selected services and account configuration. This service does not promise that all processing or storage remains in India.
The intended use and transfer of information received through Google APIs must follow the Google API Services User Data Policy, including Limited Use requirements where applicable. Publication of this statement is not Google verification or a compliance certification.
05. Protection and authorized access
The planned controls include encrypted network connections, encryption of the archive before it reaches Drive, restricted automation credentials, and no public file sharing. The automated job is intended to use a public encryption key; the owner keeps the matching private recovery key separately.
Temporary unencrypted exports must be removed from the runner when the job finishes, including failure paths. The implementation and evidence for that cleanup, credential protection, provider retention and log redaction remain to be verified.
Decrypted records are intended only for the authorized owner or people specifically approved for recovery or support. No system can promise absolute security. Losing the recovery key may make encrypted copies unusable.
06. Retention and deletion
The proposed rolling retention is 30 days for new backups created by this job. Existing manual backups are excluded. Cleanup begins disabled and must not run until file ownership, scope and recovery safeguards are tested.
Once separately enabled, cleanup is intended to move eligible expired job-owned files to Drive Trash, while preserving a verified recoverable copy. It must not automatically empty Trash. Google normally permanently deletes files after 30 days in Trash; the owner may permanently delete them sooner. See Google’s deletion guidance.
Operational logs have separate provider retention settings. Their final retention period must be recorded before activation. Any legal or business requirement to retain original records remains separate from this rolling backup window; the backup policy is not permission to erase required business records.
07. Your choices and requests
The owner may pause the scheduled job and remove the app’s access in Google Account settings. Revocation prevents future use of that authorization; it does not automatically delete existing backups or data already processed by other services.
To request access information, correction of contact details, deletion or help with disconnection, email cossyseating@gmail.com. Requests may require verification of authority. Do not send passwords, tokens, recovery keys or database exports by email.
Deletion of stored copies and removal of credentials are separate actions. Provider retention, legal obligations and recovery requirements may affect what can be removed and when; no immediate deletion across all providers is promised.
08. Information-page visitors
These information pages contain no app-added analytics, advertising, forms, account login, scripts or tracking cookies. They do not connect to the ERP or Google Drive. Clicking a contact link opens the visitor’s email application; clicking a provider reference navigates to that provider.
These public information pages are hosted on Cloudflare Pages. Cloudflare processes requests to deliver and protect the site, which may include IP address, browser information and security logs, under its privacy policy. We do not collect visitor information through forms or install advertising trackers on these pages. Provider log retention is governed by the provider’s service and policies; we do not promise immediate deletion of its security records.
09. Changes and contact
This version takes effect on 12 October 2026 for these information pages and the described setup activities. Before the backup service is activated, its actual operation, final monitoring/email providers and log-retention settings must be checked against this policy and any necessary updates published. Material changes to data use or access would require updated disclosures and, where required, fresh consent before the change takes effect.
Questions: cossyseating@gmail.com · Marrow Industries Private Limited (Cossy Seating).