This page explains how Sahl keeps and protects your company's data. It is written for both the IT manager and the HR director. It describes what we do today in plain words, and it states only what we commit to.
Sahl is a cloud HR service provided by [the company's legal name]. The customer company is the controller of its employees' data under the Personal Data Protection Law, and Sahl is a processor that handles this data on the customer's behalf and on its instructions. This relationship is set out in the data processing agreement.
1. Where the data is kept
Customer data is kept in Saudi Arabia. The service is hosted on Frappe Cloud, operated by Frappe Technologies, on servers in Jeddah, in Oracle Cloud's Jeddah region. We commit to keeping customer data in Saudi Arabia.
Some supporting services may receive a limited part of the data to do one task, such as delivering phone notifications. All of them are listed with their locations in section 10.
2. A separate site and database for each company
Each company gets its own site and its own database, on a subdomain with its name under Sahl's domain. No two companies share a database, and no customer's data passes into another customer's database.
3. Encryption, passwords and secrets
- Data travels between the browser or the app and the server over an encrypted connection (HTTPS with TLS) on every page.
- Passwords are stored hashed and cannot be read. No one can learn a password from the system, Sahl's staff included.
- Secret keys the company adds for its own services, such as an AI key, a text message account or an accounting system, are stored encrypted and are never shown again after they are saved.
- Sahl does not see card details when the subscription is paid. The card is entered in Moyasar's own form, and Sahl keeps only Moyasar's token and the card's last four digits.
4. Backups
- The hosting platform takes an automated backup of each customer's site every day.
- Backups are kept off the main server, and they also stay in Saudi Arabia.
- A backup is taken before every update to the service.
- Old backups are removed automatically on the hosting platform's schedule.
5. Who at Sahl can reach your site
Sahl's staff open a customer's site in two cases only:
- To give support the customer asks for.
- To keep the service running and secure.
Sahl's staff who can reach the data are bound by confidentiality. Sahl processes customer data only to provide the service to that customer.
6. Access control inside your company
The customer decides who sees what on its site:
- HR staff: each member has a role, which is HR manager, HR specialist or payroll specialist. Each section of the system has three levels: no access, view or manage. A member's access can be limited to certain branches or departments.
- Managers: see their team and approve their team's requests.
- Employees: see only their own data and requests.
The underlying Frappe screens that Sahl is built on are closed to everyone except the built-in Administrator account. All other users work inside Sahl's interface only, under the permissions above.
7. Signing in
- An employee signs in with a one-time code sent by email. The code can also be sent by WhatsApp or text message if the company connects its own account with a message provider.
- Each phone that signs in to the Sahl app has its own key. The employee or HR can remove the key of any phone, and that phone then loses access to the account.
- The customer is responsible for keeping its users' accounts safe and for what its users do. We recommend removing access for people who leave and removing lost phones without delay.
8. History of requests and changes
- Every request keeps its full history: who sent it, who approved it, and when each step happened.
- Every change made through the AI is noted on the record of the person whose data changed.
9. Attendance and location
If the company turns location on, Sahl keeps the employee's location at the moment of check-in only, together with signals from the phone that help detect fake GPS. If the company does not turn it on, Sahl does not keep the employee's location.
10. Sub-processors
These are the parties that may receive part of the customer's data, what for, and where:
| Who | What for | Where |
|---|---|---|
| Frappe Technologies (Frappe Cloud) | Hosting, database, backups and outgoing email of the customer's site | Jeddah, Saudi Arabia |
| Oracle | The data centre that Frappe Cloud runs on | Jeddah, Saudi Arabia |
| Moyasar | Card payments for the subscription. Sahl never sees the card and keeps only Moyasar's token and the last four digits | Saudi Arabia |
| Google Firebase Cloud Messaging | Delivering phone notifications. Only the notification's title and short text are sent | Outside Saudi Arabia, on Google's network |
| Google Gemini | Only if the customer turns AI on with its own Google key: the text or picture the AI is asked to read | Google, under the customer's own contract with Google |
| Unifonic or Msegat | Only if the customer turns on text messages with its own account: the phone number and the sign-in code | Saudi Arabia |
| The customer's accounting system (Odoo, Qoyod, Daftra, Wafeq or Zoho Books) | Only if the customer connects it with its own key: payroll journal totals and payments | The customer's choice |
Sahl gives at least 30 days' notice by email before adding a sub-processor that receives customer data, and the customer may object.
11. Artificial intelligence
- AI is off by default. It works only if the company turns it on with its own Google key.
- Sahl does not provide a key of its own, and it sends no data to an AI service unless the company turns this on.
- When AI is on, only the text or picture the AI is asked to read is sent to Google Gemini, under the company's own contract with Google.
- Every change made through the AI is recorded, as described in section 8.
12. Data when the subscription ends
- The customer can export its data, including people, requests, payroll and reports to Excel, and documents, while its site is active or read only.
- After the subscription ends or is suspended, the data is kept for at least 90 days. After that, Sahl may delete it after notifying the customer by email.
- Backups are removed on the hosting platform's schedule.
The details are in the terms and conditions.
13. If a security incident happens
If Sahl becomes aware of a personal data breach affecting customer data, it tells the customer without undue delay and within 48 hours of becoming aware, with what is known at that time. This allows the customer to notify the Saudi Data and AI Authority (SDAIA) within the 72 hours set by the regulations, and to tell the people affected.
The obligations of both parties are set out in the data processing agreement.
14. Reporting a security issue
If you find a vulnerability or a security issue in Sahl, write to us at [the email address]. A useful report includes:
- A short description of the issue.
- The address of the page or the part concerned.
- The steps to reproduce it.
- A way to contact you.
Please do not access other people's data, do not disrupt the service, and do not publish the issue before we fix it. We review every report and contact the person who sent it.
15. Related documents
- Privacy policy: the data Sahl keeps about visitors to the website and about its customers.
- Data processing agreement: Sahl's obligations as the processor of your employees' data.
- Service level agreement: the availability target, support hours and response targets.
- Terms and conditions and acceptable use policy.
For any question about this page, contact us at [the email address] or [the phone number], or through the contact page.
This English text is a translation. The Arabic text prevails. العربية