Google Play Data Safety - Aptora Mobile 360
- Effective Date: August 26, 2026
- Last updated: September 3, 2026
Google Play requires every app to declare what it collects, what it shares and how it protects it. This is that declaration in full. The store listing shows a shortened version of the same answers.
How to read this. Collected means the information leaves the device and reaches your company’s system. Shared means it is passed to a third party for their own use — which nothing here is. Optional means the app works if you decline.
Â
Location
| Data type | Collected | Shared | Required | Why |
|---|---|---|---|---|
| Approximate location | Yes | No | Optional | App functionality — showing the office where field staff are, and finding you on a map |
| Precise location | Yes | No | Optional | App functionality — the same, plus where a photo was taken and where a signature was given |
Â
Collected only where the licensing business has switched location sharing on, and only with the device permission. Never collected in the background by the web app, and never after a reboot by the Android app.
Personal information
| Data type | Collected | Shared | Required | Why |
|---|---|---|---|---|
| Name | Yes | No | Required | App functionality, Account management |
| User IDs | Yes | No | Required | App functionality, Account management |
| Email address | Yes | No | Optional | App functionality — sending documents, and the customer records you work with |
| Phone number | Yes | No | Optional | App functionality — calling a customer, and the customer records you work with |
| Address | Yes | No | Optional | App functionality — the job’s address, so it can be mapped and routed to |
| Race, ethnicity, political or religious beliefs, sexual orientation | No | No | — | Never collected |
Â
Financial information
| Data type | Collected | Shared | Required | Why |
|---|---|---|---|---|
| User payment information | Yes | No | Optional | App functionality — taking a card payment for a job |
| Purchase history | Yes | No | Optional | App functionality — the invoices, estimates and payments recorded against a job |
| Credit score, other financial information | No | No | — | Never collected |
Â
Card details are keyed by the person taking the payment, sent to the licensing business’s own payment gateway over an encrypted connection, and authorized there. The security code is never stored. Aptora is not a payment processor and never holds the money.
Photos, files and messages
| Data type | Collected | Shared | Required | Why |
|---|---|---|---|---|
| Photos | Yes | No | Optional | App functionality — attaching pictures to a job |
| Videos | No | No | — | Not supported |
| Files and documents | Yes | No | Optional | App functionality — attaching a document to a job or a customer |
| Other in-app messages | Yes | No | Optional | App functionality — the in-app chat between colleagues, where the business uses it |
| Emails, SMS or MMS from your device | No | No | — | The app never reads your messages. Mail and texts a business sends are sent from the server. |
| Audio files, music, voice recordings | No | No | — | Never collected |
Â
App activity and performance
| Data type | Collected | Shared | Required | Why |
|---|---|---|---|---|
| App interactions | Yes | No | Required | App functionality — the business’s audit trail of who recorded or changed what |
| Other user-generated content | Yes | No | Optional | App functionality — job notes, signatures and the work you record |
| Crash logs | Yes | No | Required | App functionality — finding and fixing faults |
| Diagnostics | Yes | No | Required | App functionality — the same |
| In-app search history | No | No | — | Searches are answered and not kept |
| Installed apps | No | No | — | Never collected |
| Web browsing history | No | No | — | Never collected |
Â
Device identifiers
| Data type | Collected | Shared | Required | Why |
|---|---|---|---|---|
| Device or other IDs | Yes | No | Optional | App functionality — matching a handset to a person for location sharing, and delivering notifications to one device |
| Advertising ID | No | No | — | There is no advertising in the app |
Â
The identifier the Android app uses is one it generates for itself. It is not your phone’s serial number, IMEI or advertising ID; the app cannot read those and does not try.
Health, fitness, contacts and calendar
None collected. The app has no access to health or fitness data, no access to your contacts, and no access to your calendar.
Security practices
| Data is encrypted in transit | Yes |
| You can request that your data be deleted | Yes |
| Data is sold to third parties | No |
| Data is used for advertising or marketing | No |
| Users are tracked across other apps and websites | No |
| The app is designed for or directed to children | No |
Your data explains how to ask for information to be corrected or deleted, and who to ask.
Who else receives information
Google counts a transfer to a service provider that acts on our instructions as processing rather than sharing, which is why every Shared answer above is No. Being straight about it anyway: hosting and file storage, sign-in, maps and addresses, weather, text messaging and payment authorization are each handled by a named provider, listed with what reaches them in section 5 of the Privacy Notice. None of them is permitted to use the information for anything but the service they provide, and nothing is sold.
Contact
Aptora Corporation
8877 Bourgade Avenue
Lenexa, Kansas 66219
United States
Email: helpdesk@aptora.com
Phone: (913) 492-9930
Web: https://www.aptora.com

