1. About RANSSET EOP
RANSSET EOP is an enterprise operations platform owned by شركة رانست ذ.م.م (RANSSET LLC), unified number 7055361153, Eastern Province, Saudi Arabia. It supports organization-managed employee accounts, projects, attendance, reports, field work and fleet operations. This policy also covers people whose work records are entered by an organization without an individual login.
For privacy inquiries and personal-data or account-deletion requests, contact privacy@ransset.sa. For technical support, contact support@ransset.sa.
2. Responsibility for your information
Your employer or other customer organization determines the purposes for which its employee and operational records are used, the projects and attendance rules that apply, and which personnel may access them. RANSSET handles organization-controlled information to operate and support the service on the organization's instructions. The applicable agreement and the organization's employee notice explain their respective responsibilities.
RANSSET also handles information for its own direct support and privacy correspondence, platform account administration and service security. These purposes are distinct from the organization's use of workforce records. Responsibility depends on the processing activity; an administrator's technical access does not by itself determine the legal role.
3. Information we handle
Information depends on the functions used, the organization and the user's permissions:
- Identity and work information: names, employee and account identifiers, national ID or Iqama where required, date of birth, nationality, contact details, job title, department, project membership, supervisor, account status and permissions.
- Blood type: optional and used only for employee identification cards. You can leave it blank when completing onboarding or editing your personal profile.
- Authentication information: password or PIN hashes, verification and reset records, session information and security events.
- Attendance and field records: check-in/out times, attempts and outcomes, corrections, site and zone information, precise coordinates, accuracy and timestamps. Active fleet missions can also record speed, direction and links to the relevant device, vehicle and driver.
- Work content: reports, tasks, work orders, visits, faults, observations, approvals, signatures, photos, attachments, documents, file names, versions, sharing details and audit histories.
- Communications and support: messages, recipients, delivery results, preferences, descriptions and selected screenshots. Support submissions can include account/company/project context, page URL and query, visible errors, browser information, platform, language and screen dimensions.
- Device and security information: generated browser/device identifiers used to associate attendance attempts or missions, session and activity records, and relevant request information. Some sign-in paths use the network address supplied by a trusted proxy to limit attempts.
The currently operated product does not provide financial features or collect IBANs, salaries or allowances. User-supplied documents, reports or screenshots can nevertheless contain sensitive information. Submit only content necessary and authorized for the work.
4. Sources, purposes and choices
Information comes from you, your organization, authorized colleagues, device/browser functions used for a work activity, and activity within the service. It is used to manage accounts and access, prepare employee ID cards, record attendance, coordinate work and field missions, prepare and approve reports, manage work files, send operational communications, respond to requests and protect the service.
Required information depends on the function. Location-dependent attendance needs a valid position; station capture requires camera access and a photograph. Other fields and attachments may be omitted where the form allows. Refusing an essential permission can prevent that function from completing; contact your organization about an alternative work procedure. A device permission does not authorize unrelated uses of your information.
5. Precise location
Precise GPS is used for attendance check-in/out and field operations. Attendance and station capture obtain a position for the operation, verify the site or zone and record the result. Visit and maintenance actions may attach a position to a work event; those flows can proceed without coordinates when location is unavailable.
During an active fleet mission, the mission screen receives repeated location updates and attempts to transmit them periodically. Records may include coordinates, accuracy, speed, direction and time for mission operations and authorized review.
Employees are not continuously tracked outside attendance and field-operation activities. An active mission can involve repeated readings, rather than a single position. Leaving the active mission screen stops its browser location watcher, but does not itself end the mission recorded on the server. Connectivity and device/browser behavior, including hiding a page or locking the device, can affect updates.
You can change location permission in device/browser settings. Previously recorded positions remain subject to access and retention rules.
6. Attendance photos, camera and files
The attendance station shows the employee a camera preview and captures a still photo for the attendance event. Photos are stored for manual review by authorized personnel when necessary. Employees can see the live preview but do not have a personal gallery or history of stored attendance photos. They may still request access to their personal data.
There is no automatic facial identity recognition or matching. Local face-position guidance helps frame the photo inside the browser; it does not identify the person. Preview frames are not sent to a remote face-recognition service. The separately captured attendance photo is uploaded to the application. Camera capture has audio disabled, and the preview stops when the capture flow is cleared or left.
Other functions accept selected photos or files for profiles, signatures, work evidence, reports and support. Files may be resized or converted during upload. Selecting a file does not authorize scanning the entire photo library. Camera permissions can be managed in device/browser settings.
7. Cookies, browser storage and diagnostics
Session cookies support sign-in and the selected project, attendance, fleet or station context. Cookies and browser storage may also retain language, theme and interface preferences. Generated device identifiers associate attempts or missions with a browser/device; they are not proof of a person's identity.
Encrypted report-recovery copies may be stored in the browser separately from server-saved drafts. Clearing browser storage removes local preferences and recovery data, not server records. Downloads and exports must be managed separately by their holders.
The service records operational audits, delivery results and relevant errors. Search and filter inputs are sent to retrieve results and may appear in support-page context. Operational dashboards summarize work records. These are operational and security functions, not advertising tracking; hosting and request logs may also contain technical information.
9. Hosting and international transfers
Current hosting is provided by OVH outside Saudi Arabia. Your information is therefore not represented as residing exclusively in Saudi Arabia. A move to Saudi hosting is planned but has not been completed.
Email, maps, hosting, backups and support arrangements may involve processing in other countries, whose data-protection rules may differ. A planned hosting migration does not change current processing locations or mean that every provider or copy will move. Contact privacy@ransset.sa for information about locations and transfer arrangements relevant to your records.
10. Protection of information
The application uses organization/project access controls, password hashing, protected access to media, session controls and audit records. Local report-recovery copies are encrypted. These measures do not amount to a guarantee that every database, file, backup or communication is end-to-end encrypted, or that unauthorized access is impossible.
Access to stored attendance photos is restricted to authorized review; viewing a live camera preview is separate from access to stored evidence. Keep credentials private and avoid sending passwords or unnecessary identity documents in support or privacy emails.
11. Retention, contract end and deletion
Operational reports, attachments and work photos are kept during the customer's project. Attendance-evidence photos have a separate retention target.
- Attendance photos: the intended retention period is 30 days. Actual removal depends on the configured retention period, successful cleanup and any authorized evidence hold. Restricting access after expiry is different from physically deleting a file. Automatic deletion on day 30 is not guaranteed.
- Contract termination: customers receive 30 days after termination to export or transfer their data. Contact support to arrange the applicable access or transfer process.
- After the export period: customer-data deletion is not automatic. It requires explicit approval and execution by the RANSSET owner. Data remains stored until that process is completed, subject to applicable legal requirements. This internal approval step does not override applicable personal-data rights.
- Backups: the retention and rotation target is 30 days, subject to legal exceptions, actual operation and safe handling of shared multi-tenant backups. It is not an unconditional deletion deadline. Handling one customer's data must not damage another customer's backup; backup expiry and restoration require controlled handling.
- Local recovery and export files: report-recovery authorization expires after 24 hours, and expired browser entries are cleaned when recovery storage is accessed. Generated project-archive packages normally expire within seven days or earlier for included evidence. These periods do not erase source records or previously downloaded copies.
Deactivating an account, removing access, moving a record to trash or voiding it is not necessarily erasure. Audit metadata or historical references may remain, and connected business records can affect deletion. When handling a request, the retained information, reason and applicable retention period need to be considered and explained. No universal immediate-erasure deadline applies to every record.
12. Privacy and account-deletion requests
Send requests to privacy@ransset.sa. You may request information about processing, access or a copy, correction, deletion of personal data or an account, and withdrawal of consent where consent is the applicable basis, subject to applicable rights and lawful exceptions.
- State that the request concerns RANSSET EOP.
- Identify your organization/project where relevant and provide a contact or account identifier.
- Describe the information or account concerned and the action requested.
- Do not send a password or full identity document in the initial email. Further information may be requested to verify identity or authority proportionately.
Requests about organization-controlled records require coordination with the responsible organization. Applicable rights and permitted retention must be assessed; owner approval is not an unrestricted right to refuse a valid statutory request. Account suspension is not the same as deletion of the account and associated data.
You do not need a personal photo-history screen to request access. You may also contact your organization's responsible person. For escalation, contact the privacy mailbox or, where applicable, the competent authority. Saudi data-protection information is available through SDAIA.
13. Audience and operational decisions
RANSSET EOP is an enterprise work platform with organization-managed employee accounts, not a children's consumer service. Organizations may enter records about workers without login accounts and other people mentioned in work content.
Attendance and geofence calculations, workflow routing and summaries support operations. Authorized personnel review evidence and corrections. Face-position guidance is not identity verification. Organizations remain responsible for their use of work information and decisions affecting employees.
14. Changes to this policy
This policy may be updated to reflect changes in the service and its information practices. Material changes should be communicated through the policy and relevant notices before new collection or use begins.
The Arabic and English versions describe the same practices. For questions about this policy or your information, contact privacy@ransset.sa.