QadarimBack to Qadarim home

Privacy and Evidence-Handling Notice

PRIVACY AND EVIDENCE-HANDLING NOTICE

Purpose

Qadarim requests only the evidence needed to reconstruct and assess the one workflow named in the SOW, support the five diagnostic outputs, administer the engagement, and preserve required transaction records.

Evidence Qadarim may request

  • public booking pages, service menus, policies, FAQs, and public booking journeys;
  • relevant workflow or SOP documents for the selected workflow;
  • configuration screenshots limited to the selected workflow;
  • redacted examples of communications, exceptions, or handoffs; and
  • clarification through screen sharing without transferring system access.

Information that must not be supplied

Do not provide passwords, authentication codes, API keys, credentials, production-system/database/codebase/admin/payment-account access, payment-card or bank-account data, protected health information, identifiable customer information, customer lists, sensitive personal data, or information unrelated to the selected workflow.

Redaction responsibility

Before submission, the client must remove customer names and other identifying details from examples and screenshots. Qadarim must not ask the client to weaken this redaction requirement to make analysis easier.

Access and storage

Access is restricted to the person performing the diagnostic. Evidence must be stored only in access-controlled Qadarim systems.

A separate client subfolder and retention record must be created for each paid diagnostic before evidence is accepted. External sharing, if later required for a real engagement, must be limited to the minimum necessary party and must be separately authorized and verified.

Confidentiality and reuse

Non-public evidence is used only for the selected diagnostic and its administration. It may not be reused for marketing, model training, another client, or another workflow without explicit written permission.

Retention

Client diagnostic evidence: delete 90 calendar days after final delivery, or earlier upon a valid contractual request, unless a legal obligation requires longer retention.

Contracts, invoices, payment records, and legally required records: retain for the applicable legal period.

Opt-out suppression data: retain only the minimum form needed to prevent re-contact.

The retention register must record category, deletion due date, and deletion completion.

Early deletion request

  1. Record the request date, requester, engagement ID, and evidence categories.
  2. Confirm whether any requested item is diagnostic evidence or a record that must be retained under an applicable legal or contractual obligation.
  3. Delete eligible diagnostic evidence from the controlled storage location as soon as practicable.
  4. Record deletion completion and any item retained, with the reason.
  5. Confirm completion to the requester through the verified business contact route.

Accidental prohibited-data receipt

If prohibited data is received unintentionally:

1) stop processing it;

2) isolate it from diagnostic analysis;

3) notify the sender that the material is outside the permitted boundary;

4) delete it securely as soon as practicable; and

5) record the incident and deletion action.

Do not copy prohibited data into the tracker, notes, screenshots, email, or AI prompts.

Privacy/security concern route

Business contact: ronatal@qadarim.com.

This route must pass current send/receive verification before SPA v0.2 outreach is released.

RETENTION / DELETION LOG TEMPLATE

Engagement ID
[ID]
Evidence category
[CATEGORY]
Storage location
[CONTROLLED LOCATION]
Final delivery date
[DATE]
Deletion due date
[DATE = 90 calendar days after final delivery unless earlier valid request]
Early deletion requested
[YES/NO]
Request date
[DATE]
Legal/contractual hold required
[YES/NO/NOT DETERMINED]
Deletion completed
[DATE/TIME]
Verified by
[NAME]
Notes
[NOTES]