Data transparency

Data Safety & Use

This page explains product behavior to users and does not replace the Data Safety form in Google Play Console. Final store answers must match the exact application build, SDKs, and enabled services at publication time.

Last updated
September 3, 2026
Version
1.0
Operator
WESSAAL

Core data categories

  • Account and identity information linked to organization access and permissions.
  • Location during the attendance action when workplace-location verification is required.
  • Network information needed to verify workplace Wi-Fi context.
  • Attendance activity such as check-in/check-out time, state, and attendance-related requests.
  • Device, diagnostic, and security information needed to operate, protect, and troubleshoot the service.

Purposes

  • Core app functionality.
  • Attendance-context verification.
  • Security and abuse prevention.
  • Support and troubleshooting.
  • Reporting and management operations under organization permissions.

Sharing

We do not sell user data. Necessary data may be shared with hosting, infrastructure, support, communications, or operational-channel providers such as WhatsApp when enabled, to the extent needed to deliver the function.

Background location

The published RAKZ product scope does not rely on continuous background location tracking. Location verification is tied to the attendance action and configured workplace context.

Deletion and retention

Deletion or deactivation requests are handled according to organization role and applicable obligations. See Account & Data Deletion for the request path.

Contact

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.

Related pages

TermsSupportAccount & data deletionSecurity