Retention and Deletion
Content Swarm keeps personal data only while it is needed for the service, legal duties, security, or disputes. The existing policy states this principle but the inspected code and documents do not contain a complete numerical schedule. Where a period is not documented, this table says so rather than guessing.
| Data type | How long | Why | How to delete |
|---|---|---|---|
| Account and contact data | No complete period is defined in the code or current policy. | Account administration, service delivery, support, security, and legal duties. | Ask for deletion at support@contentswarm.io. Content Swarm will verify the request and apply any required legal hold. |
| Team or swarm membership and company email | Company email records are removed when a user is removed from a team. No period is documented for the membership record, history, or removal audit log. | Team administration, access, reporting, and audit. | A team administrator can remove membership. Contact support for deletion of the account and related records. |
| LinkedIn access and refresh tokens | The code tracks token expiry but does not define a deletion period. Tokens are preserved when a user leaves a team. | LinkedIn connection, authorised API actions, token refresh, and reconnection. | Contact support to disconnect LinkedIn and delete stored tokens. The product control and operational deletion time are not documented in the inspected materials. |
| Posts, post URLs, attachments, generated content, comments, shares, and reactions | Selected or posted comment text and task records are stored without a scheduled deletion period in the code. Unselected AI suggestions may only be returned in the API response, but provider retention is not documented in the inspected materials. | Provide content and engagement features, team coordination, audit, and reporting. | Delete the relevant content in the product where a control is available, or contact support for deletion or export. |
| Product analytics and trackers | The product code and inspected provider configuration do not set a complete retention period. | Measure feature use, diagnose problems, and improve the service. | Use available consent or opt-out controls and contact support. Provider-side deletion may be needed. |
| Application errors, audit records, and security logs | Reconnect attempt records are scheduled for cleanup after 30 days. No period is documented for other logs, error records, issue tracking, or security evidence. | Security, incident response, debugging, audit, and service reliability. | Contact support. Some records may be retained to protect the service or meet legal duties. |
| Email and support communications | No retention period is documented in the inspected materials. | Support, service notices, delivery evidence, and legal records. | Contact support and identify the messages or request concerned. |
| Backups | Backup frequency, isolation, and expiry are not documented in the inspected repositories. | Recovery, resilience, and incident response. | Deleted data will be put beyond ordinary use in backups and removed as the backup cycle expires, once the cycle is confirmed. |
When a customer contract ends
The Data Processing Agreement gives the customer a choice to return or delete customer personal data, unless law requires retention. The precise production deletion window, export format, backup cycle, and evidence of deletion still need confirmation.
The inspected materials do not state the deletion window after contract end, the export process, backup expiry, legal hold process, or how completion is recorded.
Deletion requests
Email support@contentswarm.io. State whether the request concerns an account, LinkedIn connection, team, content item, extension data, analytics, or all personal data. We may ask for information needed to verify identity and authority.
Related information
See the Privacy Policy, Subprocessor Information, and AI Provider Information.
Content Swarm Limited, 727-729 High Road, London N12 0BP, United Kingdom. Contact support@contentswarm.io.