NORTH · LEGAL · DATA PROCESSING ADDENDUM
Data Processing Addendum — Technical Exhibits
The technical detail behind the DPA. What we process, where it goes, how it's protected, and how data subject rights are supported. The core promise: no LLM reads your documents, and document bytes are not kept: never for instrument uploads, at most 24 hours for platform documents.
UseNorth is a product of Lodecrest (Pty) Ltd (registration number 2026/557367/07, South Africa). In this addendum, "NORTH" means Lodecrest (Pty) Ltd (registration number 2026/557367/07), acting as operator (processor) for the client.
Exhibit A — Categories of Data Processed
- Document content: no LLM or other AI model ever receives it. Instrument uploads are processed in memory during the request and never stored. Documents uploaded to a platform initiative are stored for at most 24 hours so the deterministic read can complete (sealed with HMAC-SHA-256, encrypted at rest by our database sub-processor, Supabase), then deleted; a one-click wipe deletes them sooner. After that only the SHA-256 hash and extracted metadata persist.
- Instrument run metadata: run ID, creation timestamp, expiry timestamp, document hash, read results. Stored in the platform database. Auto-deleted after TTL (24h default).
- Receipt data: notary chain entries (sequence number, hashes, timestamps). Stored permanently in the append-only ledger. Contains no document content.
- Evidence items: control IDs, verdict types (confirmed/overridden/gap), answer summaries, document reference hashes. Stored in the initiative graph. No document content.
- User account data: email address, hashed password (if password auth), authentication tokens. Stored in the authentication database.
- Email delivery data: recipient address, delivery status. Transmitted to Resend for delivery. See Sub-processor Register.
Exhibit B — Sub-processor Register
- See /residency for the complete, machine-readable sub-processor register.
- Vercel Inc. — application hosting (US East primary)
- Supabase Pte Ltd — database and authentication (Singapore, configurable)
- Upstash Inc. — rate limiting (global edge)
- Resend Inc. — email delivery (US East)
Exhibit C — Security Measures
- Transport encryption: TLS 1.2+ on all connections (enforced by Vercel edge)
- At-rest encryption: Supabase managed encryption (AES-256)
- Access control: Row-Level Security (RLS) on all tables; service-role access only from NORTH servers
- Rate limiting: per-IP and global rate limits on all public endpoints (fail-closed in production)
- Prompt-injection defence: uploaded documents are quarantined-scanned before any parsing; injection indicators are refused, hashed, and receipted without being read
- No LLM inference: document content is never sent to any language model; the read is deterministic (rules only)
- Tamper-evidence: the value-event ledger is hash-chained from genesis; any modification breaks the chain and is detectable at the public verify desk
- Key custody: notary operator keys are Ed25519, held in environment variables (deployment secret store), never in code
Exhibit D — Data Subject Rights Support
- Right to access: the client can export all evidence items and receipt data via the API
- Right to rectification: evidence items can be superseded (new items appended; original preserved in the ledger)
- Right to erasure: instrument run records auto-delete per TTL; account deletion removes authentication data. Notary chain entries cannot be deleted (they contain no personal data — only hashes and timestamps)
- Right to data portability: all evidence and receipt data is exportable as JSON
- Right to object: the client can stop processing at any time by discontinuing use
Exhibit E — Breach Notification
- NORTH will notify the client within 72 hours of becoming aware of a personal data breach affecting the client's data.
- Notification will include: the nature of the breach, categories and approximate number of data subjects affected, likely consequences, and measures taken.
- Document content exposure is limited by design: instrument uploads are never stored, and platform documents exist at rest for at most 24 hours, sealed and encrypted, before they are deleted.
This is a template for legal review. It is not legal advice. Consult your counsel before use.