Privacy Policy

Version 1.3 · effective 26 October 2026 · Bahasa Indonesia

This policy explains how RilRoute — the RilRoute Survey app, RilRoute Console (the web workspace for transport authorities), RilRoute Central Monitoring (RCM) (vehicle video and position monitoring, see section 10), RilRoute Fleet, the RilRoute Driver app, and vehicle devices (see section 11), and the services at rilroute.com — processes personal data. We follow the data protection laws that apply where the service is used, including Indonesia’s Personal Data Protection Law (Law No. 27 of 2022).

1. Controller

IT Techno Solutindo (ITS). Contact: ittechnosolutindo@gmail.com.

2. Who uses the services

RilRoute services are only for people given access by an administrator: surveyors, reviewers and approvers of the transport authority that owns the routes, and authority administrators (Survey, Console); operator administrators, operator staff, and drivers (Fleet, Driver); users of a fleet company (RCM); and ITS administrators. They are not public apps and are not intended for anyone under 18. Sections 3–9 describe Survey and Console; sections 10 and 11 add what is specific to RCM and to Fleet, Driver, and vehicle devices.

3. Data we process

DataWhen and how
AccountEmail address, name, preferred language, and the roles given to you (per authority, or per region for surveyors). With Google sign-in we only use your verified email address to match your account; your Google profile photo is not stored.
Sign-in and audit recordsWhen you sign in: time, IP address, and browser or app type (user agent). When an administrator adds or changes users, roles, authorities, or networks: who made the change, what changed, time, and IP address. Used only for account security and audit.
Sign-in code (OTP)Sent to your email, valid for 5 minutes. The server stores a hash, not the code.
Precise GPS locationOnly from when you tap Start recording or Start test until you tap Finish — including while the screen is off or the app is in the background. A “RilRoute is recording” notification is shown the whole time. Outside a recording or test, the app does not track your location.
Stop photosPhotos you take yourself when marking a stop, resized (max. 1600 px, about 400 KB). Please avoid photographing faces or licence plates.
Device dataA random installation ID, app version, and a vehicle code if you enter one. With each recording or test: phone manufacturer and model; Android version; SIM operator name (for example Telkomsel); connection type at start (mobile data, Wi-Fi, none); GPS chip model; whether dual-frequency (L5) satellite signals were received; battery saver on or off; precise or approximate location permission; and where you placed the phone (dashboard, near a window, handheld, pocket or bag). With each GPS point: number of satellites used and visible, average signal strength, satellite systems used (GPS, Galileo, BeiDou, and so on), accuracy estimates for position, altitude, speed and heading, and whether Android reported the location as fake (mock). We do not read IMEI, the SIM phone number, serial numbers, advertising ID, your contacts, or the list of installed apps.
Technical logsKept on the phone for 7 days. Sent only if you export them for support; tokens and sign-in codes are masked.

4. Why we process it

  • To build, test, and update the paths and stops of public transport routes.
  • To maintain a versioned route registry reviewed and approved by the local transport authority.
  • Accountability: recording who recorded, tested, reviewed, and approved each version.
  • Account security and technical support.
  • GPS quality, using the device data above: deciding which GPS points are accurate enough to build a route path; choosing recording settings (accuracy limit, point interval) that suit each phone type and phone placement; updating the phone-placement guidance for surveyors; finding the cause of failed recordings or uploads (for example battery saver or no connection); and flagging points from fake locations so they are not used for official routes — a flagged recording is reviewed again.

Legal bases: performing your assignment or work agreement, and our legitimate interest in accurate official route data, account security, and audit. Location, camera, and notification permissions are phone settings that make the features work; you can turn them off at any time (see section 8).

5. Who receives data

  • The transport authority that owns the route: recordings and test results, including the device and GPS-quality summary, for review and approval. Other authorities do not see them.
  • The public and partners: only published route data (paths, stops, order). It does not contain surveyor identities.
  • Service providers: Google (Google sign-in and delivery of sign-in code emails) and the server providers operated by ITS.

We do not sell personal data or use it for advertising.

6. Storage and security

  • Data is sent over HTTPS. Databases and photo storage sit on a private server network.
  • Access is limited by role and by the authority that owns each route; every request is checked against your current roles.
  • Sign-in tokens on the phone are kept in the device’s secure storage.
  • Data may be stored in a country other than yours; we apply the same protections wherever it is stored.

7. Retention

  • On the phone: GPS points of a recording are deleted 7 days after the server confirms it; logs are deleted after 7 days.
  • On the server: recordings, tests, their device and GPS-quality data, and stop photos are kept as long as needed for the route registry and the audit trail of route versions.
  • Sign-in and audit records are kept as a security and audit trail.
  • Inactive accounts can be deleted on request, except approval records that must be kept for audit.

8. Your rights

You can ask to access, copy, correct, or delete your personal data, withdraw consent, or object to processing. Email ittechnosolutindo@gmail.com; we respond within 3 × 24 hours or sooner if local law requires. You can revoke location, camera, and notification permissions at any time in your phone settings; without location access, recording and testing cannot be used.

9. Changes

Changes are published on this page with a new version number and effective date. Important changes are announced in the app or by email.

10. RilRoute Central Monitoring (RCM)

RCM (rcm.rilroute.com and the RCM API) lets a fleet company watch its own vehicles: live and recorded video from the vehicle video recorder (MDVR), vehicle position, and safety alarms. For the people in those vehicles, the fleet company that uses RCM decides what is recorded and why (it is the controller); ITS operates RCM on its behalf (as processor). For RCM user accounts, ITS is the controller.

DataWhen and how
RCM accountEmail address, name, company, role, password (stored as a hash), sign-in codes sent by email (stored as a hash), trusted-device records, and sign-in time and IP address.
VideoLive video and recordings from the cameras installed by the fleet company (road, cabin, driver, and side cameras). Cameras can capture the driver, passengers, and people around the vehicle. Recordings stay on the vehicle recorder; RCM fetches a recording only when an authorised user asks for it. Live video is only streamed while someone is watching.
Position and statusVehicle GPS position, speed, direction, ignition and online status, sent by the recorder.
Safety alarmsAlarms from driver-monitoring and driver-assistance cameras (for example fatigue, phone use, distraction, collision or blind-spot warnings), with time, place, and a video link; who handled each alarm and when.
Driver recordsEntered by the fleet company: driver name, employee or driver code, contact, licence and card details, photo, and documents it uploads.
Audit logWho viewed or changed what in RCM, when, and from which IP address.
  • Purpose: fleet safety and supervision, incident and complaint handling, evidence for accidents, and vehicle operations. Not for advertising.
  • Who sees it: only users of the fleet company that owns the vehicle (and its parent company, if set up that way), according to their role; ITS administrators for support and security. Through the RCM API the fleet company may give its own systems, or a supervising party such as the transport operator it serves, access to its own vehicles only.
  • Fleet company duties: tell drivers and passengers that cameras are in use (for example with stickers in the vehicle), and handle their requests together with ITS.
  • Retention: recordings follow the capacity of the vehicle recorder; positions and alarms on the RCM server are kept for the period agreed with the fleet company and then deleted; RCM accounts until they are closed.
  • Requests: drivers, passengers, and others captured by RCM can contact the fleet company or ITS at ittechnosolutindo@gmail.com.

11. RilRoute Fleet, RilRoute Driver, and vehicle devices

RilRoute Fleet (fleet.rilroute.com) lets a transport operator manage its vehicles, devices, drivers, schedules, and trips. Data comes from devices in the vehicle: the RilRoute Driver app, GPS trackers, ABS Controller, passenger announcers, and RilRoute Link. For drivers and vehicles, the operator decides what is collected and why (it is the controller); ITS operates RilRoute Fleet on its behalf (as processor). For Fleet user accounts, ITS is the controller.

DataWhen and how
Fleet accountEmail address, name, operator, and role (operator admin or staff), with the same sign-in and audit records as section 3.
Driver recordsEntered by the operator: driver name, driver code, phone number, and active status. The driver PIN and one-time activation code are stored only as hashes. Failed PIN attempts are counted to lock the account temporarily.
Vehicle positionFrom the vehicle’s GPS tracker, ABS Controller, or vehicle video recorder while the device is on; from the RilRoute Driver app only during a trip started by the driver. Position, speed, heading, and time.
Trips and eventsTrip start and end, stops reached or missed, leaving the route, the driver signed in to the trip, panic button presses, and proof that an on-board advertisement was shown.
Device dataDevice ID, app version, network and battery status, GPS signal quality, and connection times.
  • Purpose: fleet operations, schedule and route compliance, passenger information (stop announcements), safety (panic alerts), and support.
  • Who sees it: users of the operator that owns the vehicle, according to their role; the transport authority only for vehicles on routes it has permitted to that operator (route compliance), never for other vehicles; ITS administrators for support and security.
  • Retention: raw vehicle positions are kept for 90 days and then deleted in monthly batches; trips and events as long as needed for operations and compliance reporting; driver records until the operator removes them.
  • Driver app permissions: location is used only during a trip; you can revoke it in the phone settings, but trips cannot then be recorded.
  • Requests: drivers can contact their operator or ITS at ittechnosolutindo@gmail.com.
Bahasa Indonesia

Kebijakan Privasi

Versi 1.3 · berlaku sejak 26 Oktober 2026 · English

Kebijakan ini menjelaskan data pribadi yang diproses oleh RilRoute, yaitu aplikasi RilRoute Survey, RilRoute Console (ruang kerja web untuk otoritas transportasi), RilRoute Central Monitoring (RCM) (pemantauan video dan posisi kendaraan, lihat bagian 10), RilRoute Fleet, aplikasi RilRoute Driver, dan perangkat kendaraan (lihat bagian 11), serta layanan di rilroute.com. Kami mengikuti hukum perlindungan data yang berlaku di tempat layanan digunakan, termasuk Undang-Undang Nomor 27 Tahun 2022 tentang Pelindungan Data Pribadi.

1. Pengendali data

IT Techno Solutindo (ITS). Kontak: ittechnosolutindo@gmail.com.

2. Siapa pengguna layanan

Layanan RilRoute hanya untuk orang yang diberi akses oleh admin: surveyor, peninjau dan penyetuju dari otoritas transportasi pemilik trayek, dan admin instansi (Survey, Console); admin operator, staf operator, dan sopir (Fleet, Driver); pengguna perusahaan armada (RCM); serta admin ITS. Layanan ini bukan aplikasi umum dan tidak ditujukan bagi anak di bawah 18 tahun. Bagian 3–9 menjelaskan Survey dan Console; bagian 10 dan 11 menambahkan hal khusus RCM serta Fleet, Driver, dan perangkat kendaraan.

3. Data yang kami proses

DataKapan dan bagaimana
AkunAlamat email, nama, bahasa pilihan, dan peran yang diberikan kepada Anda (per instansi, atau per wilayah untuk surveyor). Saat masuk dengan Google, kami hanya memakai alamat email terverifikasi untuk mencocokkan akun; foto profil Google tidak disimpan.
Catatan masuk dan auditSaat Anda masuk: waktu, alamat IP, dan jenis peramban atau aplikasi (user agent). Saat admin menambah atau mengubah pengguna, peran, instansi, atau jaringan: siapa yang mengubah, apa yang berubah, waktu, dan alamat IP. Hanya untuk keamanan akun dan audit.
Kode masuk (OTP)Dikirim ke email Anda, berlaku 5 menit. Server menyimpan bentuk tersandi (hash), bukan kodenya.
Lokasi GPS presisiHanya sejak Anda menekan Mulai rekam atau Mulai uji sampai menekan Selesai, termasuk saat layar mati atau aplikasi di latar belakang. Selama itu notifikasi “RilRoute merekam” selalu tampil. Di luar rekaman/uji, aplikasi tidak melacak lokasi.
Foto halteFoto yang Anda ambil sendiri saat menandai halte, dikecilkan (maks. 1600 piksel, ±400 KB). Hindari memotret wajah orang atau pelat nomor.
Data perangkatID instalasi acak, versi aplikasi, dan kode kendaraan bila Anda mengisinya. Setiap rekaman atau uji: pabrikan dan model HP; versi Android; nama operator SIM (mis. Telkomsel); jenis koneksi saat mulai (data seluler, Wi-Fi, tanpa koneksi); model chip GPS; apakah sinyal satelit dua frekuensi (L5) diterima; mode hemat daya aktif atau tidak; izin lokasi presisi atau perkiraan; dan letak HP yang Anda pilih (dasbor, dekat jendela, dipegang, saku atau tas). Setiap titik GPS: jumlah satelit terpakai dan terlihat, rata-rata kuat sinyal, sistem satelit yang dipakai (GPS, Galileo, BeiDou, dan lainnya), perkiraan akurasi posisi, ketinggian, kecepatan, dan arah, serta apakah Android melaporkan lokasinya palsu (mock). Kami tidak membaca IMEI, nomor telepon kartu SIM, nomor seri, ID iklan, kontak, atau daftar aplikasi terpasang.
Log teknisDisimpan di HP selama 7 hari. Hanya dikirim bila Anda sendiri mengekspornya untuk dukungan teknis; token dan kode masuk disamarkan.

4. Tujuan pemrosesan

  • Membentuk, menguji, dan memperbarui jalur serta halte trayek angkutan umum.
  • Menyusun registri trayek berversi yang ditinjau dan disetujui otoritas transportasi setempat.
  • Akuntabilitas: mencatat siapa merekam, menguji, meninjau, dan menyetujui setiap versi.
  • Keamanan akun dan dukungan teknis.
  • Mutu GPS, memakai data perangkat di atas: menentukan titik GPS mana yang cukup akurat untuk membentuk jalur; memilih pengaturan perekaman (batas akurasi, selang titik) yang cocok untuk tiap jenis HP dan letak HP; memperbarui panduan letak HP bagi surveyor; mencari penyebab rekaman atau pengiriman yang gagal (mis. mode hemat daya atau tanpa koneksi); dan menandai titik dari lokasi palsu agar tidak dipakai untuk trayek resmi — rekaman yang ditandai ditinjau ulang.

Dasar pemrosesan: pelaksanaan penugasan atau perjanjian kerja Anda, serta kepentingan yang sah atas data trayek resmi yang akurat, keamanan akun, dan audit. Izin lokasi, kamera, dan notifikasi adalah pengaturan HP agar fitur bekerja; Anda dapat mematikannya kapan saja (lihat bagian 8).

5. Pihak yang menerima data

  • Otoritas transportasi pemilik trayek: hasil rekaman dan uji, termasuk ringkasan perangkat dan mutu GPS, untuk peninjauan dan persetujuan. Instansi lain tidak melihatnya.
  • Publik dan mitra: hanya data trayek yang sudah terbit (jalur, halte, urutan), tanpa identitas surveyor.
  • Penyedia layanan: Google (masuk dengan Google dan pengiriman email kode masuk) dan penyedia server yang dikelola ITS.

Kami tidak menjual data pribadi dan tidak memakainya untuk iklan.

6. Penyimpanan dan keamanan

  • Data dikirim melalui HTTPS. Basis data dan penyimpanan foto berada di jaringan privat server.
  • Akses dibatasi menurut peran dan instansi pemilik trayek; setiap permintaan diperiksa terhadap peran Anda saat itu.
  • Token masuk di HP disimpan di penyimpanan aman perangkat.
  • Data dapat disimpan di negara selain negara Anda; perlindungan yang sama tetap kami terapkan.

7. Lama penyimpanan

  • Di HP: titik GPS rekaman dihapus 7 hari setelah server mengonfirmasi; log dihapus setelah 7 hari.
  • Di server: rekaman, uji, data perangkat dan mutu GPS-nya, serta foto halte disimpan selama diperlukan untuk registri trayek dan jejak audit versi trayek.
  • Catatan masuk dan audit disimpan sebagai jejak keamanan dan audit.
  • Akun tidak aktif dapat dihapus atas permintaan, kecuali catatan persetujuan yang wajib dipertahankan untuk audit.

8. Hak Anda

Anda berhak meminta akses, salinan, perbaikan, atau penghapusan data pribadi, menarik persetujuan, dan mengajukan keberatan. Kirim ke ittechnosolutindo@gmail.com; kami menanggapi paling lambat 3 × 24 jam, atau lebih cepat bila diwajibkan hukum setempat. Izin lokasi, kamera, dan notifikasi dapat dicabut kapan saja di pengaturan HP; tanpa izin lokasi, fitur rekam dan uji tidak dapat dipakai.

9. Perubahan

Perubahan dicantumkan di halaman ini dengan nomor versi dan tanggal berlaku baru. Perubahan penting diberitahukan melalui aplikasi atau email.

10. RilRoute Central Monitoring (RCM)

RCM (rcm.rilroute.com dan RCM API) dipakai perusahaan armada untuk memantau kendaraannya sendiri: video langsung dan rekaman dari perekam video kendaraan (MDVR), posisi kendaraan, dan alarm keselamatan. Untuk orang yang berada di kendaraan, perusahaan armada pemakai RCM yang menentukan apa yang direkam dan untuk apa (pengendali data); ITS menjalankan RCM atas namanya (prosesor data). Untuk akun pengguna RCM, ITS adalah pengendali data.

DataKapan dan bagaimana
Akun RCMAlamat email, nama, perusahaan, peran, kata sandi (disimpan tersandi/hash), kode masuk yang dikirim lewat email (disimpan tersandi), catatan perangkat tepercaya, serta waktu dan alamat IP saat masuk.
VideoVideo langsung dan rekaman dari kamera yang dipasang perusahaan armada (kamera jalan, kabin, pengemudi, dan samping). Kamera dapat merekam pengemudi, penumpang, dan orang di sekitar kendaraan. Rekaman tetap tersimpan di perekam kendaraan; RCM hanya mengambil rekaman bila diminta pengguna yang berwenang. Video langsung hanya dialirkan selama ada yang menonton.
Posisi dan statusPosisi GPS, kecepatan, arah, status mesin, dan status online kendaraan yang dikirim perekam.
Alarm keselamatanAlarm dari kamera pemantau pengemudi dan bantuan mengemudi (mis. kantuk, memakai HP, tidak fokus, peringatan tabrakan atau titik buta), beserta waktu, tempat, dan tautan video; siapa yang menangani alarm dan kapan.
Data pengemudiDiisi perusahaan armada: nama pengemudi, kode pegawai atau pengemudi, kontak, data SIM dan kartu, foto, dan dokumen yang diunggahnya.
Log auditSiapa melihat atau mengubah apa di RCM, kapan, dan dari alamat IP mana.
  • Tujuan: keselamatan dan pengawasan armada, penanganan kejadian dan keluhan, bukti saat kecelakaan, dan operasional kendaraan. Tidak untuk iklan.
  • Yang dapat melihat: hanya pengguna perusahaan armada pemilik kendaraan (dan induk perusahaannya bila diatur demikian) sesuai perannya; admin ITS untuk dukungan dan keamanan. Lewat RCM API, perusahaan armada dapat memberi akses kepada sistemnya sendiri atau pihak pengawas seperti operator angkutan yang dilayaninya, terbatas pada kendaraannya sendiri.
  • Kewajiban perusahaan armada: memberi tahu pengemudi dan penumpang bahwa ada kamera (mis. stiker di kendaraan) dan menangani permintaan mereka bersama ITS.
  • Lama penyimpanan: rekaman mengikuti kapasitas perekam kendaraan; posisi dan alarm di server RCM disimpan selama jangka waktu yang disepakati dengan perusahaan armada lalu dihapus; akun RCM sampai ditutup.
  • Permintaan: pengemudi, penumpang, dan orang lain yang terekam RCM dapat menghubungi perusahaan armada atau ITS di ittechnosolutindo@gmail.com.

11. RilRoute Fleet, RilRoute Driver, dan perangkat kendaraan

RilRoute Fleet (fleet.rilroute.com) dipakai operator angkutan untuk mengelola kendaraan, perangkat, sopir, jadwal, dan rit. Datanya berasal dari perangkat di kendaraan: aplikasi RilRoute Driver, GPS tracker, ABS Controller, perangkat pengumuman penumpang, dan RilRoute Link. Untuk data sopir dan kendaraan, operator yang menentukan apa yang dikumpulkan dan untuk apa (pengendali data); ITS menjalankan RilRoute Fleet atas namanya (prosesor data). Untuk akun pengguna Fleet, ITS adalah pengendali data.

DataKapan dan bagaimana
Akun FleetAlamat email, nama, operator, dan peran (admin atau staf operator), dengan catatan masuk dan audit yang sama seperti bagian 3.
Data sopirDiisi operator: nama sopir, kode sopir, nomor telepon, dan status aktif. PIN sopir dan kode aktivasi sekali pakai hanya disimpan dalam bentuk tersandi (hash). Percobaan PIN yang salah dihitung untuk mengunci sementara.
Posisi kendaraanDari GPS tracker, ABS Controller, atau perekam video kendaraan selama perangkat menyala; dari aplikasi RilRoute Driver hanya selama rit yang dimulai sopir. Posisi, kecepatan, arah, dan waktu.
Rit dan kejadianMulai dan akhir rit, halte yang dicapai atau terlewat, keluar dari trayek, sopir yang masuk pada rit itu, tombol darurat, dan bukti tayang iklan di kendaraan.
Data perangkatID perangkat, versi aplikasi, status jaringan dan baterai, mutu sinyal GPS, dan waktu tersambung.
  • Tujuan: operasional armada, kepatuhan jadwal dan trayek, informasi penumpang (pengumuman halte), keselamatan (peringatan darurat), dan dukungan teknis.
  • Yang dapat melihat: pengguna operator pemilik kendaraan sesuai perannya; otoritas transportasi hanya untuk kendaraan di trayek yang izinnya diberikan kepada operator itu (kepatuhan trayek), tidak untuk kendaraan lain; admin ITS untuk dukungan dan keamanan.
  • Lama penyimpanan: posisi mentah kendaraan disimpan 90 hari lalu dihapus per bulan; rit dan kejadian selama diperlukan untuk operasional dan laporan kepatuhan; data sopir sampai dihapus operator.
  • Izin aplikasi Driver: lokasi hanya dipakai selama rit; izin dapat dicabut di pengaturan HP, tetapi rit tidak dapat dicatat tanpa izin itu.
  • Permintaan: sopir dapat menghubungi operatornya atau ITS di ittechnosolutindo@gmail.com.