LegalLead360 Legal
Lead360 Data Retention and Deletion Policy
How Lead360 retains, exports, suppresses, deletes, and verifies erasure across accounts, communications, recordings, AI data, providers, and backups.
Retention depends on the record, account state, provider, customer configuration, legal duties, and technical deletion path. Hiding or limiting retrieval is not the same as verified erasure.
Retention principles
- Keep personal information only for an identified service, security, legal, contractual, or suppression purpose.
- Use shorter periods for sensitive information and recordings where practical.
- Permit customer export and deletion through available tools and verified support workflows.
- Restrict retained records from new uses after the original purpose ends.
- Document legal holds and deletion exceptions.
Operational retention schedule
| Record group | General approach |
|---|---|
| Active account and configuration | Retained while the service is active and as needed for support, security, billing, and continuity. |
| Disabled sub-account | Generally restorable for 90 days, then eligible for permanent deletion. |
| CRM and customer content | Retained while active or until a valid customer deletion instruction, subject to linked records and exceptions. |
| Communications and recordings | Retained according to customer configuration, provider availability, account needs, and legal requirements. Customers should set the shortest practical period. |
| AI conversations, memory, vectors, traces, and exports | Retained while needed for the configured feature, review, audit, security, or support. Retrieval windows do not automatically erase all underlying records. |
| Payment, tax, consent, fraud, and security records | Retained for applicable legal, accounting, dispute, evidence, and security periods. |
| Backups and snapshots | Retained in rotating or operational cycles and removed or overwritten according to the applicable system process. |
| Suppression records | A minimal record may be retained to ensure an opt-out, objection, or do-not-contact request remains effective. |
Sub-account restoration and purge
A disabled sub-account generally enters a 90-day restoration window. During that time, operational data may remain available for restoration. After the window, the account becomes eligible for deletion. Eligibility is not a representation that all data has already been permanently erased.
A purge inventory or manifest identifies data locations and is not itself proof that deletion ran. A verified purge requires execution across applicable active databases, files, objects, vectors, tenant services, and provider workflows, followed by recorded results and exception handling.
Contact deletion and linked records
Deleting a contact record does not necessarily remove forms, attribution and IP records, conversations, recordings, payments, invoices, consent evidence, automation history, AI memory, vectors, Sales360 research, provider copies, or backups. Some records may relate to multiple people or must remain for legal or security reasons.
Where verified erasure is required, the customer should submit a scoped request identifying the person, account, channels, providers, and relevant date range. Lead360 will identify active locations, delete or de-identify eligible records, document exceptions, and confirm completion based on available tools.
AI memory and learning data
Memory Brain revisions, Memory Sets, Learning Collections, Live Insights, Piece bindings, conversation history, vectors, evaluations, and model traces may be stored separately. A setting that limits retrieval by age or context affects what a bot can use, but does not consistently delete every underlying record.
To remove AI-related data, delete or supersede the source, remove affected bindings, identify vector and trace locations, and use the verified erasure process. Aggregated or de-identified findings may remain where they cannot reasonably be linked back to a person.
Provider and backup copies
Connected providers may keep independent copies according to their instructions, legal duties, fraud controls, or retention policies. Disconnecting an integration or deleting data in Lead360 does not automatically delete provider data. Customers must complete provider deletion separately where Lead360 does not control it.
Deleted data may remain in protected backups until the relevant backup is overwritten or expires. Backup data is isolated from ordinary use and restored only for continuity, security, or recovery. If restored, applicable deletion instructions should be re-applied where technically feasible.
Legal holds and exceptions
Lead360 may retain limited information where necessary for tax, accounting, chargebacks, fraud prevention, consent evidence, security, litigation, legal claims, regulatory obligations, or suppression. A legal hold pauses deletion only for relevant records and should be removed when the purpose ends.
Request export or verified erasure
- Export needed information using available account tools before closing or deleting data.
- Email [email protected] with the subject Data Export or Verified Erasure.
- Identify the customer account, sub-account, person, data types, channels, providers, and request authority.
- Complete reasonable identity and authority verification.
- Review the completion report, retained exceptions, provider actions, and any remaining backup cycle.
Contact
Questions about this document
Email [email protected] and include the document name, customer account, and the issue you want us to review. Do not send passwords, private keys, payment credentials, or PHI.
Contact Lead360