# Data-sharing agreement (template): anonymous anti-trafficking totals

*Template, 19 October 2026. Have counsel adapt the legal clauses (marked ⚖) for each partner and country before signing. Plain
words on purpose: both sides should be able to read it.*

**Between** [Bible Study Helper operator, legal name, address] ("the Provider")
**and** [Partner organisation, legal name, address] ("the Partner").

## 1. Background

The Provider runs biblestudyhelper.org, a free website with tools that help people check job offers, recognise the signs of
forced labour and human trafficking, and find help. The tools keep only anonymous counts: no names, contact details, identifiers
or message text. The Partner works to prevent trafficking or to help its victims.

## 2. Purpose

The Provider shares totals so that the Partner can:

- see which warning signs and needs appear in which countries and routes;
- plan prevention, outreach, hotline staffing and support;
- check and improve the Provider's tools and directory (the Partner may tell the Provider where its data looks wrong).

**The Partner will not use the data**: to identify, locate or contact any person or small group; for immigration or criminal
enforcement against workers or victims; to profile people for advertising; for resale or any commercial product; or for any
purpose not listed above without the Provider's written consent.

## 3. What is shared

- **Totals only**, by country (the phone's country, from the network), month and, where available, language, route (origin →
  destination) and traffic source group (paid ads, shares, search, direct). Annex A lists every table and field.
- **Never**: single records, message text, identifiers, times finer than a month, or any number under 10.
- Delivery: the monthly country brief (PDF or HTML) and, if agreed, the same tables as CSV, sent by [secure channel].

## 4. Small numbers and re-identification

- Every number under 10 is left out by the Provider before sharing. The Partner keeps that rule in anything it publishes or passes
  on, including tables derived from the data.
- The Partner will not try to identify anyone, and will not combine the data with other data in a way that could single out a
  person or a small community.
- If the Partner finds that a person or small group could be identified, it stops using that part, tells the Provider within 72
  hours, and deletes it if asked.

## 5. Reading the data correctly

The Partner will read and cite the data with the method note (Annex B): it comes from people who chose to use the tools and who
mostly reached the site through ads; it is a signal, not a prevalence estimate; one person can be counted more than once; some
labels are made by an AI model and can be wrong. Public use cites "Bible Study Helper (biblestudyhelper.org), anonymous tool
counts, [month/period]" and states the paid-traffic share given in the brief.

## 6. Security

The Partner keeps the data on systems with access limited to named staff, protected by passwords and two-step sign-in, and does not
upload it to public AI tools or public storage. Each side names a contact (Annex C).

## 7. Onward sharing and publication

No onward sharing without the Provider's written consent. Publications may include totals of 10 or more with the citation and the
method note. The Provider may publish that the Partner receives the data.

## 8. Keeping and deleting

The Partner keeps shared files for at most [24] months, then deletes them, unless both sides agree in writing to keep a specific
summary longer. On termination, the Partner deletes everything received within 30 days and confirms it in writing.

## 9. Incidents

Each side tells the other within 72 hours of finding a loss, leak or misuse of the shared data, with what happened and what it is
doing about it.

## 10. Checks

The Provider may ask once a year how the data is used and stored, and the Partner answers in writing within 30 days.

## 11. Term and ending

From signature for [12] months, renewing for 12 months unless either side gives 30 days' written notice. Either side may end it
at once if the other breaks sections 2, 4 or 7.

## 12. ⚖ Legal clauses (for counsel)

Liability and its limits; no warranty on data accuracy (the data is provided as is); governing law and courts; data-protection
roles (with anonymous totals neither side should be a controller of personal data, but confirm for each country); notices.

## Signatures

| | Provider | Partner |
|---|---|---|
| Name | | |
| Title | | |
| Date | | |

---

## Annex A: data dictionary (from the observatory, `GET /api/admin/observatory`)

| Table | Fields |
|---|---|
| Use of the tools | per country and month: self-checks, AI job-offer checks, private-chat messages, flagged questions, one-tap answers, help actions |
| Warning signs (ILO) | the ILO's 11 indicators of forced labour, with the count from each tool |
| Self-checks | per question: answered, yes, not sure, no, yes share |
| Private chat | messages by subject, by stage (planning to go / has an offer / abroad now), by kind of work, by danger level |
| Flagged questions | by subject and by sign |
| One-tap questions | per question: shown, answered, answers and shares |
| After a risky result | "What will you do now?" after a job-offer, contract or agency check showed warning signs: shown, answered, each answer and its share (will not pay or go, ask more questions, talk to family, still go, not sure), by tool and by result; stated intent at that moment, not what people did later |
| Routes | origin → destination with the tools behind each count and how each end is known |
| Recruitment | recruitment cost (SDG 10.7.1): who paid (the worker or the family), the cost as a band of months of pay abroad, its median band by home country and by route (home country → region of the job); job offers checked (where offers came from, visa, job type) |
| Help-seeking | hotline taps, registry and agency checks, chats, reports, check-ins, warnings shared |
| Traffic source | share of counts from paid ads, shares, search, direct |
| Mapping | every count's id → ILO indicator, CTDC means of control, CTDC type of exploitation; kind = indicator, risk sign, need or context |

## Annex B: method note

Included in every brief and in the observatory's `method` block: what the tools are, what is counted, small-number rules, how
routes are worked out, traffic sources, known limits.

## Annex C: contacts

| | Provider | Partner |
|---|---|---|
| Data contact | | |
| Security incidents | | |
