Everything covering how Trazer is provided, how data is handled, and what each side is committing to. Written against how the platform actually works rather than adapted from a template.
The agreement covering your use of Trazer.
The contract itself. Without it you have no agreed limitation of liability, no payment terms, and no stated basis for suspending an account.
Read thisWhat personal data we handle, why, and what rights people have.
Legally required. The UAE Personal Data Protection Law applies, and any customer with EU or UK contacts brings GDPR into scope too. This is also the first document an enterprise buyer's legal team asks for.
Read thisEvery third party that touches customer data, and why.
Enterprise and government buyers ask for this before signing, and data protection law expects transparency about it. Publishing it removes a recurring blocker from your sales cycle.
Read thisWhat the platform may not be used for.
This is what lets you suspend an abusive account without breaching your own contract. It also protects your sending domain reputation, which matters because the product sends email.
Read thisWhat we store in your browser and why.
Required wherever you set non-essential cookies. Keeping the site to strictly necessary storage is the cheapest path to compliance, and it is worth staying that way deliberately.
Read thisThe processor terms customers sign alongside the main agreement.
Any customer with a compliance function will require this before go-live. Having it ready shortens enterprise deals considerably.
Read thisUptime, support response times and service credits.
Larger customers ask for one before signing. The targets below are deliberately conservative, because a commitment you miss costs more than one you never made.
Read this