> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dispoiq.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Data retention, export and deletion

> Understand account closure, lawful retention and support-managed requests.

Effective date: October 8, 2026. Document version: 1.0.

DispoIQ LLC provides business software for managing deals, contacts and communications. This policy explains the distinction between ending paid access, requesting an export, removing a record and deleting information from the systems involved in the service.

Your accepted Terms and applicable Privacy Notice address related subscription and personal-information matters. A separately agreed [Data processing addendum](/policies/data-processing-addendum) governs its covered customer-directed processing. Publishing this policy does not independently amend an existing agreement, replace an individual's privacy rights or grant new rights in licensed information.

## 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:

| Interval | What it means |
| - | - |
| **90 days from the end of paid access** | The customer may request export of Customer Content and Recipient Submissions it is entitled to receive. This is an export-request window; it does not extend ordinary paid application access. |
| **After 180 days from the end of paid access** | DispoIQ may delete eligible workspace records. This is an eligibility threshold, not a guarantee that every record or copy is erased on day 180. |

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](mailto: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](mailto: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.

| Records | Relevant retention criteria |
| - | - |
| Workspace contacts, notes, groups, deal materials and recipient submissions | The enabled service and lawful customer instructions; the adopted post-access export and possible deletion windows; a valid earlier deletion request or applicable obligation; narrowly relevant unresolved matters. |
| Import history, stored mapped rows and source/enrichment results | Import reconciliation and correction, duplicate outcomes, permitted follow-up or enrichment and actual source restrictions. Original ignored CSV cells may never have been stored. Separate import and source records need their own deletion treatment. |
| Communications, delivery events, engagement histories and derived summaries | Providing the customer's communication/reporting functions, resolving delivery and usage outcomes, and responding to relevant complaints or disputes. Removing a contact does not necessarily remove these records or summaries. |
| Consent, opt-out and suppression evidence | Maintaining applicable communication restrictions and demonstrating the relevant permission, withdrawal or compliance history. Keep the information necessary for those purposes, rather than treating the entire marketing profile as required suppression evidence. |
| Subscription, invoice, payment, wallet and usage-reconciliation records | Maintaining financial entitlements, reconciling incurred charges and pending outcomes, correcting billing errors, accounting/tax obligations and relevant disputes. These purposes can continue after paid access ends. |
| Account, access and security/diagnostic records | Managing identity and permissions, investigating specific failures or abuse, and meeting applicable security or legal obligations. Customer removal does not erase independently held authentication or diagnostic records. |
| Support correspondence and privacy-request records | Resolving the request, recording the response and verification necessary for it, and meeting relevant complaint, dispute or legal recordkeeping requirements. Avoid keeping unnecessary identification evidence. |
| Waitlist, website, analytics and referral records | Their specific inquiry, attribution, measurement or partner-administration purpose and applicable choices. Browser-cookie lifetimes do not describe server-record retention, and a subscriber's closure date does not govern every visitor's record. |

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.

## 5. Provider copies, files, backups and deletion completion

Application records, uploaded files, derived reports, logs, provider records and backups can require different deletion actions. Deleting a record in DispoIQ does not automatically erase independent copies held by the customer, an intended recipient or the original data source.

For providers acting on our behalf, applicable processing agreements and law govern the deletion instructions and cooperation required. The limits of a self-service control do not excuse a legally required deletion or provider-notification obligation. Independently held payment, carrier, source or recipient records need their own applicable assessment.

Support will coordinate authorized deletion work for the relevant active records and related stored imports, derived information and files, and any required onward instructions or cooperation. We will record the scope and outcome, including justified retained information and remaining required work, rather than confirm complete erasure solely from a record-level deletion. Retained copies must be protected, restricted to their justified purpose or another lawful agreed instruction, and deleted when the justification ends, subject to applicable requirements.

Backups and archived copies will be addressed under the applicable law and accepted processing terms. If those requirements permit deletion to be deferred for a protected backup or archive, the copy must remain restricted and the deletion or other required treatment must be carried out when restoration, access or another applicable trigger requires it. This is not a general exemption for backups or permission to reuse information whose use is restricted.

This policy offers no fixed backup rotation, deletion-job schedule, universal erasure certificate or guaranteed backup-erasure date. Retained personal information remains subject to applicable confidentiality, security and permitted-use restrictions. Restoring data must not be treated as authorization to disregard a valid deletion, correction or opt-out instruction.

## 6. Wallet entitlements and external resources

The 90-day export window and possible deletion after 180 days **do not expire or forfeit unused wallet funds purchased with money**. Under the adopted billing policy, those funds are ordinarily nonrefundable and retained for reactivation, with the separately specified refund exceptions preserved. Records needed to maintain the financial entitlement require separate treatment from disposable workspace content. See the [Subscription, cancellation and refund policy](/policies/billing-refunds).

The number-rental policy is a **flat USD \$5 per rented number per month**, with **no volume tiers and no separate number activation fee**. Registration, messaging and subscription charges are separate under their accepted schedules. The [Phone number management guide](/help/phone-numbers) explains purchase, billing and operational details; the first USD \$5 rental charge applies only after successful number activation and covers one month, with subsequent USD \$5 renewals on that number's monthly anniversary. This policy does not establish an enabled recurring collection process.

If you voluntarily release a number before its paid rental month ends, there is no ordinary prorated refund for the unused rental time. Billing-error corrections, refunds required by applicable law and any refund DispoIQ expressly owes remain preserved. This rule does not reduce separate remedies for DispoIQ-caused suspension, breach or early termination.

Rented phone numbers are released when paid subscription access ends, unless you separately agree to paid retention identifying the numbers and the charges and terms you accept. Canceling renewal does not release them immediately: ordinary paid access continues to the end of the paid period. Before an end-of-access release, DispoIQ will warn you about losing the number and explain any transfer process actually available for it. A request for retention or transfer does not establish an agreement or guarantee availability or recovery.

The export-request window does not extend number retention or messaging access. Data deletion and resource release remain different actions. This policy does not establish an automated release or billing-stop workflow, a free grace period, unlimited continuing charges or automatic card-funding authorization. Any other separately recurring resource requires its own accepted terms.

Support will record the end of paid access and any separately accepted paid-retention arrangement, coordinate the warning and release described above with authorized technical staff, and arrange for future rental renewals to stop for a released number. We will explain any transfer process actually available, record the release or retention outcome and address remaining required billing or transfer steps. Valid charges already incurred and applicable refund rights remain governed by the accepted agreement; releasing a number does not create a second charge for the same rental period. This support-led procedure does not establish an automated executor or make an unavailable transfer or recovery possible.

No new wallet-expiration date, resource charge, number-transfer entitlement or refund restriction is created by this policy.

## 7. Individual privacy requests

You do not need a subscription or an account to send a privacy request to **[support@dispoiq.app](mailto:support@dispoiq.app)**. Where a business using DispoIQ controls the relevant information, identify that business and contact it as well; we may need to coordinate the request with it. A request concerning DispoIQ's own processing follows our privacy contact route.

Support manages these requests using proportionate verification, secure fulfillment arrangements and technical escalation as needed, as described in the support procedure above. These steps do not suspend mandatory deadlines or impose identity checks on every opt-out.

The 90/180-day account-closure intervals are not individual-rights deadlines. Applicable access, correction, deletion, portability and other rights, verification requirements and response periods follow the law and actual processing role. A source-license restriction on commercial export must not be used to defeat a non-excludable privacy right.

Your applicable Privacy Notice explains the related scope and request route. For questions about retention, export or deletion, contact [support@dispoiq.app](mailto:support@dispoiq.app) or write to DispoIQ LLC, 7901 4th St N STE 300, St Petersburg, FL 33702, United States. Please avoid unnecessary sensitive information in your initial message.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.