Effective date: May 2026
Last updated: May 2026
This page explains how BuildPod handles customer data, operational records, backups, retention, exports, deletion, tenant isolation, and incident response.
Customer owns its operational and business data entered into BuildPod OS.
BuildPod processes customer data to provide, secure, support, maintain, troubleshoot, improve, and administer the service. BuildPod generally acts as a service provider or processor for business customer data, subject to the applicable agreement.
A separate Data Processing Addendum may be made available for eligible business or enterprise customers, or where required by contract. This page does not imply that a signed DPA automatically exists.
BuildPod maintains platform backup and recovery procedures according to operational practices. Backups support platform recovery, not unlimited customer-controlled undo.
Backup and point-in-time recovery processes are designed for platform-level recovery after incidents, failed deployments, infrastructure issues, or broad data integrity events. They are not a guaranteed individual item rollback service.
No backup system can eliminate every recovery risk. Customers should export business records needed for their own compliance, accounting, archive, or operational needs.
Active account data is generally retained while the account is active. Terminated or deleted account data may be retained for a reasonable period for backup, legal, security, dispute, fraud-prevention, and operational needs.
Legal hold, billing disputes, investigation, security review, fraud prevention, operational integrity, or compliance obligations may require BuildPod to retain certain records longer than an ordinary deletion or account-closure request.
Backup deletion follows backup rotation. Exact retention may vary by plan, agreement, legal requirement, or operational need.
Exports may be available in-app or through support. Large or complex exports may require support. Export formats and availability may vary by module, data type, plan, technical readiness, and whether the requested data is active, archived, or stored in audit-oriented records.
Deletion requests are subject to legal, contractual, security, backup, and operational limits. Deleted data may remain in backups until rotation. Some records may be archived instead of hard-deleted for audit, safety, security, billing, or traceability reasons.
BuildPod uses organization scoping, role-based access, and server-derived organization context to separate customer environments. Diagnostic tools are developer-gated and are not available to tenant admins by default.
BuildPod investigates security and data incidents. Customer notification is handled according to applicable law and agreements.
Contact BuildPod through the support or account contact information made available in the service or in your order/subscription materials.