Version 1.3. Effective date: October 20, 2026. Prepared with AI assistance and not reviewed by a licensed lawyer. Not legal advice.

Acquiror AI provides informational output only, not investment, legal, tax, accounting, lending, or valuation advice; see the Terms of Service, AI Features and Output.

Cookie Policy

On this page

This policy explains the cookies and similar storage technologies used by Acquiror AI, a product of Umplify Technologies Inc. Capitalized terms not defined here have the meanings given in the Terms of Service. It covers two different surfaces, and the two are not the same:

The Acquiror AI product application (the authenticated deal-management platform your team logs into).
The Acquiror AI marketing website (acquiror.ai), a separate system from the product application.

For what personal information we collect and why, see our Privacy Policy. This page is about the storage mechanisms themselves.

1. The product application

The product application uses only essential authentication and session storage. There are no advertising cookies and no analytics cookies anywhere in the product application.

Specifically:

Authentication tokens: sign-in is handled by Microsoft's identity service through the Microsoft Authentication Library (MSAL). Our configuration stores the resulting tokens in your browser's local storage, not in a cookie. The product does not set an authentication cookie at all. The Microsoft sign-in page itself, which is a Microsoft service on a Microsoft domain, sets its own cookies under Microsoft's privacy statement.
Preferences: local storage also holds your display theme, time zone, and preferred currency so the app opens the way you left it (the theme and time zone keys include your user identifier so that each person on a shared browser keeps their own). This storage is essential to the product working as configured and cannot be turned off without signing out.
No advertising cookies. The product application does not set cookies for advertising, retargeting, or cross-site tracking, and does not sell or share your data for cross-context behavioral advertising.
No analytics cookies in the product. The product application contains no Google Analytics, no tracking pixels, and no third-party analytics or session-replay software. The in-product "Analytics" features you may see (for example, deal pipeline summaries or risk distribution views) are internal deal-management reporting built on your own tenant's data. They are not web analytics and do not involve any tracking cookie.
Third-party requests without cookies. The product application loads its icon font from Google Fonts and its brand fonts and stylesheet from our own storage account on Microsoft's cloud. Google receives the requesting browser's IP address and user agent for the font request; no cookie is set and no Customer Data is involved.
Payment pages. When you open checkout or the billing portal, you are on Stripe's domain, and Stripe sets its own cookies under Stripe's privacy policy.

Categories used in the product application

Category	Used in product?	Examples	Can you control it?
Essential (strictly necessary)	Yes	MSAL authentication tokens and session state, and your theme, time zone, and currency preferences, held in browser local storage	No. These are required for sign-in and core functionality. You can clear them at any time by clearing your browser's site data, which will sign you out.
Analytics (first-party or third-party)	No	Not applicable	Not applicable
Advertising / targeting	No	Not applicable	Not applicable

Do Not Track and Global Privacy Control

Because the product application does not sell or share personal information, does not conduct cross-context behavioral or targeted advertising, and does not set analytics or advertising cookies, there is nothing for a Do Not Track or Global Privacy Control (GPC) signal to switch off within the product application itself. We nonetheless recognize these signals as a valid request not to be tracked, consistent with our broader "we do not sell, share, or serve targeted ads" position described in our Privacy Policy.

We use Microsoft's cloud monitoring service for backend application performance monitoring and error logging. This is server-side telemetry: it is generated by our backend services observing requests, not by a script or cookie running in your browser. No browser monitoring SDK from that service is installed in the product application, so no client-side telemetry cookie is set by this system. See our Privacy Policy for what request-level data server-side telemetry may capture and how long it is retained.

2. The marketing website (acquiror.ai)

The marketing website uses Google Analytics 4 to understand aggregate site usage, and only on these terms:

Analytics is off by default. A consent bar is shown on first visit, unless your browser sends a Global Privacy Control or Do Not Track signal, in which case the bar is not shown and analytics never load. Until you click Accept, the Google Analytics script is not loaded on any page and no analytics cookie or identifier is set; if you decline or ignore the bar it never loads.
If you accept, analytics storage is enabled with IP anonymization requested; advertising storage, advertising user data, and ad personalization stay off, and Google signals are off. Google then sets its own first-party analytics cookies on acquiror.ai (named "_ga" and "_ga_" followed by the property identifier, with lifetimes set by Google, which its documentation currently states as up to two years). The events we send are page views, clicks on calls to action and sign-in links (with the page path and the button's position), and a confirmation event when a form is submitted successfully (with the page and which form, never the content you entered); Google Analytics also records its own standard engagement events.
Your choice is kept in your browser's local storage, not in a cookie. There is no separate settings control on the site; to change your choice, clear the site's data in your browser and the consent bar will appear again.
Pages with a form run Cloudflare Turnstile, a bot check (loaded with the contact page, and on other forms when you start filling them in). Turnstile may set a cookie or use local storage on Cloudflare's domain for that check, under Cloudflare's privacy policy. It is not used for advertising.
The marketing website does not set advertising or cross-site tracking cookies, does not run ad pixels, and does not sell or share data for cross-context behavioral advertising.
Declining analytics is treated as equivalent to an opt-out; Global Privacy Control and Do Not Track signals are honoured consistently with that position.

This section describes the marketing website only. It does not describe the product application, which is covered in Section 1 above and does not use Google Analytics at all. If you are unsure which surface you are using, the product application requires sign-in; the marketing website does not.

3. Categories, summarized

Category	Product application	Marketing website
Essential	Yes (auth, session, and preference local storage)	Yes (consent choice in local storage; bot check on form pages)
Analytics	No	Yes, only after you accept (Google Analytics 4)
Advertising / targeting	No	No

4. How to control cookies and storage

In the product application: essential storage cannot be disabled without signing out, because it is required for authentication. You can clear it at any time through your browser's site-data settings.
On the marketing website: use the consent bar shown on first visit, or clear this site's browser data to bring the bar back and change your choice.
Browser-level controls: your browser lets you block or delete cookies and local storage generally. Blocking storage for the product application will prevent you from signing in.

For questions about this policy or to exercise a privacy right, see the contact information in our Privacy Policy.