1. Introduction
This Cookie Policy explains how INXA Partnership ("INXA", "we", "us", or "our") uses cookies and similar technologies when you access or use the INXA Partnership website and related online services.
Cookies help us operate the Service, maintain secure sessions, remember preferences and understand how the Service is used.
This Cookie Policy should be read together with our Privacy Policy and Terms of Service.
2. What Are Cookies?
Cookies are small text files or similar identifiers that may be stored on your device when you visit a website.
They allow a website to recognize a browser or device and, depending on their purpose, perform functions such as:
- maintaining a login session;
- remembering preferences;
- protecting against unauthorized access;
- maintaining security;
- measuring technical performance;
- understanding how visitors interact with the Service.
Other technologies, such as local storage, session storage, pixels or similar identifiers, may perform functions comparable to cookies.
For simplicity, this Policy refers to all such technologies as "cookies" unless a distinction is relevant.
3. Why INXA Uses Cookies
INXA may use cookies and similar technologies for several purposes.
3.1 Strictly Necessary Cookies
These technologies are required for the basic operation and security of the Service. They may be used to:
- maintain sessions;
- authenticate users;
- maintain access to protected areas;
- protect against unauthorized activity;
- maintain security;
- preserve workflow state;
- support essential technical functionality.
These cookies generally cannot be disabled through the Service because doing so may prevent essential functionality from operating correctly.
4. Functional Cookies
Where used, functional cookies allow INXA to remember choices and preferences. They may support:
- language preferences;
- interface preferences;
- session configuration;
- workflow settings;
- other functionality requested by the user.
These technologies are intended to improve the usability of the Service.
5. Analytics and Performance Technologies
Where enabled, INXA may use analytics or performance technologies to understand how the Service operates and how users interact with it. This may include information such as: pages visited; approximate session duration; interactions with features; browser and device information; technical errors; and performance information.
Analytics information may be used to: identify technical problems; improve usability; measure service performance; and understand aggregate usage patterns.
Where applicable law requires consent for non-essential analytics technologies, INXA will request consent before activating them.
6. Marketing and Advertising Cookies
INXA does not intend to use cookies for behavioral advertising as an inherent requirement of the INXA Partnership Service.
If marketing or advertising technologies are introduced in the future, they will be implemented in accordance with applicable law and, where required, subject to appropriate consent.
7. Third-Party Cookies
Some functionality may rely on third-party services. Depending on the services actually integrated into INXA, these may include providers supporting: authentication, security, identity verification, analytics, AI infrastructure, electronic signatures, or other technical services.
Such providers may place their own cookies or similar technologies. Their processing may be governed by their own privacy policies and terms.
INXA seeks to use third-party technologies only where they are reasonably necessary or otherwise appropriately authorized.
8. Session and Security Technologies
Some INXA functionality requires temporary identifiers to maintain a secure interaction with the Service. For example, an authenticated session may require the Service to recognize that multiple requests originate from the same authorized session.
These technologies may expire when: the session ends; the user logs out; a defined period has elapsed; or the relevant workflow is completed.
Security-related identifiers may be retained or processed for longer periods where necessary to protect the Service or investigate unauthorized activity.
9. XCircle and Access Technologies
Certain INXA workflows may use an XCircle Token or related access mechanism.
Such mechanisms are primarily intended to establish controlled access to a specific INXA workflow or partnership environment. They should not be interpreted as advertising cookies.
Where an access token or identifier is stored in the browser, it may be used to maintain the relevant workflow or access state.
10. Cookie Categories
Depending on the configuration of the Service, cookies may generally fall into the following categories:
| Category |
Purpose |
May require consent |
| Necessary |
Security, authentication and core functionality |
Generally no, where legally exempt |
| Functional |
Preferences and requested functionality |
Depends on jurisdiction |
| Analytics |
Performance and aggregate usage analysis |
Often yes |
| Marketing |
Advertising and behavioral tracking |
Generally yes |
The actual cookies and technologies deployed may change as the Service evolves.
11. Cookie Consent
Where applicable law requires consent for non-essential cookies, INXA will provide an appropriate consent mechanism. You may be able to: accept optional cookies; reject optional cookies; manage cookie preferences; or change your preferences later.
Rejecting optional cookies should not prevent access to core functionality unless a particular feature depends on that technology.
12. Browser Controls
Most modern browsers allow you to control or delete cookies through their settings. You may generally: block cookies; delete existing cookies; receive notifications when cookies are placed; or configure exceptions for specific websites.
Disabling necessary cookies may affect the operation of INXA Partnership. Browser settings vary depending on the browser and version you use.
13. Do Not Track
Some browsers provide "Do Not Track" or similar signals.
Because there is currently no universally consistent technical standard for interpreting all such signals, INXA may not respond to every browser-based signal in the same manner.
Where applicable law requires a specific response to recognized privacy signals, INXA will comply with the relevant requirements.
14. Personal Information
Some cookies and similar technologies may be associated with information that can identify or relate to a user.
Where this occurs, the information is handled in accordance with the INXA Privacy Policy and applicable data-protection law.
Cookies should therefore not be considered entirely separate from our broader data-protection practices.
15. Retention
Cookies may have different lifetimes.
Session cookies
These normally expire when the browser session ends.
Persistent cookies
These remain on the device for a defined period or until deleted.
The retention period depends on the purpose of the technology. Security, authentication and workflow technologies may have different retention requirements from analytics technologies.
16. Changes to This Cookie Policy
We may update this Cookie Policy when: the Service changes; new technologies are introduced; existing technologies are removed; legal requirements change; or our privacy practices change.
The "Last updated" date at the top of this Policy indicates when it was most recently revised.
17. Contact
If you have questions about cookies or similar technologies used by INXA Partnership, please contact:
18. INXA Privacy Principle
INXA is designed around a broader principle of responsible digital infrastructure. We seek to use tracking and identification technologies proportionately to the purpose for which they are required.
Necessary when necessary.
Transparent when optional.
Controlled when sensitive.
Minimal by design.
INXA PARTNERSHIP
Trusted Business Relationships for the Agentic Era.
INXA AI+ • Beyond the Prompt.