These are practices we agree with each client and write into the agreement. They are not badges. What applies to your deployment is in your proposal, and nothing on this page replaces the terms you sign.
Eight practices, each with the part that is written down for you.
Hosting can be in Saudi Arabia, on your own servers, or in a global cloud region. We raise it at the scoping session, before any screen is designed.
Written into your agreement The hosting location, and the location of backup copies.
Each product runs as its own deployment for your company, with your users and your data, not as an account inside a shared system.
Written into your agreement What is deployed for you and where it runs.
Each user sees only what their role allows. Approval limits follow your delegation structure, and administrators are named.
Written into your agreement Roles, who holds administrator rights, and approval limits.
Changes and approvals are logged with the person and the time. For approvals that is the approver's name and when they decided.
Written into your agreement What is logged and who may read the log.
How often copies are taken, how long they are kept and where they are stored are set per deployment. A restore is tested rather than assumed.
Written into your agreement Frequency, retention, storage location and how restores are tested.
Access is limited to the people working on your project or its support, and the purpose is agreed with you. When their involvement ends, so does their access.
Written into your agreement Who has access, for what purpose, and how it is removed.
You can take your data out in readable formats. What is retained, for how long, and when it is deleted is agreed in advance, not left to be asked.
Written into your agreement Export format, retention and deletion.
Updates are scheduled with you, and the agreement sets support levels, response times and update schedules. On your own servers, you control the accounts you give us.
Written into your agreement Support levels, response times and update schedule.
The right one depends on your data, your sector and your contracts. We build to your decision.
Read the guide: hosting in the Kingdom or on your own servers
Runs in a data centre inside the Kingdom. We operate it with you, or a managed provider does.
On your premises or in rented space. You operate the servers; we deploy, update and support under the access you give us.
Runs in a public-cloud region outside the Kingdom. Transfer rules for personal data are checked first.
Write to support@muznit.com. A person reads every report and replies to the sender.
Please give us a reasonable chance to look into it before sharing details publicly, and do not access other people's data to prove a point.
This page describes how we work. It does not promise a particular level of availability and it is not the result of an independent audit. Specific commitments exist only in your signed agreement.
You choose: hosting in Saudi Arabia, your own servers, or a global cloud region. The location, and where backup copies are kept, are written into your agreement.
Your data is used to run your deployment and to support it. It is not used for MUZN IT's marketing and it is not shared with third parties for their own purposes.
Web access to deployments we host is over HTTPS. Further requirements, such as how backups are protected, are agreed per project.
You operate the servers and control access to them. We deploy, update and support the software under the access you grant. The split is written in the agreement.
If your policy requires an independent review, tell us at scoping so it is planned and written into the project.
Bring your hosting, access and retention requirements to the scoping session. They are written into your proposal.