Privacy Policy

Last updated: 25 October 2026 · Versi Bahasa Melayu

In short

  • While you navigate, your location is sent to Gerak Luu servers to look up speed limits and to find a new route if you leave yours.
  • Searches and destinations are sent to our servers to find places and routes. They are answered, not stored.
  • A map problem report you choose to send contains a location, and the note, line or photo you add.
  • Data is linked to the app installation, not to your name or email. No account is needed.
  • No ads, no tracking, your data is not sold. Delete everything in Tetapan (Settings) › Padam data saya.

1. Who we are

Gerak Luu is operated by APPVOLUSI SDN. BHD. (“we”), the data user for the personal data described here under Malaysia’s Personal Data Protection Act 2010 (PDPA).

This policy covers the Gerak Luu iPhone app (including its CarPlay screen), the server services the app uses, the Gerak Luu web console, and this website (gerakluu.com).

2. What we collect and why

2.1 Installation identifier

The first time the app opens, it registers with our server and receives a random token. The token is kept in your iPhone’s Keychain, on that device only, and is not carried to other devices in backups. The server stores only a hash of the token, never the token itself.

With the installation we store: the platform (iOS), app version, iPhone model (for example “iPhone15,2”), iOS version, when it was registered and when it was last used.

Why: to authenticate requests, to limit abuse (rate limits), and to make sure only you can see your own reports.

2.2 Location

  • On the phone: to show where you are on the map and to guide you.
  • While navigating: your current position is sent to the server to look up the speed limit of the road you are on, and to find a new route if you leave yours. Guidance continues when the screen is off or you switch apps (iOS shows the blue location indicator); this stops when navigation ends.
  • Planning a route: the start point, destination and route options (for example “Elak tol”, avoid tolls) are sent to calculate the route; the route’s shape is sent to calculate a toll estimate.
  • Search: if you allow location, your position is sent with a search so nearby places rank first.
  • Road closures: the map area on screen is sent to load road closures in that area.

Route, speed limit, toll and search requests are answered and not stored in our database. The iPhone app does not record or upload your drive (GPS) traces.

If you have turned “Precise Location” off, the app may ask for precise location temporarily while navigating, because an approximate location is not enough for turn instructions.

2.3 Search and Google Maps links

The text you search for is sent to our server and answered from our own places database. It is not stored.

If you paste a Google Maps short link (maps.app.goo.gl or goo.gl/maps), the short link holds no coordinates. Our server asks Google where the link points. Google receives the link and the IP address of our server, not your IP address. Full Google Maps links, coordinates and Plus Codes are read directly without contacting Google.

2.4 Map problem reports (your choice)

If you choose to report a map problem, the report contains:

  • the problem type, the problem’s location, and the nearest road;
  • your note, a line you draw on the map, and a photo you pick (if any);
  • the app version;
  • if sent from search (“Hasil tak betul?”, wrong result): that search text, the results shown, the result you picked, and your location at the time;
  • if sent while navigating: the route request (including the start point and destination), the instruction being given, the route’s shape, and the car’s position.

Photos are downscaled on the phone and re-processed on the server; photo metadata (EXIF, including any GPS location in the photo) is removed. The app asks for camera or photo access only when you want to add a photo, and only the photo you pick is sent.

Map problem reports are private: only you (the same installation, or the same account) and the Gerak Luu staff who review them can see them. Staff can change a report’s status and reply; the app checks for these updates when it is open. A report that could not be sent yet is kept on the phone until it is sent.

Why: to fix the map, search and routing.

2.5 Community road reports

Our service supports road condition reports (for example a pothole, a closed road or a flood) that other users can see. The current iPhone app does not send reports of this kind. When the feature is used, reports are shown to other users without the reporter’s identity (type, location, note, road name and time only). To prevent abuse, we keep a keyed hash of your network prefix (/24 for IPv4, /64 for IPv6, never the full address) and the installation’s age; the hash is deleted after 24 hours.

2.6 Accounts (optional, web console)

The iPhone app needs no account and has no sign-in. If you register an account through the Gerak Luu web console, we store your email, display name, phone number (if given), your password as an argon2id hash (never the password itself), and the saved places, vehicles and profile picture you add. The web console uses one necessary cookie, __Host-gerakluu_session (HttpOnly, SameSite=Strict, Secure), to keep you signed in, and keeps the installation token and theme preference in browser storage.

2.7 Data that stays on your phone

The following is kept on your iPhone only: saved places (for example Home, Work), a trip that can be resumed after the app is closed (destination, route options and time; offered for up to 2 hours), reports marked to send later, unsent reports and their photos, temporary map copies, and your settings. This data is sent only when you use it, for example as a route destination.

2.8 Server logs

Our servers keep technical logs for security and troubleshooting: IP address, time, request method and path, status code and response size. Request parameters (for example the coordinates for a speed limit, or search text) are not logged. Map tile request paths contain tile numbers, which roughly show which map area was loaded. These logs are kept in size-limited files that are overwritten automatically. Credentials are never written to logs.

2.9 This website

gerakluu.com uses no cookies, analytics, trackers or third-party resources. Fonts are self-hosted.

3. What we don’t do

  • We do not sell your data.
  • We show no ads and do not use your data for advertising.
  • We do not track you across other companies’ apps or websites, and the app contains no third-party analytics or advertising SDKs.
  • We do not ask for your name, email or phone number to use the app.

4. Consent and your choices

The first time you open the app, a “Sebelum anda mula” (Before you start) notice explains what is sent to our servers. We process your personal data with your consent and only to provide the app’s features.

  • Location, camera and photos are each requested by iOS when first needed. You can refuse or withdraw these permissions at any time in iOS Settings.
  • The map and search work without sharing your location. Turn-by-turn navigation needs location.
  • Reports are always your choice.
  • You can withdraw consent by stopping use of the app and deleting your data (section 7).

5. Who we share data with

We only share data with parties that process it on our behalf to run the service:

  • Cloudflare: all traffic to our servers passes through Cloudflare’s network (protection and delivery), and database backups are stored in Cloudflare R2 storage.
  • Our virtual server (VPS) provider, which hosts our servers and database.
  • Google: only to expand Google Maps short links you paste (section 2.3). No other data is sent to Google.

We may also disclose data when required by law or a valid court order. If staff correct an error in OpenStreetMap based on your report, only the map correction is shared, never your details.

Our servers are located in Malaysia, and Cloudflare’s network operates in many countries. Your data may be processed outside Malaysia; we only use providers that protect data to a standard comparable with the PDPA.

6. How long we keep data

DataPeriod
Route, speed limit, toll and search requestsNot stored; answered and forgotten.
Map problem reportsUntil you delete them. Once a report has been closed for 30 days, or 90 days after it was sent (whichever comes first), your precise location in the search and route context is rounded to about 1 km and the route shape is removed. The problem’s location, drawn line, search text and search results stay, because they are the map error to be fixed.
Photos of rejected or duplicate reportsDeleted 30 days after the status changed.
Network hashes for community reportsDeleted after 24 hours.
Installations and accountsUntil you delete them.
Database backupsUp to 30 days, then overwritten. Data you delete may remain in backups until this period ends.

7. Deleting your data

In the app: open search, tap Tetapan (Settings), then Padam data saya (Delete my data) under Privasi (Privacy). This:

  • deletes from our servers your map problem reports with their photos and status history, and any drive traces linked to this installation;
  • anonymises your community road reports (owner, note and photo removed; type, place and time kept because other users have already seen them), and marks still-active closed-road or flood reports as resolved;
  • revokes the installation token;
  • if you are signed in, deletes your account too (your password is required);
  • deletes on the phone: saved places, unsent reports, the resumable trip, temporary copies and credentials. Settings such as appearance are kept because they are not about you.

The server is deleted first. If you are offline, nothing is deleted and the app tells you. Road closures that staff created from your report remain (with no link to you) because they protect other drivers.

Deleting the app alone does not delete data on our servers. Use “Padam data saya” first, or contact us.

8. Your rights under the PDPA

You have the right to:

  • access the personal data we hold about you;
  • correct data that is inaccurate, incomplete or misleading;
  • withdraw consent and ask us to stop processing;
  • ask us to stop processing that is likely to cause you damage or distress.

You can see your own reports and their status in the app under Tetapan › Laporan saya (Settings › My reports). For other requests, email us at dev@appvolusi.com. We will reply within 21 days. Because the app does not ask for your name or email, we may ask for details to confirm the data is yours (for example details of a report you sent).

9. Security

  • All connections between the app and our servers use HTTPS.
  • Tokens and sessions are stored as hashes; passwords are stored as argon2id hashes.
  • Every recording is linked to its owner; other people’s data cannot be read through the API.
  • Rate limits restrict abuse; staff access is limited to staff accounts.
  • The token on your phone is kept in the iOS Keychain, for that device only.

No system is perfectly secure. If a data breach affects you, we will notify you and the authorities as required by law.

10. Children

Gerak Luu is built for drivers and is not directed at children. We do not knowingly collect personal data from children. If you are a parent or guardian and believe your child has sent us data, contact us and we will delete it.

11. Map data

The map, road and place names in Gerak Luu come from OpenStreetMap, © OpenStreetMap contributors, under the Open Database License (ODbL). We do not send your personal data to OpenStreetMap.

12. Changes to this policy

We will update this policy when the app or service changes, and change the “Last updated” date above. If a change is significant, we will show a notice in the app before it takes effect.

13. Contact us

APPVOLUSI SDN. BHD.
Email: dev@appvolusi.com

This policy is available in Malay and English. If they differ, the Malay version applies.