Deletion is connector-level
Deleting a connector discards the data synced through it and the record IDs built from it. That’s the whole of what you can delete yourself - see Delete Connector. Anything narrower - one model, one field, a subset of employees - is a support request. Nothing on your end deletes below the connector.The 7-day window
A deleted connector’s data is recoverable for seven days. Inside that window, email support@bindbee.dev with the connector ID and the deletion can be stopped before it completes. After seven days the data is permanently removed and cannot be retrieved - not by you, and not by support. This clears Bindbee’s copy only. Anything you have already synced into your own store is yours to delete, so plan retention on your side against the same event.Retention and deletion follow Bindbee’s SOC 2, ISO and GDPR commitments - see the Trust Center.
Deleting a subset of data
A customer often narrows what they are willing to share after the fact. They authorize everything, data syncs, and then they decide only US employees should ever have been sent. Narrowing your scope stops future collection, but it does not remove what has already synced. For that, email support@bindbee.dev with the connector and the filter that describes what should go.Related
- Delete Connector - the endpoint
- Scoping - stopping collection, which deletion does not do
- Roles & permissions - who can delete a Production connector
- Go-Live checklist - offboarding and retention before launch