Cookies and analytics - DispoIQ Docs & Help Center

Effective date: October 8, 2026. Document version: v1.0. DispoIQ LLC uses browser technologies to provide account access, remember preferences, understand website and app use, and record engagement with deal pages. This notice covers the marketing website, the signed-in application, buyer-facing deal pages, and the documentation website at docs.dispoiq.app. The technologies differ across these surfaces. For personal-information questions or requests, contact support@dispoiq.app. The Service Categories Overview describes the functions and information involved in third-party services. This notice does not itself supply consent to tracking or permission to send marketing messages.

1. What these technologies do

Cookies are small records stored by your browser and sent with relevant website requests. Local storage remembers information in your browser between visits; session storage holds information for a browser-managed page session. Scripts, analytics requests and event beacons can send information without using a cookie. Depending on the page and enabled service, information can include browser or device identifiers, account and workspace identifiers, network information, referring sites, campaign details, pages viewed, timing and interactions. An identifier can relate to a person even when it does not contain a name or email address. A first-party cookie does not necessarily mean that information remains only with DispoIQ.

2. Where collection occurs

Surface	Function and purpose
Marketing website	First-touch attribution records how a visitor reaches selected marketing pages. Referral tools can associate a signup with a referral and subscription activity to administer commissions. Where website analytics is enabled and operating, measurement records selected page views and events, such as a successful waitlist submission.
Signed-in application and account access	An authentication provider handles sign-in and session management. Browser preferences remember table columns, column widths, map style and an in-progress campaign reference. Where product analytics is enabled, it measures authenticated app use with account and workspace identifiers.
Buyer-facing deal pages	First-party engagement collection records page visits, time on the page, scrolling, section and photo interactions, clicks and offer-related events. These records help the relevant customer understand interest in a deal. They are separate from marketing-site and authenticated-app analytics measurement.
Documentation website	A documentation hosting provider serves docs.dispoiq.app, handles technical page and search requests, and includes browser tools for technical, page-use and search measurement. These functions are separate from customer deal-page engagement.
Diagnostics and external resources	Where configured, a diagnostic provider receives diagnostic events; a person submitting a problem report may also provide contact details and a description. Loading maps or other external resources can send request information directly to the relevant providers. These requests are distinct from advertising measurement.

The reviewed product-analytics configuration uses opaque member and workspace identifiers, applies route and element masking, and disables session recording. The reviewed diagnostic-report configuration disables screenshots. These measures do not make every event anonymous or guarantee that a voluntarily submitted report contains no personal information. A personalized deal link can associate viewing activity with the contact to whom the link was issued. If a link is forwarded, activity can be associated with that contact even when someone else viewed the page. Clearing a browser identifier does not remove activity already recorded or the identifying information in a personalized link. The selected marketing-analytics property currently reports no received website data. Its enhanced cross-device signals and user-provided data collection are not enabled, and no advertising-account links are configured for that property. This does not establish that no browser requests occur, that other tools are absent, or that all service processing is advertising-free. The selected property’s record-retention settings are two months for event data and fourteen months for user data, with reset on new user activity enabled. Those selected settings are not the expiry of every browser cookie, every aggregate report, server log or other provider’s records. Authentication and other provider-managed storage depend on the actual tool and configuration; the first-party periods in section 3 do not supply a universal provider-storage period. Documentation measurement tools can process technical identifiers, page activity and search interactions when they operate. Our documentation configuration has no added analytics integration or cookie-consent setup; that does not disable the hosting platform’s own tools. Provider-managed identifiers and browser or server retention vary by tool and selected configuration. Contact support@dispoiq.app for identifying, retention or processing-location information required for the relevant activity or relationship. Missing details do not waive a required disclosure or safeguard, and this notice does not incorporate another provider’s default lifetime as a verified DispoIQ setting.

3. First-party browser storage

The following periods are configured browser-storage limits. Browser restrictions, clearing and session restoration can affect how long information remains. They are different from retention of records already sent to a server.

Name or storage	Purpose	Configured browser period
`dq_attr` cookie	Remembers the initial marketing landing-page category, referring hostname and bounded campaign fields; these can accompany a waitlist submission	Up to 30 days
`dq_wl_receipt` cookie	Holds a short confirmation used to measure an accepted waitlist submission, without storing the submitted name, email or phone number in this receipt	Up to 15 minutes; consumed and removed when handled by the measurement component
`__Host-dispoiq_referral` cookie, where referral redirects are enabled	Records signed referral-attribution identifiers	Up to 30 days
`gsfl_session_id` in session storage	Links deal-page events within a browser-managed session	Session storage; no separate application expiry timer
App preferences in local storage	Remembers deal-table columns and widths and investor-map style	No fixed application expiry; retained until replaced or cleared
Campaign reference in local storage	Helps recover an in-progress investor campaign	No fixed application expiry; can be removed by the app or cleared in the browser

Clearing browser storage does not by itself delete account, referral, waitlist, analytics or deal-engagement records held elsewhere. The subscription export and deletion windows do not define cookie lifetimes or postpone applicable individual privacy rights.

4. Providers and further uses

Authentication, analytics, diagnostics, maps and documentation hosting involve different providers and data flows. Their selected settings and agreements determine the information received, processing locations and permitted uses. Provider defaults do not establish the settings selected for DispoIQ. Authentication, chosen display preferences, referral attribution, product measurement and deal-engagement scoring have different purposes. They must be distinguished from advertising based on activity across different businesses’ websites or apps. The selected marketing-analytics settings above do not establish every recipient’s role or all processing purposes. A first-party cookie, opaque identifier or analytics label does not by itself make a disclosure anonymous or exempt from individual rights. 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. Necessary service processing and the customer sender’s access to its own recipients, conversations and permission records remain distinct. Consent given to one sender is not permission for another sender. Cookie choices do not establish marketing-message consent or override this restriction. Independently sourced contact results are a separate activity. Prospective mobile-result delivery requires source permissions, collection-time commitments, required notices and permissions, and applicable individual-rights controls before release; it does not imply that paying customers have already received sourced mobile numbers. Storing or relabeling customer-provided information does not make it independent source data. DispoIQ currently does not use customer-provided contacts, messages, consent records or private deal engagement to enrich another customer’s records, create advertising audiences, resell data or train AI models. Any future arrangement must respect the applicable processing terms, confidentiality, source limits, provided-mobile restriction and individual rights, with required advance disclosure, permissions and choices before the new use begins. This is not a present blanket secondary-use permission or a statement about every provider’s separate activity. Paid buyer-search and enrichment disclosures of source property/company and owner/address/phone/email information are distinct from cookie-based advertising. Covered sale, sharing or targeted-advertising rules still require their actual notices, opt-outs and restrictions; neither a supplier licence nor browser settings waive them. Source records or flows subject to an earlier no-sale or incompatible-disclosure commitment must be restricted until any permitted disclosure has a lawful promise-consistent basis and the required notices, permissions and rights controls. Updating this notice does not cancel a prior commitment or cure incompatible processing.

5. Your choices

You can use your browser’s settings to restrict cookies or clear cookies and site storage. These settings can affect sign-in, remembered preferences and other functionality. Choices generally need to be made for each browser and device, and clearing storage can remove saved choices. Browser restrictions and provider-specific opt-out tools, where available, can have limited effects. They do not necessarily disable DispoIQ’s first-party deal engagement, authenticated-app analytics, documentation processing or all technical requests. Global Privacy Control and older Do Not Track settings are different browser signals. Their treatment must be described accurately for each surface and applicable law. A browser-storage restriction is also different from a request to access, correct or delete personal information. 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 here. Browser blocking and clearing are the available browser-level choices described above; they are not a guarantee that every technical request or stored server record stops. The support route is not an automatic handler for Global Privacy Control or another browser opt-out preference signal. Where applicable law requires honoring such a signal or supplying an online opt-out, that mechanism must operate for the covered processing; email or a general notice is not a substitute. Tracking requiring consent or a presently unavailable safeguard must be restricted until the required permission or control is in place. These requirements apply to the affected activity and individuals rather than declaring every browser technology subject to the same rule. For questions or privacy requests, email support@dispoiq.app and describe the page, interaction or choice involved. You do not need a paid DispoIQ account to contact us about your information. Please avoid sending passwords, session tokens, API keys, complete contact lists or identity documents in an initial message. Support records requests, identifies the relevant activity/customer, applies identity or workspace-authority checks proportionate to the request and law, and coordinates secure fulfillment or authorized technical escalation. An opt-out does not automatically require identity verification. Required response methods, deadlines, permissions and regulator procedures remain controlling; this notice adds no discretionary acknowledgment or resolution-time guarantee. Contacting support does not itself switch off every tracker or erase every copy.

6. Changes

We will keep this notice aligned with the technologies and purposes in use and provide any notice or choice required by applicable law. Publishing a revised notice does not itself authorize a new use of information or supply consent where consent is required.

​1. What these technologies do

​2. Where collection occurs

​3. First-party browser storage

​4. Providers and further uses

​5. Your choices

​6. Changes