Cookie Policy

This Cookie Policy applies to DeepSearch websites, web applications, and other browser-based experiences that link to it. Mobile apps may use SDKs, device identifiers, local app storage, and operating-system permissions that serve similar functions even when they are not technically cookies.

The Privacy Policy explains who controls the resulting personal data, why it is processed, who receives it, international transfers, retention, and privacy rights. This page provides the more specific technology notice. A cookie notice is not, by itself, consent to optional tracking.

• Cookies are small values a site asks a browser to store and send back with later requests.
• Local and session storage keep values in the browser without automatically attaching them to every network request.
• Pixels, tags, and beacons are code or small resources that record when a page, message, or action was viewed.
• SDKs are software modules integrated into a website or app that can provide analytics, authentication, messaging, payments, or other features.
• Device and network signals include IP address, browser, app version, operating system, language, screen, referral, and security data used with or without a stored identifier.

A technology can be first-party, meaning set in the DeepSearch context, or third-party, meaning a provider can read or set it under its own domain or SDK. The same provider can use more than one technology.

Necessary storage supports functions you request or that are essential to security and delivery. It may be used to keep an authenticated session, prevent cross-site request forgery, route traffic, remember a checkout state, enforce rate and abuse controls, balance load, store a privacy choice, protect an API or account, and complete a payment.

Examples include authentication values created by our identity provider, short-lived security and transaction values, and the DeepSearch analytics preference or suppression cookie. The exact name and duration can change with security architecture. Blocking this category can sign you out, break checkout, prevent a saved privacy choice, or make the Service unavailable.

Functional storage can remember language, theme, interface state, dismissed messages, recent product choices, and other settings that make the Service easier to use. Some settings are stored in the browser; signed-in settings may also be stored with the account so they work across devices.

A functional value may be necessary when you explicitly request the feature, but optional in another context. Clearing it may reset the interface without deleting server-side account data.

When configured and not suppressed, DeepSearch uses PostHog and its own analytics to understand visits and product use. These tools can process page or screen views, referral and campaign data, approximate location derived from IP, device and browser details, session timing, feature interactions, purchase or conversion events, account or pseudonymous identifiers, and diagnostic information.

PostHog uses browser local storage to keep a pseudonymous visitor identifier. Signed-in activity is linked using the account ID, without sending names, email addresses, search queries or private page addresses. Automatic form capture and session recording are disabled. Analytics integrations are designed to load outside the critical rendering path and may activate after an interaction or delay. Delay does not change whether a legal choice is required.

We use this information to measure reliability and performance, understand feature adoption and funnels, diagnose errors, prevent fraudulent attribution, and improve the product. It is not needed to perform a specific search, and the control below can stop future optional analytics loads in this browser after reload.

We use Dub to attribute affiliate referrals, verified sign-ups, purchases, renewals, and refunds. A referral link can set the dub_id cookie for up to 90 days. Dub receives the referral identifier, a pseudonymous account identifier, and payment amount, currency, and transaction references. This integration does not send search queries, prompts, search results, or card details. The optional analytics preference below also controls loading the Dub browser script.

OneSignal or an equivalent provider may support web or app notifications when configured. It may use browser storage, a service worker, a push-subscription identifier, app or device information, permission status, and an account association needed to deliver, suppress, or measure a notification.

A browser or operating-system permission is separate from a marketing consent. You can deny or revoke push permission in the browser or device settings. Service and security messages may still be sent through another channel when necessary to operate an account or transaction.

If enabled, Meta Pixel and server-side advertising integrations may measure referrals, advertising campaigns, visits, sign-ups, or purchases. Meta technologies can use identifiers such as _fbp and, after an advertising click, _fbc. Google or another configured tag may use its own advertising or analytics identifiers.

These providers can combine information according to their own policies when they act independently. Some laws call this targeted advertising, cross-context behavioral advertising, sale, or sharing even when DeepSearch does not receive money for the disclosure. Availability depends on configuration; listing a provider does not mean its advertising tool runs on every visit.

Stripe, Apple, and Google may use cookies, SDKs, device signals, fraud controls, and payment-session storage to display and secure checkout, remember a wallet, authenticate a payer, process a transaction, prevent fraud, manage a subscription, or provide a receipt. Their storage is governed by their own notices as well as payment and financial rules.

A linked source, embedded media player, map, or externally hosted content may also set third-party technology when you load or interact with it. We seek to limit unnecessary embeds, but an independent destination controls its own technologies after you leave DeepSearch.

A session value is normally removed when the browser session ends. A persistent value remains until its stated expiry, you clear it, or it is replaced. We set the optional-analytics preference for up to 12 months so your choice is not requested repeatedly. Authentication, security, attribution, and provider values may have shorter or longer durations appropriate to their function.

Providers can change cookie names and durations as their services evolve. The browser's storage inspector and the provider's current notice are the most precise sources for a value present on your device at a particular moment. Retention of server-side event data is separate from the lifetime of the cookie that helped create it.

Use this browser-level control to allow or turn off DeepSearch optional analytics integrations. Turning them off writes a preference and, after reload, prevents our configured analytics, measurement pixel, and web-notification integrations from loading through the shared analytics gate. Strictly necessary authentication, security, payment, and preference storage remains available.

The setting applies only to this browser profile. Repeat it on another browser or device. Turning analytics off does not automatically erase server-side events already collected or third-party cookies already stored. Clear those through browser controls and use the privacy-right process below if you also want an eligible server-side deletion or opt-out request.

Most browsers let you view, delete, block, or restrict cookies by site and erase local storage. You can also block third-party cookies, limit cross-site tracking, disable a content blocker exception, or use a private browsing window. Mobile systems offer advertising, tracking, notification, and app-data controls.

Blocking all storage can prevent login, saved settings, checkout, or fraud protection. Private browsing limits persistence on the device but does not make network activity anonymous to websites, internet providers, employers, or authorities. DeepSearch Anonymous Chat is a conversation-history control, not a cookie blocker or anonymity service.

Browser signals are still implemented differently across laws, browsers, and providers. Where a legally recognized opt-out preference signal applies to our processing, we will treat it as a request for the browser or device that sent it, subject to reasonable verification and technical support. You can always use the control above or email us rather than relying only on a signal.

A legacy "Do Not Track" header does not have a single agreed technical or legal meaning, so sites and third parties may not respond to it uniformly. The absence of a response to that header does not limit a statutory opt-out, deletion, objection, or complaint right.

The legal rule depends on the technology, purpose, and location. Strictly necessary storage generally does not require the same choice as analytics or advertising. Where law requires prior consent for non-essential storage or access, consent must be informed, specific, freely given, and expressed by a clear action; continuing to browse is not treated as a consent merely because this Policy exists. Where law permits another basis, we assess the purpose, necessity, impact, and available controls.

You may withdraw a saved optional choice at any time with equal ease by using the control above. Withdrawal applies prospectively and does not make earlier lawful processing unlawful.

Cookie deletion in a browser and deletion of event data on a server are different actions. Depending on your location, you may ask to access, delete, correct, object to, or opt out of eligible personal data as described in the Privacy Policy. Include the browser, approximate date, and relevant account email or identifier where available so we can locate the data without collecting unnecessary information.

Send questions or rights requests to support@deepsearch.app. We may update this Policy when a provider, technology, purpose, or legal requirement changes. The revised date at the top identifies the current version.

DeepSearch is operated by RELOAD TECHNOLOGIES - FZCO.