About
Why this exists
A signing platform built Arabic-first, where the evidence behind a signature is the product rather than a feature of it.
The problem we started from
Most signing tools treat Arabic as a translation job — the interface flips, the PDF does not, and the certificate that is supposed to prove what happened comes out in a language the counterparty cannot read.
We started from the other end: right-to-left in the interface, in the emails, and in the sealed document itself, with the sender choosing which language the certificate is written in because that is a property of the agreement rather than of whoever happens to be logged in.
Evidence over ceremony
A signature is only worth anything if you can defend it later. Every action on a document — opened, verified, signed, declined — is written to an append-only log with a timestamp, an IP address and a browser, and reproduced on the certificate attached to the finished file.
The sealed PDF is hashed, and anyone can check a copy against that hash without an account and without having been party to the agreement.
What we will not do
We do not read your documents, we do not sell your data, and we do not use what you upload to train anything.
We also do not claim more than we can support. Our compliance page says plainly which standards our signatures meet and which they do not, including the ones we would rather be able to claim.