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

# Privacy policy

> How DispoIQ handles personal information and privacy requests.

Effective date: October 8, 2026. Document version: **v1.0**.

DispoIQ LLC ("DispoIQ," "we," "us," or "our") provides business software for managing real estate deals, buyers, contacts, and communications. This policy explains how personal information is handled through our website and service, including customer workspaces, buyer-facing deal pages, and referral-partner features.

Our address is 7901 4th St N STE 300, St Petersburg, FL 33702. Our designated contact for privacy and customer requests is **[support@dispoiq.app](mailto:support@dispoiq.app)**. Messages to that address are routed to our support inbox.

## At a glance

* We receive information from account users and visitors, from businesses using DispoIQ, and from property and contact-data sources.
* A business using DispoIQ can store information about you even if you have never created a DispoIQ account.
* When you open a business's deal link, that business can receive information about your visit and engagement. A personalized or forwarded link can associate a visit with the buyer attached to that link.
* Communications, offers, and contact information submitted through a customer's deal page are available to that customer and its authorized team.
* Service providers process information for functions such as authentication, hosting, payments, messaging, data enrichment, analytics, and error reporting.
* Contact us or the relevant business to request help with your information. Applicable rights and the correct route depend on the information and our role.

## 1. Our role and the businesses using DispoIQ

We use account, billing, website, support, and referral information to operate our own business and service. Customers decide which people they add to their workspaces, which deals they publish, and which communications they send. We also provide functionality for discovering and enriching property and buyer information from third-party sources.

For personal information a customer uploads or collects through its workspace, we provide the software and process that information to deliver the service. The customer is responsible for its own collection, notices, permitted uses, and communications. Its privacy notice may explain practices beyond the processing described here.

Processing responsibilities depend on the activity, applicable law and any separately agreed processing terms. We determine the purposes of our own account, billing, website, support and referral processing. Customers direct the use of their workspace records and communications, while independently sourced discovery information involves separate source and recipient relationships. This policy does not incorporate a data processing agreement or establish that one has been accepted.

This policy does not replace a customer's privacy notice, establish messaging consent, or change rights under applicable law. External websites and providers may have their own notices for services they provide directly.

## 2. Information we receive and why

The categories below describe information involved in the service. The information actually processed depends on the pages you visit and the features you or the relevant customer use. Listing an optional feature here does not mean it is enabled for every customer or that it processes every visitor's information.

CRM and deal sharing, buyer search and skip tracing, and SMS messaging are currently available to paying customer workspaces. Automations and affiliate referral payouts are also enabled features. Application emails currently provide notifications to users; customer email sending is not an enabled feature. Particular functions depend on the customer's feature access and configuration. The mobile-result disclosure in section 5 describes prospective availability; it does not state that paying customers have already received sourced mobile numbers.

| Information | Where it comes from | How it is used |
| - | - | - |
| Account and workspace information: names, email addresses, organization details, account identifiers, roles, preferences, and invitation records | You, your workspace administrator, and our authentication provider | Create and manage accounts, authenticate users, provide permissions, manage seats, and send account notifications |
| Waitlist and inquiry information: name, email, mobile number, plan interest, contact history, and messaging opt-in records | Website forms and your communications with us | Manage access requests, respond to you, and send permitted updates; preserve consent and opt-out records |
| Buyer and contact records: names, company associations, phone numbers, emails, property or mailing addresses, buying preferences, notes, tags, and contact status | Customers, imports, offers, and property or contact-data providers | Maintain customer records, organize audiences, match and deduplicate records, and support permitted customer communications |
| Property and transaction information: ownership, property characteristics, location, sale and mortgage history, and relevant company or filing information | Customers, public-record sources accessed through providers, and licensed data providers | Search for properties and potential buyers, display deal information, and enrich or corroborate customer records |
| Customer content and recipient submissions: contact details, offer price, financing, proposed closing date, earnest money, contingencies, uploaded photographs and documents, replies, and other submitted content | Customers, deal visitors, buyers, and communication recipients | Present deals, deliver offers and replies, support follow-up, and store submissions for the customer's authorized users |
| Messages and related records: message content, sender and recipient numbers or addresses, attachments where supported, timestamps, replies, delivery or failure information, email-open and link-click events where enabled, and opt-out status | Customers, recipients, and communications providers | Route communications, display conversations, report engagement, troubleshoot delivery, calculate usage, and enforce messaging restrictions |
| Messaging registration information: legal business name, business address, tax identifier, website, authorized representative details, registration descriptions, and sample messages | Customer administrators and communications providers | Submit and maintain messaging registrations and respond to registration requirements |
| Billing information: plan, subscriptions, invoices, payments, usage, wallet activity, payment-provider identifiers, and payment-method summaries | Customers and payment providers | Process payments, manage subscriptions and usage balances, reconcile charges, and maintain transaction records |
| Referral-partner information: applicant identity and business information, website, promotion descriptions, application decisions, referral activity, commission and payout records | Applicants, partners, referred visitors, and payout providers | Evaluate applications, attribute referrals, prevent abuse, administer commissions, and process payouts |
| Website, device, and usage information: browser and device information, network information, referral and campaign information, page views, interactions, and technical identifiers | Your browser, service requests, and analytics or monitoring tools | Operate the service, understand marketing and product use, assess deal engagement, diagnose problems, and prevent misuse |
| Support and diagnostic information: correspondence, issue descriptions, voluntarily submitted name and email, error details, and relevant technical context | You and service monitoring | Respond to requests, investigate failures, and improve reliability |

Payment entry is handled through the payment provider's checkout or payment components. DispoIQ receives transaction information and payment-method summaries rather than collecting full card numbers in its own form.

Names, addresses, property interests, and inferred buyer characteristics can relate to identifiable people even when obtained from business or public-record sources. A match or inferred association may be incomplete or incorrect. Finding a phone number does not establish permission to send marketing messages.

Messaging registration uses a business tax identifier and authorized representative details to submit and maintain the registration. Payment and payout functions involve financial and transaction information; deal offers can include financing and earnest-money details. These records can contain personal information about representatives, sole proprietors or transaction participants. Notes, messages and uploaded files can also contain sensitive information supplied by a customer or visitor.

Please avoid submitting unnecessary health information, government identification documents, account credentials, full payment-card details or other sensitive personal information in free-text fields or deal materials. Provide information needed for a specific lawful function through its appropriate channel. We will assess reports of inappropriate sensitive-information handling through the support procedure in section 8 and coordinate necessary protective action with the relevant customer or authorized technical staff. This policy does not authorize a new use or disclosure merely because information was submitted.

Enabled automations can use campaign and contact information, message events, replies and recorded link activity to evaluate customer-configured triggers and conditions and carry out supported follow-up steps. Supported messaging steps use templates for texts or tracked deal links; their use remains subject to messaging permissions and restrictions. A configured workflow does not establish that every step will run or that a message will be delivered.

Application notifications use recipient addresses and relevant account or event information. Referral functions use application, attribution, commission and payout information as described in the table; an enabled payout feature does not mean every partner has received a payout. Search and enrichment use the criteria and identity or address information needed for the selected lookup and return permitted results. The active path and returned fields depend on the feature and its configuration; this description does not say every alternative source or fallback is enabled.

Submitting contact details, an offer, or a reply makes that submission available to the relevant customer; it does not by itself transfer your intellectual property rights, make you a subscriber under the Terms of Service, or establish marketing-text permission. The business publishing a deal or sending a communication directs the customer purpose and audience. DispoIQ hosts and routes supported submissions for that business and its authorized team. Deal-page engagement is described in section 3.

Customers must provide required collection and communication notices and have the permissions needed for their instructions, content and audiences. A submission or page visit is not blanket permission for unrelated marketing or use by another sender. A customer's notice or instruction does not remove DispoIQ's own duties, individual rights, or the customer-provided information restrictions in section 5. Contact the relevant business or **[support@dispoiq.app](mailto:support@dispoiq.app)** if you need help identifying the responsible customer or addressing the information.

## 3. Deal-page engagement and inferred interest

Deal pages record visits and interactions such as time on the page, scrolling, sections viewed, photo interactions, clicks, and offer activity. A browser-session identifier connects interactions within a visit. Personalized links and buyer-associated links can connect this activity to the customer’s buyer record.

Engagement scores combine recorded signals such as time spent, sections viewed, scrolling, interactions, return visits, and offer activity using fixed scoring rules. The customer can use these summaries and scores to understand apparent interest and prioritize follow-up. These are inferences from recorded interactions, not proof that a particular person viewed the page or intends to purchase. Forwarding a personalized link can result in another person's activity being attributed to the buyer associated with that link. Treat personalized links as private.

The scoring rules assign points to recorded activity and combine them into an apparent-interest score. Longer recorded visits, qualifying section views, scrolling, interactions, return visits and offer activity can increase the score. These summaries can affect the order in which a customer reviews buyers or prioritizes follow-up. The customer decides how to use them in its business; the score does not verify identity, finances, creditworthiness or transaction eligibility, or establish permission to send a message.

If you believe an association or summary is inaccurate, or have a question about its use, contact the business responsible for the deal or **[support@dispoiq.app](mailto:support@dispoiq.app)**. We will assess the relevant processing and coordinate the request through section 8. Required explanation, correction, objection or review rights must be handled under the applicable procedure; describing fixed rules does not exclude an activity from a legal profiling or automated-decision requirement.

## 4. Cookies, browser storage, and third-party tools

Authentication, website attribution, referrals, analytics, and deal-session tracking use cookies or browser storage. The first-party marketing attribution cookie, `dq_attr`, records the initial landing page, referring hostname, and bounded campaign fields for up to 30 days. The waitlist success receipt, `dq_wl_receipt`, lasts up to 15 minutes and is consumed to count a submission. Referral attribution, when enabled, uses the `__Host-dispoiq_referral` cookie for 30 days. Deal tracking uses a browser-session identifier. These browser lifetimes do not describe how long related server records are retained.

Where configured, separate analytics services measure selected public marketing pages and authenticated application pages. The implementations restrict those integrations to their respective surfaces rather than using them to measure buyer-facing deal pages. Deal-page engagement is recorded by DispoIQ's own tracking service. Error monitoring and voluntarily submitted issue reports use a separate diagnostic provider. Map displays can cause your browser to request map resources directly from a mapping provider, which receives information needed to serve the request.

Our hosted documentation includes tools for technical, page-use and search measurement. Public marketing pages also include referral-attribution tools, which can associate a waitlist signup with a referral and pass referral identifiers with subscription activity to administer commissions. These tools are distinct from customer deal-engagement records. Analytics and diagnostic integrations can process technical identifiers and activity when they operate; their presence is not a statement that every tool collects information on every page or that the information is anonymous.

We do not currently provide a general tracking-preferences panel or a Do Not Track-based choice mechanism for the first-party attribution and deal-engagement tracking described above. Browser cookie restrictions can limit storage but do not necessarily stop all server-side processing or remove existing records. Contact [support@dispoiq.app](mailto:support@dispoiq.app) with tracking questions or requests. That contact route is not an automatic handler for browser opt-out preference signals such as Global Privacy Control.

Tracking that requires consent or a legally required opt-out mechanism must not proceed without that permission or mechanism. Applicable opt-out preference signals must be honored for the processing they cover; a browser cookie setting, support email or this policy does not replace a required technical control. Provider storage and retention depend on the particular tool and its configuration; the browser periods above are not a promise of one retention period for all analytics or diagnostic information.

Browser settings can limit cookies and storage, although restricting necessary storage can affect authentication and service functions. This policy does not incorporate an unpublished Cookie & Analytics Notice.

## 5. Who receives information

Information is made available for the purposes described above to:

* **The relevant customer and its authorized users.** They receive their workspace records, deal submissions, conversations, and engagement information. Workspace administrators manage access within their business.
* **Customers using buyer search or contact enrichment and their authorized users.** When results are made available in those features, these customers receive the returned contact information for their own permitted business use. The mobile-result scope and requirements are explained below.
* **Intended recipients and deal visitors.** Sending a message or publishing a deal makes its content available to the recipient or people with access to the deal. Files and images included in published deals may be accessible through their resource URLs. Do not upload content you lack authority to disclose.
* **Service providers.** Providers support hosting, databases, storage, authentication, payments, email and text delivery, messaging registration, data lookup and enrichment, maps, analytics, diagnostics, and support-request handling. Requests for enrichment can include identity and address information needed for a lookup. Communications providers and carriers receive the content and routing information necessary to process messages.

The [Service Categories Overview](https://docs.dispoiq.app/policies/service-categories) explains the functions and information involved. A provider's role depends on the activity; payment, communications, registration and data-source relationships can involve purposes and duties separate from processing workspace records on instructions. Support and authorized technical personnel may handle information needed to operate the service, address requests and investigate issues within their applicable authority. A customer-selected integration may have its own agreement and privacy notice.

The Service Categories Overview is not a complete identified subprocessor roster and supplies no subprocessor authorization. Contact **[support@dispoiq.app](mailto:support@dispoiq.app)** for identifying or other processing information required for your relationship. Applicable law and any separately agreed processing terms continue to govern required information and safeguards, including information or authorization required before processing begins.

### Provided mobile information and messaging consent

Mobile numbers and messaging-consent records provided to us for our own account, waitlist, inquiry, or other direct communications, or supplied by a customer for its own communications, are not shared with third parties or affiliates for their separate marketing or promotional purposes. Service providers may process this information as necessary to provide messaging and related service functions. Customer senders retain access to their own recipients, conversations, consent records, and opt-out information. Consent given to one sender is not permission for another sender to contact the person.

### Contact information from independent sources

Buyer search and contact enrichment obtain information from property and contact-data sources. When mobile-number results become available in a feature, they may be provided to paying customers using that feature for their own permitted business use. Customers must comply with applicable source restrictions, individual rights, our messaging requirements, and applicable law before contacting a person. A lookup, match, or mobile-number classification does not establish the person's permission to receive marketing messages.

This prospective disclosure does not authorize use or disclosure contrary to commitments applying when information was collected. Source permissions, required notices and permissions, and applicable rights controls must be in place before these results are made available. Storing or relabeling customer-provided information does not turn it into independently sourced information or override customer-processing instructions, confidentiality, applicable Terms content restrictions, any separately agreed data processing agreement, or the customer-provided-record and future-use safeguards below.

We will honor applicable source limits on customer display, onward use, export, confidentiality, correction and marketing cessation. A right to display a result within an enabled feature does not grant unrestricted bulk export or permission to contact the person. Required permissions, notices and rights controls must precede the disclosure they cover. Earlier commitments remain binding on the information and activities to which they apply; new source access or a revised notice does not cancel them.

### Customer-provided records and future secondary uses

We currently do not use customers' uploaded contacts, message content, messaging-consent records, or private deal-page engagement to enrich another customer's records, create advertising audiences, resell data, or train AI models. This statement concerns those customer-provided records. It does not describe independently sourced discovery information or change the service processing described elsewhere in this policy.

We may introduce future arrangements for those secondary uses only after specifically disclosing the affected information, purposes, recipients, and relevant changes to our role and individual choices. Before a new use begins, we must obtain any necessary customer authorization or validly agreed processing amendment, give affected individuals the notices required by applicable law, obtain consent where required, and put applicable opt-out and other rights controls in place and honor them. This is a future-options process, not a statement that those uses or controls are currently enabled. Customer agreement alone does not supply an individual's required consent.

Any future arrangement must respect binding data processing terms, confidentiality, source-license restrictions, the mobile-information and messaging-consent nonsharing restriction above, and applicable law. A policy update or relabeling of records cannot override those limits. New arrangements apply only prospectively after their requirements are met; posting an update or continued use alone does not erase collection-time commitments or retroactively authorize incompatible processing.

### Licensed information, sale, sharing, and advertising

Our paid buyer-search and contact-enrichment features make property and company records and returned owner, address, phone and email information available to customers and their authorized teams for permitted business use. Access is provided through paid features; those recipients use the results for their own business purposes and are not classified as our service providers simply because they subscribe. Not every returned field is necessarily public information, and a phone result does not establish marketing consent or that sourced mobile results have already been delivered.

Making personal information available to another business for payment or other valuable consideration can constitute a sale under privacy law. The paid source-information disclosures described here must be treated as covered sales where the applicable definition and scope are met, with the required notices, opt-out methods and restrictions. Source licensing does not waive those protections. Sharing for cross-context advertising and targeted advertising are separate activities, not automatic synonyms for every service-provider disclosure or paid lookup. The customer-provided-record restrictions above remain in effect; this policy supplies no permission to create advertising audiences from those records.

Information subject to an earlier no-sale or incompatible disclosure commitment must not be made available for payment contrary to that commitment. We must restrict the affected records or disclosure activity until any proposed use is consistent with the binding commitment and the required lawful basis, notices, permissions and rights controls are in place. Publishing this notice does not establish that these steps have been completed, cancel a prior protection or excuse an earlier incompatible disclosure. For newly permitted source disclosures, the requirements must be satisfied before release; independently sourced information cannot be used to bypass the provided-mobile, consent or future-use protections above.

Contact [support@dispoiq.app](mailto:support@dispoiq.app) with a question about source information concerning you or to exercise an applicable sale, advertising, correction or deletion right under section 8. We will assess the relevant information, source and recipient activity and coordinate required action, including applicable source restrictions on further marketing. Required technical opt-out methods or preference signals cannot be replaced by this email route.

## 6. Processing permissions and international handling

We offer business subscriptions to customers throughout the United States. Customers currently manage and message contacts in the United States and Canada, and messaging destinations are limited to those two countries. Those customer-contact activities and messaging limits do not establish every individual's location, where information is processed, or which privacy laws apply to it. The Florida governing-law provision in the subscription Terms does not displace applicable individual privacy rights.

We process information for the specific purposes explained in this policy. Where consent is required, a separate collection or opt-in process must establish that consent; using the service or reading this policy does not by itself supply it.

Account and business processing supports requested service functions, account administration, payments, security, support and permitted communications. Customer-directed processing follows the customer's lawful purposes and instructions, subject to our own duties. Independently obtained information and disclosures to customers require their own source permissions, lawful collection and disclosure grounds, and any required indirect-collection notices. A supplier licence, public-record label or a US or Canadian phone number does not establish that every field or use is exempt from privacy requirements.

The rights and procedures in section 8 apply according to the information, the relevant processing and the individual's jurisdiction. Business-only subscriptions do not remove protections for identifiable individuals. We do not treat our subscription governing law as a waiver of those protections or this policy as consent to a purpose that requires a separate permission.

Providers and authorized personnel may handle information in locations different from where an individual lives. Handling can involve countries outside the individual's state, province or country. We do not promise that all processing or storage takes place in the United States or Canada. Contact **[support@dispoiq.app](mailto:support@dispoiq.app)** for processing-location and safeguard information required by applicable law or a separately agreed processing relationship. Required disclosures and safeguards remain applicable; a provider's business address or available region list does not establish where a particular activity occurs.

## 7. Retention and deletion

Retention depends on the purpose of the record, customer instructions where applicable, legal requirements, unresolved transactions or disputes, and the need to preserve security and opt-out evidence. Canceling a subscription or removing a user is not necessarily the same as deleting all associated information.

After a customer's paid subscription access ends, the customer has **90 days from that end of paid access to request an export of information it is entitled to receive**. Contact **[support@dispoiq.app](mailto:support@dispoiq.app)** to make the request. Support coordinates the requester's authority, the eligible records and an appropriate secure delivery process with authorized technical staff and, where needed, the relevant customer or provider. The request window does not extend ordinary paid application access or grant additional rights to licensed third-party information. It does not promise a particular format or a complete copy of every service record.

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.

DispoIQ **may delete eligible workspace records after 180 days measured from the end of paid subscription access**. These account-closure windows do not expire unused wallet funds purchased with money. This is not a guarantee that all information is erased on day 180. Applicable retention duties, legal holds, transaction records, suppression evidence, provider records, and backup handling may require different treatment. These account-closure windows do not postpone an individual's privacy request or change any shorter deadline or other requirement imposed by applicable law.

The contact-management feature includes recoverable deletion, which retains a contact record, and a separate permanent-deletion operation. Other information, such as import rows, message histories, provider records, audit records, suppression records, or backups, may remain outside that operation.

## 8. Your choices and privacy requests

Contact **[support@dispoiq.app](mailto:support@dispoiq.app)** or write to DispoIQ LLC at the address above with a privacy question or request. Tell us how you interacted with the service and, if relevant, which customer contacted you or hosted the deal page. Please do not include identity documents or other sensitive information in your initial message.

For information controlled by a customer, contact that business as well. We may need to coordinate with it to address the request while protecting other people's information. If your request concerns our own processing, use the DispoIQ contact route above.

Account users can update supported profile and notification settings. For texts, use the opt-out instructions in the message, such as replying STOP; contact the sender or DispoIQ if you need help. Stopping texts does not necessarily stop email or delete a contact record. Email unsubscribe controls, where provided, apply separately.

You do not need a paid subscription or an account to contact us with a privacy request. Support logs requests, identifies the relevant information and business, and applies identity or workspace-authority checks proportionate to the request and applicable law. If more evidence is needed, support arranges an appropriate way to provide it. Support coordinates fulfillment with authorized technical staff and, where needed, the relevant customer or provider; before disclosing records or confirming an action, we check entitlement and protect other people's information. Work beyond support's authority is escalated for technical handling.

These steps do not impose identity checks on every opt-out or make every deadline begin only after verification. Legally required deadlines, explanations, permitted extensions and protections remain applicable. This policy sets no new privacy-request fee, discretionary response-time guarantee, instant access or complete-erasure promise. A representative acting for you should explain that role; any required authorization and verification follow the applicable procedure.

Depending on the law that applies to the particular processing, you may be entitled to:

* Obtain access to your personal information and information about its sources, purposes and recipients.
* Correct inaccurate information, request deletion, or receive an available portable copy.
* Withdraw consent or object to or restrict processing where those rights apply. Withdrawal does not retrospectively make earlier lawful processing unlawful.
* Opt out of a covered sale, sharing for cross-context advertising, targeted advertising or legally covered profiling, and limit covered uses or disclosures of sensitive information. A messaging opt-out is a separate choice and does not by itself exercise all of these rights.
* Appeal a denied request where an appeal right applies, and complain to the competent privacy regulator. We will not discriminate against you for exercising a protected privacy right.

Use [support@dispoiq.app](mailto:support@dispoiq.app) or the postal address above to identify the information and right involved. If we decline or limit a request, we will give the explanation and information required by applicable law. To seek reconsideration or a required appeal, contact the same address and identify the decision; support will coordinate the applicable review and provide any required regulator-complaint information. You do not need our permission to contact a regulator; the regulator's own complaint and admissibility procedures apply.

For covered Canadian processing, you may request access to and correction of personal information and information about its use and disclosure, challenge compliance, and withdraw consent subject to applicable legal or contractual limits. You can complain to the [Office of the Privacy Commissioner of Canada](https://www.priv.gc.ca/en/report-a-concern/) or the competent provincial authority. For covered California processing, applicable rights include knowing, correcting or deleting information, opting out of sale or sharing, limiting covered sensitive-information uses and exercising rights without prohibited discrimination; complaints may be made to the [California Privacy Protection Agency](https://cppa.ca.gov/webapplications/complaint) or [California Attorney General](https://oag.ca.gov/contact/consumer-complaint-against-business-or-company). These descriptions do not declare that every DispoIQ activity or customer is covered by the same law.

If you need an accessible way to read this notice or submit a request, contact [support@dispoiq.app](mailto:support@dispoiq.app) and explain the assistance needed without sending unnecessary sensitive information. Required methods, preference-signal handling, deadlines and permitted exceptions remain controlling; the contact route does not replace a legally required online opt-out or technical signal mechanism.

## 9. Security and children

The application implements authentication, permission checks, and customer-scoped access controls. No online service can guarantee absolute security. The [Security Overview](https://docs.dispoiq.app/policies/security) explains account safeguards, information-handling limits and how to report a security concern. Retention does not guarantee restoration or backup recovery.

Support will record and triage security reports and escalate suspected incidents for authorized technical assessment. DispoIQ will assess the affected information and systems, take appropriate containment and corrective steps, and coordinate necessary cooperation with affected customers and relevant service providers. We will notify affected customers, individuals or authorities when applicable law or a separately agreed processing commitment requires it, using the required timing, content and procedure. An ongoing investigation does not permit delaying a required notice beyond its applicable deadline. A report is not itself confirmation that an incident has occurred.

This reporting procedure sets no guaranteed acknowledgment or resolution time.

DispoIQ subscriptions are for business use. Each individual customer, individual accepting the Terms for a customer, and signed-in workspace user must be at least 18 years old and also have reached the applicable legal age of majority where they live. This workspace-account eligibility rule does not apply merely because a person visits or interacts with a customer's deal page without signing in to a workspace. It does not establish the ages of people described in customer records. Account eligibility is a rule for workspace use, not a statement that every visitor or person in a record is an adult or that age is technically verified in every interaction. Customer records, messages, photographs and submissions may concern people who do not hold workspace accounts.

If you believe a child has provided information inappropriately, an underage person is using a workspace, or information about a child requires protective handling, contact **[support@dispoiq.app](mailto:support@dispoiq.app)** without sending unnecessary identity documents in the initial message. Support will assess the collection context and relevant customer's role, escalate for authorized handling, and coordinate required restrictions, removal, notices or permissions under applicable law. This process does not replace any parental permission or other safeguard that must be in place before covered collection begins.

## 10. Updates

We will identify this policy's effective date and revise it when our processing changes. We will make the updated policy available at its published address, identify its effective date and preserve the previous version when replacing it. We will provide any notices required for a material change using the applicable timing and procedure. Changes do not remove collection-time commitments or any required notice, permission or choice before new processing begins. Continued use alone does not supply consent where consent to new processing is required.

Changes involving the future secondary-use arrangements described in section 5 must satisfy that section's advance-disclosure, permission, and control requirements before any new use begins.


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