Some of the data that would make your questions sharper is also data you’d rather not hand to anyone: customers’ emails, phone numbers, account records. You don’t have to choose between the two. Each way of connecting data to Crunch has a way to keep the raw personal values on your side, so what Crunch reads is only what you’ve decided to let out.
On your website
Hash emails and phone numbers in the visitor’s browser before they are sent. Hashing turns a value like an email address into a scrambled code, so the address itself never travels. See Hashing user IDs for how to set it up.
In your database (Team)
The on-prem sync connector runs in your network — on your own machines — and applies a rule to every column before anything leaves. A connector is the piece that moves data from one of your sources to Crunch. Each column’s rule is one of:
- drop — the column isn’t sent at all;
- hash — it’s sent as a scrambled code instead of the raw value;
- round or truncate — it’s sent less precisely;
- send — it’s sent as it is.
Two safeguards sit underneath the rules:
- A column without a rule is dropped. Forgetting to write a rule never lets a column out.
- A local floor file can force a column to be dropped or hashed whatever the rules say. It’s kept locally, on your side.
In your data lake (Team)
Link tables with a read-only user — a login that can read but not change anything — and only the schemas you allow. A schema is a named group of tables, so you choose exactly which groups Crunch can see.
Need more?
For anything beyond these, talk to us about Business.
Related
- What we collect — exactly what each connection sends.
- Hashing user IDs — setting up hashing on your website.
- On-prem sync — the rules and floor file in detail.