Security and data protection

Each customer's environment is a separate, single-purpose cloud project (Google Cloud, EU region). This is the strongest isolation boundary modern cloud technology offers: your data, processing, secrets, and logs live in a project shared with no other customer. Data is never moved between customers.

The principle of least privilege applies throughout. Raw data access is closed by default - only designated service accounts can reach it, not people. Secrets (API keys, passwords) are kept in a secure vault, never in code or files. Every access is traceable.

AI answers are always computed from your actual data - not from estimates or model memory. Your data is not used to train AI models. The business knowledge Atlas accumulates about your company - definitions, rules, context - belongs to you and survives every platform release.

AtlasAction agent boundaries are enforced by infrastructure, not instructions - an agent operates only within the permissions and tools it has been granted, even if it were to err. There are multiple layers of protection:

• API credentials permit only specific operations (e.g. creating a draft order, not confirming it)
• An agent can only reach the tools defined for it
• The agent's ERP user account has restricted permissions - a last line of defense inside the ERP itself
• Rate and volume limits rule out runaway activity

Agents create drafts that your team confirms in the ERP you already use. Every run is logged: what the agent read, what it did, and why.

All environments are monitored continuously - data refresh failures and anomalies reach our team automatically. The central monitoring system holds no customer data: it sees technical health signals only, never your business numbers.

Data is stored and processed in the European Union. Personal data processing is minimized - the analytics is about business data, not profiling people. Data processing terms are fixed in the service agreement; when the agreement ends, your data is deleted.