Our cookie telemetry operates under strict consent boundaries

This telemetry specification took effect on 2026-10-22 across our Chicago infrastructure.

This technical notice defines every client-side storage token, tracking mechanism, and network telemetry signal deployed on ai-fromus.shop. These pages take effect on 2026-10-22. As an engineering and advisory portal operated by Ai Fromus, trading at ai-fromus.shop, we maintain transparent technical boundaries: we do not load third-party marketing tags indiscriminately, and we do not persist invasive behavioral profiles. The rules outlined below govern all visitor sessions initiating through modern web browsers.

We distinguish between strictly necessary runtime storage, analytical telemetry, and campaign attribution.

Client storage mechanisms on this domain are segmented into three explicit operational classifications, each bound to specific functional requirements:

1. Strictly Necessary Runtime Storage: These elements are required for core site operations. They include the cryptographic session token for our live support chat widget (tilided.php), form CSRF submission nonces, and the site_consent_v2 token storing your privacy choices. These do not track personal behavior across third-party websites and cannot be disabled without breaking interactive portal capabilities.

2. Analytical & Diagnostic Telemetry: These signals measure aggregate interface performance, page rendering latency, diagnostic tool computation errors, and benchmark asset loading speeds. They help our engineering desk detect broken model links or mobile rendering defects.

3. Advertising & Campaign Attribution: Identifiers that record whether a visitor reached our Chicago advisory platform via sponsored search ads. These tokens capture network click IDs so that ad platforms can register conversions without exposing private corporate inquiries.

Our persistent storage inventory details purpose, origin, and exact lifecycle duration.

Below is the complete inventory of client-side cookies and browser storage keys utilized on this platform:

We do not store passwords, credit card numbers, or unencrypted personal credentials inside client-side storage keys at any time.

Campaign traffic from google ads, microsoft advertising, and Meta Ads carries inbound click identifiers.

This platform receives commercial visitors through sponsored campaigns executed across leading advertising networks: Google Ads, Microsoft Advertising and Meta Ads send traffic here. When a user clicks a sponsored link leading to our consulting services or benchmark guides, the ad network appends a distinct parameter to the URL:

1. google ads: Appends the gclid (Google Click Identifier) query parameter to destination links, facilitating server-side conversion validation.

2. microsoft advertising: Appends the msclkid (Microsoft Click Identifier) parameter to evaluate search query intent and prevent fraudulent ad traffic.

3. Meta Ads: Appends the fbclid query parameter when technical buyers navigate from sponsored developer community announcements.

These query parameters are captured by our web server solely to determine which advisory topics generate legitimate engineering interest. They are never paired with personal identifiable records without voluntary form submission.

Google Consent Mode v2 enforces four denied signals until explicit client authorization is granted.

Our engineering stack integrates Google consent mode v2 at the network gateway level. Consent Mode holds ad_storage, ad_user_data, ad_personalization and analytics_storage denied until the visitor allows storage, and sets them back to denied the moment the visitor declines or withdraws consent.

Before any user interaction with our privacy interface, the four standard consent flags are strictly set to denied:

1. ad_storage: "denied" — Prevents storage of cookies used for advertising attribution.

2. ad_user_data: "denied" — Halts transmission of user telemetry to Google for ad measurement.

3. ad_personalization: "denied" — Disables remarketing and demographic personalization profiles.

4. analytics_storage: "denied" — Prevents analytical cookies from setting persistent client IDs.

These four signals are upgraded to granted only when a visitor explicitly selects “Allow Storage”. If the visitor chooses “Decline All”, the parameters remain denied. If a visitor later revokes consent, our consent manager immediately re-issues denied commands to all runtime tags.

Visitors exercise initial consent via the banner dock and may modify settings at any moment in the footer.

When you first access ai-fromus.shop, an unobtrusive banner dock appears at the bottom of the viewport. This dock provides two balanced controls: “Allow Storage” to authorize analytical and advertising parameters, or “Decline All” to reject non-essential telemetry.

You are never locked out of our research articles, benchmark data, or contact directory if you refuse storage. Furthermore, you may change your decision at any time: simply scroll to the footer on any page and click the Cookie Settings button. This will instantly redisplay the consent interface, allowing you to withdraw or modify your stored preferences.

Declining non-essential storage preserves full portal access while disabling external telemetry.

We believe in technical transparency. If you choose to decline analytics and advertising storage:

1. What Still Works: All editorial benchmark articles, LLM teardowns, workflow automation guides, the interactive model and token diagnostic lookup tool, the direct consultation inquiry form, and the real-time support chat terminal remain 100% operational.

2. What Stops: Third-party advertising tags from Google Ads, Microsoft Advertising, and Meta Ads are suppressed. No persistent conversion tracking cookies are written to your local disk, and the four Consent Mode v2 flags remain permanently denied.

External platform privacy statements govern data processed across third-party networks.

For visitors interested in examining the specific processing policies enforced by our advertising and telemetry partners, please consult their official statutory documentation:

1. Google Ads & Analytics: Google’s data governance practices and privacy frameworks are accessible at policies.google.com.

2. Microsoft Advertising: Microsoft’s telemetry handling, Bing ad click attribution, and security guidelines are documented in the Microsoft privacy statement at privacy.microsoft.com/privacystatement (privacy.microsoft.com).

3. Meta Platforms: Meta’s commercial data policies and advertising network standards can be inspected via their official developer privacy center.

Our Chicago engineering team answers specific cookie inquiries directly via telephone or email.

If you have questions regarding a specific token name, storage duration, or Consent Mode signal implementation on ai-fromus.shop, contact our Chicago technical desk:

Ai Fromus, trading at ai-fromus.shop
400 East Monroe Street, Chicago, Illinois 60603, Chicago, Illinois, United States
Direct Telephone: +1 (218) 555-3428
Technical Inquiry Email: [email protected]
Corporate legal proof: Registered in Chicago, Illinois, LLC № 12345678