1. Ending access and the account-closure windows
For ordinary cancellation of subscription renewal, paid access ends at the end of the paid subscription period. Suspension and other termination are separate matters governed by the applicable agreement. Clicking Cancel, removing a team member or stopping use is not itself deletion of the workspace. After paid subscription access ends:
The two intervals start when paid access actually ends, rather than when cancellation is requested. They do not postpone a valid individual privacy request, override a shorter legal or separately agreed processing obligation, or remove a legally required right after the export-request window.
Data retention is not a promise of restoration. Keep independent copies of business records you are entitled to retain. Reactivation does not guarantee recovery of records already permanently deleted.
2. Requesting an export
Contact support@dispoiq.app within the 90-day window to request a post-access export. Identify your business, the relevant workspace and the categories of information requested. We need to establish your authority before disclosing workspace records. Do not send passwords, API keys, full contact lists or identity documents in the initial message. A request received within the 90-day request window is not canceled merely because that window expires. DispoIQ will preserve the information it is authorized to provide and needs to fulfill that request until the request is fulfilled or otherwise lawfully resolved, except to the extent an earlier deletion obligation requires a different result. Routine deletion after 180 days will not by itself defeat such a timely request. An export must respect the customer’s permissions, other people’s rights and applicable source licenses. Customer Content, recipient submissions and licensed property or contact information can have different treatment. Saving a sourced record to a workspace, paying for a lookup or adding your notes does not create unrestricted redistribution or post-subscription retention rights in the underlying licensed information. Ask support about the applicable source restrictions for the information involved. Specific report downloads are different from a complete workspace export. For example, the contact import report supports a rejected-row CSV containing stored mapped contact fields and outcome information. It is not a copy of every original CSV column: ignored columns and the original file’s exact formatting are not reconstructed. A filtered reporting CSV likewise does not export every underlying contact, message, attachment or engagement record. Support manages post-access export and deletion requests through support@dispoiq.app. We log the request, check identity and workspace authority proportionately, and coordinate secure fulfillment with authorized technical staff as needed. Additional evidence must be limited to what the request and applicable law require, with an appropriate way to provide it. Work beyond support’s authority is escalated for technical handling. Support will identify the information you are entitled to receive, check the applicable permissions and coordinate an appropriate export format and secure delivery with authorized technical staff. For a lawful deletion request, we will identify the covered records and coordinate the necessary actions rather than treating removal from one screen as completion. We will record the outcome, any justified remaining retention and further action required by applicable law or the accepted processing terms. Where those terms or law require return or deletion at the end of covered processing, DispoIQ will carry it out, at the customer’s choice where required, except for retention required by law. The commercial windows above do not defer those duties or an earlier binding source-license obligation. This policy does not promise an instant download, a particular full-workspace format, access to another customer’s records or a new export/assistance fee. The adopted support-managed process does not establish that every extraction or secure-delivery tool is implemented.3. Removing contacts, numbers, deals and users
Recoverable contact deletion. Moving a contact to Deleted contacts retains its record and group memberships so that it can be restored. It is not erasure of personal information. A retained deleted contact can also continue to affect duplicate matching. Permanent contact deletion. The separate permanent-deletion action requires confirmation and applies to a previously deleted contact. Related records can restrict whether the operation succeeds. It does not mean that every associated import row, conversation, delivery event, audit record or provider copy has been erased. A successful permanent deletion is not a normal restore operation. Phone removal and suppression. Removing or archiving a phone line and deleting a contact are different operations. An archived phone history can remain. Deletion is not permission to contact someone again: recipient opt-outs and other valid suppression grounds must still be honored. A record’s removal must not be used to bypass suppression through a new import or another sending number. Deals and uploaded materials. Removing a deal and removing its stored files are separate parts of deletion. In-flight communications and related records can affect the operation. Removing the database record does not by itself establish that every uploaded object, publicly served copy, cache or recipient’s download has disappeared. Team access. Removing a workspace member changes that person’s workspace access. It is not deletion of the business’s workspace, every historical action or the person’s entire authentication-provider identity. Contact support if the requested action goes beyond an available record-level control. Do not treat a failed deletion attempt or disappearance from one screen as confirmation of complete erasure.4. Retention by category and purpose
Retention depends on what the record is for, the instructions and permissions that apply to it, unresolved matters and applicable law. A reason to retain one category does not authorize keeping every other category indefinitely.
DispoIQ will use the criteria above to determine what information remains necessary and when it must be removed. Support will coordinate review with authorized staff when the relevant purpose ends or a request, instruction or applicable obligation requires action. The review will identify the affected categories, applicable duties and disposal or restricted-retention steps. Information no longer justified by a relevant purpose will be deleted, subject to applicable requirements. A hold will be limited to the information and period justified by its reason, reviewed when that reason changes or ends, and released when preservation is no longer required. These criteria do not establish a fixed retention period for every record or an automated deletion schedule.
Any retention exception must have an applicable purpose or requirement and remain limited to the relevant information. Retaining a record does not authorize an unrelated marketing, resale or model-training use. A legal hold concerns records relevant to the matter requiring preservation; it is not a general exception for all workspace information.