Explanation
Privacy and trust
What Yaqeen stores, which privacy requests staff can log, and how anyone can check the controls that run today.
This page explains how Yaqeen handles personal data, how a privacy request is processed, and where you can check our claims. Yaqeen holds no certification, and a lawyer has not reviewed these pages. Legal deadlines and retention periods are for your counsel to set.
What is stored#
Identifiers such as national ID, phone, email and bank account arrive already hashed with your key. The new-store intake refuses a raw value with not_hashed. The payout feed does not check the format, so send hashes only. Yaqeen is built to hold hashes, not raw values.
Appeal documents sit in private storage. A document opens only through a link that expires in 5 minutes, and every opening is written to the audit log.
Privacy requests#
A reviewer or admin logs an access or erasure request for a merchant owner with POST /api/v1/privacy/requests/. The request gets a due date. The default is 30 days. If your counsel needs a different period, ask your Yaqeen contact to change it.
- Access. Closing the request returns a copy of the owner's data once.
- Erasure. Closing the request removes what identifies the owner: names, contact and address fields, identifier hashes (replaced by random tokens), accounts and sign-in links, push tokens, assistant chats, statements, messages and appeal files. Ids, money rows, decisions, reviewer notes and the audit log stay, because they are kept for other reasons and the books must still add up. See Data we store.
- Refusal. Erasure is blocked while a legal hold, an open hold or an open appeal exists. Closing the request then answers
409 blockedwith the reasons. The reviewer can close it as refused by sending arefuse_note.
A reviewer or admin can place a legal hold, and only an admin can end one. API keys can never reach privacy endpoints.
Exports#
GET /api/v1/cases/{id}/export/ returns the whole case file with a SHA-256 hash of its content. Add ?as=html to print it to PDF from a browser. GET /api/v1/audit/export/?from=&to= returns audit lines for a range of up to 92 days, with their hashes, and says whether the chain verifies. Both exports are themselves audited.
Google sign-in and personal data#
A person who signs in with Google gives us their Google account id and email address. We keep both so an admin can see who asked for access. The email is also their username. Nothing else from the Google profile is read or stored. Google learns that the person opened the sign-in page and used its button. The button loads only on the sign-in page, never on the public site.
Sign-up and personal data#
A person who signs up with a username and password gives us an email address. We keep it so an admin can decide. The email is not confirmed, so an admin reads it as a claim. It is not written to the audit log, because the log can never be erased.
Claude and Codex#
Staff can connect Claude or Codex over MCP. What the client looks up goes to its provider, so an admin can turn on redaction or switch it off for the organization. See AI and your data.
Public pages#
The Yaqeen site has a privacy notice, terms, a cookie page that lists every cookie and storage key, a trust page and a sub-processor list. They are in English and Arabic. Sign-up asks you to accept the current version of the privacy notice and terms, and Yaqeen records which version (GET /api/v1/privacy/policy/ returns it). Nothing in this stack sets a cookie for analytics or advertising, so there is no consent choice. A short cookie note says this once and can be closed. See Data we store, AI and your data, Sub-processors and Retention.
Ask about your own data#
A merchant owner can ask for a copy of their data or for erasure from their own account with POST /api/v1/privacy/me/requests/ and a kind of access or erasure. The request lands in the same list as the ones staff log, with the same due date, and a reviewer or admin answers it. Only one request of each kind can be open at a time.
Check us#
Three endpoints need no sign-in:
GET /api/v1/trust/status/shows current status and uptime. Uptime is the share of health readings, taken every 5 minutes, in which nothing needed attention.GET /api/v1/trust/controls/lists the controls that run today and where to check each one.GET /api/v1/trust/incidents/lists past incidents.
The controls list says plainly that no certification is held. See Security for the controls in more detail.
Related#
- Security: the controls in place
- How the audit chain works: what the log proves
- Export and verify audit: the steps