01. Purpose and current status
Marrow ERP Private Backups is a proposed internal recovery tool for Marrow Industries Private Limited (Cossy Seating). It is intended to create encrypted copies of the authorized ERP database in the owner’s Google Drive.
The automated service is not active. The Google connection, scheduled job, retention, alerts and end-to-end recovery must be verified before reliance on the service. These pages do not provide a new ERP login or access to any business data.
03. Owner responsibilities
- Maintain control of the connected accounts and protect sign-in with strong credentials and appropriate multi-factor authentication.
- Keep the recovery private key safely and separately from the automated job. Test access to it without exposing it in chat, email or logs.
- Confirm that the business has authority to back up the records involved and that the chosen providers and locations are acceptable.
- Keep sufficient storage available, review backup failures and periodically rehearse recovery.
- Maintain any required long-term business or statutory records separately from the rolling recovery-copy policy.
- Report suspected credential exposure promptly and revoke affected access where necessary.
04. Backup scope and recovery
The intended daily schedule is 3:40 AM India time, with 30 days of new job-owned copies. That is a proposed schedule, not a guarantee that every run will occur. Existing manual backups are excluded from automatic cleanup.
A database export is not necessarily a complete copy of the whole platform. For example, file contents held in Supabase Storage require separate handling; database entries that refer to those files do not include the file bytes. Configuration and other dependencies also need an agreed coverage inventory.
A file’s existence does not prove recovery. Upload checks, integrity checks and restoration into a separate environment must be performed. The backup job must not automatically restore over the live ERP. Any live recovery requires separate authorization and a reviewed recovery plan.
No recovery-time or maximum-data-loss commitment has been agreed. Lost recovery keys, missing assets, corrupt exports and provider failures can prevent or delay restoration.
05. Availability, limits and costs
The initial design aims to operate within existing free allowances, with paid usage blocked before activation. It does not promise that providers will remain free or that storage, run time or email quotas will always be sufficient.
Scheduled jobs may be delayed, missed or interrupted. Network failures, account suspension, expired authorization, provider limits and service changes may affect backups or alerts. Independent failure and missed-run alerts are planned but not yet verified.
No paid plan, subscription or additional spending is authorized by viewing these pages. Any proposed paid upgrade requires the owner’s separate approval. This tool is not a substitute for a broader business continuity plan.
06. Third-party services and privacy
The proposed service uses Supabase, GitHub Actions and Google Drive, with separate monitoring and email services to be finalized. Those providers operate under their own terms and policies. Their availability, retention and account decisions are not controlled by this tool.
GitHub would temporarily process unencrypted database records before encryption; Google Drive would receive encrypted archives. See the privacy policy for the intended data use, permissions, retention and owner choices.
These pages do not indicate endorsement, certification or verification by Google or any other provider.
07. Pausing or ending use
The owner may pause the schedule, revoke Google authorization and remove the dedicated automation credentials. These are separate controls and should be checked together when ending the service.
Ending access does not automatically delete stored backups. The owner must separately decide which copies to keep or remove, considering recovery needs and any applicable record-retention duties. Removing all copies or losing the recovery key can make restoration impossible.
Future automated cleanup is intended to use recoverable Drive Trash rather than permanent deletion. Google’s normal Trash expiry still applies, and the owner can delete files permanently sooner.
08. Updates, review and contact
The operator name and contact information have been confirmed by the owner. Service coverage and final provider settings must be checked before backup activation, and these terms updated if necessary. Material changes to access, data handling or costs require updated disclosures and the appropriate approval before implementation.
These terms do not attempt to remove rights that cannot lawfully be excluded. They are not a legal compliance certification or a guarantee of recovery; independent legal advice may be appropriate for the business’s obligations.
Contact: cossyseating@gmail.com · Marrow Industries Private Limited (Cossy Seating). Do not send passwords, access tokens or recovery keys.