Cookie Policy

This Cookie Policy explains how Sloancode Technology Group LLC (“Sloancode,” “we,” “us,” or “our”) uses cookies and similar technologies in connection with Sloancode AI websites, web applications, portals, and other online services that link to this Policy (collectively, the “Online Services”).

Sloancode AI is an enterprise AI platform and product brand operated by Sloancode Technology Group LLC. This Cookie Policy supplements the Sloancode AI Privacy Policy and should be read together with that policy.

This Policy covers not only conventional browser cookies but also, where used, local or session storage, pixels, tags, scripts, software development kits (“SDKs”), device identifiers, link-decoration technologies, fingerprinting or similar storage/access technologies, and comparable mechanisms (“Cookies and Similar Technologies”).

The exact technologies used can change as the Online Services evolve. The production Cookie Inventory and cookie-preference interface should provide the current operational details for technologies actually deployed.

1. What Cookies and Similar Technologies Are

Cookies are small data files or identifiers that a website can store on, or retrieve from, a browser or device. They can allow an Online Service to recognize a browser or device, maintain a session, remember preferences, support security, understand usage, or enable other functionality.

Similar technologies may perform comparable functions without using a traditional cookie file. Depending on the technology, information may be stored locally on a device, transmitted through a pixel or tag, associated with a device or browser identifier, or inferred from technical characteristics.

2. Scope of This Policy

This Policy applies to Sloancode AI Online Services that link to it. It does not automatically govern unrelated websites, consulting services, or other offerings of Sloancode Technology Group LLC that publish a different cookie or privacy notice.

Third-party websites and services reached through links from Sloancode AI are governed by their own privacy and cookie practices.

3. First-Party and Third-Party Technologies

First-party technologies are set or controlled through the Sloancode AI domain or Online Service being visited.

Third-party technologies are provided by another organization whose services are integrated into the Online Services, such as analytics, video, support, authentication, communications, fraud-prevention, advertising, or other providers.

A third party’s ability to collect, combine, or use information is governed by applicable law, our contractual/configuration controls where applicable, and that third party’s own terms and privacy practices.

4. Session and Persistent Technologies

Session technologies generally expire when the browser session ends. Persistent technologies remain for a defined period or until deleted, subject to their configured lifetime and browser/device behavior.

Sloancode will seek to configure retention periods that are proportionate to the purpose of the technology and applicable legal requirements.

5. Categories of Cookies and Similar Technologies

Sloancode may use the following categories, but only categories actually verified in production should be enabled and disclosed in the final Cookie Inventory.

Strictly Necessary / Essential

Technologies necessary to provide an Online Service or functionality requested by the user, maintain sessions, authenticate users, route traffic, prevent fraud or abuse, preserve security, remember privacy choices, or perform other essential operations.

Functional / Preference

Technologies that remember optional settings or preferences, such as language, interface choices, saved configurations, or other convenience features.

Analytics / Performance

Technologies used to understand how Online Services are used, measure performance, identify errors, improve navigation, evaluate feature adoption, and generate usage statistics.

Advertising / Targeting

Technologies, if used, that support advertising, audience measurement, cross-site or cross-context behavioral advertising, campaign attribution, retargeting, or similar marketing functions. This category must not be represented as active unless verified.

Embedded Content / Third-Party Media

Technologies associated with embedded video, maps, social features, chat, scheduling, forms, or other third-party content. Where legally required, non-essential third-party content should not activate tracking until the user has made the required choice.

6. Purposes for Which We May Use These Technologies

operate, secure, and maintain Online Services;
authenticate users and maintain sessions;
prevent fraud, abuse, account compromise, and malicious activity;
remember privacy and cookie preferences;
remember user-selected functionality or settings;
measure traffic, performance, reliability, and feature usage;
diagnose errors and improve Online Services;
understand campaign attribution and marketing effectiveness where legally permitted;
provide embedded or third-party functionality requested by users;
comply with legal, security, and recordkeeping obligations.

7. Strictly Necessary Technologies

Where applicable law permits, technologies that are strictly necessary to transmit a communication or provide an online service or functionality specifically requested by the user may operate without optional consent.

Sloancode should still disclose material essential technologies transparently even where consent is not required.

A technology is not treated as strictly necessary merely because it is convenient, commercially useful, helpful for analytics, or necessary for Sloancode’s own advertising objectives.

Where applicable law requires consent before storing or accessing non-essential information on a user’s device, Sloancode will seek consent before activating the relevant technologies.

Consent should be freely given, specific, informed, and indicated through an affirmative action where required. Merely continuing to browse should not be treated as consent where the governing law requires an affirmative choice.

Non-essential technologies should remain blocked until the required consent is obtained in jurisdictions where prior consent is required.

Where used, the cookie banner or consent management platform (“CMP”) should present choices in a clear and non-deceptive manner.

provide a meaningful choice to accept or reject non-essential categories where required;
avoid pre-selected optional categories where that would invalidate consent;
make rejection reasonably accessible and not materially more difficult than acceptance where applicable law requires comparable choice;
allow granular category choices where appropriate;
provide access to Cookie Settings after the initial choice;
record consent/preference evidence appropriate to applicable law;
apply the user’s current preference to technologies controlled through the CMP.

10. Withdrawal and Changing Preferences

Where consent is the basis for a technology, users may withdraw that consent through the available Cookie Settings or other disclosed mechanism.

Withdrawal will apply prospectively. It does not necessarily delete information already lawfully collected or remove cookies already stored on a device; users may also need to delete existing cookies through browser/device controls.

Sloancode should make withdrawal of consent as practicable as giving it where required by law.

Sloancode may use an essential cookie or similar mechanism to remember a user’s privacy choices.

Preference records may include the categories accepted/rejected, date/time, consent framework/version, jurisdiction or region signal where relevant, and a pseudonymous browser/device identifier.

Preference records should be retained only for a period reasonably necessary to demonstrate and honor choices and then refreshed or deleted according to the implemented consent framework.

12. Re-Prompting and Material Changes

Sloancode may ask users to make a new choice when the consent record expires, material cookie practices change, a new purpose or materially different third party is introduced, applicable law requires renewed consent, or the prior choice can no longer be reliably applied.

Re-prompt frequency should not be manipulated to pressure users into accepting optional technologies.

13. Analytics and Measurement

If analytics technologies are used, Sloancode may use them to measure visits, navigation, feature usage, performance, error conditions, conversion events, and other usage patterns.

Analytics should be configured to minimize unnecessary Personal Data where reasonably feasible, including limiting identifiers, retention, sharing, and cross-service uses.

Where analytics requires consent under applicable law, it should not activate until that consent is obtained.

14. Advertising and Cross-Context Behavioral Advertising

Sloancode must not state that it uses targeted advertising, cross-context behavioral advertising, retargeting, or advertising cookies unless those technologies are actually deployed.

If such technologies are introduced, Sloancode will update this Policy and the Cookie Inventory and implement consent/opt-out mechanisms required by applicable law.

Where a technology constitutes “sharing,” targeted advertising, sale, profiling, or a comparable regulated activity under applicable U.S. state privacy law, Sloancode will provide the applicable rights and signals required by law.

15. Opt-Out Preference Signals and Global Privacy Control

Where applicable law requires recognition of a legally valid browser- or device-based opt-out preference signal, Sloancode will process that signal as required for the covered activities.

The production implementation must determine which Online Services, activities, jurisdictions, and identifiers are subject to such signals and must avoid claiming support until the behavior is verified.

A signal that applies to sale/sharing or targeted advertising is distinct from cookie consent under laws that separately require consent for storage/access technologies; both frameworks may need to be implemented.

16. Do Not Track

Browser “Do Not Track” signals are not necessarily equivalent to legally recognized opt-out preference signals. Sloancode will describe its response to Do Not Track only after the actual production behavior is confirmed.

The final website should not make an unsupported statement that Sloancode honors or ignores a particular signal.

17. Local Storage and Session Storage

The Online Services may use browser local storage or session storage to maintain application state, security information, preferences, or other functionality.

Where these technologies store or access information on a user’s device, they may be subject to the same or similar legal requirements as cookies, depending on jurisdiction.

18. Pixels, Tags, and Scripts

Pixels, tags, scripts, and similar code can transmit information when a page loads or an action occurs. They may be used for analytics, performance, security, conversion measurement, embedded functionality, or marketing where enabled.

The final Cookie Inventory should identify material third-party tags and their purposes rather than relying on the generic label “cookies.”

19. Device Fingerprinting and Similar Techniques

Sloancode should not deploy device fingerprinting or probabilistic identification for advertising, tracking, or fraud purposes without a documented legal and privacy review.

If fingerprinting or comparable techniques are used for essential security or fraud prevention, the purpose, proportionality, retention, and legal basis should be documented and disclosed where required.

Such techniques must not be silently categorized as ordinary essential cookies without confirming that the applicable exemption actually applies.

20. Link Decoration and Navigational Tracking

Tracking parameters or identifiers may be appended to links for attribution, routing, security, or analytics. Where link decoration enables tracking across sites or services, it must be evaluated under applicable cookie, privacy, sale/sharing, and targeted-advertising rules.

Sensitive identifiers should not be placed in URLs where they could be exposed through browser history, referrer headers, logs, or third parties.

21. Authentication and Account Technologies

Authenticated Sloancode AI portals may use essential session, authentication, security, anti-forgery, load-balancing, or account-state technologies.

Authentication cookies should be scoped, secured, and retained consistent with verified application-security requirements.

Authentication should not be bundled with unrelated advertising tracking as a condition of using a necessary account function.

22. Security and Fraud-Prevention Technologies

Sloancode may use technologies designed to detect suspicious activity, protect accounts, prevent automated abuse, enforce rate limits, identify malicious traffic, and maintain service integrity.

Where a security technology qualifies for a consent exemption, its use should remain limited to the qualifying security purpose unless another lawful basis/consent applies.

23. Chat, Forms, Scheduling, and Support Tools

Online Services may include forms, chat, scheduling, support, or lead-capture functionality. Such tools may use Cookies and Similar Technologies to maintain sessions, prevent abuse, route submissions, or measure interactions.

If a third-party tool sets non-essential technologies, it should be classified and controlled through the consent framework where required.

Submission of a form or initiation of chat does not itself constitute consent to unrelated tracking or marketing technologies.

Embedded content may cause third parties to receive device/browser information or set technologies when loaded.

Where prior consent is required for non-essential third-party content, Sloancode should use consent-gated loading or a comparable mechanism.

Users may be able to access equivalent content directly from the third party, subject to that third party’s policies.

25. AI Product and Application Telemetry

Sloancode AI applications may generate operational telemetry such as feature events, error logs, performance metrics, authentication events, and security signals.

Not all server-side telemetry is a cookie or device-storage technology. However, where telemetry depends on storing/accessing information on a device or involves Personal Data, applicable cookie and privacy requirements must be evaluated.

Product telemetry must not be automatically described as anonymous unless it has been verified to meet the applicable standard for anonymous or de-identified data.

26. Website Personalization

If personalization technologies are used, they may remember choices or tailor content based on prior interactions.

Personalization that is merely convenient should not be categorized as strictly necessary where applicable law requires consent for optional storage/access.

Personalization involving profiling or sensitive data requires additional legal review.

27. Children

Sloancode AI Online Services are principally designed for business and enterprise use. Sloancode does not intend to use Cookies and Similar Technologies to behaviorally target children.

If an Online Service is intentionally directed to children or Sloancode has actual knowledge triggering child-specific requirements, the cookie/consent design must be reviewed under applicable child-privacy laws before deployment.

28. Sensitive Personal Data

Sloancode should not intentionally place sensitive Personal Data in cookie values, URLs, advertising identifiers, or tracking parameters unless technically necessary, appropriately protected, and legally authorized.

Tracking involving health, precise location, biometric, financial, children’s, or other sensitive information requires enhanced review and controls.

Cookie and similar-technology lifetimes should be proportionate to their purposes.

The final Cookie Inventory must state actual durations or meaningful retention descriptions based on production configuration.

A vendor’s maximum technical cookie lifetime should not automatically become Sloancode’s stated retention period if Sloancode configures a shorter period.

30. Browser and Device Controls

Most browsers and devices allow users to delete or block cookies and manage certain tracking permissions.

Blocking all cookies may affect authentication, security, preferences, or other functionality that depends on essential technologies.

Browser/device controls do not replace Sloancode’s obligation to provide legally required consent or opt-out mechanisms.

31. Third-Party Browser Extensions and Privacy Tools

Users may use privacy extensions, content blockers, DNS tools, or browser settings that block scripts or cookies. Such tools may cause portions of the Online Services to function differently.

Sloancode does not control third-party privacy tools and cannot guarantee compatibility with every configuration.

Sloancode may use coarse location information, such as country or region inferred from network information, to determine which privacy choices or consent framework to present.

Regional logic must not be used to evade protections applicable to a user, and precise geolocation should not be collected merely to choose a cookie banner unless necessary and lawful.

33. International Visitors

Cookie and similar-technology requirements vary by jurisdiction. Sloancode may present different controls based on applicable law while maintaining a consistent baseline of transparency.

For jurisdictions requiring prior consent for non-essential storage/access technologies, Sloancode should use prior blocking and valid consent before activation.

For jurisdictions that regulate sale, sharing, targeted advertising, or profiling through opt-out rights, Sloancode should provide the applicable opt-out mechanism if the covered activity occurs.

34. Relationship to the Privacy Policy

The Sloancode AI Privacy Policy describes broader collection, use, disclosure, retention, and rights practices involving Personal Data. This Cookie Policy focuses on Cookies and Similar Technologies.

If information collected through a cookie or similar technology is Personal Data, the Privacy Policy and applicable data-protection law also apply.

35. Relationship to Customer-Controlled Sloancode AI Deployments

A Sloancode AI Customer may independently deploy Sloancode-powered widgets, chat, voice, forms, or integrations on the Customer’s own website or application.

Where the Customer controls that website/application and determines its tracking practices, the Customer is responsible for its own cookie notice, consent mechanism, and legal obligations. Sloancode’s role in processing Customer Personal Data is governed by the Agreement and DPA.

This Sloancode AI Cookie Policy does not automatically substitute for a Customer’s own website cookie policy.

36. Changes to This Policy

Sloancode may update this Cookie Policy as technologies, Online Services, vendors, purposes, or laws change.

The “Last Updated” date should reflect the latest material revision. Where a material change requires renewed consent, Sloancode will seek a new choice through the implemented consent mechanism.

37. Contact

Sloancode Technology Group LLC
Attn: Sloancode AI Privacy
99 Wall Street
Suite 3772
New York, NY 10005
United States

Legal: legal@sloancode.com

Support: support@sloancode.com

Privacy: privacy@