Privacy & workforce data

Privacy Policy

This notice explains how RTA Security handles personal data when administrators coordinate field operations and employees receive, perform and complete security assignments.

Effective 26 August 2026 Last updated 27 September 2026 Version 1.0

Location-sharing disclosure

Location is used only for eligible work assignments

RTA Security collects precise location data to enable live dispatch coordination, assignment progress, arrival and site verification, employee safety, movement history, and operational records. On iOS, sharing occurs only while the app is open and stops when you leave or close it. On Android, location can continue in the background with permission. Location may continue during a recorded break while the assignment remains active. Operational tracking stops when the assignment is completed or ended, or when tracking is otherwise no longer eligible. Location data is not used for advertising and is not sold.

01

Scope, who we are and who controls your data

This Privacy Policy applies to the RTA Security mobile application for iOS and Android and its related administrator services (together, the “Service”). RTA Security is a workforce coordination product published and operated by Digital Keed (“RTA Security,” “we,” “us” or “our”).

RTA Security is available to independent security teams and organisations. A user may create a new isolated workspace and become its first administrator, then invite employees and other administrators. The organisation that operates a workspace, assigns jobs and manages field employees is the “Employer.” For employee workforce data, the Employer will normally decide why and how the data is processed and is therefore the data controller. RTA Security normally processes that data on the Employer’s behalf as its service provider or processor. The Employer remains responsible for its lawful basis, employee notices, workplace policies, access decisions and retention requirements.

For data we process for our own service security, account administration, support, legal compliance and operation of this public policy page, RTA Security may act as an independent controller. If your Employer provides a separate workforce privacy notice, read it together with this Policy; that notice explains Employer-specific practices and local employment rules.

02

Privacy at a glance

Work-related use

Data supports assignments, dispatch, time records, site verification and safety.

Limited tracking

Operational location tracking is tied to eligible active assignments—not general off-duty monitoring.

Human oversight

Location or integrity signals must not be the sole basis for disciplinary decisions.

No advertising sale

We do not sell personal data or use precise location for behavioural advertising.

03

Personal data we process

The exact data depends on your role, device permissions and use of the Service.

CategoryExamplesHow it is obtained
Account and identity Name or username, role, employer/company, account status, administrator email, encrypted authentication credentials, activation and recovery status. Provided by an administrator, employee or authentication service.
Assignment and work records Job title, client/site, instructions, scheduled time, acceptance, readiness, departure, arrival, work start, break, resume, completion and replacement-job events. Created by administrators, employees and server-validated workflows.
Location and movement Precise latitude/longitude, timestamp, accuracy, speed or motion indicators, last known position, movement trail, distance to site and geofence result. Collected from the device during an eligible assignment, subject to OS permissions and availability.
Time and attendance Server-recorded work and break intervals, net active time, regular time, administrator-visible additional time, lateness and daily summaries. Calculated from job events and validated server timestamps.
Device and notification data Platform, app version, device/session identifiers, push token, notification delivery state, permission state and tracking availability. Generated by the app, operating system, Expo, Apple or Firebase.
Diagnostics and security Sanitised error reports, safe support reference, operation name, failure code, suspicious or inaccurate location signals and audit events. Generated when the Service is used or an error occurs.
Requests and communications Access-code requests, account-deletion requests and support communications. Submitted by a user or administrator.

The Service is not designed to collect contacts, call or SMS history, payment card data, health data, advertising identifiers, microphone recordings, photos, videos or biometric templates. If a future feature requires a new data category, we will update this Policy and provide any required notice or permission request before collection.

04

How workforce location tracking works

When tracking may start

Tracking is linked to an eligible assignment and may begin when an employee accepts that assignment or enters another server-approved active state. The app requests precise foreground location while using the app. iOS does not request Always access or collect background locations. Android can request background location so dispatch can see progress while the screen is locked, another app is open or RTA Security is not visible.

What happens during an active assignment

  • Authorised administrators and dispatchers may see the employee’s recent position, freshness, accuracy, movement status and route history.
  • Location may be checked when the employee marks departure, arrival, work start, return from break or completion.
  • Site-radius checks may confirm whether the employee is near the assigned location. A failed check can prevent a location-dependent action until the employee returns.
  • A recorded break is excluded from net work time. Because the assignment remains active, location may continue for operational safety, assignment integrity and return-to-site verification.
  • If the device is temporarily offline, observations may be stored in an encrypted local queue and uploaded when connectivity returns.

When tracking stops

Operational tracking is intended to stop when the job is completed, ended by dispatch or no longer eligible for tracking. It can also be interrupted by logout, account deletion, revoked permissions, device settings, force-stop, battery restrictions, operating-system behaviour or loss of connectivity. The Service records tracking availability so dispatch is not misled by an old or low-accuracy position.

Platform indicators and controls

Android shows a persistent foreground-service notification while eligible background tracking is active. iOS may show its system location indicator. Users can review permissions in device settings. Disabling required location access may prevent location-dependent job actions, but it does not authorise hidden or unrelated tracking.

05

Why data is used and the legal bases

Depending on the country, Employer and context, processing may rely on:

  • Contract and employment administration: to provide assigned work, document performance of operational tasks and administer accounts.
  • Legitimate interests: to coordinate security staff, protect employees and sites, maintain reliable records, prevent misuse and secure the Service, where those interests are not overridden by individual rights.
  • Legal obligations: including applicable employment, working-time, safety, tax, payroll, record-keeping, investigation and data-protection obligations.
  • Vital interests or safety: in exceptional situations where processing is necessary to protect a person.
  • Consent: only where local law makes consent appropriate and it can be freely given and withdrawn. Consent is not assumed to be the primary basis in an employment relationship.

We and the Employer use personal data to:

  • authenticate administrators and employees and keep authorised devices signed in;
  • create, dispatch, accept, replace, perform and close assignments;
  • show current operational status and location to authorised dispatch staff;
  • calculate work, break and additional-time records from server timestamps;
  • send assignment, replacement, timing, access and safety notifications;
  • provide maps, address suggestions, navigation handoff and site-radius checks;
  • detect stale, unavailable, implausible or low-accuracy location signals;
  • respond to access recovery, deletion and support requests;
  • secure, debug, audit and improve the Service; and
  • comply with law and enforce agreements.

RTA Security does not make solely automated disciplinary or employment decisions. Status, location, lateness and integrity signals can be incomplete or wrong and should be reviewed by an authorised person with relevant context before action is taken.

06

Who can receive personal data

We disclose data only as necessary for the purposes above:

  • The Employer: authorised administrators, owners, dispatchers, HR or support personnel, according to role and operational need.
  • Supabase: cloud database, authentication, realtime updates and server functions.
  • Google Maps Platform and Places: maps, geocoding, address suggestions and related mapping functions.
  • Expo: application build/update infrastructure and Expo push-notification routing.
  • Firebase Cloud Messaging: delivery of Android notifications.
  • Apple Push Notification service: delivery of iOS notifications.
  • Vercel: hosting of this public Policy; Vercel may process standard web request and security logs when this page is visited.
  • Professional advisers and authorities: where reasonably necessary for legal claims, compliance, safety, fraud prevention or a valid legal request.
  • Corporate transactions: if the Service or business is reorganised, financed, acquired or transferred, subject to confidentiality and applicable law.

Service providers are expected to process data under contractual, confidentiality and security obligations. We do not sell personal data, share it for cross-context behavioural advertising or use precise workforce location to build advertising profiles.

07

Retention, account deletion and disposal

Request account deletion without the app: Employees and administrators can email digital.leart@gmail.com with the subject “RTA Security account deletion”, their account email or username and workspace name. You do not need to install or sign in to the app. Do not send a password, access code or location history. Management verifies the request, processes administrator account deletion within two calendar days (including weekends), and confirms completion to the account email. If workspace continuity needs confirmation, management will contact you within that period. Personal account and authentication information is deleted or anonymised; shared workspace records and records retained for the legitimate reasons described below may remain.

Data is retained only as long as necessary for its purpose, using these criteria:

Live locationThe current live projection is used during an eligible assignment and ceases to be live when tracking ends. Historical observations may remain in the assignment record under the Employer’s retention schedule.
Offline location queueHeld encrypted on the device, partitioned by employee account, for upload retries. Queued observations and acknowledgement receipts expire after 24 hours. Upload retries do not require continued GPS collection after the assignment ends.
Detailed location historyThe proposed schedule is six calendar months, separate from work records. This cleanup is activated only after the Employer documents the applicable policy; it must not be described as an active deletion guarantee before that configuration is verified.
Job, time and audit recordsKept for the Employer’s documented operational, payroll, dispute, safety and legal-retention period. The Employer determines the applicable schedule under local law.
Account and profileKept while the account is active and afterwards only where needed for account closure, security, legal obligations or linked work records.
Push tokensKept while the device is registered; invalid tokens are disabled and tokens are removed or disassociated when no longer required.
Sanitised error telemetryNormally deleted after 30 days unless a shorter period applies or a specific security investigation legally requires longer retention.

Employees can delete their own account in Account > Account management > Delete account. Administrators can submit a durable deletion request in Account settings. Management processes administrator requests within the deadline shown in the app and confirms completion to the account email. The administrator account remains active until processing starts, and a pending request can be cancelled. Other members and shared workspace records remain. Deleting an account ends future access and eligible tracking, but does not necessarily erase records the Employer must retain for payroll, working-time, safety, legal claims, compliance or audit. Where full deletion is not possible, data will be restricted, minimised or de-identified where appropriate.

08

Security, integrity and accuracy

Safeguards include encrypted network transport, authenticated access, company and role-based authorisation, database row-level security, protected server functions, server-recorded command timestamps, encrypted local storage for queued location, restricted production configuration and sanitisation of error telemetry. Access is limited according to operational role.

No system is perfectly secure or “100% accurate.” GPS, network conditions, device sensors, permission settings, buildings, battery-saving features and operating systems can delay or distort location. The Service therefore stores accuracy and freshness information and can label a position unavailable, stale or low-accuracy instead of presenting it as certain. Users and administrators should report suspected errors and verify important decisions with other evidence.

09

Your privacy rights

Subject to applicable law, including the Swiss Federal Act on Data Protection, the EU General Data Protection Regulation and German data-protection law, you may have the right to:

  • obtain information about and access to your personal data;
  • correct inaccurate or incomplete data;
  • request deletion or restriction of processing;
  • object to processing based on legitimate interests;
  • receive certain data in a portable format;
  • withdraw consent where processing relies on consent, without affecting earlier lawful processing;
  • request human review of a decision and challenge inaccurate operational signals; and
  • complain to the Swiss Federal Data Protection and Information Commissioner or the competent EU/EEA supervisory authority.

Start with your Employer’s administrator, HR or privacy contact because the Employer normally controls workforce records. You may also contact RTA Security using the details below. We may need to verify identity and authority before acting. Rights can be limited where retention or processing is required by law or necessary to protect another person’s rights.

10

International processing and Kosovo demo mode

The Service may be used in Switzerland and Germany, while providers and support systems may process data in other countries. The relevant controller will use applicable safeguards for restricted transfers, such as an adequacy decision, data-protection agreement or standard contractual clauses, and will identify destination countries where required by Swiss law.

Kosovo support is intended only for controlled demonstration and testing. Demo accounts and synthetic assignments should be used; production employee or client records must not be copied into a demo environment. If real personal data is used in Kosovo, the Employer must first confirm a lawful basis, notice, transfer mechanism and security controls.

11

Children

RTA Security is a workplace application for authorised adult administrators and employees. It is not directed to children and must not be used to create an account for anyone under 18. Contact us if you believe a child’s data has been entered into the Service.

Work time, travel and breaks

Accepting an assignment can begin operational location sharing. Acceptance, travel and confirming arrival do not start the app’s on-site work timer. Work time starts when the employee confirms Start work at the site. A recorded break pauses net work time; returning from the break preserves time worked before it. For example, 30 minutes of work, a 15-minute break and another 45 minutes of work produces 75 net work minutes.

Location sharing can continue during travel and recorded breaks while the assignment remains eligible. The app’s on-site total does not determine all payable or legally recognised working time. The Employer must account separately for travel, waiting or other time where applicable law, collective agreements or the employment contract require it.

Employee terms of use

These usage rules explain operation of the app. Viewing this page does not record contractual acceptance or consent to monitoring. They do not replace an employment contract, collective agreement, mandatory rights or the Employer’s workplace instructions.

Authorised use and account security

Use only the account assigned to you and only for authorised company work. Keep credentials private, do not share access codes, and report suspected unauthorised access. Do not access another employee’s records or bypass company access controls.

Accurate records and corrections

Confirm assignment, arrival, work and break actions accurately. Do not submit simulated GPS or deliberately falsify time records. Device estimates and network delivery can be wrong: report missing work or inaccurate location to dispatch and request human review. An app signal alone should not be treated as proof of misconduct.

Safety and service availability

Do not operate the app while driving or when it is unsafe. Push notifications, maps and location delivery depend on permissions, connectivity, device settings and providers. The app is not an emergency service; use your agreed emergency procedure. Contact dispatch if a technical problem prevents an action.

Permissions, account closure and employee rights

You can review permissions in device settings and request account deletion in the app. Restricted permissions may prevent site verification; agree an alternative reporting process with the Employer. Account closure may take time while provider deletion is retried; required work records can remain pseudonymised under the applicable retention schedule. No clause waives statutory privacy, pay, safety or employment rights.

Employer-specific notice

The Employer must provide its legal identity, address, privacy contact, relevant processing purposes and basis, retention schedule and applicable transfer countries/safeguards. This platform description does not substitute for that company-specific information.

12

Changes to this Policy

We may update this Policy when the Service, providers or legal requirements change. The current version and effective date will remain available at this URL. Material changes will be communicated in the app, through the Employer or by another appropriate method before they take effect where law requires. Earlier versions may be requested from the contact below.

13

Contact and exercise your rights

For RTA workforce-record questions, contact RTA Security GmbH, Wehntalerstrasse 36, 8057 Zürich, Switzerland, at alijaj@rtasecurity.ch. These company details are published on rtasecurity.ch. For questions about the platform, this Policy, security or a privacy request, contact:

Product and service operator RTA Security · Digital Keed
Privacy contact digital.leart@gmail.com
Response information Include your username, Employer and request type. Do not email an activation code, password or precise location history.

About this policy website

This static page does not set advertising cookies and does not run product analytics. Its hosting provider may receive standard request information such as IP address, browser type, timestamp and security logs to deliver and protect the page.