Privacy Policy

Draft — last updated 6 July 2026. This draft has not yet been reviewed by legal counsel.

What we collect

Account data (email, authentication records), the organizational and waqf data you enter (assets, leases, cases, beneficiaries, donations, accounting entries), uploaded documents, and standard technical logs.

How it is used

Solely to operate the platform: authentication, record keeping, verification, and the transparency features you choose to enable. We do not sell personal data.

Public vs. private data

Records belonging to a waqf marked publicare visible to anyone via the explorer and public APIs — but only as proofs (event types, hashes, timestamps). Record contents, beneficiary personal data, and documents remain restricted to your organization's members. Donor names on donations are visible to your organization; donors may give anonymously.

Append-only records

Chained protocol records are immutable by design, and their hashes may be anchored to external timestamping networks. Personal data should not be placed in chained record payloads; where it is, erasure of the payload may be legally and technically constrained. Ordinary (non-chained) data can be corrected or deleted on request.

Storage and processors

Data is stored with Supabase (hosted PostgreSQL and object storage). Document downloads use short-lived signed URLs. Hash digests — never document contents — are transmitted to OpenTimestamps calendar servers when anchoring is used.

Your rights

You may request access to, correction of, or deletion of your personal data (subject to the append-only constraints above) by contacting the operator of this deployment.