Version 1.24. Effective date: 9 November 2026.
Responsible Party: Tsamaya (Pty) Ltd, a private company registered in South Africa
Registration number: 2023/990736/07
Physical and postal address: 10 Audocia Place, Hurlingham Manor, Sandton, 2196, South Africa
Information Officer: Kyle Kimble (Director)
Email: info@tsamayaapp.co.za
Telephone: 073 285 5752
Website: https://tsamayaapp.co.za
1. Introduction
1.1 Tsamaya is a navigation app for South African metros. It suggests driving routes with lower statistical exposure to the areas and roads that our statistical risk data rates as higher risk. This policy explains what Personal Information the Tsamaya App and our Website (tsamayaapp.co.za) Process, why, who receives it, how long we keep it, and your rights under the Protection of Personal Information Act 4 of 2013 (POPIA). Earlier versions are listed in clause 24.
1.2 This policy is given in terms of section 18 (Notification to data subject when collecting personal information) of POPIA. It should be read together with our Terms of Use, which govern your use of the App, and our PAIA Manual, which describes the records we hold and how to request access to them. Both are available on the Website.
1.3 Tsamaya is the Responsible Party for the Personal Information described in this policy and decides why and how it is Processed. Where a provider listed in clause 13 Processes Personal Information on our behalf, it does so as our Operator.
2. Definitions
2.1 In this policy, the words below have the following meanings. Defined words are capitalised, and words in the singular include the plural and vice versa:
2.1.1 “App” means the Tsamaya navigation application for Apple and Android phones, including its versions for Apple CarPlay and Android Auto;
2.1.2 “Consent” means a voluntary, specific and informed expression of will by which you agree to the Processing of your Personal Information for a particular purpose, for example by granting a permission on your phone or by choosing to use an optional feature;
2.1.3 “Data Subject”, “you” or “your” means the person to whom Personal Information relates, such as a driver who uses the App, a person who follows a shared trip, a visitor to the Website or a person who contacts us;
2.1.4 “Data Subject Request Form” means the form in Annexure A to this policy (also attached as Annexure B to the PAIA Manual) by which you may make a Request;
2.1.5 “Direct Marketing” means approaching you, by an electronic communication such as a push notification or an email, to promote the App or any of its features, including Premium;
2.1.6 “HERE” means HERE Europe B.V., a mapping and location-data company in the Netherlands, which is Tsamaya's backup place-search provider;
2.1.7 “Information Officer” means the person responsible for Tsamaya's compliance with POPIA and PAIA and for dealing with Requests, whose details are set out in clause 23;
2.1.8 “Information Regulator” means the independent body established in terms of section 39 (Establishment of Information Regulator) of POPIA, which monitors and enforces compliance with POPIA and PAIA and to which a complaint may be made;
2.1.9 “Installation ID” means the random identifier that the App creates on a phone when it is installed; it is not a name or an account, but it links the information that comes from one installation of the App;
2.1.10 “Operator” means a person or organisation that Processes Personal Information on behalf of a Responsible Party, in terms of a contract or mandate, without deciding why or how it is Processed (sometimes called a processor);
2.1.11 “PAIA” means the Promotion of Access to Information Act 2 of 2000;
2.1.12 “PAIA Manual” means the manual that Tsamaya has prepared in terms of section 51 (Manual) of PAIA, published at https://tsamayaapp.co.za/paia.html;
2.1.13 “PAIA Regulations” means the Regulations relating to the Promotion of Access to Information, 2021;
2.1.14 “Personal Information” means information that relates to an identifiable, living individual or an identifiable, existing juristic person, including an online identifier (such as the Installation ID or a network address) and location information that can be linked to that person, but not information that has been de-identified so that it can no longer be linked to that person;
2.1.15 “POPIA” means the Protection of Personal Information Act 4 of 2013;
2.1.16 “POPIA Regulations” means the Regulations relating to the Protection of Personal Information, 2018, which prescribe Form 1 (objection to Processing) and Form 2 (correction or deletion);
2.1.17 “Premium” means Tsamaya Premium, the optional paid subscription described in clause 11 of the Terms of Use;
2.1.18 “Privacy Policy” or “this policy” means this document, as updated from time to time;
2.1.19 “Process” or “Processing” means any operation or activity concerning Personal Information, whether or not by automatic means, including collecting, receiving, recording, storing, using, sharing, de-identifying, deleting or destroying it, and “Processed” has a corresponding meaning;
2.1.20 “Recipient” means a person or organisation to whom Personal Information is disclosed, including an Operator and a provider that receives Personal Information under its own terms;
2.1.21 “Request” means a request, objection, withdrawal of Consent or complaint by which you exercise a right described in clause 17;
2.1.22 “Responsible Party” means a person or organisation that decides why and how Personal Information is Processed; Tsamaya is the Responsible Party for the Personal Information described in this policy;
2.1.23 “Special Personal Information” means Personal Information about a person's religious or philosophical beliefs, race or ethnic origin, trade union membership, political persuasion, health or sex life, biometric information, or criminal behaviour;
2.1.24 “Terms of Use” means the terms on which Tsamaya makes the App available, published at https://tsamayaapp.co.za/terms.html;
2.1.25 “Tsamaya”, “we”, “us” or “our” means Tsamaya (Pty) Ltd (registration number 2023/990736/07);
2.1.26 “Website” means Tsamaya's website at https://tsamayaapp.co.za, including the trip page that shows a shared trip; and
2.1.27 “Working Day” means any day other than a Saturday, Sunday or public holiday in South Africa.
2.2 A word that is used in this policy and defined in POPIA, but not defined above, has the meaning given to it in POPIA. Where a section of legislation is referred to, its heading is included in brackets for ease of reference only.
3. Summary
3.1 Tsamaya uses your location on your phone to show the map, guide you and plan routes. For this, coordinates are sent to the services that answer each request: Mapbox for maps and routes; Google, HERE or Mapbox for place search; and our own server, to find police, roadblock and pothole notices near you and for the rain reminder. They are sent without your name or an account. We keep no history of where you are or where you go, apart from what you choose to send us (clauses 6 and 7).
3.2 Drivers do not have accounts. We show no advertising, we do not sell Personal Information and we do not track you across other apps.
3.3 Saved places (such as Home and Work), recent searches, saved routes and your trip history are stored only on your phone, and we cannot see them. A place name leaves your phone only in the ways this policy describes, including a search, the natural voice saying where you have arrived (clause 9), a live trip you choose to share (clause 7) and a report you send (clause 6).
3.4 Each installation of Tsamaya has an Installation ID. It is not your name or an account, but it links the usage events, crash reports, reports, notification registration and shared trips that come from one installation, so we treat it as Personal Information.
3.5 We collect as little as we can and, wherever we can, we de-identify information so that it can no longer be linked to an installation or a person; information de-identified in that way, such as the aggregate counts and statistics we keep, is not Personal Information. Information that can still be linked to an installation or a person, such as the Installation ID, network addresses, a shared trip, a report that carries a position and an email address you choose to give us, is Personal Information, and we handle it as this policy describes.
3.6 We collect usage events (such as a route being accepted) and crash reports. They carry that identifier, but never your name or where you went. Our crash reporting service also counts app sessions under its own random identifier, so that we know how often the App crashes. You can switch usage events off in Settings › Sharing & privacy (clause 10).
3.7 If you send a report or feedback, we store what you submit, and your email address only if you choose to give it (clause 6).
3.8 Voice reports are optional. When you tap Speak (or ask Siri) to report something on the road, your phone's own speech service turns what you say into text so that the App can choose the report. Tsamaya never records or keeps audio; only the report itself is sent (clause 8).
3.9 Tsamaya Premium is optional. If you subscribe, Apple or Google takes the payment and we never see your card. RevenueCat, the service that checks subscriptions for us, receives your store purchase records and a random id it creates, so that Premium stays on the account that paid (clause 12). Free Premium earned with accepted reports is counted against your Installation ID and given through RevenueCat only when you claim it (clause 12.10).
3.10 Notifications are optional. Nothing arrives unless your phone allows Tsamaya to send notifications, and news about new features arrives only if you ask for it. We store a delivery token for your device and the metro you are in (such as "Cape Town"), never your coordinates. With the fuel price alert on, we also store your fuel type and, with Tsamaya Premium, a date based on when your Premium ends. Each kind of notification has its own switch (clause 11).
4. Information we Process, and Why
4.1 The table below sets out the Personal Information we Process, where it goes, why we Process it and the lawful basis on which we rely under section 11 (Consent, justification and objection) of POPIA:
| Information | Where it goes | Purpose | Lawful basis (section 11 of POPIA) |
|---|---|---|---|
| Precise device location while you use Tsamaya, including in the background during a guided drive and while your phone is connected to CarPlay or Android Auto | Processed on your phone. Sent as coordinates to Mapbox (our mapping provider) for maps, routes, street names and Arrive by (with the departure time being checked); to Google, HERE through our server, or Mapbox, as the centre of a place search; and to our server (Supabase) to find police, roadblock and pothole notices near you, which uses the position for that lookup only and does not store it | Show your position; guide you; plan routes from where you are; find places near you; warn you of notices ahead | Consent (the location permission you grant) and our legitimate interest in providing the service you request |
| Destination searches | Your search text and your position (as the centre of the search) go to Google (Places API) with a random code for that search, never your Installation ID. When Google cannot answer, the same search text and an area rounded to about 100 m are sent to HERE (our backup search provider, defined in clause 2) through our server, which keeps neither, and if HERE cannot answer either, the search text and your position go to Mapbox's place search. When a place card has no opening hours, the place's name and its position, rounded to about 100 m, go to HERE through our server to look them up. A saved place that HERE found is looked up again by its HERE reference (not its name or your position) about every 25 days, through our server, which keeps nothing, so that it is kept no longer than HERE's terms allow; a recent search that HERE found is deleted after 30 days. A Premium search goes first through our server to Google, with your RevenueCat id (clause 12). Mapbox Directions builds the route from the chosen coordinates | Find places and their opening hours; build the route | Performance of the service you request |
| Weather for the rain reminder (on unless you switch it off in Settings › Alerts) | During a drive, your position rounded to about 1 km goes to our server (Supabase), which rounds it again to an area of about 5 km across and asks Apple's WeatherKit about the centre of that area, so Apple never receives your position. The answer is reused for 10 minutes for anyone in the same area and deleted within 48 hours; your position is not stored | Reminding you to switch your headlights on when it rains | Legitimate interest (road safety) |
| Spoken directions in the natural voice (on unless you switch Natural voice off in Settings › Navigation) | Each sentence to be spoken goes to our server and, unless it has been spoken before, from there to Google Cloud Text-to-Speech. The only destination or stop names it says are Home and Work: any other is "your destination" or "your stop" in this voice (clause 9) | Speaking directions in a natural voice | Legitimate interest (clear spoken guidance); you can switch it off |
| Saved places (Home, Work, favourites), recent searches, saved routes (with their start point and route line), settings, onboarding state, trip history (each guided drive's destination name, when, how far, the route option and its grade; each drive made without a route while Tsamaya is open, with when and how far; the name of the saved place a drive started at, and a drive without a route ended at, if any, and, if you add them with Premium, whether it was business or personal and your note), with Premium's SARS logbook the trips you add by hand and the vehicles (including registration numbers), costs, odometer readings and photos you give it, the photo of your car for the map marker, your emergency contact's name and number, your daily search counts, your fuel settings, any Arrive by reminder, and a navigation log of the last 72 hours | Your phone only (local app storage and its own notification service); never sent to us unless you send it (the navigation log, clause 6), except that this device's notification registration records whether the fuel price alert is on and, with it on, your fuel type (clause 11), and a saved place that HERE found is refreshed from HERE by its HERE reference (destination searches, above) | Convenience features, the search usage meter, Premium's trip history, logbook, fuel cost and Arrive by, and fixing faults | Consent |
| The Installation ID | Created on your phone and sent with usage events, crash reports, reports, the notification registration and shared trips | Linking these to one installation; spotting duplicate or abusive reports; answering your requests about your data (clause 17) | Legitimate interest |
| Technical request metadata (IP address, basic device info) | Every service the App calls receives your network address and basic device details as part of the request: Mapbox, Google, Apple, Supabase (which hosts our public zone and road dataset and, for Premium's fuel cost and toll prices, the public lists of official fuel prices and toll tariffs), RevenueCat, Sentry, and Expo when the App checks for an update (with a random update identifier for this installation). Tsamaya switches off the usage data (telemetry) Mapbox's map software would otherwise send Mapbox, a few seconds after the App first opens; versions of the App before its October 2026 update left it on, and it can include location (see Mapbox's privacy policy) | Operating, updating and securing the services | Legitimate interest |
| Reviewer account email (admin/editor users only, not drivers) | Supabase authentication | Restricting data-editing tools to authorised reviewers | Performance of contract |
| Reports and feedback you choose to submit (see clause 6) | Supabase (our hosted database); Anthropic (Claude), which helps the review team check reports; Mapbox, which names the roads and street address nearest a pinned or drawn place for that check; the review team's email (through Resend) and phone notifications (through Expo) | Reviewing and improving the risk dataset and the App | Consent (you choose to send it) |
| A live trip you choose to share, an SOS link or Guardian (see clause 7) | Supabase, and anyone who holds the link | Letting someone you choose follow your drive | Consent (you tap Share, Alert or Guardian) |
| Premium check, on every install (see clause 12) | The App asks RevenueCat whether this device has Premium, which sends a random RevenueCat id and basic device details. On an iPhone, the first check after installing also sends Apple's record of the App's download (not a payment) | Showing whether this device has Premium, and bringing back a subscription the store account already has | Legitimate interest (knowing whether this device has Premium) |
| Premium purchases, only if you subscribe (see clause 12) | Apple or Google take the payment. RevenueCat receives the store's purchase and renewal records, a random RevenueCat id and basic device details. Our server (Supabase) keeps the subscription's status against that id | Selling Premium and keeping it on the store account that paid for it | Performance of contract (the subscription you buy) |
| Free Premium for your reports (see clause 12.10) | The App sends our server (Supabase) your Installation ID, which counts your accepted reports. When you tap Claim, our server reads RevenueCat's Premium records for your RevenueCat id, asks RevenueCat to give the free month, and keeps a record of the month given with both ids | Thanking contributors with free Premium, and giving each earned month only once | Legitimate interest (counting accepted reports you chose to send); Consent (you tap Claim) |
| Refund requests, only if you cancel an annual plan bought on the App Store and ask us for a refund (clause 11.5 of the Terms of Use) | You send us by email the Apple order ID from your receipt, your name, email address and bank account details. We check the order ID against our subscription records and pay the refund by EFT from our bank account, and record the payment in our accounting system (Xero). On Google Play, refunds go through the store and we receive no bank details | Verifying and paying your refund, and keeping the records tax law requires | Performance of contract (your right to a refund) and compliance with the law (consumer protection and tax law) |
| Your voice, only while you make a voice report, ask Siri, or say a destination on Android Auto (see clause 8) | Your phone's speech service (Apple on iPhone; usually Google on Android, and Google Assistant on Android Auto) turns it into text; the audio is not recorded, kept or sent to us | Choosing the report type you said, or finding the place you asked for | Consent (the microphone and speech permissions, and your tap on Speak) |
| Open in Google Maps, only if you tap it | The route's start, destination and up to 8 points along it go to Google Maps, under Google's terms | Continuing the route in Google Maps | Consent (your tap) |
| A map link you share into Tsamaya, only if you do | To read a shortened link (for example from Google Maps or WhatsApp), the App opens the link's own address, so that site receives your network address | Finding the place the link points to | Consent (you share the link) |
4.2 Location runs in the background only during a guided drive and while your phone is connected to CarPlay or Android Auto, so that guidance continues with the screen off and the drive is recorded in your trip history on your phone. Tsamaya does not use your location when it is closed.
4.3 We do not collect your name, your contact list, payment details (Apple and Google take payment for Premium; we never see card or bank details, unless you ask us for an App Store refund (see the table above)) or advertising identifiers. If you choose an emergency contact, Tsamaya keeps their name and number on your phone and uses them only when you tap to call or message them. What you type into trip notes stays on your phone.
4.4 Supplying any of this information is voluntary: every permission and feature in this policy is optional. Without location access, Tsamaya can still plan a route from a start point you choose, but cannot show where you are or guide you.
4.5 We collect Personal Information directly from you when you use the App, send us a report or contact us; automatically from your phone when you use the App or visit the Website; and, for Premium, from Apple, Google and RevenueCat when you buy or restore a subscription. We do not buy Personal Information or obtain it from data brokers.
4.6 We will not Process your Personal Information for a purpose that is incompatible with the purpose for which we collected it, as section 15 (Further processing to be compatible with purpose of collection) of POPIA requires. Where we rely on your Consent, you may withdraw it at any time; this does not affect Processing that took place before you withdrew it.
5. What we do not do
5.1 No server-side history of your location or trips. What our server holds is listed in clauses 6, 7, 10 and 12: reports you choose to send (some of which carry a position), a live trip you choose to share (deleted within 30 days after its link stops working), and positions used for a single lookup and then discarded.
5.2 No advertising or ad-tech SDKs, and no advertising identifier.
5.3 No sale or sharing of Personal Information for anyone's marketing.
5.4 No decision about you with legal or similarly significant effects based solely on automated Processing (section 71 (Automated decision making) of POPIA), and no profiling for advertising. One automated check affects notifications only: an installation that behaves like an app-store review or test device stops receiving notifications. If you think this has happened to you, contact us and we will switch them back on.
5.5 No audio recording. The microphone is used only while you are making a voice report (clause 8), and nothing it hears is kept.
6. User Reports and Feedback
6.1 You can suggest updates to risk areas and roads, rate trips, report what you see on the road, and send feedback or bug reports without an account. When you submit a report, we store:
6.1.1 your selections: the risk tier you suggest, the kinds of incident you select, and the timing you choose;
6.1.2 whatever you type in the note or message field (please do not include Personal Information about yourself or others); a report made during a drive fills in the road you were driving on, and one made from the car screen or through Siri also your speed and direction of travel at that moment;
6.1.3 the area or road the report concerns (and any line or area you draw, with the points you tapped), the time band, and the App version;
6.1.4 an Installation ID generated on your device, used to spot duplicate or abusive submissions, to find your reports if you ask us about them, and to count your accepted reports towards free Premium (clause 12.10); it is not an account and identifies the installation, not you;
6.1.5 your email address, only if you choose to give it, used only to reply to that report.
6.2 Trip ratings store coarse trip statistics (such as a distance bucket, the time band, the route option and whether a reroute happened) and, for each rated area or road the drive passed through, its name and your answer, but never your start or end locations. A rating is sent when you tap Good or Not good (with any details you then add), or when you close the rating after answering at least one question.
6.3 "This route looks wrong" reports store your comment, the destination's name, the route option, its distance and time, the metro, the time band, the App version and the Installation ID, together with the start and end rounded to about 100 m, the lines of the routes we offered without their first and last 200 m, and the names of the risk areas and roads each route avoided or passed. The review team uses them to find and fix routing mistakes.
6.4 A navigation log you send from Settings › Help & About (Help & feedback) helps us find a fault. You choose the version without locations, or the full log, which includes positions and place names from your recent drives. It goes by email to admin@tsamayaapp.co.za with your Installation ID and a summary of your settings.
6.5 Reports are suggestions for human review; they never change the live dataset automatically, except for speed cameras: a camera reported at the same spot from three different installations is added to the map without waiting for review, and drivers' answers to "still there?" on a reported camera extend, shorten or end how long it shows. Each such answer stores the Installation ID, so one installation counts once. When a report arrives, the review team is told by email (sent through Resend) and by a notification on their phones (sent through Expo), which can carry the report's text and place name.
6.6 Some reports are also checked by Claude, an AI assistant made by Anthropic, to help the review team: area and road reports and trip ratings with details automatically, and other reports, such as crime spot reports, when the team asks. We use Claude through Anthropic's API under Anthropic's commercial terms, which do not allow Anthropic to train its models on what it receives. Claude receives what the report says, its area, road, pinned point or rounded spot and the street address nearest to it, its timing, and what the App already holds there, such as the current rating or nearby hotspots. It never receives your Installation ID or email address. Claude may search public sources, and its answer is advice for the review team: it never approves or declines a report by itself. Anthropic's own terms and Privacy Policy (www.anthropic.com/legal/privacy) apply to what it receives.
6.7 Please do not include Special Personal Information, such as information about anyone's health or alleged criminal behaviour, or the name of any person, in a report or note. A crime spot report concerns a place, not a person. If a report contains Special Personal Information or other Personal Information about an identifiable person, the review team will remove it.
6.8 Some kinds of report carry a position, because the position is what is reported:
6.8.1 Police, roadblock and pothole notices are public: other drivers nearby see "Police reported ahead" for about an hour, and "Pothole reported ahead" for about four days. We store the spot where your car was when you reported, its direction of travel and the time. Your Installation ID and a scrambled form of your network address (a hash under a secret key that only our server holds, so nobody without that key can turn it back into the address) are kept apart from the notice, only to merge repeat reports and to limit abuse, and are never shown to anyone. Notices are deleted within 48 hours after they expire. If you pass a police, roadblock or pothole notice another driver reported, Tsamaya may ask you "still there?". Your answer is stored with your Installation ID and the same kind of scrambled network address, only to count each installation once and to limit abuse; neither is ever shown to anyone, and both are deleted with the notice. Answering "Still there" keeps the notice up for another hour, up to four hours after it was first reported (a pothole notice for another four days, up to 30 days after it was first reported). A roadblock report is also filed for the review team as a report under this clause (the road you were on, from the car screen or Siri your speed and direction, the time band and your Installation ID), kept as other reports are (clause 15).
6.8.2 Speed camera reports store the spot you reported, the kind of camera, the metro, the speed limit if you gave one, any comment you add, and the Installation ID, for the review team, which confirms or rejects the camera (clause 15 says how long the report is kept).
6.8.3 Crime spot reports (a hijacking or smash-and-grab spot you pin on the map) and suggested corrections to a hotspot's position store the spot you pinned, not where you are, with the place name nearest to it, the kind of spot, when it happened if you say, your comment and the Installation ID, for the review team. An approved spot is shown on every driver's map with a name and safety tip chosen by the review team; your comment and identifier are never shown.
6.8.4 On a road we have not rated yet, Tsamaya may ask during a drive "What colour is this road?". If you answer, we store the colour you chose, the road's name, the spot where your car was when you answered, the time band, the App version and the Installation ID, for the review team, which uses them to rate the road (clause 15 says how long the report is kept). If you close the question without answering, nothing is sent.
6.8.5 A one-tap road or area rating, or a one-tap crime or hazard report, sent while driving (on the phone, from CarPlay or Android Auto, or by voice with Siri) stores where your car was, rounded to about 100 m, and, where the App knows it, your direction of travel as one of eight compass points (such as "north-east"), with the Installation ID, for the review team. The team uses it to work out which road and which stretch you mean and to group reports about the same stretch. Claude (clause 6.6) receives the rounded spot and direction, and Mapbox receives the rounded spot to name the nearest roads for that check. Both are removed on the clock in clause 15. A report you write yourself in the report form carries no spot.
7. Live Trip Sharing, SOS and Guardian (optional)
7.1 You can choose to let someone follow your drive on a private web link. Nothing is shared unless you start it:
7.1.1 Share, during a drive, creates a link for that trip and opens your phone's share sheet, so that you choose who receives it.
7.1.2 SOS › Alert creates an emergency link and opens your phone's messaging app with a message to your emergency contact, which you send yourself. The message contains your exact position as a Google Maps link and the emergency link.
7.1.3 Guardian uses one lasting link for your installation, which you send once to someone you trust. After that, each time you switch Guardian on (for example from the car screen), your drive is published to that same link until you switch it off or arrive.
7.2 While a trip is shared, we store on our server (Supabase) your current location and heading, your destination (its position and name) and estimated arrival time, the route line you are driving (which starts where you set off, and so shows your starting point) and the Installation ID, but never your name or an account. If someone opens the link inside the Tsamaya App, their own Installation ID is stored with the trip so that their app can follow it. Only someone who holds the link (a random token that cannot be guessed) can see the trip, so share it only with people you trust.
7.3 When you end the trip or arrive, live updates stop and the private link expires 30 minutes later. While a trip is still active, the link can be viewed for up to 12 hours after your last update (SOS links for up to 24 hours, so that a helper can keep checking on you). We delete the trip's stored location, destination and route within 30 days after its link stops working, and sooner on request via the contact address. Apart from police, roadblock and pothole reports and the reports in clause 6 that carry a position, this is the only case where your location is stored on our server.
8. Voice Reports and Siri (optional)
8.1 If you tap Speak in the report screen (on your phone, CarPlay or Android Auto), Tsamaya asks for microphone and speech recognition access, then listens for a few seconds for what you say, such as "police" or "speed camera". Your phone's own speech service turns the words into text: Apple's speech recognition on an iPhone, and the speech recognition service on an Android phone (usually Google's). Depending on the phone and the language, that service may Process the audio on the phone or on the provider's servers, under the provider's own privacy terms.
8.2 Tsamaya uses the text only to choose the report type, and then files exactly the report a tap would (see clause 6). We do not record, store or send the audio, and we do not keep the text. If you ask Siri instead ("report police in Tsamaya"), Siri does the listening and passes Tsamaya only the report type. If you ask Siri for directions in Tsamaya, Siri (Apple) hears the place you name and passes it to Tsamaya, which looks it up like any search (clause 4). On Android Auto, a destination you say is heard by Google Assistant, which passes Tsamaya the words in the same way.
8.3 You can refuse or withdraw microphone and speech access at any time in your phone's settings. Every report can still be made by tapping.
9. Spoken Directions (natural voice)
9.1 With Natural voice on (Settings › Navigation, on unless you switch it off), each sentence Tsamaya speaks is made by Google Cloud Text-to-Speech through our server. Most sentences are directions such as "Turn left onto Jan Smuts Avenue". The closing sentences say where you have arrived, but in this voice the only destination or stop names they use are Home and Work: any other destination or stop (a street address, a place you named) is "your destination" or "your stop", so it never leaves your phone this way. Your phone's own voice, which sends nothing, still says the name.
9.2 Our server keeps the audio of each sentence in a cache it shares between drivers, so that the same sentence is never made twice. The cache stores a sentence's sound under a code made from its words, with no Installation ID and nothing else about you or your device, and it cannot be listed or browsed. Google receives only the sentence, from our server, never anything about you. Versions of the App before its October 2026 update could also send the name of a destination or stop in the closing sentence. Our server now answers such a sentence with the same sentence without the name ("You have arrived at your destination. Go well."), so the name is never made into speech or stored. Clips those versions made earlier remain in the cache, which cannot be listed and links them to no one. Switch Natural voice off and Tsamaya uses your phone's own voice, which sends nothing.
10. Usage Analytics and Crash Reporting
10.1 Tsamaya records usage events so that we can see whether people find the App useful, and what to improve or fix. Examples include the App being opened, a route being requested, shown, accepted, started, completed or abandoned, a reroute, a report being sent, a route being shared, and the Premium screen being shown or a purchase being made. These events carry only short, coarse details (such as the metro you are in, the route option chosen, rounded distances and durations, the safety grades of the options, and whether a route was rerouted), together with the Installation ID described in clause 6, a random number for that app session, the App version, the build channel and the platform. They never include your name, an account, your start or end locations, place names, or precise coordinates. We also keep a record of each installation (when it was first seen, its platform, app version and metro) so that we can count installations. We use these events to understand use in aggregate, to tell the team when a new installation first opens the App (with its platform and metro), and to recognise app-store review and test devices (clause 5); never to profile you for advertising or to decide anything else about you. You can switch usage events off at any time in Settings › Sharing & privacy (Share usage data).
10.2 Crash reporting is switched on. When the App crashes or meets an unexpected error, it sends a technical report to Sentry so that we can find and fix the fault. So that we can see how often the App crashes, the crash reporting software also tells Sentry when each app session starts and ends, and whether it ended in a crash, with the App version and a random identifier Sentry's software creates for this installation (not the Installation ID in clause 6); this happens whether or not usage events are switched on.
10.3 A crash report contains the error and its stack trace, your device model and operating system version, the App and update version, and the Installation ID described in clause 6. It also carries a short trail of recent app events (a reroute, a change in risk level, connecting to a car screen) and of the services the App recently called, so that we can see what led up to the failure.
10.4 That trail is filtered on your phone before anything is sent: place names, your starting point and destination, searches and coordinates are stripped out, a web request keeps only the service's name (such as "api.mapbox.com/directions"), never the rest of its address, and only simple values are allowed through. Versions of the App before its October 2026 update sent the full address of recent web requests, which for map, route and search requests can contain coordinates or the text of a search. A crash report never contains your name or an account. Sentry stores this data in the European Union.
10.5 We use crash reports only to fix faults. They are not used to profile you and are not shared for any other purpose.
11. Push Notifications (optional)
11.1 If you allow notifications, Tsamaya can tell you about road closures, protests and race-day disruption in your city. A second, separate switch covers news about new app features, and a third tells you, before fuel prices change, whether to fill up or wait: with Tsamaya Premium usually on the Monday before the change, otherwise at noon the day before. Nothing arrives unless your phone lets Tsamaya send notifications (you are asked first; older Android versions allow it when the App is installed). Once it does, the road closure switch is on until you switch it off. News about new features is sent only if you ask for it ("Turn on, with app news" when Tsamaya first asks, or its switch in Settings); our server sends app news only to a device whose driver chose it, so a version of the App from before October 2026, which cannot record that choice, gets none. Each switch can be turned off on its own at any time under Settings › Alerts › Notifications. The fuel price alert is on until you turn it off. On a device without Premium where you have not set that alert yourself, it follows the other two switches instead: it is on while either of them is on, and off when both are off. This does not apply to a device set up before the October 2026 update, where the alert stays on as though you had chosen it, as it was then. Turn all of them off, or block Tsamaya's notifications in your phone's own settings, and we delete this device's registration (in the second case, the next time you open the App).
11.2 To deliver notifications, we store the following for each device:
11.2.1 the push token that Expo, Apple or Google issues for that installation (a delivery address for the device, not a name, an account or a contact detail);
11.2.2 the Installation ID described in clause 6, so that a device which re-registers is recognised instead of duplicated;
11.2.3 the platform (iOS or Android) and the App version;
11.2.4 the metro you are in: a city name such as "Cape Town", chosen from the metros we cover, so that a Cape Town closure alert does not go to drivers in Johannesburg. It is never a set of coordinates, a street or a trip;
11.2.5 which of the switches are on (road closures, app news and the fuel price alert), and when you chose app news;
11.2.6 with the fuel price alert on: the fuel you chose, such as petrol 95, so that the alert names your fuel (both fuels when Premium's logbook has two vehicles on different fuels; none until you choose one, and the alert then names petrol 95 and diesel 50 ppm), and with Premium a date until which this device should get it first: about a month after the current Premium period ends when the plan renews (so a renewal never interrupts the alert), the day after it ends when it will not renew, and about a month ahead for Premium with no end date. The App sends that date again each time it starts. With the alert off, neither is stored.
11.3 Every notification comes from Tsamaya, and each kind can be stopped with its switch in Settings. We do not send notifications on behalf of anyone else, or to carry anyone else's advertising. A person writes and approves every notification before it is sent, except the fuel price alert. That alert is drafted automatically from the official announcement of the new prices and is normally approved by a person. It is sent once per price change, first to Premium devices and then, at noon the day before the change, to every other device with the alert on. You can switch it off. Nothing is sent because of where you are or where you drive. If the delivery service tells us a token no longer works, for example after you uninstall the App, we stop using it.
11.4 App news notifications promote the App and its features and are therefore Direct Marketing. As section 69 (Direct marketing by means of unsolicited electronic communications) of POPIA requires, we send them only to a device whose user has chosen to receive them, and you may stop them at any time, free of charge, by switching off App news in Settings › Alerts › Notifications or by contacting us. We do not use your Personal Information for anyone else's Direct Marketing.
12. Tsamaya Premium (optional subscription)
12.1 Tsamaya Premium is an optional subscription (clause 11 of the Terms of Use). If you never subscribe, the only part of this clause that applies to you is that the App asks RevenueCat whether this device has Premium, which sends RevenueCat the random id and device details described below. On an iPhone, the first such check after installing also sends Apple's record of the App's own download (not a payment), so that a subscription already on the same Apple ID comes back without a tap.
12.2 When you subscribe, you pay Apple (App Store) or Google (Google Play) under their own terms. We never see your card or bank details, your name or your email address, unless you ask us to refund an annual plan bought on the App Store (clause 11.5 of the Terms of Use), when you send us your name, email address, bank details and Apple order ID.
12.3 To check that a subscription is real, and to keep Premium on the right account, the App uses RevenueCat, a subscription service. RevenueCat receives:
12.3.1 a random RevenueCat id that the App creates on your device. It is not an account, and it is not the Installation ID in clause 6 (the two are linked only if you claim free Premium for your reports, clause 12.10);
12.3.2 the store's purchase and renewal records for Tsamaya Premium: which plan, when it started, when it renews or ends, and whether a free trial or a billing problem applies;
12.3.3 basic device details sent with each request: the device model, operating system and app version, language and store country. On an iPhone, RevenueCat's software also sends Apple's identifier for vendor, an id that is the same for every app from one developer on that phone. Tsamaya does not give RevenueCat any advertising identifier.
12.4 On Android, Google's backup service may keep a paying subscriber's RevenueCat id so that Premium comes back after a reinstall.
12.5 RevenueCat tells our server (Supabase) when a subscription starts, renews, ends or moves to another phone. We keep that status (the RevenueCat id, the plan, the store, the dates and RevenueCat's message about each change) so that we can count subscribers and answer billing questions. It contains no name, email or location.
12.6 Premium's more detailed place searches go through our server to Google with your RevenueCat id, so that our server can count how many Premium searches that id made each day (the count is deleted after 35 days); the search itself is not stored.
12.7 We use this information only to provide Premium. It is not used for advertising or profiling.
12.8 One-time purchases (clause 12 of the Terms of Use: car photo unlocks and search packs) go through the same store and RevenueCat, which receives the same kind of purchase record for them. How many pack searches you have used is counted only on your phone.
12.9 Premium's other features work on your device. Trip history (with the SARS logbook's tags and notes, and trips you add by hand), your fuel settings, the vehicles, costs and odometer readings you give the logbook, the photos of odometers and slips you take or choose for it, and any Arrive by or logbook reminder are kept only on your phone (with the fuel price alert on, your fuel type is also stored with this device's notification registration, clause 11). For the logbook's "From", a drive that starts at one of your saved places (such as Home or Work) is named after it, on your phone. Tsamaya asks for your camera only when you tap to photograph an odometer or a slip, and a photo you choose instead is copied into the App; the photos are never uploaded. To measure a trip you add by hand, a place you search for is looked up like any search (clause 4), the two places you pick are sent to Mapbox for a route, as for any route, and only their names are kept with the trip. A logbook you export, and its photos, are files that go only where you send them. Fuel cost and toll prices (for the vehicle class you choose) read the official fuel prices and toll tariffs from our public lists on our server, which contain no information about you, and Arrive by asks Mapbox how long the route takes at the time you would leave.
12.10 Free Premium for your reports. Road and area reports that the review team accepts earn free months of Premium (clause 11.11 of the Terms of Use). To show how far yours have come, the App sends our server your Installation ID when a report of yours is accepted and when you open Settings or the Premium screen, and our server counts the accepted reports that carry it; nothing new is collected for this. An accepted report counts for two years after it is accepted, until the Installation ID is removed from it (clause 15). When you tap Claim, the App also sends your RevenueCat id. Our server reads RevenueCat's Premium records for that id (to see whether a paid plan or a free month is already running) and asks RevenueCat to switch Premium on for it until a set date. We keep a record of each month given (the two ids, when it starts and when it ends) so that a month is given only once. This record is the only place where the two ids are linked, and it is not used for anything else.
13. Operators and Other Recipients
13.1 We share Personal Information only with the Recipients listed below, and only the information each needs for the task described. We do not sell Personal Information.
| Provider | Role | Data touched |
|---|---|---|
| Mapbox, Inc. (USA) | Map tiles, routing, street names and addresses (reverse-geocoding), place search when Google and HERE cannot answer, the map on our trip page, and naming the roads near a reported place for the review team | Coordinates, search text (as a last resort), IP, device metadata, and, in versions of the App before October 2026, the map software's own usage data (see Mapbox's privacy policy) |
| Google LLC (USA) | Place search and autocomplete (Google Maps Platform, Places API) | Destination search text and the position at the centre of the search (see Google's privacy policy); for a Premium search, sent by our server |
| Google LLC (USA) | Spoken directions in the natural voice (Google Cloud Text-to-Speech), sent by our server | The sentence to be spoken (directions name streets), never a destination or stop name other than Home or Work: our server removes one an older version of the App sends (clause 9); nothing about you or your device |
| HERE Europe B.V. (Netherlands) | Backup place search, only when Google's search cannot answer (for example when it is over its daily limit), and opening hours for a place card that has none | Destination search text, or a place's name, and an approximate location rounded to about 100 m, or the HERE reference of a place it found earlier, sent through our server (Supabase), which keeps none of them. HERE's End User Terms (www.here.com/en-gb/terms/here-end-user-terms) and Privacy Policy (legal.here.com/en-gb/privacy) apply to those searches. Places found this way are kept on your device for at most 30 days unless refreshed, as HERE's terms require |
| Apple Inc. (USA) | Weather for the rain reminder (Apple WeatherKit) | Only the centre of an area about 5 km across, sent by our server; never your position, and nothing that identifies you or your device |
| Supabase, Inc. (servers in London, United Kingdom) | Hosts our public risk-zone dataset, user reports, reviewer authentication, usage events, push registrations, Premium status, the voice cache, and any live trip you choose to share; runs the server functions described in this policy | IP address and request metadata; report contents (including any email address given); reviewer email addresses; usage events; the Installation ID; shared-trip location and route |
| Apple Inc. (USA) | App distribution (App Store, TestFlight), and payment for Premium on iPhone | As set out in Apple's terms |
| RevenueCat, Inc. (USA) | Checks Premium subscriptions with Apple and Google (clause 12) | A random RevenueCat id, the store's purchase and renewal records, device model, OS and app version, language and store country; on iPhone, Apple's identifier for vendor |
| Apple Inc. (USA) / Google LLC (USA) | Speech to text for voice reports, only while you make one, and Siri or Google Assistant if you use them (clause 8) | The few seconds of speech while the App listens, under the provider's own terms. Tsamaya receives only the recognised text and keeps none of it |
| Google LLC (USA) | App distribution on Android (Google Play), and payment for Premium on Android | As set out in Google Play's terms |
| Functional Software, Inc. dba Sentry (EU data region, Germany) | Crash and error reporting | The error and its stack trace, device model, OS version, app and update version, the Installation ID, a filtered trail of recent app events, the names of the services recently called, and when each app session started and ended, under Sentry's own random identifier for the installation (clause 10) |
| Anthropic, PBC (USA) | Claude, an AI assistant that helps the review team check reports (clause 6), through Anthropic's API under its commercial terms | What a report says, its place, pinned point or rounded spot and the street address nearest to it, its timing, and what the App already holds there. Never your Installation ID or email address. Anthropic's own terms and Privacy Policy (www.anthropic.com/legal/privacy) apply to what it receives |
| Expo (650 Industries, Inc., USA) | App updates; push-notification delivery, if you opt in (clause 11); notifications to the review team about new reports (clause 6) | A random update identifier, app version and platform; device push token, notification title and text |
| Apple Inc. (USA) / Google LLC (USA) | Push delivery to the device itself (APNs / Firebase Cloud Messaging) | Device push token, notification title and text |
| Resend (Plus Five Five, Inc., USA) | Emails to the review team about new reports (clause 6) | The report's text, area and rating, never your Installation ID |
| Cloudflare, Inc. (USA) and GitHub, Inc. (USA) | Our Website's visitor statistics (Cloudflare Web Analytics) and hosting (GitHub Pages) (clause 21) | Pages visited, referring site, browser, device type and country; IP address and request logs |
| Xero Limited (New Zealand) | Accounting system in which we record donations, refunds and our other payments (clauses 4 and 21) | Names and payment references and, for refunds, bank account details |
13.2 Where a provider Processes information only on our instructions, it is an Operator under POPIA and is bound by a written agreement that requires it to keep the information confidential and secure (sections 20 (Information processed by operator or person acting under authority) and 21 (Security measures regarding information processed by operator) of POPIA). Where a provider's own terms and privacy policy also apply to what it receives (for example, the Apple App Store and Google Play, and Apple's and Google's speech services, Siri and Google Assistant in clause 8), that provider decides for itself how it handles that information and is responsible for it under its own terms and the law that applies to it.
13.3 We may also disclose Personal Information to our professional advisers (such as our attorneys and accountants), who are bound by a duty of confidentiality; to the South African Revenue Service, the Information Regulator, courts and other authorities where the law requires it; and to a buyer of, or investor in, our business, subject to confidentiality undertakings and to this policy.
14. Information Sent Outside South Africa
14.1 Most of these providers Process information outside South Africa: in the United Kingdom (Supabase), the European Union (Sentry, HERE), and the United States (the others), and Xero, a New Zealand company, stores information in the United States. Section 72 (Transfers of personal information outside Republic) of POPIA allows this where the Recipient is subject to a law, binding corporate rules or a binding agreement that gives the information protection substantially similar to POPIA, or where the transfer is necessary to provide the service you asked for. Each provider is bound by its own data-protection terms with us, and the United Kingdom and the European Union have data-protection laws comparable to POPIA; for providers in the United States, which has no general data-protection law comparable to POPIA, we rely on the binding data-protection terms each provider has agreed with us and on the transfer being necessary to provide the service you asked for. We send each provider only what it needs for the task described above.
15. Retention
15.1 We keep Personal Information only for as long as we need it for the purpose for which we collected it, unless a longer period is required or authorised by law or reasonably needed for a lawful purpose related to our functions, as section 14 (Retention and restriction of records) of POPIA permits. The periods below are maximum periods. When a period ends, we delete or destroy the Personal Information, or de-identify it so that it can no longer be linked to you:
| Information | How long we keep it |
|---|---|
| Positions used for a single request (routes, searches, notices near you, the rain reminder), and search text | Not stored by us. Our hosting provider's routine request logs, which include IP addresses, are kept for no longer than 7 days |
| Shared live trips, SOS links and Guardian drives | Visible via the link while the trip is active (up to 12 hours after the last update; SOS links up to 24 hours); once you arrive or end the trip the link expires 30 minutes later. The stored location, destination and route are deleted within 30 days after the link stops working, or sooner on request |
| Police, roadblock and pothole notices, with their reporters' identifiers, hashed network addresses and still-there answers | Deleted a day after the notice expires |
| Weather answers for the rain reminder (clause 4) | Reused for 10 minutes for drivers in the same area and deleted within 48 hours; your position is not stored |
| Speed camera reports and answers | A report keeps your Installation ID and comment for up to two years after it is reviewed; an answer to "still there?" is deleted two years after you give it |
| Reports, suggestions, trip ratings, "This route looks wrong" reports and crime spot reports | Until reviewed and actioned, then up to two years as the record behind a change to the risk data. Two years after a report is reviewed, or two years after it was sent if it is never reviewed, the Installation ID, email address, note and Claude's notes on it are removed, along with the spot stored with an answer to "What colour is this road?" (clause 6.8.4) and the rounded spot and direction stored with a one-tap report (clause 6.8.5). The route lines and rounded start and end of a "This route looks wrong" report are deleted 12 months after the report |
| An email address you add to a report | Until we have replied, and at most 12 months |
| A navigation log you email to us | Until the fault it helps with is solved, and at most 12 months |
| Usage events and installation records | Usage events are deleted after 24 months; an installation record's identifier is replaced once the installation has sent no usage event for 24 months, so only the count remains |
| Crash reports | Deleted by Sentry after at most 90 days |
| Push registrations (clause 11) | Retained while notifications are switched on. Deleted immediately when you turn all the notification switches off, or the next time you open the App after blocking Tsamaya's notifications in your phone's settings; a registration the delivery service reports as uninstalled is retired and deleted within 6 months. The record of a notification we sent keeps the device tokens it went to for 30 days |
| Premium records (clause 12) | Kept while the subscription is active and then for five years from the date on which the tax return to which they relate is submitted, as section 29 (Duty to keep records) of the Tax Administration Act 28 of 2011 requires; the daily count of Premium searches is deleted after 35 days. RevenueCat keeps its own records under its terms |
| Records of free Premium given for reports (clause 12.10) | Deleted two years after the free month ends |
| Refund requests and records of refunds paid (Apple order ID, name, email address and bank account details) | Used only to verify and pay the refund. Kept for five years from the date on which the tax return to which they relate is submitted, as section 29 (Duty to keep records) of the Tax Administration Act 28 of 2011 requires |
| Donation records (the name and payment reference your bank shows us) (clause 21) | Kept for five years from the date on which the tax return to which they relate is submitted, as section 29 (Duty to keep records) of the Tax Administration Act 28 of 2011 requires |
| Voice cache (clause 9) | Kept while it is useful to avoid making the same sentence twice. It holds no identifier, and since the October 2026 update nothing new in it names a destination or stop other than Home or Work; clips earlier versions made remain, unlisted and linked to no one. Clips are not deleted after a set period, because the cache holds no Personal Information |
| Requests you make under clause 18, our responses and the record of each Request | Five years after the Request is closed, after which they are securely destroyed |
| Website request logs and visit statistics (clause 21) | Request logs, which include IP addresses, are kept by GitHub, our hosting provider, under its own privacy statement, and we have no access to them; visit statistics are kept only in aggregate form, which cannot be linked to you |
| Reviewer accounts | Retained while the reviewer is authorised, and deleted within 30 days after the reviewer's authorisation ends |
| On your phone: saved places, recent searches, saved routes (up to 30), settings, trip history, the logbook's vehicles, costs, readings and photos, the emergency contact, search counts and the navigation log | Kept until you delete them or uninstall the App. Trip history, and the logbook's costs and readings with their photos, keep at most the last 26 months (so a tax year can still be exported after it ends), and you can delete them at any time in the App (Trip history, Delete trip history); search counts keep the last 14 days; the navigation log keeps the last 72 hours. Uninstalling Tsamaya removes everything it kept on your phone. Your phone's own backup (iCloud or Google) may include this data; it stays in your own account and we cannot see it |
| Places found through HERE and kept on your phone | At most 30 days unless refreshed from HERE, as HERE's terms require; a recent search found through HERE is deleted after 30 days |
16. Security
16.1 We protect the information we hold with transport encryption (HTTPS/TLS) on all network calls and row-level security on our hosted database. Reports are stored under insert-only access rules: the App's public key cannot read them back. Only authorised reviewers can read reports, and only through accounts restricted to that work. Our providers are bound by their own data-protection terms. No system is completely secure, and we cannot guarantee absolute security.
16.2 Our technical and organisational measures, which we take as section 19 (Security measures on integrity and confidentiality of personal information) of POPIA requires, include:
16.2.1 encryption in transit (HTTPS/TLS) on every network call;
16.2.2 row-level security on our database, with reports stored under insert-only access rules so that the App cannot read them back;
16.2.3 access to reports only by authorised reviewers, through individual accounts restricted to that work;
16.2.4 data minimisation: saved places, trip history, the logbook and your emergency contact stay on your phone, and network addresses stored with police, roadblock and pothole notices are kept only as a keyed hash;
16.2.5 filtering on your phone that removes place names, coordinates and search text from crash reports before they are sent;
16.2.6 the retention periods in clause 15, enforced by automatic daily deletion jobs;
16.2.7 written agreements with our Operators that require them to keep Personal Information confidential and secure; and
16.2.8 regular review of these measures, and updating them as risks and technology change.
16.3 If we have reasonable grounds to believe that someone has gained unauthorised access to Personal Information we hold, we will, as soon as reasonably possible after discovering the compromise, notify the Information Regulator and, where we can identify and reach them, the people affected, as section 22 (Notification of security compromises) of POPIA requires.
17. Your Rights (POPIA)
17.1 In terms of section 5 (Rights of data subjects) of POPIA, and subject to the limits set out in POPIA and PAIA, you have the right to:
17.1.1 ask, free of charge, whether we hold Personal Information about you, and for a copy of it, including the identity of the third parties, or categories of third parties, who have or have had access to it (section 23 (Access to personal information) of POPIA);
17.1.2 ask us to correct or delete it where it is inaccurate, irrelevant, excessive, out of date, incomplete, misleading or obtained unlawfully, and to destroy or delete a record of it that we are no longer authorised to keep (section 24 (Correction of personal information) of POPIA);
17.1.3 be told what Personal Information we collect and why, as this policy does (section 18 (Notification to data subject when collecting personal information) of POPIA), and to be told if someone has accessed or acquired your Personal Information without authority (section 22 (Notification of security compromises) of POPIA);
17.1.4 object to our Processing it on reasonable grounds where we rely on our legitimate interests (section 11(3)(a) (Consent, justification and objection) of POPIA); many of these choices are also switches in the App (location, notifications, usage events, natural voice);
17.1.5 object at any time, free of charge, to the Processing of your Personal Information for Direct Marketing, such as App news notifications (section 11(3)(b) (Consent, justification and objection) of POPIA and section 69 (Direct marketing by means of unsolicited electronic communications) of POPIA);
17.1.6 withdraw your Consent at any time, where we rely on it, without affecting the lawfulness of Processing that took place before you withdrew it (section 11(2)(b) (Consent, justification and objection) of POPIA);
17.1.7 not be subject to a decision based solely on automated Processing that has legal consequences for you or affects you to a substantial degree (section 71 (Automated decision making) of POPIA);
17.1.8 complain to the Information Regulator (section 74 (Complaints) of POPIA) and institute civil proceedings regarding any interference with your Personal Information (section 99 (Civil remedies) of POPIA). The Information Regulator's details are:
17.1.8.1 Physical Address: Woodmead North Office Park, 54 Maxwell Drive, Woodmead, Johannesburg, 2191;
17.1.8.2 Telephone: 010 023 5200;
17.1.8.3 Toll-free: 0800 017 160;
17.1.8.4 Email Address: enquiries@inforegulator.org.za;
17.1.8.5 Website: https://inforegulator.org.za.
17.1.8.6 The Information Regulator receives complaints about Personal Information through its eServices portal (https://eservices.inforegulator.org.za).
18. How to Exercise Your Rights
18.1 To exercise any right, email info@tsamayaapp.co.za, or contact us in any other way that suits you. There is no charge. Because Tsamaya has no accounts, we find what we hold through your installation: tell us what you sent and roughly when, or send us your Installation ID, which you can copy from Settings › Help & About. We may ask for this to confirm that a Request comes from the installation concerned. We respond within 30 days. Our PAIA Manual, which explains how to request any record we hold and what it costs, is at tsamayaapp.co.za/paia.html. Because we hold little Personal Information about drivers, many Requests will be answered by confirming what we hold for your installation, which is often nothing beyond what is on your phone.
18.2 You may make a Request by completing the Data Subject Request Form in Annexure A and sending it to our Information Officer at info@tsamayaapp.co.za, or by post or hand delivery to the address in clause 23. You may instead use the forms prescribed by law, which we will provide on request:
18.2.1 Form 1 of the POPIA Regulations, to object to the Processing of your Personal Information;
18.2.2 Form 2 of the POPIA Regulations, to request the correction or deletion of your Personal Information, or the destruction or deletion of a record of it; and
18.2.3 Form 2 of the PAIA Regulations (Request for Access to Record), to request access to a record under PAIA, as explained in our PAIA Manual.
18.3 We will not refuse to consider a Request merely because it was not made on a particular form. If you need help, for example because of a disability or because you cannot read or write, our Information Officer will help you to make your Request.
18.4 If you make a Request on behalf of someone else, you must provide proof of your authority to act for that person, such as a power of attorney or, for a child, proof that you are the child's parent or guardian.
18.5 To protect your Personal Information from being disclosed to, or changed by, the wrong person, we will verify that a Request comes from the installation or person concerned before we act on it. For information linked to your installation, the Installation ID is enough, and we will not ask for your identity document. We use the information you give us for verification only for that purpose.
18.6 When we receive your Request, we will record it, give it a reference number and send you a written acknowledgement within two Working Days, confirming the date on which we received it, any information we still need from you and the date by which we will respond.
18.7 We will deal with your Request within the following periods, calculated from the date on which our Information Officer receives it:
18.7.1 stopping Direct Marketing: immediately, with confirmation within five Working Days;
18.7.2 an objection or a withdrawal of Consent: confirmation within five Working Days;
18.7.3 correction, deletion or destruction: as soon as reasonably practicable, and in any event within 30 days; and
18.7.4 confirmation of whether we hold your Personal Information, and access to it: within 30 days, which we may extend once by up to 30 days where PAIA permits, in which case we will tell you in writing, with reasons, before the original period ends.
18.8 If we do not agree that information should be corrected, we will, at your request, attach a note to it recording that you asked for it to be corrected. Where a correction or deletion affects decisions about you, we will, where reasonably practicable, inform the persons to whom we disclosed the information.
18.9 We do not charge any fee for confirming whether we hold your Personal Information, for an electronic copy of it, for correcting or deleting it, for accepting an objection or a withdrawal of Consent, or for stopping Direct Marketing. A fee may be payable only where you ask for printed copies of records, as set out in our PAIA Manual, and we will tell you before any fee is due.
18.10 We may refuse a Request for access, in whole or in part, only on the grounds set out in Chapter 4 of Part 3 (Grounds for refusal of access to records) of PAIA, for example where giving you access would unreasonably disclose Personal Information about another person. If we refuse, we will tell you in writing, give adequate reasons and inform you of your right to complain to the Information Regulator or to apply to court.
18.11 If you are not satisfied with our response, you may ask our Information Officer to reconsider it, and the Information Officer will respond in writing within ten Working Days. You may also, at any time, complain to the Information Regulator, whose details are set out in clause 23.
18.12 We keep a record of each Request, how it was verified, the action taken and the outcome for the period set out in clause 15, with access limited to our Information Officer.
19. Children
19.1 Tsamaya is a driving app for people aged 18 or older and is not directed at children. We do not knowingly Process children's Personal Information. If you believe a child has sent us a report or shared a trip, contact us and we will delete it.
20. Risk Data is not Personal Information
20.1 The risk zones and road classifications shown in the App are derived from public, aggregated sources (including SAPS crime statistics and OpenStreetMap) and curated review. They describe places, never individuals, and contain no Personal Information.
21. Our Website
21.1 Our Website, tsamayaapp.co.za, is hosted on GitHub Pages and counts visits with Cloudflare Web Analytics, which sets no cookies and stores nothing on your device. It records the pages visited, the referring site, browser and device type and country, to show us how many people visit and which pages they read; it is not used to identify you. The hosting provider receives your IP address with each request, as it does for any website. The contact page opens your own email app; the Website itself collects nothing you type. If you make a donation by EFT using the bank details on our sponsor page, our bank shows us your name and the reference on the payment, which we record in our accounting system (Xero); we use them only to record and, if you ask, give you a receipt for your donation, and keep them for the period set out in clause 15. Donations are not tax-deductible.
21.2 The trip page (track.html) shows a shared trip (clause 7) to whoever holds its link: the viewer's browser fetches the trip from our server and draws it on a map from Mapbox, so Mapbox receives the viewer's network address and the map area around the trip. The trip page does not load the visitor statistics, because its address carries the trip's private link. We do not record who views it.
22. Changes
22.1 We will publish changes here and update the version and effective date at the top. We will draw your attention to material changes in the App, before the change takes effect, and where a change involves Processing your Personal Information for a new purpose, we will ask for your Consent where POPIA requires it.
23. Contact details
23.1 If you have a question about this policy or about how we handle your Personal Information, or wish to make a Request, please contact our Information Officer:
Information Officer: Kyle Kimble (Director)
Email: info@tsamayaapp.co.za
Telephone: 073 285 5752
Physical and postal address: 10 Audocia Place, Hurlingham Manor, Sandton, 2196, South Africa
Deputy Information Officer: None appointed
23.2 If you are not satisfied with how we have dealt with your concern, you may contact the Information Regulator:
Physical address: Woodmead North Office Park, 54 Maxwell Drive, Woodmead, Johannesburg, 2191
Telephone: 010 023 5200; toll-free: 0800 017 160
General enquiries: enquiries@inforegulator.org.za
Complaints about Personal Information (POPIA): Through the eServices portal at https://eservices.inforegulator.org.za
Complaints about access to information (PAIA): PAIAComplaints@inforegulator.org.za
Website: https://inforegulator.org.za
24. Version history
24.1 The table below records the changes made to this policy. References to clause numbers in versions before 1.20 are to the numbering used at the time.
| Version | Date | Summary of changes |
|---|---|---|
| 1.24 | 9 November 2026 | New clause 6.8.5: a one-tap rating or report sent while driving stores where your car was, rounded to about 100 m, and your direction as a compass point, so the review team can tell which stretch of road it means. Claude and Mapbox receive the rounded spot for that check. Clauses 6.6, 15 and the recipients table say so; it is removed after two years with the Installation ID. No other change. |
| 1.23 | 5 November 2026 | Clause 15: says what happens to a report nobody reviews (its identifiers are removed two years after it was sent, as already happened), and the spot stored with an answer to "What colour is this road?" is now removed at the same time. No retention period is longer, and nothing new is collected. |
| 1.22 | 4 November 2026 | Free Premium for your reports: clauses 3, 6 and 12 (new clause 12.10) explain how accepted reports are counted by Installation ID and how a claimed month is given through RevenueCat, the processing table adds a row for it, and clause 15 sets how long the record of each month given is kept. |
| 1.21 | 4 November 2026 | Clause 6.8.4 added: an answer to the in-drive "What colour is this road?" question stores the spot where your car was, which the App already sent but clause 6.8 did not list. No other change to what we collect, why, who receives it, how long we keep it, or your rights. |
| 1.20 | 1 November 2026 | Legal review by ZS Attorneys Inc. (22 October 2026): refund requests for App Store annual plans added to clauses 4, 12 and 15; retention periods confirmed; donations recorded in Xero (clauses 13, 15 and 21); the Responsible Party's details tabulated; all paragraphs numbered and clauses renumbered (bullet points replaced by numbered clauses); new clause 1 (Introduction) and clause 2 (Definitions), with defined terms used consistently; the Summary explains which information is de-identified and which is Personal Information; clause 4 adds how we collect Personal Information and the rule on further Processing; clause 6 adds Special Personal Information; clause 11 adds Direct Marketing; clause 13 explains Operators and other Recipients; clause 14 explains the basis for transfers to the United States; clause 15 sets specific retention periods and adds new categories; clause 16 lists our security measures and notification of a security compromise as soon as reasonably possible; clause 17 sets out all your rights under POPIA; new clause 18 explains how to exercise them; clause 21 covers donations by EFT; clause 22 gives notice before changes take effect; new clause 23 (contact details) and Annexure A (Data Subject Request Form). On publication: the retention period for weather answers in clause 15 corrected to 48 hours, as clause 4 says, and Xero's region (the United States) given in clause 14. |
| 1.19 | 13 October 2026 | Clauses 1, 2 and 3: pothole notices, public like police and roadblock notices but shown for about four days, up to 30 days with "still there" answers; stored, kept and deleted as police and roadblock notices are. |
| 1.18 | 12 October 2026 | Wording edited for clarity and consistency throughout; no change to what we collect, why, who receives it, how long we keep it, or your rights. |
| 1.17 | 12 October 2026 | Clause 8: a link to our PAIA Manual. |
| 1.16 | 12 October 2026 | Clauses 3c and 5: when an older version of the App asks for a closing sentence that names a destination or stop, our server answers with the same sentence without the name, in the natural voice, instead of refusing it, so no version speaks the name in the phone's own voice. |
| 1.15 | 11 October 2026 | Pre-launch privacy review: added the Responsible Party's address and Information Officer; clause 1 now says where location goes, including our server for nearby notices, and that location runs in the background only during a guided drive or a car connection; added clause 3c on the natural voice (Google Cloud Text-to-Speech through our server; since the October 2026 update it names no destination or stop but Home and Work, our server refuses other names, and the shared cache cannot be listed); clauses 1 and 5 add Mapbox's place search as the last fallback and say Mapbox's telemetry is switched off; clause 3 discloses "This route looks wrong" reports, the rated areas and roads in trip ratings, the navigation log you can send, and the review team's email and notifications; clause 3a now says the shared route line shows your starting point, adds SOS and Guardian, viewers' identifiers and a 30-day deletion; clause 3 adds the roadblock report filed for review, a keyed hash of police reporters' network addresses, and Claude through Anthropic's API under commercial terms; clause 4 says usage events are linked to the Installation ID, what they are used for and that they can be switched off, that crash reports keep only a service's name from a web address, and that Sentry receives a record of each app session; clause 4a: app news only for drivers who ask for it; clause 4b discloses the server-side count of Premium searches; clause 5 adds Supabase's London region, Google Cloud Text-to-Speech, HERE place details, Expo updates, Resend, Cloudflare and GitHub; new clause 5a on transfers outside South Africa; clause 6 gives a period for every kind of data; clause 7 adds breach notification; clause 8 explains how to make a request without an account (the Installation ID in Settings) and corrects the Information Regulator's complaints address; clause 9 sets the age at 18; new clause 11 on our Website. |
| 1.14 | 11 October 2026 | Clause 3: if you pass a police or roadblock notice another driver reported, Tsamaya may ask you "still there?"; your answer is stored with your Installation ID and a hashed form of your network address only to count each installation once and to limit abuse, and both are deleted with the notice; "Still there" keeps the notice up for another hour, up to four hours after it was first reported. |
| 1.13 | 6 October 2026 | Clauses 3 and 5: Claude, an AI assistant made by Anthropic, helps the review team check reports; it receives a report's content, place and timing, never your Installation ID or email address, its answer is advice only, and Anthropic's own terms and privacy policy apply to what it receives; clause 1 lists Anthropic and Mapbox against reports. |
| 1.12 | 5 October 2026 | Clause 4a: with the fuel price alert on, we store the fuels it is about: the one you chose, both when Premium's logbook has two vehicles on different fuels, or none until you choose one, when the alert names petrol 95 and diesel 50 ppm. |
| 1.11 | 4 October 2026 | Clause 3: a hijacking or smash-and-grab spot you pin on the map, and a suggested correction to a hotspot's position, carry the spot you pinned, not where you are; an approved spot is shown on every driver's map without your comment or identifier; a speed camera report can carry a comment, and one reported from three installations at the same spot is added without review, and drivers' still-there answers can extend, shorten or end one. |
| 1.10 | 4 October 2026 | Clauses 1, 4b and 6: Premium's SARS logbook keeps up to two vehicles, their costs and odometer readings, and photos you take or choose of odometers and slips, all only on your phone; Tsamaya asks for the camera only when you tap to take such a photo; a trip you add by hand can be measured by sending the two places you pick to Mapbox for a route, as for any route, and only their names are kept; the logbook's reminders are notifications set on your phone, not sent by us. |
| 1.9 | 1 October 2026 | Clause 4b: one-time purchases, car photo unlocks and search packs, go through the same store and RevenueCat; pack searches used are counted only on your phone. |
| 1.8 | 1 October 2026 | Clauses 1 and 5: the rain reminder asks Apple WeatherKit about the weather in an area about 5 km across, through our server, which receives your position rounded to about 1 km and does not store it; Apple never receives your position. |
| 1.7 | 30 September 2026 | Clause 4a: the fuel price alert is now for every device with its switch on, with Tsamaya Premium usually on the Monday before a change and otherwise at noon the day before; for it we store your fuel type, and a Premium end date only with Premium; clauses 1, 4b and 6: trip history keeps about 26 months, also records drives made without a route while Tsamaya is open (free drive, or CarPlay or Android Auto connected), and, for Premium's SARS logbook, the name of the saved place a drive started at, and your business or personal tag and note, all on your device; toll prices come from our public list of toll tariffs; a logbook you export goes only where you send it. |
| 1.6 | 28 September 2026 | Clause 4a: Premium's fuel price alert, a third notification switch, is the one notification sent automatically, once per price change, and for it we store your fuel type and until when you have Premium; clause 4a also lists which switches are on, and blocking Tsamaya's notifications in your phone's settings deletes the registration too; clause 6 and the short version to match, and a note that your phone's own backup may include what is kept on it. |
| 1.5 | 28 September 2026 | Trip history, the search usage meter and the fuel settings are kept only on your device, clauses 1 and 6 and the short version; Arrive by sends Mapbox the departure time it checks, and a leave reminder is set on your device, clause 1; fuel prices for Premium's fuel cost come from our public price list, which holds nothing about you, clauses 1 and 4b. |
| 1.4 | 28 September 2026 | Added clause 4b on Tsamaya Premium, the optional subscription: Apple or Google take the payment, RevenueCat checks subscriptions using a random id it creates and the store's purchase records, on iPhone RevenueCat also sends Apple's identifier for vendor, and our server keeps each subscription's status; RevenueCat added to clause 5, Premium to clauses 1 and 6. |
| 1.3 | 27 September 2026 | Added HERE as a backup place-search provider in clauses 1 and 5: when Google's search cannot answer, for example because it is over its daily limit, your search text and an approximate area are sent to HERE through our server, and HERE's own End User Terms and Privacy Policy apply to that search. |
| 1.2 | 26 September 2026 | Added clause 3b on voice reports: the microphone and speech recognition are used only when you tap Speak or ask Siri to make a report, and no audio is kept; clause 3 now describes the two report types that carry a position, live police and roadblock notices and speed camera reports; clauses 1, 2 and 5 updated to match. |
| 1.1 | 9 September 2026 | Corrected clause 4a, which said the stored metro is chosen from six areas when the service covers twelve, and aligned the clause 1 description and clause 3a wording with the definition of "lower-risk" in the Terms of Use. |
| 1.0 | 25 August 2026 | Enabled crash reporting and disclosed it before switching it on, as v0.9 undertook to do: clause 4 now describes what a crash report contains, that the event trail is filtered on-device to remove coordinates, place names and destinations, and that the data is stored in the EU; clause 5 adds Sentry as a processor. |
| 0.9 | 9 August 2026 | Added clause 4a disclosing optional push notifications: the device push token, platform and coarse metro stored per device, the two independent opt-in switches, and Expo/APNs/FCM as delivery processors. |
| 0.8 | Not recorded | Moved the Responsible Party from Kyle Guy Kimble personally to Tsamaya (Pty) Ltd, unified contact on info@tsamayaapp.co.za, added Google Play as an Android distribution processor, and generalised iOS-only wording, all ahead of the Google Play listing under the company's developer account. |
| 0.7 | Not recorded | Corrected live-trip link expiry to match implementation (active trips 12 h rolling, ended/arrived trips ~30 min, SOS links 24 h), clauses 3a and 6. |
| 0.6 | Not recorded | Disclosed optional live trip sharing, clauses 3a, 2, 5 and 6. |
| 0.5 | Not recorded | Added Google Places API as the place-search processor, clauses 1 and 5. |
Annexure A: Data Subject Request Form
Sections 5, 11(3), 23 and 24 of POPIA. This form appears as Annexure A to the Privacy Policy and as Annexure B to the PAIA Manual. Clause 18 of the Privacy Policy explains how we deal with a Request made on it, including verification, timelines and fees. There is no charge, except for printed copies requested under PAIA. Words in this form that begin with a capital letter have the meanings given to them in the Privacy Policy.
Notes
1. Use this form for any Request under POPIA: access to your Personal Information, correction, deletion or destruction, an objection (including to Direct Marketing), withdrawal of Consent or review of a decision based solely on automated Processing. It contains all the information required by Form 1 (objection) and Form 2 (correction or deletion) of the POPIA Regulations, so you do not need to complete those forms separately.
2. Affidavits or other documentary evidence in support of an objection or a Request for correction, deletion or destruction may be attached.
3. If the space provided is inadequate, attach additional pages and sign each page.
To: Tsamaya (Pty) Ltd (Responsible Party)
Name of Responsible Party: Tsamaya (Pty) Ltd (registration number 2023/990736/07)
Information Officer: Kyle Kimble (Director)
Postal and physical address: 10 Audocia Place, Hurlingham Manor, Sandton, 2196, South Africa
Telephone: 073 285 5752
Email: info@tsamayaapp.co.za
Part A: Your details
Name and surname (optional where the Request concerns only information linked to your installation): ____________________
Email address or other contact detail for our reply: ____________________
Residential, postal or business address (optional): ____________________
Contact number(s) (optional): ____________________
Installation ID (Settings › Help & About in the App), if the Request concerns information linked to your installation: ____________________
Your relationship with Tsamaya: ☐ Driver who uses the App ☐ Person who followed a shared trip ☐ Visitor to the Website ☐ Supplier, donor or other contact ☐ Other (please specify): ____________
Part B: Details of representative (complete only if you act on behalf of the Data Subject)
Name and surname: ____________________
Email address and telephone number: ____________________
Capacity in which you act: ☐ Parent or guardian ☐ Holder of a power of attorney ☐ Other (please specify): ____________
Part C: Type of Request (tick all that apply)
Request: ☐ Confirm whether Tsamaya holds my Personal Information ☐ Provide a copy or description of my Personal Information and the persons who have had access to it ☐ Correct my Personal Information ☐ Delete or destroy my Personal Information ☐ Object to the Processing of my Personal Information on reasonable grounds (section 11(3)(a) of POPIA) ☐ Stop Direct Marketing (App news notifications) (section 11(3)(b) of POPIA) ☐ Withdraw my Consent ☐ Review a decision about me based solely on automated Processing ☐ Other (please specify): ____________
Part D: Details of your Request
Personal Information or report concerned, and roughly when you sent it: ____________________
For correction: the information that is incorrect and the correct information: ____________________
For deletion, objection or withdrawal of Consent (sections 11(3) and 24(1) of POPIA): the information concerned and your detailed reasons: ____________________
Any other information that will help us to deal with your Request: ____________________
Part E: How you would like to receive our response
Manner: ☐ By email (free of charge) ☐ By post ☐ Inspection at our address
Preferred language: ☐ English ☐ Other: ____________
Part F: Supporting documents (attach copies)
Documents: ☐ Proof of authority, if you are a representative (for example, a power of attorney or proof of guardianship) ☐ Documents supporting a Request for correction, deletion or destruction, or an objection (affidavits or other documentary evidence) ☐ A copy of your identity document, only if the Request concerns information that identifies you by name (not needed for information linked to your Installation ID)
Part G: Declaration
I confirm that the information in this form is true and correct, and that I am the Data Subject or am authorised to act on the Data Subject's behalf. I understand that Tsamaya will use the information in this form only to verify the Request and to deal with it.
Signed at ____________________ on this ______ day of ____________________ 20____
______________________________________
Signature of Data Subject / authorised person
For office use only
Reference number: ____________________
Date received: ____________________
Verification (date and method): ____________________
Acknowledgement sent (date): ____________________
Outcome and date of response: ____________________
Information Officer signature: ____________________