Slice Intelligence Data Charter v1.0
Why this exists
This charter sets the rules Hot Slice Creative follows when it uses anyone's data to build benchmarks. It replaces Data Charter v0.1, an internal document, and makes its rules public in one place anyone can read.
Slice Intelligence is the name for Hot Slice's benchmark layer: combined figures, such as what a healthy tour looks like at a given point in a sales cycle, built from the Tour Health Score, The Chef, and connected tour data from partners like RoadOps.
The charter protects three groups: the artists and managers who use Hot Slice products, the partners whose platforms send us data, and Hot Slice itself, by keeping every promise here one the running systems already keep.
The rules
Rules 1 to 4 are the four rules of Data Charter v0.1, unchanged. Rules 5 to 9 write down protections the systems already enforce.
- Opt-in only. Your data counts toward a benchmark only if you say yes. The Tour Health Score checkbox starts unchecked, and The Chef asks at sign-up or in settings. No choice on file means you are left out. Your latest choice always wins, and switching it off stops any further use.
- Aggregate only. Benchmarks are combined figures. One person's or one tour's data is never shared outside Hot Slice.
- Minimum group of 10. Any group smaller than 10 people is hidden, and so is its size. Shares are worked out so a hidden group's size cannot be found by subtraction. Benchmarks stay internal until at least 10 people have opted in.
- Deletion on request. Deleting your Chef account erases your benchmark data automatically. For anything else, email mgmt@1hotslice.com and we delete it, by person or by tour. Combined figures that cannot identify anyone may remain.
- What goes in, and what never does. Benchmarks use scores, tour figures, figures we calculate from them (such as sell-through or miles between shows), and topic labels from The Chef (such as "routing"). Names, email addresses, and the words you type never go in. Any record carrying extra fields is rejected.
- Internal IDs, not identities. Your email is replaced with an internal ID before anything is stored, and kept apart from benchmark data. A partner's own IDs, such as a RoadOps team ID, are swapped for internal tour keys the same way.
- Partner data is read-only. We only read from connected partners like RoadOps and never write back. Only figures we calculate count toward benchmarks, never the partner's raw records. Where a partner agreement sets stricter terms, those terms apply.
- Not for sale. We do not sell personal information or raw data, from users or partners. No paid product built on benchmarks launches without attorney review and written terms with every data partner whose data it draws on.
- Separate keys for separate jobs. The products that send benchmark data cannot look anyone up or delete anyone. Those actions need a separate key held by Hot Slice alone.
How each rule is enforced
Every rule above is carried out by the running systems, not by a promise alone.
| Rule | Where it is enforced |
|---|---|
| 1. Opt-in only | Each record stores the consent choice in force when it was made. Only people whose latest choice is yes are counted. No choice on file counts as no. |
| 2. Aggregate only | The benchmark service returns combined figures only and is reachable by Hot Slice alone. |
| 3. Minimum group of 10 | Groups under 10 are suppressed with their size hidden. Shares are calculated only across groups of 10 or more, so they always add to 100. |
| 4. Deletion on request | A delete removes a person's identity and every record tied to it, or a tour's mapping and every record for that tour. Deleting a Chef account triggers it automatically. |
| 5. What goes in | Every record is checked against a fixed format. Any record with a name, an email, message text, or any unlisted field is rejected. |
| 6. Internal IDs | Emails and partner IDs are converted to internal IDs before storage and kept in a separate table. |
| 7. Partner data | Partner connections request read-only access. Only calculated figures are recorded. |
| 8. Not for sale | No paid data product exists. Any future one needs attorney review and written partner terms first. |
| 9. Separate keys | The key the products use can only add records. Lookup and deletion need a separate key held by Hot Slice. |
Changes and contact
This is version 1.0, effective October 14, 2026. It replaces Data Charter v0.1 and keeps all four of its rules.
- Every change gets a new version number and date on this page.
- If a change is significant, we give notice before it takes effect, by email or in the product.
- The Hot Slice Creative Privacy Policy covers everything else we do with information. Where the two overlap, the stricter rule applies.
Questions or requests: mgmt@1hotslice.com. A real person answers.