> For the complete documentation index, see [llms.txt](https://docs.aloop.icustomer.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aloop.icustomer.ai/security-and-compliance/security-model.md).

# Security model

How iCustomer Platform protects your data: encryption, workspace isolation, PII handling, consent-aware activation, and access control.

Your data runs your go-to-market. The platform is built so it stays yours.

## The basics

* **Encryption everywhere.** Data is encrypted in transit and at rest.
* **Workspace isolation.** Each workspace's data, context, and memory are its own. Nothing is shared across workspaces or tenants.
* **Your data never trains public models.** What the system learns from your workspace stays in your workspace.
* **Access is role-based.** Who can see and change what is governed by [users and roles](/settings/users-and-roles.md). Sign in with Google or with email and a one-time code. API access uses scoped, revocable keys.

## Where it runs

* **Enterprise** runs in your cloud or warehouse. "Zero egress" means exactly this: no warehouse data leaves except governed, customer-approved activations. The connection is in place, and nothing is copied out to run the platform.
* **SMB** runs in our managed cloud.

Same architecture, different home.

## Third-party data never enters raw

* Licensed data from our 50+ data vendors is resolved to OneSource IDs before it reaches your audiences.
* It is never written raw into your CRM or media accounts.
* You see one counterparty and one meter, iCustomer credits, with no vendor contracts of your own.
* Deletion requests propagate at the OneSource ID level, which keeps provenance clean.

## PII handling, per field

You choose how each sensitive field is handled at ingestion:

* **Hash**: one-way, still usable for identity matching and ad-platform audiences without exposing the raw value.
* **Mask**: partial visibility for operators.
* **Encrypt**: reversible, for fields authorized users need to read back.
* **Exclude**: not ingested at all.

Hashing is consistent within your workspace, which is what lets identity resolution and audience matching work on protected values.

## Consent-aware by design

Consent and suppression flags travel with your data and flow into every activation. Suppressed records are excluded before anything reaches a destination, and opt-outs are honored across channels. See [Guardrails and suppression](/plays/guardrails-and-suppression.md).

## More detail

The full control set runs from deny-by-default network rules and encrypted backups to annual risk and vendor assessments. Detailed policies and our sub-processor list are available on request from your iCustomer contact.

Our [Privacy Policy](https://www.icustomer.ai/privacy-policy) covers data handling in full. For compliance programs, see [SOC 2](/security-and-compliance/soc2.md) and [GDPR, CCPA and DSAR](/security-and-compliance/gdpr-ccpa-dsar.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.aloop.icustomer.ai/security-and-compliance/security-model.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.