No direct identifiers required.
A plain, buyer-safe summary of how WeaveSight handles your data — built for review by your data, security, legal and finance teams. We work from a minimised, pseudonymised dataset with no direct identifiers; we retain it as your knowledge repository for the life of the contract and delete it on contract end (or on request). WeaveSight acts as a data processor on your documented instructions.
The minimum to estimate incremental response — and nothing more.
What we require
- a pseudonymised customer key (hashed by you)
- a few binned pre-campaign features (e.g. tenure band, activity band, region)
- campaign exposure — what action each key was sent
- outcomes — e.g. order / revenue, post-campaign
- cost / margin fields for the budget readout
What's not in the modelling dataset
- names, emails, phone numbers, addresses
- device IDs or any direct identity fields
- raw identity tables, or anything that lets us identify an individual
A hashed key you can re-link is pseudonymised data, which we treat with full care. Re-identification happens only inside your systems — we are never given the means to do it.
You stay in control of the path.
Most engagements start from a client-prepared pseudonymised extract or CSV, or restricted read access to a prepared warehouse view containing only the agreed modelling fields. Where it helps, we assist in defining the SQL. You re-identify and activate the recommendations inside your own systems.
Encrypted, least-privilege, logged.
The operating controls we apply to every engagement, before any client data moves.
Encryption
In transit (TLS) and at rest on every system that touches the data, including endpoints and backups.
Least-privilege access
Need-to-know only, MFA on accounts that touch client data, and a single isolated location per client. No client data in code or repositories.
Audit logging
Access to and movement of data is logged — who, what and when.
Your knowledge repository for the life of the contract. Deleted on contract end.
Your data carries no direct identifiers. During the contract we retain the pseudonymised modelling data and the derived experiment record — what was tested, the results, insights and recommendations — as your compounding knowledge repository, so learnings build across projects instead of resetting each time. It is used solely for your projects, never to train cross-client models or for any other client. It is deleted on contract termination (or on request at any time), with confirmation available. Backup retention and deletion follow the agreed DPA schedule.
Processor role, clear terms, no surprises.
Sub-processors
We maintain a register of any vendor that could touch your data (e.g. cloud compute / storage) with its data-processing terms. We share the current list on request and introduce no new data-touching sub-processor without due diligence.
Your protections
- NDA and DPA available as standard before any data moves
- we process only on your documented instructions
- breach process: we notify you without undue delay and support your obligations
- we assist with data-subject requests and deletion within scope
- we support your data-residency requirements
- we do not use your data to train cross-client models, or for any other client, without written permission
- outputs are decision support — you remain responsible for activation, lawful basis, notices and opt-outs
Privacy- and security-by-design.
WeaveSight is architected against a standing set of compliance principles — data minimisation, encryption, least privilege, retention / deletion, audit logging and sub-processor control — aligned to GDPR, SOC 2 and ISO 27001.
- GDPR — designed to support GDPR-compliant processing as a processor under a DPA (not a blanket "GDPR-compliant" claim). A re-linkable pseudonymised key may still be personal data under applicable law; you remain the controller.
- SOC 2 / ISO 27001 — not certified or audited. The operating model is designed to align with common SOC 2 and ISO 27001 control areas, with formal certification pursued when an engagement requires it.
- Happy to complete your security questionnaire in the meantime.
Send us your security questionnaire.
We'll answer it, share our sub-processor list, and put an NDA and DPA in place before any data moves.