1. Product and WESSAAL relationship
RAKZ is an independent Smart Attendance product identity operated by WESSAAL. Purchase, subscription, billing, and entitlement management happen through WESSAAL unless an approved customer agreement says otherwise.
2. Access and accounts
Access to RAKZ is linked to the organization, workspace, and permissions managed by authorized administrators. Users must not share passwords or verification codes, use another person's account, or bypass assigned permissions.
Employee access is generally tied to the user's relationship with an organization and its administration rather than open consumer self-registration.
3. Current RAKZ scope
- Android employee app for check-in/check-out and enabled attendance-related functions.
- Workplace location and Wi-Fi verification during attendance actions according to organization settings.
- Management web experience for attendance states, employees, requests, reports, and operating setup.
- Automation and operational notifications where enabled; WhatsApp is the currently supported operational notification channel.
4. Organization configuration and policy
The organization defines workplaces, networks, schedules, policies, permissions, and operating rules applicable to its users. RAKZ does not replace the organization's HR policies or legal obligations, and customers are responsible for configuring the product consistently with their operations and applicable requirements.
5. Location and network use
Location and network permissions must be used for the product purposes disclosed to users. RAKZ must not be used to create continuous monitoring outside published functionality or to bypass privacy, employment, or access controls.
6. Acceptable use
- Do not bypass location, network, device, or permission verification.
- Do not submit misleading information or impersonate another user.
- Do not probe, attack, disrupt, or access another organization's data without authorization.
- Do not use the service in violation of law, individual rights, or approved organization policy.
7. Availability and changes
We aim to provide the service reliably, but some functions may depend on network connectivity, device permissions, third-party services, or maintenance. We may update RAKZ to improve security, performance, and usability while respecting applicable contracts and commitments.
8. Third-party channels
Some functions may depend on third-party services such as payment providers or WhatsApp when notifications are enabled. Those services are also subject to provider terms and policies and may be affected by provider availability or operating limits.
9. Privacy and security
Data processing is subject to the RAKZ Privacy Policy, related WESSAAL policies, and applicable customer agreements. Users are responsible for protecting devices and credentials and reporting suspected unauthorized access.
10. Suspension and termination
User access may be restricted or removed when the user's relationship with the organization ends, permissions change, or a legitimate security or contractual reason applies. Organization subscription changes and cancellation follow the WESSAAL customer agreement and subscription state.
11. Support and contact
For RAKZ support, use WESSAAL Support at support.wessaal.com. For direct correspondence or privacy requests, use info@wessaal.com. Do not send passwords, OTP codes, or sensitive payment information in support requests.
A RAKZ-related question?
Use the official support portal for support requests and the official email for privacy or requests that require direct correspondence. Do not send passwords, verification codes, or sensitive payment data.