The questions a club should ask before trusting software.

Tenant isolation

One club cannot see another club's data

Every record belongs to exactly one club, enforced at the database level rather than by application code remembering to filter. The serving process runs with a database role that has no ability to bypass those rules, and a test suite authenticates as one club and actively attempts to read and write another club's records across every table, on every build.

A request for a record belonging to another club answers as not found rather than forbidden, so the existence of other clubs is not disclosed.

Personal data

Riders, guardians and minors

Riding clubs hold data about children, their guardians and sometimes their medical notes. That is the most sensitive category on the system and it is treated that way. Medical notes are encrypted under a key held outside the database, never appear in list responses, and every read of them is written to the audit log.

Data subject export and erasure are first class, audited operations rather than manual database surgery, which is what the UAE Personal Data Protection Law expects and what a club will need when a parent asks.

Audit log

Append only, by database privilege rather than by convention. There is no code path that edits or deletes history.

Encryption

In transit everywhere. At rest for the database, plus column level encryption on medical notes under a separate key.

Access

Every action requires a role that permits it, checked on the server. The client's opinion about who you are is never trusted.

Payments

Money never passes through Hesani

Rider payments run through a licensed payment provider, with your club as the merchant. Funds settle to the club directly. Hesani never holds, pools or controls rider money, and there is no account, wallet or balance anywhere in the system that could.

That is an architectural property, not a policy promise. There is no entity in the database and no code path capable of receiving club funds, and automated tests enforce that on every build so it cannot quietly change later.

Card data

Never on our servers

Card details go from the rider's browser directly to the payment provider and never touch Hesani's systems. What we store is a reference, so there is no card data here to lose.