IMP · live document
Data processing summary (DPA-ready)
Controller/processor outline for privacy counsel.
IMP — Data processing summary (DPA-ready outline)
Important: This is a summary for buyers and counsel, not a signed Data Processing Agreement. Your legal team should finalise roles, SCCs, and schedules with Altamont Digital.
1. Parties (typical SaaS pattern)
| Role | Who |
|---|---|
| Controller | Customer organisation (NGO / ministry / firm) deciding purposes of processing |
| Processor | Altamont Digital operating IMP on the customer’s behalf |
| Sub-processors | Infrastructure and auth providers (hosting, database, Clerk) — list maintained for enterprise contracts |
2. Categories of personal data (examples)
| Category | Examples in IMP | Notes |
|---|---|---|
| Account users | Name, email, role | Staff of the customer |
| People / beneficiaries | Names, contact, demographics as entered | Customer-defined |
| Consent records | Purpose, status, timestamps | Not auto-granted by AI |
| Programme / MERL | Indicators, results, learning notes | May be non-personal |
| Evaluation evidence | Interview notes, survey imports, Kobo pulls | May include quotes |
| IRB working dossier | Investigator names, letter links | Drafts; not a filing |
| Finance | Claimants, vendors, amounts | Staff / supplier data |
| Integration secrets | Encrypted Kobo token | Processor stores to pull on instruction |
Customers control what is uploaded. IMP provides structure and access control.
3. Purposes of processing
- Provide multi-tenant workspace features (delivery, MERL, evaluation, EMS)
- Authentication and security
- Optional AI drafting where configured
- Optional Kobo pull on the customer’s instruction
- Support and product improvement under contract
4. Lawful basis (customer responsibility)
Customers determine lawful basis for beneficiary and research data (consent, legitimate interest, public task, etc.). IMP records consent when customers enter it.
5. International transfers
Production is typically cloud-hosted. Transfer mechanisms (SCCs / UK IDTA / etc.) are set in the signed DPA for the customer’s jurisdiction.
6. Retention and deletion
- Active data retained while the organisation subscription is active
- On contract end: export assistance + deletion per DPA schedule
- Audit logs may be retained longer for security
- Kobo tokens deleted with the connection or at contract end
7. Data subject rights
Customers handle rights requests for their data subjects; Altamont assists as processor under the DPA (access, correction, deletion, export).
8. Security measures (high level)
See Security & trust overview — multi-tenant isolation, HTTPS, role-based access, encrypted integration secrets, audit of Accept / import / pull.
9. Sub-processors (indicative)
| Function | Typical provider class |
|---|---|
| App hosting | Vercel or equivalent |
| Database | Managed PostgreSQL |
| Auth | Clerk |
| Object storage | Supabase or equivalent (where used) |
| AI inference (optional) | xAI / configured LLM provider when keys present |
Enterprise customers receive an up-to-date sub-processor list on request.
10. Next step for procurement
- Download this summary + Security overview (HTML or markdown)
- Request the full DPA template from Altamont Digital
- Align with your privacy officer before pilot go-live
Document version: 2026-08 · Counsel finalises the binding DPA