Privacy Policy

Last updated: 10 November 2026

This Privacy Policy explains how OpDesk (Pty) Ltd (registration number 2026/648649/07, "OpDesk", "we", "us") collects, uses, and protects personal information, in compliance with the Protection of Personal Information Act, 2013 ("POPIA"). This policy covers both the OpDesk operations management platform (including the OpDesk Android app), RollingRover Productions, our web design service, and our tourism directory sites ZAtours (zatours.co.za), Route22 Zululand (route22zululand.co.za) and Cape Karoo Loop. These are trading lines of OpDesk (Pty) Ltd rather than separate legal entities. Each directory site also has a short privacy notice describing what is specific to it; this policy applies to all of them.

OpDesk is registered with the Information Regulator of South Africa under registration number 2026-066318.

1. An important distinction: when OpDesk is the "responsible party" vs. the "operator"

Under POPIA, this distinction matters, and we want to be upfront about it rather than blur the two together:

  • For information you give us directly — creating an OpDesk account, your business details, billing information, or a RollingRover web design enquiry — OpDesk is the responsible party. We determine why and how that information is processed, and this policy describes that processing.
  • For guest, booking, and staff information that an OpDesk customer (a lodge, tour operator, or other business using our platform) enters into their own OpDesk account — including field-log locations or routes linked to identifiable guides, rangers, trackers, crew, guests, or vehicles — OpDesk acts only as an operator (broadly equivalent to a data processor) on that customer's behalf. That customer is the responsible party for this information and their own privacy policy — not this one — governs how they use it. We process it only on their instructions, to provide the platform, and do not use it for our own separate purposes — with one bounded exception: for a customer who has chosen commission billing (section 2), we total their confirmed bookings each period solely to calculate the subscription amount they owe us, as described in section 3. We do not use booking or guest details for any other purpose of our own.

2. Information we collect

Depending on how you interact with us, we may collect:

  • Account information: name, email address, phone number, business name, operator type, and password (stored in encrypted/hashed form, never in plain text).
  • Billing information: billing currency, subscription plan, billing model (flat-rate or commission), payment confirmation records, and (for affiliates) payout details. Payment-card details are handled by the relevant payment provider and are not stored by OpDesk. On commission billing, we also record each billing period's total confirmed-booking value and the commission amount calculated from it.
  • RollingRover enquiries: name, email, phone, business name, and project details submitted through our web design quote request form.
  • Affiliate programme information: applicants' and affiliates' names, contact details, referral relationships, commission rates and records, payout and bank details, and information about businesses referred through the programme.
  • Booking and guest information: names, contact details, booking details, and message preferences, including optional guest-journey email consent and withdrawal timestamps, entered by an OpDesk customer or submitted through that customer's booking form. OpDesk handles this information as an operator on that customer's instructions, not for its own independent purposes.
  • Field-log and location information (where the feature is used): GPS coordinates, map pins and sighting locations, outing or route tracks imported from GPX, KML or GeoJSON files, timestamps, notes and photos, and associated user, vehicle or crew identifiers. A user may add a point using their device's GPS (after granting browser permission), select it on a map, or import a file. OpDesk does not continuously track a device. If a location or route identifies or can be linked to a person — for example, by showing where a guide, ranger, tracker or crew member was, or by locating a guest or a guest's vehicle — it is that person's personal information, even when the record was made to document an animal sighting. This information is entered by customers and their users; OpDesk handles it as an operator on the customer's instructions.
  • Support and communication records: support tickets, and the content of emails or messages you send us.
  • Technical information: browser and device details, service and security logs, and approximate country (used to suggest a likely local currency). If you allow optional analytics, Vercel Analytics also collects usage and device information on public marketing pages.

3. Why we process your information

We process personal information for the following purposes, consistent with POPIA's conditions for lawful processing:

  • To create and administer your account, and to provide the OpDesk platform (necessary to perform our contract with you).
  • On a customer's instructions, to store, display, map and report field-log sightings, locations and route records for reserve and field operations. We do not use these records to track people or devices for our own purposes.
  • To process billing and subscription payments, including, on commission-billing plans, totalling an operator's own confirmed bookings each period to calculate the amount they owe us.
  • To respond to support requests and RollingRover project enquiries.
  • To send service-related communications, such as account, booking, billing and support messages. OpDesk does not currently send its own marketing emails. Configurable, non-essential guest-journey emails are sent only when a guest has affirmatively opted in on the booking form and have an unsubscribe link. The operator chooses their content and is responsible for lawful use; OpDesk sends them only on the operator's instructions.
  • To maintain the security, integrity, and reliability of the platform.
  • To comply with our legal obligations, including tax, accounting, and regulatory recordkeeping.
  • If you allow optional cookies, to understand public-site usage and attribute an eligible business signup to its referring affiliate.

4. Who receives personal information

We do not sell personal information. We disclose it only as needed to provide our services, meet legal obligations, or administer the affiliate programme:

  • Supabase — database hosting and authentication.
  • Vercel — application hosting, infrastructure, and (only if you allow optional analytics) public-site usage analytics.
  • Google — Google Fonts delivers the typefaces used by the site; loading those files also makes technical request information, such as your IP address, available to Google.
  • PayFast — OpDesk subscription payments and, where an operator chooses PayFast, that operator's booking payments.
  • TurnStay and DPO — booking payment processing when the relevant operator has enabled that provider. The operator uses its own payment account; the selected provider receives the information needed to process the payment.
  • Resend — transactional email delivery, including account, booking, billing, support, and operator-configured guest-journey messages.
  • Meta (WhatsApp Business Platform) — delivery of booking and reminder messages to staff and to guests who message us on WhatsApp.
  • Telegram — delivery of booking updates and reminders to guests who choose to connect, and lead alerts to qualifying operators.

When an operator enables online booking payments, the operator remains the merchant and receives the funds through its selected payment account. OpDesk sends the provider the booking reference, amount, currency, and guest details needed to create or verify the payment. OpDesk does not collect or store payment-card numbers. The provider's own privacy terms also apply to its processing.

Affiliates and resellers: approved affiliates receive only the account and referral information needed to administer referrals and commissions. Depending on their role, this can include a referred business's name, account status, plan, add-ons, and sales or commission totals, and a head marketer's own sub-affiliate names, contact details, status, and commission rate. Affiliates do not receive guest or staff records, payment-card details, or bank account details of referred businesses. OpDesk determines and remains responsible for its own use and disclosure of this information, sets access limits, and requires affiliates to use it only for the programme and protect it. Each OpDesk customer remains responsible for personal information about its own guests and staff.

Apps from outside developers (TowerLens, BarePOS and others): OpDesk builds, supports, secures and distributes some apps made by outside developers. We may show these apps on our own website and social media, but we never collect or use your personal information to market or sell them, and we never contact people or businesses directly to market or sell them. When you buy or license one, OpDesk is the responsible party for what we collect to sell, license, bill and support it: your name, business name, email, licence details, payments and support questions. The app's developer can see your name, business name and email, your licence and payment records for their app, and the support questions you send about it, only so they can support the app and answer you. Each developer acts as our operator under POPIA: they must sign our App Developer Agreement, keep the information confidential and secure, use it for nothing else (including their own marketing), tell us at once about any breach, and register their own Information Officer with the Information Regulator. We keep a record of each developer's Information Officer. Developers do not see payment-card details.

Some service providers may process information on servers located outside South Africa. Where this occurs, we rely on the safeguards POPIA permits for cross-border transfer, including that the recipient is subject to a law, binding agreement, or contractual terms that provide an adequate level of protection substantially similar to POPIA's conditions.

5. How we protect your information

We use technical and organisational measures appropriate to the risk, including encryption of data in transit and at rest, role-based access control, row-level database security so one customer's data is never visible to another, and restricted administrative access. No system is perfectly secure, but we take reasonable steps to prevent loss, unauthorised access, and unlawful processing.

If we have reasonable grounds to believe that your personal information has been accessed or acquired by an unauthorised person, we will notify the Information Regulator and you as soon as reasonably possible, as required by section 22 of POPIA. The notice will explain the possible consequences, what we have done or will do about it, and what you can do to protect yourself. Where we hold the information as an operator for an OpDesk customer, we notify that customer immediately so they can meet their own obligations.

6. How long we keep it

We apply retention periods according to the purpose and type of information. Account and affiliate records are kept while the account or programme relationship is active and for up to 90 days after it ends to complete closure, export, and support; they are then deleted or anonymised unless a longer period is needed for a legal obligation, unpaid amount, security matter, or dispute. Enquiry and support records are kept for up to 24 months after the last meaningful contact, unless a matter remains open. Billing, tax, payout, and commission records are kept for the period required by applicable financial, tax, and company-record laws. Guest, staff, and other customer business information held as an operator — including field-log location and route records — is retained only on the customer's instructions and is deleted or returned when instructed or when the service ends, subject to legal obligations and secure backup rotation. We process verified deletion requests within 30 days, subject to information we must retain by law.

7. Your rights

Under POPIA, you have the right to:

  • Be notified that we hold your personal information, and what we hold.
  • Request access to the personal information we hold about you.
  • Request correction of inaccurate, outdated, or incomplete information.
  • Request deletion or destruction of personal information we no longer have a lawful basis to retain.
  • Object to processing of your personal information in certain circumstances, including for direct marketing.
  • Withdraw consent, where processing is based on consent, at any time.
  • Lodge a complaint with the Information Regulator (contact details below) if you believe we've handled your information unlawfully.

To exercise any of these rights, contact our Information Officer using the details in section 9. We may need to verify your identity before acting on a request.

8. Cookies, analytics, and browser storage

Essential authentication cookies keep you signed in and secure the service. The od_optional_consent preference cookie remembers your separate analytics and referral choices for 180 days. If you allow referral attribution, we use a first-party od_ref cookie for up to 60 days; it records a referral code so an eligible affiliate can be credited if you later create a business account. Rejecting or withdrawing that choice prevents or clears the referral cookie.

If you allow analytics, Vercel Analytics measures visits and general interaction on public marketing pages only. Analytics events do not include query strings, and account/authentication pages are excluded. We do not use analytics on the logged-in dashboard, advertising pixels, or targeted-advertising cookies. You can reject this optional purpose or change your choices at any time using Cookie settings in the footer. Currency suggestions use the approximate country supplied with a page request and do not require a tracking cookie.

The browser also stores the service worker's static app-shell files so the offline page and install assets can work without a connection. Separately, when the field log is used offline, new unsent sightings (including any location and attached photo) are stored in IndexedDB in that browser on the device and queued for upload when it reconnects. They remain there until they sync or are removed from the queue; OpDesk cannot access them before upload. The service worker does not cache API responses, bookings, guest records, or other dashboard data.

OpDesk Android app: the app opens the OpDesk website full-screen using a browser installed on your device, so the same cookies, storage, and choices described above apply. The app itself does not read your contacts, files, or other apps' data, and it does not collect location in the background. Location, camera, or notification access is requested only when you use a feature that needs it, through your device's normal permission prompt, which you can refuse or withdraw in your device settings.

9. Our Information Officer

Douw Gerbrand Grobler is OpDesk's registered Information Officer (appointed 1 September 2026), registered with the Information Regulator under registration number 2026-066318.

To make a request, ask a question, or raise a concern about how we handle personal information, contact: central@opdesk.app

10. Complaints to the Information Regulator

If you're not satisfied with our response, you may lodge a complaint with the Information Regulator of South Africa:

Website: inforegulator.org.za
Email: complaints.IR@justice.gov.za

11. Changes to this policy

We may update this policy from time to time to reflect changes in our practices or legal requirements. We'll update the "last updated" date above when we do. Material changes will be communicated to registered account holders by email.

12. Data deletion instructions

You can ask us to delete the personal information we hold about you at any time, including information connected to Facebook, WhatsApp or Telegram messaging.

To request deletion:

  1. Email central@opdesk.app with the subject "Data deletion request".
  2. Tell us who you are and how we know you: the email address or phone number you used (including the WhatsApp number or Telegram account, if the request relates to messaging) and, if you are a guest, the name of the business you booked with.
  3. We may ask you to confirm your identity before acting on the request, to protect your information.

What happens next: we acknowledge your request within 5 business days and complete it within 30 days. We delete or anonymise the personal information we hold as a responsible party, and remove your WhatsApp and Telegram connection details so we no longer message you.

Guests of an OpDesk customer: where a lodge or tour operator entered your booking details in their OpDesk account, that business is the responsible party (see section 1). We will pass your request to them and they decide on the deletion; we delete the data from our systems on their instruction.

Records we must keep: we may retain limited information where the law requires it, for example tax and accounting records. We keep only what is required, for the legally required period.

Stopping Telegram messages: you can stop Telegram updates immediately by sending STOP to the OpDesk bot, which disconnects the chat without needing a full deletion request.

See also our Terms of Service and our PAIA Manual, which sets out in more detail the categories of records we hold and how to request access to them under the Promotion of Access to Information Act.