What this policy covers and where separate customer terms apply.
Approvals and responsibilities stay visible throughout the workflow.
Responsibilities, dependencies and limitations stay explicit.
Submit a request
Email support.buildingbots@gmail.com and identify the customer or account, affected service, and whether the request concerns access, correction, export, connector disconnection, service closure or deletion. Identity and authority will be verified.
Disconnection is not deletion
Revoking a provider connection stops future authorised calls but may leave necessary configuration, audit or transaction records. Third-party platforms may also require a separate request made directly to that provider.
Cancellation is not deletion
Ending or not renewing a subscription may pause automation and begin an agreed export/read-only period. It does not automatically erase business records. Permanent offboarding includes agreed export/handover, access revocation and a separate deletion workflow.
What deletion should cover
Within Building Bots’ control: primary records, source files, derived extracts and indexes, generated artifacts, caches and connected-system copies. Backups may expire on a documented cycle rather than being selectively rewritten immediately.
Necessary exceptions
Security, incident, tax, dispute, fraud-prevention or other legally required records may need separate retention. Any verified exception should be explained rather than hidden behind a blanket refusal.
Confirmation
The request should be tracked and completion confirmed without exposing another person’s data. No fixed completion period is promised until the production workflow and applicable legal requirements are verified.
Operational details pending confirmation
Identity checks; export formats; acknowledgement/completion targets; system inventory owner; backup expiry; legal exceptions; deletion evidence; connector revocation and exceptional assistance fees.