Store Privacy Answers — Personal Assist
Standardised reference guide for submitting Personal Assist in Apple App Store Connect ("App Privacy") and Google Play Console ("Data safety"), aligning with our Privacy Policy.
https://alltechzone.au/personal-assist/privacyOff-Device Data Flows
Both stores define "collect" as transmitting data off the physical device, whether to the developer or to a third party (such as an external AI service). Data remaining on the device is not counted as collection. Personal Assist has no backend servers.
Text sent to Coach (and earlier corrections for practice drills)
Counts as CollectionTrigger: Only if user adds their own API key and asks for a grammar/writing check
Destination: Anthropic, OpenAI or Google directly from device
Explanation: Yes, to a third party. Must be declared in both stores.
Dictation audio when no offline model is installed
Not CollectionTrigger: When the user presses dictate
Destination: Apple or Google platform speech service
Explanation: No. OS-level keyboard service; the app never receives or stores the audio itself.
Exported encrypted backup file
Not CollectionTrigger: When the user manually exports and chooses a destination
Destination: Wherever the user shares it (cloud drive, local file, etc.)
Explanation: No. User-initiated sharing, AES-256 encrypted, never received by Alltechzone.
* Zero SDKs: There is no analytics, crash reporting, advertising, or tracking SDK in the app.
Apple App Store Connect — App Privacy
Do you or your third-party partners collect data from this app?
Answer: Yes. (This covers solely the optional English Coach feature; if the Coach were absent, the answer would be No).
Declare exactly one data type:
User Content → Other User Content (the text the user submits for Coach checking).
- Used for: App Functionality.
- Linked to the user's identity? No. There is no user account. The request carries the user's own API key, which authenticates with their own AI provider account, not Alltechzone.
- Used for tracking? No.
Leave all other categories unticked:
Contact Info, Health & Fitness, Financial Info, Location, Identifiers, Usage Data, and Diagnostics must remain UNTICKED. The weight log is entirely local and is never collected or transmitted.Tracking & ATT
The app does not track users. No App Tracking Transparency (ATT) prompt is required, and the Privacy Manifest specifies: NSPrivacyTracking = false.
Export Compliance
The app utilizes standard encryption (SQLCipher AES-256) strictly to protect user data locally. In Xcode: ITSAppUsesNonExemptEncryption = false, which bypasses export compliance delays.
Google Play Console — Data Safety
1. Does your app collect or share any of the required user data types?
Answer: Yes (for the optional English Coach only).
2. Is all user data collected by your app encrypted in transit?
Answer: Yes (Direct HTTPS requests to OpenAI, Anthropic, or Google APIs).
3. Do you provide a way for users to request that their data is deleted?
Answer: Yes (The in-app "Settings → Erase everything" mechanism purges all data on the device; the app maintains no server data).
Declare exactly one data type:
App activity → Other user-generated content (text evaluated by the Coach).
- Collected: Yes. Shared: Yes (Transmitted directly to third-party AI service upon user request).
- Processed ephemerally? Unticked (Third-party AI provider retention is beyond device control).
- Required or optional? Optional (The app functions completely without configuring the Coach).
- Purposes: App functionality.
Android Permissions Justifications:
CAMERACapturing photos to attach to notes.
RECORD_AUDIOLocal dictation functionality.
POST_NOTIFICATIONSScheduled task reminders.
SCHEDULE_EXACT_ALARMTime-accurate local reminder notifications.
USE_BIOMETRICAuthenticating access to the password vault.
Note: On Android 13+, the app uses the system Photo Picker and does not request broad media read permissions.
Need custom privacy documentation or developer assistance?
Our team assists developers with mobile store submissions and privacy compliance.