Cookie Policy
Global Technology Solutions Inc. is the company behind AdaptCX. This policy concerns the AdaptCX marketing website.
Cookies and similar storage
Cookies are browser-managed values associated with a domain and path. Local storage and IndexedDB are separate browser storage mechanisms. This policy distinguishes optional public website analytics from storage used for your choices and authenticated administrator functions.
Your choices
Optional analytics starts only after you affirmatively allow it. Accept optional, Reject optional and Manage preferences are available from the notice. Closing preferences, scrolling or continuing to browse is not permission. The analytics checkbox starts unchecked when there is no valid saved choice. There is no marketing toggle because the current registry has no enabled marketing integration. Cookie Settings in the footer reopens preferences. You can withdraw analytics permission at any time. Essential site functionality and self-hosted video playback remain available independently of analytics permission. Enabled forms do not require a marketing or analytics choice.
Remembering consent
The first-party adaptcx_consent_v1 local-storage record contains the schema and policy version, category choices, choice time and expiry. It contains no unique visitor identifier. Consent is valid for 180 days under the initial configuration. Local storage does not expire automatically: invalid or expired choices are removed on a subsequent visit and optional analytics remains blocked until a valid new choice. Missing, malformed, incompatible or expired records are treated as no optional permission. If browser storage is unavailable, the current page can apply your choice in memory; a later page may ask again. Choices are scoped to the website origin and are not silently shared between unrelated domains.
Optional analytics
Google Analytics is configured with measurement ID G-TTMWZ4P3L7. Before permission the application does not load the Google tag or send cookieless analytics pings. After permission it sends the current page view and legitimate subsequent events. It does not replay a stored queue of earlier interactions. Advertising consent and Google signals remain disabled. The current configuration explicitly sets Google analytics-cookie expiry to 180 days. Google may renew cookie expiry during permitted activity and browsers may impose shorter lifetimes. This does not determine Google's separate reporting-data retention. Provider settings and browser restrictions can affect the storage actually created.
Withdrawing permission
Withdrawal immediately disables future application analytics events and removes accessible first-party analytics cookies using relevant paths and domains. The page reloads if analytics software was loaded, so the next document starts with the Google tag blocked. Another open tab receives the changed preference. This website cannot delete cookies belonging to unrelated provider domains or recall requests already transmitted. Use browser/provider controls where needed. Authentication, anti-abuse storage and your essential consent preference are not removed as if they were analytics cookies.
Administrator and security functionality
CMS sign-in uses Firebase authentication persistence and is separate from ordinary public browsing. Connecting Google reporting creates the short-lived HttpOnly OAuth security cookie listed below. Rejecting optional analytics does not sign an administrator out. When an enabled form is sent, Firebase App Check and Google reCAPTCHA Enterprise perform security verification independently of analytics consent. The Firebase SDK can cache attestation tokens and SDK metadata in browser storage. Google reCAPTCHA can use security-related browser storage for its risk assessment. The verification SDK is not initialized merely because a visitor opens a page or accepts analytics. Provider settings and browser restrictions affect the storage actually created.
Global Privacy Control
The application checks the browser's Global Privacy Control signal. Advertising and related sharing integrations remain disabled, and an optional analytics choice cannot enable them. Analytics still requires an affirmative choice; the website does not interpret GPC as automatically rejecting that separate opt-in analytics choice.
Without JavaScript
The policy text remains readable without JavaScript. Optional Google tracking does not load. Previously stored cookies can be removed through browser settings; the interactive preferences dialog requires JavaScript.
Public visitor storage
| Name / storage | Provider / party | Purpose / category | Duration | Created when |
|---|---|---|---|---|
| adaptcx_consent_v1 | AdaptCX / Global Technology Solutions Inc. First-party | Remember category choices and policy/schema version; no unique visitor identifier. Essential preference | Choice is valid for 180 days. Expired data is removed on the next visit; localStorage has no native expiry. | Only when a visitor saves, accepts or rejects optional choices. |
| _ga | Google Analytics 4 First-party cookie; information sent to Google | Distinguish browser instances for optional website analytics. Optional analytics | Configured for 180 days; Google may renew expiry during permitted visits and browsers may shorten it. | Only after analytics permission, when GA4 is configured. |
| _ga_* | Google Analytics 4 First-party cookie; information sent to Google | Maintain GA4 session state. Optional analytics | Configured for 180 days; provider/browser behavior requires hosted verification. | Only after analytics permission, when GA4 is configured. |
| firebase-app-check-database / firebase-app-check-store | Google Firebase App Check First-party storage; attestation requests go to Google Firebase | Cache app-attestation tokens for a requested form submission; tokens are not lead records. Requested-form security | Tokens have the expiry assigned by Firebase. Cached browser records may persist until the SDK updates them or browser storage is cleared. | Only after an enabled form is submitted; independent of optional analytics. |
| firebase-heartbeat-database / firebase-heartbeat-store | Google Firebase SDK First-party browser storage; SDK service metadata sent to Firebase | SDK platform/version heartbeat metadata associated with initializing requested form verification. Requested-form security | Managed by the Firebase SDK and browser; browser storage may remain until updated or cleared. | When the Firebase app is initialized for a submitted form. |
| Google reCAPTCHA security storage (documented cookie: _GRECAPTCHA) | Google reCAPTCHA Enterprise Google-controlled verification service; provider storage depends on deployment/browser behavior | Risk assessment and automated-abuse checks for a requested form submission. Requested-form security | Provider-controlled and subject to browser restrictions; this website does not set its expiry. | When App Check initializes reCAPTCHA to verify a submitted form. |
Administrator-only storage
| Name / storage | Provider / party | Purpose / category | Duration | Created when |
|---|---|---|---|---|
| Firebase Auth SDK-managed browser storage | Google Firebase Authentication First-party administrator storage; Google authentication services | Maintain an authorized CMS administrator session. Admin authentication | Local authentication persistence until explicit sign-out or browser storage removal; SDK/session conditions also apply. | CMS initialization/sign-in; not required for public browsing. |
| __session | AdaptCX First-party | Protect the administrator's Google reporting OAuth connection. Admin security | Up to 10 minutes; removed at callback. | An authorized administrator starts Connect in Analytics Settings. |
Google cookie entries describe configured behavior and documented provider cookies. Browser limits and provider settings can affect expiry; source configuration is not a complete hosted cookie audit.
Privacy requests
Contact compliance@gtscx.ai. Do not include sensitive records in an initial email.