# DIREKT Research Ethics and Consent Protocol

## 1. Scope

This protocol governs Phase 1A interviews, observation, concept testing, document walkthroughs and field-verification research. It is an operational research safeguard, not a substitute for legal advice or formal institutional ethics approval where required.

## 2. Core principles

- participation is voluntary;
- refusal has no penalty;
- consent is specific and can be withdrawn;
- collect the minimum information needed;
- separate research identity from product identity;
- do not collect real verification evidence into the public repository;
- do not promise employment, provider approval, customer protection or future platform access;
- explain that DIREKT is at research stage and is not yet providing verified services;
- avoid questions that unnecessarily expose trauma, fraud losses, immigration status, exact home address or financial details;
- stop an interview when participation creates discomfort or risk.

## 3. Participant eligibility

Phase 1A participants must be adults able to provide informed consent. Research involving minors is prohibited unless a separate, owner-approved and legally reviewed protocol is created.

Potential segments:

- customers who have hired local service providers;
- independent providers and SMEs;
- institutional buyers or facility managers;
- field-verification candidates;
- representatives of training, registration, trade or regulatory bodies;
- accessibility participants.

Do not recruit people because they are currently in an emergency, active dispute or vulnerable financial situation.

## 4. Consent script

Researchers should communicate the following in plain language before recording notes:

> We are researching a possible Android service called DIREKT that may help people find local providers and understand which details have been checked. This is research, not a live service. Participation is voluntary. You may skip any question or stop at any time. We will use coded notes and will not publish your name, phone number, exact address, identity documents or certificate numbers. We may summarize anonymized findings to improve the product. Agreeing does not guarantee listing, verification, payment or future access.

Then ask separately for consent to:

1. participate in the interview;
2. allow written notes;
3. allow audio recording, if an approved private storage process exists;
4. allow observation of their device or provider-discovery process;
5. privately view example documents without copying identifiers;
6. receive a later prototype-test invitation.

Consent to one activity does not imply consent to another.

## 5. Prohibited public-repository data

Never commit:

- names, phone numbers, email addresses or national identifiers;
- exact private home or business coordinates;
- photographs of real identity documents, certificates or premises;
- licence, registration or certificate numbers that identify a participant;
- audio or video recordings;
- signatures or consent forms;
- bank, mobile-money or transaction data;
- unredacted complaint details;
- names of alleged scammers or unproven misconduct claims;
- information that could re-identify a participant through a unique combination of attributes.

## 6. Participant coding

Use coded IDs:

- `CUS-<AREA>-###` — customer;
- `PRO-<AREA>-<CATEGORY>-###` — provider;
- `OPS-<AREA>-###` — operations/field participant;
- `INS-<AREA>-###` — institutional buyer;
- `AUT-<AUTHORITY>-###` — authority or issuing-body discussion.

The key linking codes to identities must be stored privately, access-controlled and outside GitHub. Destroy it when follow-up is no longer needed, subject to approved retention rules.

## 7. Recording and storage

Written notes are the default. Audio recording is optional and requires:

- explicit consent;
- approved encrypted storage;
- restricted access;
- a documented deletion date;
- no upload to consumer transcription services without privacy review;
- a redacted summary before research findings enter the repository.

Researchers must not store sensitive evidence in personal messaging chats longer than necessary. Transfer approved material to the controlled private store and delete local copies.

## 8. Compensation

Participant compensation, when used, must:

- compensate time or transport rather than purchase positive feedback;
- be explained before participation;
- be reasonable and consistent across similar participants;
- not depend on answering every question;
- not depend on agreeing with DIREKT;
- be recorded as an operational cost without publishing participant identity.

## 9. Document walkthroughs

Providers may describe or privately show documents. Researchers must record only:

- document category;
- apparent issuing body;
- whether an expiry date exists;
- whether the holder knows how to replace or renew it;
- whether an online or issuer confirmation route appears to exist;
- verification difficulties;
- participant concerns.

Do not photograph, scan or copy identifying fields during Phase 1A unless a separate private evidence protocol has been approved.

## 10. Location observation

When testing pins, directions or premises evidence:

- obtain explicit consent;
- avoid publishing exact coordinates;
- record only coarse area, direction method and accuracy findings;
- distinguish public service area from private operational evidence;
- do not reveal a home-based provider’s private residence to customers or public testers;
- do not conduct visits where researcher or participant safety is uncertain.

## 11. Fraud and complaint disclosures

Participants may disclose scams or misconduct. Researchers must:

- avoid investigating or adjudicating the allegation;
- record the pattern rather than unnecessary identifying detail;
- state that DIREKT is not currently a complaint-resolution service;
- avoid promising recovery or enforcement;
- escalate immediate safety concerns through an approved local process;
- avoid public accusations or naming alleged offenders.

## 12. Accessibility and language

- use the participant’s preferred accessible format where feasible;
- explain technical terms such as verification, service area and evidence;
- allow extra time;
- avoid equating limited literacy or digital confidence with lack of competence;
- record terminology participants naturally use;
- do not force English when a competent local-language researcher is available.

## 13. Researcher safety

Fieldwork must use:

- scheduled visits;
- check-in/check-out procedure;
- daytime visits where possible;
- no handling of cash or original documents;
- no entry into unsafe premises;
- two-person visits for higher-risk contexts;
- an escalation contact;
- immediate stop authority for every researcher.

## 14. Consent withdrawal and deletion

A participant may request withdrawal using their research code or private contact route. The research lead must:

1. locate private source material;
2. remove it where feasible;
3. assess whether anonymized aggregate findings can still identify them;
4. update the research log without exposing the identity;
5. document any legal or technical limitation.

## 15. Publication review

Before committing a research summary:

- remove identifiers;
- generalize locations where needed;
- inspect quotations for re-identification risk;
- label evidence type and sample size;
- separate observation from interpretation;
- state contradictions and limitations;
- confirm no confidential authority discussion is disclosed;
- run the repository secret and documentation checks.

## 16. Approval requirement

No production collection of identity documents, certificates, private coordinates or background-check data may begin until privacy, retention, access-control and legal requirements are approved in later phases.