This policy explains how the MobileDoo mobile app (the “App”) for Android and iPhone handles personal data. The App is published by
Trung Nguyen (“we”, “us”). It lets people use the Odoo system of the organization they work for, such as time off, attendance,
expenses, purchasing, sales, inventory, deliveries and approvals, from a phone.
Summary
Your data lives on your organization’s Odoo server, not in the App and not in our own services. The App connects to the server address your organization gives you. In most cases your organization runs that server; if it uses a hosted Odoo from us, we operate it only on that organization’s behalf.
We do not sell data, show ads or track you across apps. The App contains no advertising or analytics SDK.
Sensitive features are off until you use them. Location is read when you check in or out, and for trip tracking only after you accept a consent notice and switch sharing on. The camera and microphone are used only for the actions you start.
Your password is not stored on the phone. After sign-in the App keeps a revocable device token in the secure storage of your phone.
The App works without any service of ours. Push notifications are optional. If your organization does not use our push relay, the App still works fully, but iPhone users receive no push notifications. When push is used, it passes through Google (Android) or Apple (iPhone) and, where the organization chooses it, through a relay we operate; on iPhone the content is end-to-end encrypted.
For questions about your own data (access, correction, deletion), contact your organization first. For anything about the App or the push relay, contact us at the address in section 14.
1. Who is responsible for what
Two parties are involved, and they have different roles.
Your organization (your employer, school or company) owns the Odoo server the App connects to. It decides what data is collected, who can see it, how long it is kept and why. For the business data described below, your organization is the data controller. Its own privacy notice applies to that data.
Trung Nguyen publishes the App. Through the App itself we do not receive your business data. Only if your organization chooses to use our optional push-notification relay (section 5) do we act as a processor for it, and as a controller for the limited operational data of that relay. An organization that does not use the relay sends us nothing.
Some organizations use a trial or hosted Odoo service operated by us. In that case we host the server on behalf of the organization, which remains the controller, and we process that data only on its instructions and under our agreement with it. This policy still describes what the App does.
The App is a tool for organizations. It is not meant for personal use without an organization that provides an Odoo server.
2. Information the App handles
The App sends the following to your organization’s Odoo server and shows what the server returns. It runs with your own Odoo account, so you see only what your Odoo permissions allow.
Category
What it includes
Why
Sign-in
Server address, database name, Odoo login and password (and a one-time code if your account uses two-factor authentication). The password is sent to your server to sign in and is not kept by the App.
To authenticate you. The server returns a device token the App uses afterwards.
Device information
Device name, platform (Android or iOS), App version, a device identifier generated by the App, the push token, and the time you were last seen.
To list and revoke your devices, and to send notifications to the right device.
Business data
Whatever your organization has enabled: employee directory entries and organization chart, time-off requests and balances, expenses, purchase and sales documents, CRM opportunities, inventory and transfers, payslips, activities and approvals, messages in your Odoo Inbox, announcements, delivery trips.
To provide the features you use.
Photos, video and files
Pictures of receipts and documents, files you attach, an optional selfie when you check in, and photos or videos used as proof of delivery.
To attach them to the record you are working on.
Location
Precise location, in two cases (see below): when you check in or out, and while you have switched on location sharing during a delivery trip.
Attendance checks and delivery tracking, if your organization uses them.
Barcodes and QR codes
Codes you scan with the camera: connection QR codes and product, lot or location barcodes.
To connect to a server and to look up or process stock. The camera image is analysed on the phone to read the code.
Location in detail
Attendance. When you check in or out, the App reads your position once, so that your organization can record it with the attendance and check it against its work areas. The App does not follow you at other times. Your organization may require the location, or may only record it.
Delivery trips. Only drivers who use the delivery-tracking feature. Nothing is sent until you accept a consent notice and switch sharing on for a trip. While sharing is on, the App records your position (coordinates, accuracy and speed) and sends it in batches to your organization’s server, including while the App is in the background: on Android through a foreground service with a visible notification, on iPhone through background location. Sharing stops when you switch it off, when the trip ends, when you sign out, or after the maximum duration set by your organization. Dispatchers of your organization can see the position on a live map.
3. Phone permissions
The App asks for a permission only when a feature needs it, and you can refuse or later withdraw it in your phone’s settings. Refusing a permission only disables the feature that needs it.
Permission
Used for
Camera
Scanning QR codes and barcodes; photographing receipts and documents; attendance selfie; proof-of-delivery photos and videos
Microphone (iPhone)
Sound in proof-of-delivery videos you record
Photos and files
Choosing an existing picture or document to attach
Location
Attendance check-in and check-out; delivery trips (section 2)
Notifications (optional)
Approvals, assigned tasks, messages and other alerts from your organization’s Odoo, if your organization has set up push. The App works without it.
Biometrics / screen lock
Optional app lock. The unlock is performed by your phone’s operating system; the App never receives your fingerprint or face data, only a yes or no.
Network
Communicating with your organization’s server
4. What is stored on your phone
Device token (and, on servers with several databases, a session identifier) in the secure storage of the phone: the iOS Keychain or Android Keystore-backed storage. The token can be revoked by you (sign out), by your organization’s administrator, and it stops working when you change your password.
Preferences: the servers you connected to, your language and theme, app-lock setting and home-screen layout choices.
Pending actions that could not be sent yet because the network was unavailable, such as an attendance check or a new record. They are sent when the connection returns and then removed.
On iPhone, trip positions waiting to be uploaded are kept in a local database until the server confirms them.
The App does not copy your Odoo database to the phone. Screens are loaded from the server when you open them.
5. Push notifications and our relay
Push notifications are optional, and the App does not need our relay to work. Without push, every feature still works; you simply do not get an alert when something happens and see new items when you open the App.
Notifications are created by your organization’s Odoo (for example “Purchase order to approve” or a new Inbox message) and delivered by the phone vendor’s service: Firebase Cloud Messaging (Google) on Android and the Apple Push Notification service on iPhone. Your organization chooses one of three setups:
No push. Nothing is sent to anyone, neither to us nor to Google or Apple. This is a valid setup on Android and on iPhone.
Directly from your organization’s Odoo to Google, using the organization’s own Firebase project. This works on Android only; iPhone does not receive push in this setup. We are not involved.
Through the MobileDoo push relay that we operate (Android and iPhone). Your organization’s Odoo sends us the notification (title, text, a reference to the record, and the push tokens of the recipients), we queue it and pass it to Google or Apple. This is the only setup in which iPhone receives push notifications.
Only in the relay setup do we handle any notification data. In that case we:
hold the message in the delivery queue until it has been sent, including retries after temporary failures; after a successful delivery it is removed within about 1 hour (this short window is used to ignore a message that is submitted twice), and a message that could not be delivered at all is removed after 7 days; we do not use its content for any other purpose;
keep delivery receipts (sent or failed, counts, invalid tokens, but not the message text) for 7 days so that the organization’s Odoo can read the results;
store the organization’s site token only as a one-way hash, and count the number of distinct recipients over 30 days, using user references and hashed device tokens, to apply the organization’s subscription;
end-to-end encrypt notifications for iPhone: the content is encrypted by your organization’s Odoo with a key that only your phone holds, so neither the relay, Google nor Apple can read it. The notification text is decrypted on the phone. (If it cannot be decrypted, a generic notification is shown.)
Notifications for Android sent through the relay are not end-to-end encrypted; they should not contain more than the short text your organization chooses to show. You can disable notifications in your phone’s settings at any time.
6. Who receives data
Your organization receives everything you do in the App, as described above, because it is the owner of the Odoo system.
Google (Firebase Cloud Messaging) and Apple (APNs), only if push notifications are used, receive push tokens and notification payloads to deliver them. Their own privacy policies apply to what they do with it.
Infrastructure providers that host the push relay, only if your organization uses the relay, process the relay data under our instructions.
Authorities and others when the law requires, or to protect rights and safety, and in a merger or sale of our business, in which case this policy continues to apply to the data.
We do not sell personal data or share it for advertising.
7. No advertising, no tracking
The App contains no advertising, analytics or crash-reporting SDK, does not build advertising profiles, and does not track you across other companies’ apps and websites. Because of that it does not need the “App Tracking Transparency” prompt on iPhone. Location is used only for the app functions described in section 2.
8. How long data is kept
On your organization’s server: for the period your organization decides. For delivery tracking its default is to keep detailed positions for 90 days and then reduce them to a rough track, and to delete proof photos and videos after a set period, all configurable by the organization.
On your phone: until you sign out, the token is revoked, or you uninstall the App. Signing out removes the stored token.
In our push relay (only if your organization uses it): as described in section 5; message content for about 1 hour after delivery (7 days if it could not be delivered), delivery receipts for 7 days, and subscription counters for as long as the organization’s subscription needs them.
9. Security
The device token is stored in the phone’s secure storage and only its hash is stored on the server.
The server, not the App, decides for every request what your Odoo account may read or do, and refuses the rest.
Notification content for iPhone is end-to-end encrypted (section 5).
Data travels between the App and your organization’s server over the address your organization configured. Organizations should use HTTPS; the App can also connect to servers inside a private network, which is the organization’s choice.
You can protect the App with your phone’s screen lock or biometrics (optional app lock).
No system is perfectly secure. If you suspect that your device or account has been compromised, sign out, change your Odoo password (this revokes every device token), and tell your organization’s administrator.
10. Your choices and rights
You can: refuse or withdraw any phone permission; switch location sharing off at any time on the trip screen; turn off notifications; enable the app lock; sign out; and remove the App.
Depending on where you live, data-protection laws such as the GDPR, the UK GDPR, the California CCPA/CPRA and Vietnam’s Decree 13/2023/ND-CP may give you rights to access your personal data, have it corrected or deleted, restrict or object to its processing, receive a copy, withdraw consent, and complain to a supervisory authority.
For the business data in Odoo (attendance, expenses, locations, documents, photos...), exercise these rights with your organization, which controls that data and can act on it. We cannot access it.
For the operational data of our push relay, or for questions about the App itself, write to us (section 14). We may need to verify who you are and, because the relay identifies people only through your organization’s references, we may need to ask your organization to help.
11. Deleting your data and signing out
The App has no account with us, so there is no MobileDoo account to delete. Your user account and records belong to your organization’s Odoo.
Remove the App’s data from your phone: open Settings in the App and choose Sign out (this revokes the device token and stops notifications for that server), or uninstall the App.
Stop sharing location: switch sharing off on the trip screen, or revoke the location permission in your phone settings.
Ask for your data to be deleted or corrected on the server: contact your organization’s Odoo administrator or data-protection contact. They can also revoke any of your devices from Settings > Mobile App > Devices in Odoo.
Relay data: write to us (section 14) if you want us to look into data held in the push relay.
12. Children
The App is a business tool for working people and is not directed to children. We do not knowingly collect personal data from children under 16 (or the age set by local law). If you believe a child has used the App, tell us and your organization so that it can be removed.
13. International transfers
Your organization chooses where its Odoo server is. If push notifications are used, they are handled by Google and Apple, and, where the relay is used, by the providers that host it, in countries that may differ from yours. Where the law requires it, these transfers rely on safeguards such as standard contractual clauses or an adequacy decision.
We will answer privacy requests within a reasonable time and in any case within the period the law sets.
15. Changes to this policy
We may update this policy when the App or the law changes. The “Last updated” date above shows the current version. For significant changes we will notify users in the App or on the store page. Continued use of the App after a change means you accept the updated policy.