Skip to content
Privacy & Data Protection

Your Maximo data stays your data.

Maxley was designed from the ground up to use isolated infrastructure in a privacy-first implementation pattern, with curated no-training models from leading providers like Anthropic.

Data Protection Model Customer-Controlled
Customer MAS
Gateway Controls
Approved AI / Workflow Use
No Training on Customer Data
No Model TrainingCustomer Maxley conversations and Maximo data are not used to train AI models.
No Cross-Tenant Data PathsMaxley deployments are isolated by customer, with no shared customer compute path.
Customer-Controlled RecordsChat history, token usage, and costs can stay inside the customer’s own Maximo database.
Privacy Philosophy

Privacy should be enforced by architecture, not just policy language.

Maxley is designed so customer data is controlled through infrastructure isolation, gateway access, Maximo permissions, customer-owned provider credentials, limited retention, and auditable usage records.

Across the broader MaxStack ecosystem, privacy also means keeping systems dedicated, minimizing unnecessary data duplication, clearly defining integration paths, and supporting customer-controlled deployment patterns.

Privacy priorities:

  • No AI provider model training on customer data
  • No persistent customer Maximo data stored on MaxStack infrastructure by Maxley
  • Customer-owned AI provider API keys
  • Chat history stored in the customer’s Maximo database
  • Uploaded files processed in memory
  • Dedicated customer deployment patterns
Privacy Layers

Privacy controls across AI, infrastructure, documents, integrations, and workflows.

Maxley Privacy Flow

Maxley limits what moves, where it moves, and who controls it.

Maxley’s privacy model is designed around customer-controlled Maximo records, gateway-mediated access, customer-owned AI provider credentials, and no AI model training on customer conversations or Maximo data.

1

User Context

Maxley starts with the authenticated user’s Maximo context and permissions.

2

Gateway Filter

Access is validated through the gateway before Maximo data is used.

3

Provider Request

Approved context is sent using the customer’s AI provider account and API key.

4

Customer Record

Chat history, usage, token counts, and cost can be stored in the customer’s Maximo database.

No data sharing for model training.

Maxley is designed so supported AI providers do not use customer Maximo data, uploaded files, or user conversations to train foundation models.

What this means in practice:

  • Customer prompts are not used for provider model training
  • Customer Maximo data is not used for provider model training
  • Customer uploaded files are not used for provider model training
  • Customer conversations are not retained by the AI provider for training
  • Customers can use their own provider account and control API access
  • Customers can manage token spend, limits, and provider policies directly
Detailed Privacy Controls

Privacy controls by category.

Want to review privacy for your environment?

Talk through Maxley gateway server isolation, data handling, an AI provider controls.