Data Processing Register

How to read this register

Each activity states a purpose, the categories of data it uses, who the data concerns, who receives it, and the basis Warsha proposes for it.

A basis marked "pending legal review" means Warsha has recorded the basis it proposes and has not obtained confirmation. As at this version, every basis is pending. Warsha states that rather than asserting a settled position it does not hold.

The machine-readable register in the platform is the authoritative inventory; this document is its published form, and the regression suite asserts the two agree.

Account and authentication

Purpose: create and secure an account, sign a person in, and recover access.

Data: name, phone number, optional email, authentication state.

Subjects: customers, workers, staff. Recipients: Supabase. Basis: performance of the agreement (pending review).

Worker verification

Purpose: establish who a worker is before they enter a customer's home.

Data: National ID images, identity fields, criminal-record certificate, reviewer assessments.

Subjects: workers. Recipients: Supabase; verification staff holding the specific capability. Basis: substantial public interest in safety, and performance of the agreement (both pending review).

Retention: original document at least one year from upload. Offence detail confined to a private reviewer record, never exported, never returned to a client.

Bookings and job execution

Purpose: arrange, perform, track and complete work.

Data: booking details, scheduling, addresses and confirmed pins, job records and photographs.

Subjects: customers and workers. Basis: performance of the agreement (pending review).

Messaging

Purpose: let the two sides of a booking communicate, and provide evidence for a dispute.

Data: message content and metadata within a booking.

Basis: performance of the agreement, and legitimate interest in dispute resolution (pending review). Messages are not read routinely; access for a report or dispute is logged.

Payments and earnings

Purpose: collect payment, calculate commission, record earnings, make payouts, process refunds.

Data: amounts, methods, ledger entries, payout records. No full card number.

Basis: performance of the agreement, and legal obligation for financial records (pending review).

Trust, safety and moderation

Purpose: prevent and respond to harm, fraud and abuse.

Data: reports, moderation records, trust state, enforcement decisions and their evidence.

Basis: legitimate interest in user safety, and legal obligation where reporting is required (pending review).

Reviews and reputation

Purpose: let customers see how a worker has performed.

Data: ratings, review text, replies, aggregate scores.

Recipients: other users, for the public parts. Basis: performance of the agreement (pending review).

Support

Purpose: answer questions and resolve problems.

Data: support conversations, case records, and the account context an agent needs.

Basis: performance of the agreement (pending review). An agent sees the case, not identity documents.

Notifications

Purpose: tell someone something they need to know about their account or a booking.

Data: event type, target account, delivery state. Payloads carry a state and nothing more — no identity number, no filename, no offence text, no address, no staff note.

Basis: performance of the agreement for service messages; consent for optional messages (pending review).

Consent and agreements

Purpose: record which version of which document a person accepted, in which language, and when.

Data: account, document key, version, decision, timestamp, language, acceptance hash, source surface, role.

Basis: legal obligation to demonstrate consent, and performance of the agreement (pending review). Records are append-only and are never rewritten.

Diagnostics

Purpose: find and fix faults.

Data: application version, platform, crash traces. No message content, no addresses, no identity data.

Basis: consent. Off unless turned on, and withdrawable at any time.