1. Scope
This notice explains how aiXuberance handles information when you visit the public website, contact us or use the cargo workspace.
2. Information we handle
Depending on how you use the service, this may include account identity, company or tenant details, support correspondence, air waybill numbers, normalized tracking events, workspace activity, security logs and technical request information.
3. Why we use it
We use information to authenticate users, provide and improve cargo workflows, retain tenant-owned shipment context, respond to support requests, protect the service, investigate failures and meet legal obligations.
4. Cargo and shipment data
Shipment information is processed to perform the requested tracking or workflow and to retain operational context within the applicable tenant. Access is designed to be tenant-scoped.
5. Service providers
We may use infrastructure, authentication, database, email, analytics and carrier-data providers where necessary to operate the service. Providers are expected to process information only for the contracted purpose and subject to appropriate safeguards.
6. Retention
We retain information for as long as needed to provide the service, preserve required operational or audit history, resolve disputes and meet legal obligations. Retention periods may vary by information type and account status.
7. Security
We use measures intended to protect information, including verified identity, tenant isolation, service authentication, access controls, encryption where appropriate, monitoring and audit records. No online system can be guaranteed completely secure.
8. Your choices
You may contact us to ask about access, correction or deletion of personal information, subject to applicable law and any information we must retain for security, contractual or legal reasons.
9. International processing
Service providers and cargo data sources may operate in different countries. Where information is transferred, we take steps intended to provide appropriate protection under applicable requirements.
10. Changes and contact
We may update this notice as the product evolves. Material changes will be reflected on this page. Existing pilot organisations should use their established onboarding contact; general guidance is available on the contact page.