Privacy and requests

This page explains how the private test version of Akula Matata Travel works. The website is not yet open to customers and does not accept payments.

Your form and communication choices

The form asks for your route, preferred date, hotel for pickup or transfer (optional), guest counts, name, reply contact and preferences. Until you choose a channel, your draft stays only in the open page’s memory: it is not saved in the website database, localStorage or page address and disappears on reload. After reviewing the text, you choose a channel and send the message yourself. Clicking WhatsApp or Telegram passes the text to the chosen service in a link to prepare the message; clicking email passes it to your email app. The website cannot confirm sending or delivery and does not receive subsequent conversation contents. The website does not send email automatically. The chosen communication service’s policies apply. Do not send passport details, health information, payment card details or children’s personal data.

Opening a chat does not confirm a booking. Agree availability, the final price, changes, cancellation and payment with Nikolai.

Who can see your data

Only the website owner can access requests and manual financial records, using ChatGPT sign-in. Editing the tour catalogue does not give a staff member access to travellers’ contact details or financial records. Passwords are not stored in the website’s code. Changes and financial entries are recorded in the admin history.

Your private status link

Previously saved requests retain their reference and private link containing a secret key. New references and links are not created. The link shows the selected route, date, status and the manager’s message, but not contact details, internal notes or the financial ledger. Do not publish it or share it with others. The website database stores a cryptographic fingerprint of the key, not the key itself. A request reference alone does not grant access. Keys left in old browser tabs do not create new requests.

WhatsApp and Telegram

Direct contact links open a chat without a form. Buttons shown after completing the form prepare your enquiry text but do not send it. If an app does not fill in the text, you can copy and paste it manually. No historical request secret key is shared. Sharing a saved tour selection on WhatsApp opens prepared text with tour names and public links. You review and send it yourself. These messaging services have their own privacy policies.

Storage and technical data

Requests and operation history are kept in the website’s protected storage. Automatic deletion after a set retention period has not yet been configured for this test version. To correct your details or ask about deletion, contact the owner using the website’s contact options. To prevent mass submissions, the server may keep a short-lived aggregate request counter without storing IP addresses. The website does not use advertising analytics services.

Saved tours

Your saved tours are stored only in your device’s browser. They are not sent to the manager or synchronised between devices. You can clear them by deleting the website’s data in your browser settings.

Where an enquiry came from

If your link contains valid source, medium and campaign labels, the website may keep these three labels in the current browser tab for browsing the catalogue. These labels are not included with the current form. Each label is limited to 64 ASCII letters, digits, hyphens and underscores and must start with a letter. A new tagged link replaces the previous campaign; ordinary navigation keeps the latest one. This feature does not save the full URL, referring page, advertising click IDs, pixels or device identifiers. These labels are not shown on your private status page.

Website activity statistics

The application counts tab visits, tour page views and clicks on Telegram, Instagram, WhatsApp and MAX links. A visit starts on opening the home page, a tour or the travel form, and after 30 minutes without navigation or contact clicks in that tab. Tab storage keeps only the last activity time; no persistent visitor identifier is created. One person can create multiple visits. Tab visits are not counted if tab storage is unavailable.

Events send a random one-event reference, event type, page type, tour slug and channel name when applicable. The application does not record full URLs, contacts, message contents, IP addresses or device fingerprints in analytics. Daily totals are retained; retry receipts expire after 48 hours and are progressively removed as subsequent events arrive. Daily aggregate deletion is not yet scheduled. Statistics are not sent to an external advertising service. Collection respects Do Not Track and Global Privacy Control and excludes the owner and known staff.

Historical forms count only when accepted by the server; new forms are disabled. Opening a messenger does not confirm that a message was sent. Message confirmation integrations are not connected. Before public launch, the owner must determine the applicable legal basis, consent settings and retention periods.

Website language

Your language choice is saved in a cookie for up to one year and in the browser’s local storage. An explicit language choice in a link is also saved. If you have not saved a choice, your browser’s language preference is used. Your location is not requested to choose a language.

Before public launch

The owner must confirm business details, the legal basis and retention period for data processing, a contact for enquiries, booking, change, cancellation and refund policies, and rights to the materials. Payment entries in the admin area are entered manually and are not confirmation from a bank or payment provider.