Data Retention and Export
AB Projects stores your data on Microsoft Azure. This article describes how data is retained and how you can get at it today — and is honest about what isn't self-serve yet.
Retention
- Task and project data is kept until it is explicitly deleted — there is no automatic time-based purge.
- Deletes are soft-deletes: when a task, project, or member is removed, the record is flagged as deleted and retained in storage rather than immediately destroyed. This is how attribution and history stay intact.
- There is currently no self-serve "restore" UI and no published recovery window. If something was deleted by mistake, contact support promptly — recovery is a manual, best-effort request, not a guaranteed time-boxed feature.
- Change history (field changes with who/when/old→new/reason) and comments are preserved for traceability, and the linked Teams channel keeps a timestamped record of activity (see Adaptive Cards and Task Previews).
Exporting data
- AB Projects does not currently offer a built-in export — there is no Reports/Export section, CSV download, or change-log export for projects (see Exporting and Accessing Project Data).
- Ways to access your data today: per-task change history, the Teams channel record, the filtered List/Gantt/Kanban views, the scheduled task digest, and programmatic queries via a connected MCP AI assistant.
- If you need a data export for an audit, migration, or compliance requirement, contact our support team — exports are handled as a manual request, not self-serve.
Hosting
- Data is hosted on Microsoft Azure infrastructure.
- For data-residency, region, or specific retention/compliance requirements, contact support or refer to your Enterprise agreement — these are handled on a per-organization basis rather than self-configured.
For any custom export or specific retention/compliance need, contact our support team.