Question 1

How does Maxima define customer data?

Accepted Answer

Maxima defines customer data as any information ingested from, processed for, or generated on behalf of your financial systems. This includes general ledger transactions, journal entries, bank statements, reconciliation records, supporting documentation, and agent-prepared outputs. All such data is classified and handled as Customer Confidential under Maxima's data classification policy.

Question 2

Can I request a copy of Maxima's SOC reports?

Accepted Answer

Yes. Maxima's SOC 2 Type II and SOC 1 Type II reports are available under NDA. Customers and prospective customers can request access through their Maxima representative or by contacting security@maxima.com.

Question 3

Where is customer data hosted?

Accepted Answer

Maxima processes and stores customer data in Google Cloud Platform data centers located in the United States. Customer data is not transferred or hosted outside the U.S.

Question 4

How does Maxima ensure customer data is not used for model training?

Accepted Answer

Maxima maintains contractual agreements with providers including OpenAI, Anthropic, and Google that explicitly prohibit the training, fine-tuning, or retention of customer data. All model usage is limited to inference-only workflows and is configured for zero data retention.

Question 5

Who at Maxima can access customer data?

Accepted Answer

Access to customer data is governed by zero-trust and least-privilege principles. Permissions are enforced through role-based and attribute-based access controls, with regular access reviews conducted by Maxima's security team. When access is no longer required, including during employee offboarding, permissions are removed on a defined and controlled schedule.

Question 6

How does Maxima enforce controls over agent-prepared outputs?

Accepted Answer

Maxima is designed so agents prepare work while authorized accounting users remain in control of review, approval, and posting. Approval gates and segregation of duties are enforced within the product, and every action is captured in an immutable audit trail with clear source-to-output lineage.

Uncompromising security & trust for agentic accounting

Uncompromising security & trust for agentic accounting

Secure by default, not by request

Data segregation

AES-256 encryption at rest

US only data hosting

TLS encryption in transit

No credential storage

SSO & Multi-factor authentication

Your data stays yours

Your data stays yours

Zero model training

Complete data isolation

Data deletion on demand

No data selling or sharing

Immutable audit logs

Transparency by design

24/7 security monitoring

Dedicated security leadership

Defined incident response

Independent penetration testing

Daily encrypted backups

Enterprise grade AI guardrails

Enterprise grade AI guardrails

Nothing posts without approval

Scoped only to accounting workflows

Exceptions surfaced, not buried

Enterprise gradecompliance & controls

Frequently asked questions

Frequently asked questions

How does Maxima define customer data?

Can I request a copy of Maxima’s SOC reports?

Where is customer data hosted?

How does Maxima ensure customer data is not used for model training?

Who at Maxima can access customer data?

How does Maxima enforce controls over agent-prepared outputs?

Move closer to an audit-ready, real-time close

The latest

Maxima raises Seed & Series A to build the agentic AI platform for enterprise accounting

Maxima raises Seed & Series A to build the agentic AI platform for enterprise accounting

AI and SOX compliance: the hidden risk of shadow preparation

AI and SOX compliance: the hidden risk of shadow preparation

Maxima named to AI64's top enterprise AI companies

Maxima named to AI64's top enterprise AI companies

Maxima raises Seed & Series A to build the agentic AI platform for enterprise accounting

AI and SOX compliance: the hidden risk of shadow preparation

Enterprise grade
compliance & controls