Privacy & security

Privacy is an operating discipline, not a badge.

Fractyl is designed to minimise unnecessary exposure while keeping privacy, governance and legal responsibility tied to the client’s actual implementation.

01

Protect data before activation

Personally identifying fields used for media activation are hashed before they leave the client environment. Delivery into third-party data clean rooms follows the identifiers and governance agreed for that environment; raw identifiers are not treated as a default activation payload.

02

Build around the client estate

Fractyl works with existing Google Cloud and customer-data architecture, reducing unnecessary movement and duplication.

03

Make audience logic reviewable

Fields, criteria, suppression rules, destinations and schedules can be reviewed before an audience is saved and synced.

04

Treat compliance as contextual

Fractyl is designed with New Zealand, Australian and relevant US privacy requirements in mind. Applicability and compliance depend on the client’s data, notices, contracts and legal advice.

The platform can enforce rules. It cannot invent permission.

Clients remain responsible for lawful collection, appropriate notices, consent where required, and accurate suppression inputs.

The Fractyl team is responsible for operating the agreed implementation, access and activation processes with appropriate technical and organisational controls.

Detailed security documentation and contractual commitments should be assessed during procurement rather than inferred from marketing copy.

Bring security, privacy and procurement into the conversation early.

Request a technical discussion