This policy explains how the Apporo platform mobile app (the "App") handles your data. The App is offered under the brand of APPORO UNION INC. ("Apporo", "we" or "us"); Apporo is the App's brand and service provider and is responsible for data processing at the App level. The App is developed for Apporo by WOOW TECH CO., LTD. (the "Developer"), which publishes it on the App Store and Google Play under its own developer account. Data inside your organization's Odoo server is the responsibility of that organization.

This policy applies only to the Apporo platform app. Other Apporo products and web services have their own privacy policies.

1. How the App works, and who is responsible for what

The App is an interface to your organization's Odoo server. You enter the server address yourself, and the App connects only to the address you entered.

• Your organization owns and operates that Odoo server and decides what is stored in it, for how long, who may view it and when it is deleted. For personal data on that server, your organization is the party that determines the purposes of processing (the data controller).
• Apporo (us) is the App's brand and service provider and is responsible for data processing at the App level: the data the App keeps on your device, the handling of push tokens, and the support and request emails you send us. Once push notifications are available, Apporo will also provide the technical infrastructure they need (section 4). For those activities we process data within the scope described in this policy.
• The Developer (WOOW TECH CO., LTD.) builds the App software on Apporo's behalf and publishes the App on the app stores as the developer of record. On Apporo's behalf it also helps with technical support and account deletion work.

Apart from the push notifications described in section 4, data moving between your phone and your organization's server does not pass through servers operated by Apporo or the Developer.

2. Where accounts come from

The App has no sign-up function, and accounts cannot be created inside the App. Your account is created by your organization's administrator and is one of two kinds:

1. Employee account (an Odoo "internal user"). This is the App's main audience, usually linked to an employee record and attendance features.
2. Portal account (an Odoo "portal user"). Some organizations set up this kind of account for customers or partners.

If you do not have an account yet, contact your organization's administrator. The deletion path differs between the two; see Account & data deletion.

3. The paths your data travels

4. Push notifications (the part that involves third parties)

Current status: push notifications for Apporo platform are not yet available as of the publication of this page. The Apporo push authorization service described below is planned and not yet in operation, so no organization's Odoo server can currently send notifications through the Apporo platform push channel. When you allow it, the App still asks the system for notification permission and obtains a push registration token from Google Firebase (see section 3 and rows 7 and 23 in section 5) so that it is ready once push becomes available. The rest of this section describes how push notifications will work once available; we will update this policy before then.

The App registers your device with your organization's Odoo server only if that server has enabled Apporo platform push. Signing in does not mean push is available; if the server has not enabled it, the App does not register the device there and you will not receive push notifications from that server.

The content of a push notification — the sender's name and the first 200 characters of the message as plain text — is sent by your organization's Odoo server and passes in the clear (protected only by TLS in transit, not end-to-end encrypted) through Google's Cloud Messaging service, and on iOS additionally through Apple's Push Notification service. In other words, notification content does leave your organization's server and passes through third parties. If your organization handles sensitive message content, its administrator should assess whether to enable this feature.

On the device, the Android App marks notifications as private: if your system settings hide sensitive content on the lock screen, the notification text is not shown there. On iOS, whether previews appear on the lock screen follows your choice in the system Notifications settings.

The device record held by your organization's Odoo contains only: the user, the push token, the device name, the platform, the app the record belongs to (Apporo platform), an active flag, the last-seen time and a consecutive-failure count. It holds no location, no IP address and no notification content. Each user keeps at most 10 active devices per server; beyond that, the oldest is deactivated automatically. When you sign out or remove a connection in the App, the App asks the server to delete this device's Apporo platform record.

The push token is sent by the App directly to your organization's Odoo and does not pass through servers operated by Apporo or the Developer. Apporo plans to operate a push authorization service (planned, not yet in operation) that only supplies enabled Odoo servers with short-lived sending authorization. That service never handles notification content; its audit log records server-deployment-level events only (deployment identifier, event type, source IP) and contains no end-user personal data. The service and its data are planned to be located in Google Cloud's Oregon, USA region (us-west1).

5. Categories of data we handle

This table maps onto both stores' privacy questionnaires: "Linked to you" corresponds to Apple's Linked to You and Google's "linked to the user's identity"; "Used for tracking" corresponds to Apple's Used for Tracking. The table scrolls horizontally.

6. Third-party services and recipients

We do not sell personal data and do not share any data for advertising or cross-app tracking. There are no data brokers, ad networks or analytics services (such as Google Analytics) in the App; technical data that the Firebase components themselves send to Google is described in row 23 of section 5. We may disclose data where required by law, court order or a lawful request from a public authority, to the extent required.

7. Permissions

7.1 Location (while using the App only)

Location has exactly one purpose: when you clock in or out on an Odoo web page and that page requests your position, so the attendance record carries the coordinates.

• The App has no background location permission and no background location service. Android declares only foreground precise and approximate location; iOS declares only "While Using the App".
• Every web location request must first pass four checks inside the App: (1) the page origin must be HTTPS; (2) the origin host must match the Odoo server you are currently signed in to; (3) the location toggle in App settings must be on; (4) the operating-system permission must allow it. Failing any one refuses the request.
• The App itself stores no coordinates and never sends them to Apporo, the Developer or any third party. The page returns them to your organization's own Odoo, where they become part of the attendance record.
• You can turn location off at any time in App settings or system settings. When it is off, the App refuses every web location request.
• The platforms behave differently: on iOS, every web location request re-runs all four checks; on Android, the system remembers your grant for a given origin, so later requests may not prompt again (you can revoke it at any time in system settings).
• Whether you can still clock in after refusing location depends on your organization's Odoo configuration — ask your administrator.

7.2 Camera and photo library

Used only when a page in your organization's Odoo presents a file-upload field and you actively choose to take a photo or pick a file. On Android, a photo taken with the camera inside the App leaves a copy in the App's private storage. That copy is not deleted automatically; it is removed when you uninstall the App.

7.3 Notifications

Used to display messages and activity notifications from your organization's Odoo. You can turn them off in your phone's system settings. Refusing or disabling notifications does not affect sign-in or other features.

7.4 Biometrics

Used only to unlock the App itself. Verification is performed entirely by the operating system; the App never receives or stores your fingerprint or face data.

8. Retention

8.1 On your phone

Local connection settings, passwords, sessions, preferences and web cache remain until you remove that connection, sign out or uninstall the App. When you sign out or remove a connection in the App, the App immediately asks the server to delete this device's push record (see 8.2). Uninstalling removes all of the App's local data, including the camera photo copies described above.

8.2 On your organization's Odoo server

Retention of that data is decided by your organization under its own policies and applicable law; the App neither configures nor can read those settings. This covers attendance records, messages, uploaded attachments and push device records. Ask your organization's administrator which retention policy applies to you.

The App attempts to delete the push device record when you sign out or remove a connection, but if there is no network connection at that moment the attempt fails and is not retried automatically. You can complete it by signing in and out again once you are back online, or ask your administrator to delete the record in Odoo.

8.3 At Google and Apple

Notification content is handled by Google and Apple during delivery. Their retention periods and processing locations are determined by their own terms and cannot be specified by the App. The same applies to the installation ID, App version and technical diagnostic data that the Firebase components send to Google (row 23 in section 5), which are retained under Google's terms.

8.4 At Apporo

• Push authorization service audit log (no end-user personal data): the service is not yet in operation, so no such log exists; before it starts, we will state its retention period in this policy.
• Support, access or deletion requests you email to us, and records of how we handled them: kept until the request is completed and then for as long as needed to demonstrate that we handled it lawfully, after which they are deleted. They are used only to answer your request and to demonstrate that we handled it lawfully.
• Backups of our systems: kept for at most 30 days on a rotating cycle and used only for disaster recovery. Deleted data disappears from backups as they rotate.

8.5 Data we are required by law to keep

Where applicable law (for example accounting, tax or employment rules) requires data to be kept, it is not deleted before the statutory period expires and is not used for any other purpose. Most such data lives in your organization's own Odoo, and that organization meets the obligation.

9. International transfers

The location of your organization's Odoo server is chosen by that organization. The App is offered in the United States, Taiwan, Hong Kong, Singapore, Malaysia, Thailand, Indonesia and the Philippines. Once push notifications are enabled, Google and Apple may process push-related data — including notification titles and bodies — on servers outside your country, including in the United States. In addition, whether or not push notifications are available, the installation ID, App version and technical diagnostic data sent by the Firebase components may be processed by Google on servers in the United States and elsewhere. The planned Apporo push authorization service will be located in the United States. Using push notifications means that data is transferred to the countries or regions where those providers operate.

10. Children

The App is business software for workplace use. It is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe that personal information of a child under 13 has been provided to us through the App, email us and we will help delete it or pass the request to the relevant organization.

11. Security

• Passwords, sessions and push tokens are stored on Android in keystore-backed AES-256-GCM encrypted storage excluded from cloud backup, and on iOS in a this-device-only Keychain not synced to iCloud.
• The App disables unencrypted HTTP and mixed content entirely and accepts HTTPS servers only.
• Web location requests must pass origin matching and two independent switches (see 7.1).
• Third-party cookies are disabled in the embedded browser, and web data of different accounts is kept separate.
• The App contains no analytics (such as Google Analytics), advertising or crash-reporting components; technical data that the Firebase components themselves send to Google is described in row 23 of section 5.

These are statements of technical measures. They are not a guarantee of absolute security and not a claim of end-to-end encryption. To report a security vulnerability, email us with "Security" in the subject line.

12. Your rights: access, correction and deletion

Depending on the law that applies where you live, you may have the right to access your personal data, obtain a copy, have it corrected or completed, object to or restrict its processing, have it deleted, and withdraw consent.

• Data on your organization's Odoo (most of the data): ask your organization's administrator first, because your organization holds it. You can also view and correct much of it (such as your name and contact details) yourself in Odoo under "My Profile" or "My Account".
• Data on your device: remove the connection in the App or uninstall the App at any time.
• Data held by Apporo (support correspondence, request records, etc.): email [email protected]. If you are not sure whom to contact, write to us anyway; we will help work it out and, where needed, pass the request to your organization.

Who handles requests: Apporo receives and handles requests; the Developer (WOOW TECH CO., LTD.) assists on Apporo's behalf with technical matters and deletion work.

Identity verification: the request must come from the same email address that is registered on your account; if you cannot send it from that address, we will ask your organization's Odoo administrator to confirm your identity. We will never ask for your password.

Response time: we will reply within 5 business days of receiving your request and complete it within 30 days. If the request concerns data on your organization's server, we will forward it to your organization within that time and keep you informed of progress.

We will not discriminate against you for exercising these rights. The full deletion process and its exceptions are on the Account & data deletion page.

13. Additional information for California residents

If the California Consumer Privacy Act (CCPA), as amended by the California Privacy Rights Act (CPRA), applies to our handling of your personal information, the following additional information applies to California residents:

• Categories of personal information collected: identifiers (login, user ID, push token, Firebase installation ID, device name or model); technical diagnostic data (such as the App version, sent to Google by the Firebase components); geolocation data (at clock-in only); electronic information you create at work (message and notification content, uploaded photos and files); internet activity information (IP address, logged by the recipient). Details are in section 5.
• Sources and purposes: provided by you and your device, used to provide App features, authentication, push notifications and security; never for advertising. As stated in Google's SDK privacy disclosures, Google may use the installation ID, App version and technical diagnostic data sent by the Firebase components to operate its services, for analytics and to improve its products, but not for advertising, and this data is not linked to your Odoo account identity.
• Sale and sharing: we do not sell personal information and do not share it for cross-context behavioral advertising. We have no actual knowledge of selling or sharing the personal information of consumers under 16.
• Sensitive personal information: account log-in credentials and precise geolocation are used only to provide the features you request, not to infer characteristics about you.
• Retention: see section 8.
• Your rights: to know, delete and correct, to opt out of sale or sharing, and not to be discriminated against for exercising them. Email [email protected]; you may also use an authorized agent. We will verify requests as described in section 12.

14. "Do Not Track" signals

The App and this website do not track you across third-party websites or apps, and do not allow third parties to collect personal information about your activity across websites through the App. We therefore handle your data the same way whether or not your browser or device sends a Do Not Track or Global Privacy Control signal.

15. Availability and languages

The App is distributed in the United States, Taiwan, Hong Kong, Singapore, Malaysia, Thailand, Indonesia and the Philippines. This policy is available in English and Traditional Chinese; if the versions differ, the English version prevails.

16. Changes to this policy and notification

If this policy changes, we will update the effective and last-updated dates on this page. For material changes (for example new data categories, new recipients or new purposes), we will notify you before they take effect through an in-App notice or an announcement on this website.

17. Contact us

APPORO UNION INC.
Address: 10050 Garvey Ave Suite 207, El Monte, CA 91733, USA
Email: [email protected]
Website: www.apporo.ai

App development and store publishing: WOOW TECH CO., LTD. Please send every privacy question about the App to the email address above.