Privacy Policy
Effective date: 20 October 2026. Version: 2.
1. Who We Are and Scope
PT Jitra Tekno Laisaka, Gempol Tengah, Sukamakmur, Telukjambe Timur, Karawang, Jawa Barat, Indonesia (“Jitra”, “we”, or “us”), explains in this Policy how personal data is processed when you visit our website, use the Jitra platform and applications, Jitra Tracker, connected devices, APIs or integrations, or contact us.
Contact legal@jitra.app for privacy matters and support@jitra.app for service assistance. This Policy describes processing; it does not, by itself, constitute consent to marketing or every processing activity.
2. Jitra's and Customers' Roles
We act as controller for processing whose purposes we determine, such as account administration, billing, security, service communications, and measurement of our service usage.
Where a customer or Organization determines why people are tracked and how their data is used, that customer generally acts as controller and Jitra processes the data on its instructions as processor. Actual activities, rather than the name of an agreement alone, determine each role.
For customer-controlled data, the applicable processing arrangements govern instructions, confidentiality, security, subprocessors, assistance with data-subject rights, and data return or deletion. Requests concerning a customer's tracking decisions may be directed to the relevant controller.
3. Data Categories and Sources
Data may come from you, Organization administrators, GPS devices, Jitra Tracker, service usage, or parties you authorize through integrations. Depending on the features used, categories include:
Account and Organization data: name, email, supplied contact details, authentication credentials, roles, settings, and consent records.
Object and tracking data: Object names/identifiers, device identifiers such as IMEI, location and time, speed/direction, trips, status, geofences, events, and telemetry actually supplied by the data source.
Transaction data: plans, quotas, subscriptions, invoices, payment status/references, and required tax information.
Technical and usage data: IP address, browser/device/operating-system information, identifiers, authentication logs, activity, errors, and diagnostic information.
Support and communications: messages, attachments, and information supplied to address requests.
Integration data: payloads, destinations, responses, and necessary logs according to configuration.
Location data may be personal data where it relates to an identified or identifiable individual, including a driver or device holder.
4. Purposes and Legal Bases
We use Object location to show current position, history, trips, events, and notifications, and to send that data to integrations an Organization administrator turns on.
Account administration, service provision, and billing may rely on performing a contract or taking steps at your request before entering a contract.
Tax records, bookkeeping, and lawful authority requests rely on the relevant legal obligations.
Security, abuse prevention, troubleshooting, and service improvement may rely on legitimate interests after considering individuals' rights, reasonable expectations, and potential impacts, or on another appropriate basis.
For non-essential analytics and marketing, we obtain consent where required or use another lawful basis appropriate to the context. Withdrawal of consent does not affect the lawfulness of earlier processing.
For tracking performed as processor, the customer determines the lawful basis and provides instructions. Customers must provide required notices and obtain consent where required. Unlawful tracking is not permitted.
5. Jitra Applications and Jitra Tracker
An Object’s location comes from a connected GPS device or, when you choose it, from Jitra Tracker on a smartphone. That location is the position, history, and events shown for the Object.
The monitoring application, on the web and on mobile, displays that Object data to people the Organization has authorized. On mobile, the application may read the phone’s location once, when you place a site, a geofence, or an address. It does not track that phone in the background, and it does not turn the phone into an Object.
Jitra Tracker for Android is the tracking source. While tracking is on, it records and sends the phone’s location so the Object can be monitored, including in the background when the operating system allows it. You can stop it with the tracking control or by turning off the location permission. Closing the screen does not always stop it. Stopping tracking does not cancel a subscription and does not delete location already sent.
6. Data Recipients
Within an Organization, data is visible to users according to the role an administrator assigns, and to people or systems the Organization chooses through sharing, notifications, or an integration. Check those recipients: a service you connect may apply its own policy.
Jitra personnel can open data only as needed to run the service, answer a support request, or investigate a security issue. Service providers process data for a specific function, such as hosting and storage, maps, service email and notifications, payment, or measurement.
We may disclose data where legally required or to lawfully protect rights and security, subject to appropriate limits. We do not sell customers' personal data.
Payment parties may act as independent controllers or merchants of record depending on their role. Card data is handled through payment parties; Jitra does not directly store full payment-card details.
7. Processing Outside Indonesia
Some processing takes place outside Indonesia. Product-usage measurement is sent to a service in the United States. Hosting, maps, email, payment, and similar providers may also process data outside Indonesia.
International transfers use the safeguards and basis required by applicable law, including requirements concerning protection levels, adequate binding arrangements, or consent where required under the applicable sequence of requirements. Merely using the service is not treated as automatically satisfying all transfer requirements.
8. Retention, Export, and Deletion
Tracking history is kept for the history period of the Organization’s active plan and storage add-on. A downgrade, or the end of that entitlement, can shorten the history that remains available. That period does not set how long account, invoice, log, or backup data is kept.
A report is removed from the report list one month after it is created. It is permanently deleted three months after it leaves the list, about four months after it was created. Account and Organization records are kept while the account or Organization is active. After closure, a limited set may remain for security, a dispute, or to finish a request, and is then deleted or de-identified. Invoices and tax records stay for as long as bookkeeping and tax law require, including after a subscription ends. Security and diagnostic logs are kept while needed to investigate abuse, errors, or an incident, and longer only when a legal hold requires it. Support messages are kept while needed to handle the request and its follow-up, then deleted.
Measurement of website visits and product use is kept for that purpose and then deleted under the retention of the measurement tool. A backup can still hold data already deleted from the live service until that backup is replaced. If a backup is restored, the same retention rules apply to the recovered data: tracking history older than the active plan and storage add-on period is deleted again by the history store, and a recovered report older than one month is removed from the report list on the next daily cleanup, then permanently deleted three months after it leaves the list.
Cancelling renewal, stopping tracking, closing an account, and deleting data are different. Cancelling renewal stops the next charge. Paid access continues until the end of the paid period, and history is not deleted by cancellation alone. Stopping tracking stops new location updates. It does not cancel the subscription or delete location already sent. Closing an account ends that person’s login. When a member is removed, the Organization’s Objects and history stay under the Organization’s control. Deletion of personal data is a separate request.
Export a copy before you close an account if you still want in-product export. Closing the account does not remove your right to ask for deletion. Send that request to legal@jitra.app, including after the account is closed. We handle it within the period required by law, except for records we must keep. Data deleted under these rules may not be recoverable.
9. Security and Incidents
We implement technical and organizational measures appropriate to the risks, including access controls and security management. No system is entirely risk-free. Protect credentials and limit Organization access according to need.
If an incident occurs, we assess and address it and notify customers, data subjects, or authorities according to our role and legal obligations. As processor, we assist controllers with their obligations. This provision does not replace legally required notification deadlines.
10. Your Rights and Requests
Depending on applicable law, you may have rights to information, access, correction, copies/portability, deletion, restriction, withdrawal of consent, objection, and other relevant rights.
Send requests to legal@jitra.app with sufficient information to identify the account and request. We may proportionately verify identity and authority; do not send passwords. Requests are handled within legally required periods. If a request is lawfully restricted or refused, we explain the reason to the extent permitted.
For Organization-controlled data, we may direct requests to the controller and assist as required. You may also complain to the competent authority.
11. Cookies and Analytics
We use cookies and local storage for sign-in, security, preferences, and the measurement described here.
GA4 is used for website marketing and conversion measurement. We use PostHog to analyze application usage events, such as pages viewed and actions taken within features. This information helps us understand usage, assess issues, and improve Jitra’s services. It may include user or Organization identifiers and is not necessarily anonymous.
Account, billing, and security messages are part of the service. You do not have to accept marketing to use Jitra. If you receive a marketing message, email support@jitra.app or legal@jitra.app and ask us to stop it. That request does not turn off account, billing, or security messages.
Consent or refusal choices are provided where legally required; non-essential analytics is not enabled before consent in contexts that require it. Browser preferences can also restrict cookies, but deleting cookies does not necessarily stop all measurement technologies.
12. Children and Third-Party Services
The services are intended for users with the required legal capacity. Processing children's data requires the legal basis and safeguards required by law; customers must not use Jitra to bypass those obligations.
Third-party websites and applications you access have their own policies. This Policy continues to apply to processing for which Jitra is responsible.
13. Changes and Contact
Material changes are notified through appropriate channels with their effective date. Where fresh consent is required, we obtain it before the relevant processing. Previous versions are retained as records.
PT Jitra Tekno Laisaka — Gempol Tengah, Sukamakmur, Telukjambe Timur, Karawang, Jawa Barat, Indonesia. Privacy: legal@jitra.app. Support: support@jitra.app.