Disconnecting and data handling
What happens when you disconnect an integration: token revocation, retention windows, and full deletion.
What Watari keeps, what it removes, and how long each thing lives.
Disconnecting an integration
Go to Settings → Connected tools, click Configure on the tool you want to disconnect, then click Disconnect at the foot of the dialog and confirm. What happens immediately:
- Watari revokes the access token on its side. The token is deleted from the database.
- Where the provider supports it, Watari makes a revocation call to the provider: GitHub App uninstall sends Watari a webhook that terminates access; Slack tokens are actively revoked; Zendesk and Intercom webhooks are deregistered. Freshdesk's inbound webhook is an Automation Rule you own, so remove that rule in Freshdesk to fully stop delivery, Watari can't deregister a webhook it didn't provision.
- No new tickets flow in from the disconnected support tool. No new posts are made to the disconnected routing destination.
For GitHub specifically, uninstalling the App from your GitHub organization settings is the authoritative revocation, not the Watari disconnect button. If you disconnect from Watari but leave the App installed on GitHub, Watari's App credentials technically remain valid until GitHub removes the installation. For a clean revocation, do both.
What stays after disconnect
Disconnecting an integration does not delete your Watari data:
- All bugs, RCAs, and draft PRs remain in the Watari dashboard.
- The ticket and bug history remains searchable and downloadable from
/issues. - Repository indexes are kept warm for 30 days after the GitHub App is disconnected. If you reconnect within that window, indexing resumes incrementally. You don't pay the cost of a full reindex.
Removing a single repository under Codebase makes the same promise: its issues stay, and what Watari learned from its code is kept 30 days, then deleted. Only owners and admins can remove a repository.
After 30 days, the repository index is purged. Bug records and RCAs that reference those code locations are still accessible; only the index itself (the searchable code representation) is removed.
Full account deletion
The workspace owner can delete the workspace from Settings → Workspace (Delete workspace, at the bottom of the page). You can also contact us or email support@watari.ai from the account owner's address.
What deletion covers:
- All bugs, RCAs, PR drafts, and linked ticket records.
- All repository indexes and code-location records.
- All OAuth tokens and integration credentials.
- All uploaded attachments.
- Your organization record, team member records, and billing history (see invoice retention below).
Deleting a workspace takes effect immediately: it disappears for every member and any subscription is cancelled. The data is then held for 30 days, during which the workspace can be restored by contacting support. After 30 days it is permanently purged, in line with GDPR and DPDP timelines.
After the 30-day recovery window, deletion is permanent and cannot be undone. Export your data before deleting if you need a record.
Data retention windows
| Data | Retention |
|---|---|
| Active workspace data | Retained indefinitely while subscription is active |
| Repository index after disconnect | 30 days from disconnect, then purged |
| Full workspace after deletion | Recoverable via support for 30 days, then fully purged |
| Webhook delivery logs | 90 days |
| Billing invoices | 7 years (statutory requirement) |
Data export
Bug list export. From /issues, use the Export CSV action to download your Mapped Issue list with titles, severities, statuses, and billing dates.
Full account export. A full structured export of all your workspace data (bugs, RCAs, ticket associations, PR links) is available on request. Email support@watari.ai or use /contact. We process export requests within 5 business days.
Next: Workspace and team: invite teammates, assign roles, and enroll in MFA: inviting teammates, managing roles, and enrolling in MFA.