YaqeenDocs
Back to Yaqeen

Explanation

Data we store

Every kind of personal data Yaqeen stores, where, in what form, why, and what an erasure request removes.

This page lists the kinds of personal data Yaqeen stores, in what form, and what an erasure request removes. The full record of processing, with field names, is available to customers on request.

Two roles#

For orders, payouts, buyers and merchant details that a customer loads, Yaqeen is a processor. The customer, as controller, decides why the data is used. For staff accounts and site visitors, Yaqeen is the controller.

What is stored#

GroupExamplesForm
Merchant ownersName in Arabic and English, nationality, gender, languagePlain
Owner and store identifiersNational ID, phone, email, bank account, commercial registrationKeyed hash
StoresName, address, website, social handlesPlain
BuyersHashed phone, email and address. District, city and postcode. Device id, card brand, last four digits, order textKeyed hashes, and plain for the coarse place and the rest. No name, phone number, email address or street address is stored, and no full card number.
IP addressesThe addressKeyed hash, plus country, city and region in plain
AppealsStatement, files, messagesPlain text, files in a private store
Staff accountsUsername, email, name, role, passwordPassword stored as a hash
AssistantMessages and replies, and the confirm cards it prepared (a card can name a store)Plain
Claude and Codex sign-insApp name and redirect addresses, the person, hashes of codes and tokens, timesKeyed hash for secrets, plain for the rest. See Retention.
Audit logActor id, action, subject idIds only, never changed

A keyed hash is pseudonymised, not anonymous. See Privacy and trust.

What an erasure request removes#

Closing an erasure request replaces the owner's and stores' names, contact fields and address fields, and replaces every identifier hash with a random token, so the rows can no longer be linked to a person. It ends the owner's accounts and their Google links, deletes their push tokens and assistant chats, deletes every assistant confirm card they made or that is about their holds or appeals, blanks appeal statements, dispute statements, messages and notifications, and removes appeal files from the private store. If the store cannot be reached, nothing is erased and the request stays open to run again.

What stays#

  • Ids, amounts, dates and statuses, so totals still add up.
  • Reviewer notes and decision notes, as the record of why a hold was decided.
  • The audit log, which holds ids and action names and is append-only.
  • Copies in backups until they expire.

Erasure is blocked while a legal hold, an open hold, an open appeal or an open dispute exists. The request then answers 409 blocked with the reasons, and a reviewer can close it as refused with a note.

Up Down to moveEnter to openEsc to close