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

# Service categories

> Service functions, information handling and requests for processing details.

Last updated: October 8, 2026.

DispoIQ LLC uses providers to operate its application, communications, documentation website, and customer support. This page describes service categories and the functions for which providers receive information. A provider's role depends on the particular activity: processing customer workspace information on instructions differs from handling DispoIQ's own account, billing, support, or website information.

This overview does not grant processing authorization or incorporate a Data Processing Addendum. For questions about personal-information handling, contact **[support@dispoiq.app](mailto:support@dispoiq.app)**.

## 1. Service categories and scope

The following categories describe service functions and the information involved, rather than saying that every provider receives every workspace record. This overview does not identify the providers engaged for each activity or serve as a complete subprocessor roster. Applicable law and any separately agreed Data Processing Addendum continue to govern required provider-identification information, authorization, notices and objections; category labels do not satisfy those requirements by themselves.

Contact **[support@dispoiq.app](mailto:support@dispoiq.app)** for provider-identifying information, processing-location information, and authorization details required for your applicable processing relationship. We will supply information required by applicable law or a separately agreed Data Processing Addendum through an appropriate channel. This overview does not limit any required disclosure, or replace information or authorization that must be provided before processing begins.

| Service category | Function | Relevant information | Scope |
| - | - | - | - |
| Application hosting | Serve the application and deal pages and run enabled service functions | Request and network information, content needed to respond to requests, and operational records | Application users and deal visitors; the information involved depends on the requested function |
| Database and uploaded-file storage | Store service records and support uploaded deal materials | Account and workspace records, contacts, messages, offers, engagement records, and uploaded photographs or documents, as applicable | Records used by the relevant feature; this category does not promise a particular storage region or that every file is private |
| SMS delivery and reply handling | Route permitted texts, receive replies, and report message outcomes | Sender and recipient numbers, message content, timestamps, delivery or failure information, and relevant opt-out records | Customers using enabled SMS functions and their recipients; delivery involves communications providers and carriers |
| Messaging registration and review | Submit and maintain registrations needed for supported messaging | Business name, address, tax identifier, representative details, registration descriptions, sample messages, and permission descriptions | Customers registering for messaging; information is supplied to the relevant registration and review participants |
| User-notification email | Send application notifications to users | Recipient email address, notification content, routing information, and delivery records | Application notifications; this entry does not describe an enabled customer email-sending feature |
| Billing and referral handling | Process subscriptions and payments and administer enabled referral commissions and payouts | Billing and transaction details, payment-method summaries, provider identifiers, referral attribution, commission and payout records, and relevant recipient details | Customers and referral participants using those functions; payment or payout providers may collect additional information directly |
| Property search and contact enrichment | Respond to enabled property searches and customer-directed lookups | Search criteria and identity or address information needed for a lookup; returned property, ownership and contact information within the permitted feature scope | Customers using these features; source permissions and availability govern which results can be supplied, and a lookup does not establish messaging consent |
| Map resources | Display maps for properties and search results | Map or property locations and technical request information needed to serve map resources | Users viewing supported maps; displaying a property location is not a statement that the service collects the user’s device location |
| Diagnostics and operational monitoring | Investigate errors, support issue reports, and monitor service operation | Error details, relevant technical context, account or workspace identifiers where included, operational records, and information voluntarily submitted in an issue report | Where configured for the relevant surface; diagnostic records can contain personal information and are not assumed to be anonymous |
| Website and product analytics | Measure selected marketing pages and authenticated application use | Browser and usage information, technical identifiers, selected page or control events, and relevant account or workspace associations | Where configured on those surfaces; buyer-facing deal engagement is recorded separately by DispoIQ’s own tracking service |
| Authentication and account access | User authentication and account access | User identity and contact information, account and organization identifiers, authentication and session information | People signing in to the application; not a general transfer of customer contact lists to the authentication provider |
| Customer support and request intake | Support correspondence and privacy-request intake | Sender and recipient details, message content, attachments supplied in correspondence, and conversation records | Requests received by the connected support inbox; not a copy of every workspace's records |
| Company email and routing | Company email, including routing support and privacy correspondence | Email addresses, message content, attachments, and delivery information | Company mail and the intake path to the support inbox |
| Documentation hosting | Hosting the documentation website at docs.dispoiq.app | Published documentation and technical information involved in serving website requests | Documentation visitors; not hosting the application database or receiving customer contact lists through this documentation setup |

## 2. Locations and onward processing

A provider's business address is different from its processing locations. Providers may use infrastructure, affiliates, support personnel, or further service providers in multiple countries. A published list of available regions does not identify the settings selected for DispoIQ.

This overview offers no US-only storage or processing guarantee. Limiting messaging destinations to the United States and Canada does not limit every location in which information is handled.

## 3. Other recipients and services

Customer communications involve delivery providers and telecommunications carriers. Messaging registration can also disclose business and representative information to the relevant registration and review participants. Their roles must be assessed for the particular service, including any independent regulatory or network purposes.

Payment providers can process transaction information both to deliver payment services and for their own fraud-prevention, regulatory, or other disclosed purposes. Independently sourced property or contact-information suppliers also require separate assessment: supplying data to DispoIQ, receiving a customer-directed lookup, and independently reusing information are different activities.

DispoIQ's own website or product analytics are distinct from hosting records on a customer's instructions. A customer-selected integration may have its own agreement and privacy notice. These distinctions do not excuse any disclosure or contractual protection required for the actual processing.

Published deal content is also available to the audience with access to the deal, and recipients receive messages addressed to them. Those disclosures are different from engaging a provider to process information on instructions. A personalized deal link does not establish that every linked file is private.

## 4. Changes and questions

DispoIQ's Data Processing Addendum provides general authorization, when separately accepted, to engage or replace subprocessors at any time for any lawful business reason consistent with that addendum. Its default does not require change notice, individual approval or an objection opportunity. Notices, opportunities to object, specific authorizations and identifying information required by applicable law or a separately accepted agreement remain required, before engagement where required. The addendum's processing limits, downstream safeguards, transfer requirements and DispoIQ's own responsibility continue to apply.

The subscription price-change notice remains separate from this subprocessor-change policy. Posting this overview alone does not establish acceptance of a Data Processing Addendum or authorize a new processing purpose.

For questions about these service categories or the handling of your information, contact **[support@dispoiq.app](mailto:support@dispoiq.app)**. Please avoid sending passwords, API keys, complete contact lists, or identity documents in an initial message.


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