Three principles for how JourneyOS handles client data.

JourneyOS is a behavioral funnel intelligence layer for consumer brands. Three principles govern how JourneyOS handles client data during a pilot engagement. The principles below are the public-facing statement; the operational specifics live on /security; the formal legal coverage lives in /legal/privacy and the per-pilot data processing agreement.

The three principles.

Your data is not training data for JourneyOS models

Client data is processed per engagement. JourneyOS does not aggregate data across clients and does not train models on client data. The customer-types and behavioral inferences ship back to you and stay there.

No cross-client aggregation

Each pilot is siloed. There is no cross-client data pool, no cross-client insight transfer, and no benchmark layer built from another client's data.

Client-owned outputs

You keep everything JourneyOS generates. JourneyOS does not retain rights over client outputs after deletion.

Where to find data-handling specifics (/security).

The principles above describe what JourneyOS will and will not do with client data. The operational specifics (storage location, encryption at rest, encryption in transit, retention defaults, deletion process) live on /security. The /security page also includes a frequently-asked questions section that covers SOC 2 status, GDPR and DPDP awareness, and cross-client siloing in detail.

How the principles apply per pilot.

Each pilot engagement signs a data processing agreement before any data exchange. The agreement specifies the data types JourneyOS will process, the retention defaults, the deletion process, and any client-environment processing requirements. The three principles above are the floor; the data processing agreement can extend them but cannot weaken them.