Local by default
ODO is local-first. By default, your garage and records stay encrypted on this device. ODO does not collect live or background GPS.
DATA PRIVACY
Privacy and data handling notice
Your vehicle history is yours to manage. Learn how ODO protects your records and keeps you in control of backup, reports, and sharing.
Effective 2 August 2026 · Last reviewed 24 August 2026Privacy at a glance
Start with the essentials. Read the practical answers and full notice below when you need more detail.
Cloud features are your choice
You choose when to sign in, turn cloud backup off, request a report, use a workshop handoff, or share a report. Eligible Standard accounts start with cloud backup on only when no explicit preference exists. ODO processes the data needed for the feature you choose.
Identifying details stay separate
ODO does not add your name, plate number, gallery pointers, or device file paths to structured cloud vehicle records. Trip, place, timestamp, cost, service, and evidence data can still be personal data even when identifying details are stored separately.
Questions you may have
Does anything leave my phone by default?
Without sign-in or a cloud feature, your garage and records stay in the encrypted database on your device. ODO does not collect live or background GPS. If you sign in, ODO processes your account details separately.
What personal information does ODO process?
ODO does not store your name, plate number, gallery pointers, or device file paths in structured cloud vehicle records. Sign-in details are stored separately. When you request a report, the app sends your plate number and required vehicle details to ODO for processing and they become part of the PDF. A workshop handoff can include reporter, workshop, and service details.
What changes when I enable cloud backup?
For eligible Standard accounts, cloud backup is on by default only when no explicit preference exists. Turning it off stops future backup without deleting existing cloud data. ODO backs up eligible vehicle recovery fields, mileage and service records, and at most one current evidence image per backed-up row.
What happens when I create, share, or verify a report?
ODO uses the plate number and required vehicle details to create the PDF. These details remain outside structured cloud vehicle records but stay in the report. Anyone you give the PDF or verification link to can view that item. Public verification checks report identity and file integrity; it does not prove that every statement in the report is true. ODO cannot recall copies shared outside the service.
How can I edit, export, or delete my information?
You can edit or delete active records and export available reports through ODO. Synced deletions are recorded so they can reach your other devices. When ODO confirms an account-deletion request, account access ends immediately and cannot be restored. Permanent removal of account-associated cloud data begins immediately and completes through a bounded backend process. Retained reports stop verifying, but copies shared outside ODO remain outside its control. App Store or Google Play subscriptions must be cancelled separately. Contact ODO Malaysia to request access, correction, export, or account deletion.
What happens when I use a workshop QR code or link?
The owner creates a short-lived handoff for one workshop submission. A person with the valid link can see the submission form and send reporter, workshop, and service details. The link normally expires after ten minutes or one successful submission and does not give the workshop access to your garage.
How does ODO protect my information?
ODO uses a device-bound encrypted database, TLS, authenticated owner checks, encrypted temporary report input, owner-scoped storage, private report rendering, and file checksums. Sensitive request bodies, plate numbers, device paths, evidence bytes, and PDF bytes are excluded from logs.
What happens when I join an ODO waitlist?
ODO stores your waitlist email address, selected product interests, referral source, and submission timestamps on AWS so it can send the one-time feature availability notifications you requested. Contact ODO Malaysia to request deletion.
Privacy notice
Effective 2 August 2026 · Last reviewed 24 August 2026. This notice covers the ODO app, cloud services, reports, public verification, workshop handoffs, and marketing waitlists.
Who is responsible and what this notice covers
ODO Malaysia is responsible for information processed through the ODO mobile app, signed-in cloud services, generated PDF reports, public report verification, workshop QR or link handoffs, marketing waitlists, and associated support and security operations.
Information processed in each context
ODO processes account and installation identifiers; basic vehicle recovery fields; trip, mileage, odometer, service, cost, timestamp, and place information you enter; record status, revision, permanent change status, and synced deletion or revocation metadata; attachment references and evidence; workshop, reporter, and service submission details; generated PDFs; report IDs, checksums, expiry, and verification results; waitlist email, selected interests, referral source, and submission timestamps; and limited operational metadata. ODO does not collect live or background GPS.
Sources of personal data
ODO obtains personal data directly from you when you create an account, enter records, request a report, contact support, or join a waitlist; from a workshop reporter when you create and share a handoff; and automatically from the app and service when they create installation identifiers, timestamps, verification results, and limited security or operational events. Address suggestions may come from Google Places. ODO does not obtain live or background GPS.
Why information is used and when it leaves the device
Anonymous records remain in the device-bound encrypted local database. ODO uses information to authenticate accounts; save, restore, and synchronize selected records; detect conflicts; preserve permanent change status; create and retrieve reports; import workshop submissions; verify report identity and checksums; secure the service; and diagnose failures with non-sensitive events. Structured cloud rows exclude plate numbers, gallery pointers, device paths, and local-only attachment URIs. Sign-in details are processed separately.
Required and optional information
Using ODO without signing in does not require account information. Account details are required for signed-in services. Plate number and the vehicle fields identified by the app are required to generate a report. A waitlist email address and at least one selected interest are required to join a waitlist. Other record details and evidence are optional unless the relevant screen identifies them as required. If required information is not provided, ODO cannot provide the corresponding account, report, handoff, or notification feature.
Reports, sharing, and public verification
When you request a report, the app sends the plate number and allowed vehicle fields over TLS. ODO stores them in encrypted temporary input, renders them into the PDF, and excludes them from structured report metadata, queue messages, logs, metrics, and traces. Report downloads stay owner-scoped. Public verification is accountless and limited to one report. It confirms report identity and file integrity, not the truth of every statement. ODO cannot control PDFs or links shared outside the service.
Recipients, providers, and processing locations
ODO discloses personal data only as needed to service providers that operate authentication, APIs, storage, report processing, hosting, delivery, security, address selection, support, and payment functions; to people you choose to receive a report or handoff; to professional advisers and authorities where reasonably necessary or legally required; or in connection with a genuine financing, reorganisation, or transfer of the business subject to appropriate confidentiality measures. Amazon Web Services provides core cloud services and Google Places can provide workshop address selection. Core regional resources are in Asia Pacific (Malaysia), while some delivery, security, or provider infrastructure may process data outside Malaysia. Where a cross-border transfer occurs, ODO will take the steps required by applicable Malaysian law.
Your choices and privacy requests
You may request access to or correction of personal data held by ODO, withdraw consent or limit optional processing where applicable, request an available export, object to feature notifications, or request eligible deletion. ODO may ask for information reasonably necessary to verify your identity and protect the account before acting. Withdrawing required information or consent may prevent ODO from providing the related feature, but does not affect processing already lawfully completed. Send requests or complaints to the contact address below.
Retention, deletion, and privacy requests
Cloud records, reports, and related metadata are retained for five complete calendar years unless removed earlier through account deletion. When ODO confirms account deletion, access ends immediately and cannot be recovered. ODO immediately begins permanent removal of account-associated cloud records, evidence, retained reports, report metadata, and public-verification data; secure backend erasure completes through a bounded operational process. Reports then stop verifying. Copies previously shared outside ODO remain outside its control. Deleting an ODO account does not cancel an App Store or Google Play subscription. Temporary report input is deleted after success or permanent failure, subject to the bounded retry period. Waitlist details are retained until the selected feature notifications have been completed or you request deletion.
Security controls
ODO uses a device-bound encrypted database, TLS, authenticated owner checks, encrypted temporary report input, owner-scoped storage, immutable checksums, private report rendering, and controls designed to keep sensitive request bodies, plate numbers, device paths, evidence bytes, and PDF bytes out of operational logs. No internet service can guarantee absolute security.
Children and changes to this notice
ODO is not designed to collect personal data from children. A person who does not have legal capacity to use the Services should do so only with the involvement of a parent or legal guardian. Contact ODO Malaysia if you believe a child’s personal data has been submitted inappropriately. ODO may update this notice when its practices or legal obligations change and will update the review date and provide reasonable notice of material changes where appropriate.
- Cloud records, reports, and metadata
- Five complete calendar years. An item from year Y becomes eligible for deletion on 1 January of Y + 6.
- Temporary report input
- Deleted after success or permanent failure, subject to the bounded report retry period.
- Report job metadata
- Normally retained for seven days after a terminal state.
- Workshop handoff
- Normally expires after ten minutes or one successful submission.
- Waitlist details
- Retained until the selected feature notifications have been completed or you request deletion.