King James 1611 AssistantGoogle Play Data safety (operator worksheet)
Play Data safety is about the Android App, not Tawk.to on this website. Do not mark website chat as App-collected data. If the Play build is F-Droid-like (no Together), answer Together rows as “not collected.” If the Play build is the standard flavor with Together, use the Together rows.
Overview questions
| Console question | Standard flavor (Together capable) | F-Droid flavor |
|---|---|---|
| Does the app collect or share user data? | Yes — only if the user turns Online Mode on and uses Together, Hugging Face download, the gated Cloudflare Gemma E4B download, LMCloud, or device speech. Baseline reading: collected data stays on device and is not shared off device by us | No Together collection. Optional HF / Cloudflare model download / LMCloud / device speech still possible if those code paths remain |
| All users can request deletion? | Yes — account-deletion.html | Uninstall / clear data; no Together account |
| Data encrypted in transit? | Yes for Together (HTTPS), Hugging Face (HTTPS), and the gated Cloudflare model Worker (HTTPS). LMCloud may use HTTPS to your PC or HTTP only on private LAN/CGNAT addresses as gated in-app | Same for remaining network paths |
| Users can request that data be deleted? | Yes | Yes (on-device) |
| Committed to Play Families policy? | No (Together is 13+ UGC) | Optional; still a Bible app with UGC-free default |
| Independent security review? | No (do not claim SOC2 for this App) | No |
Data types — collected? shared? required? purposes
“Collected” in Play means the App sends it off the device. On-device-only storage is generally not “collected” unless it leaves the device. Together is collected. Ask chats are not collected by us. Device speech may send audio to the OEM/Google recognizer — disclose as collected by a third party if you use voice, or explain in privacy (we disclose it; Play’s “ephemeral” processing may apply if not stored by you).
| Play data type | Collected by App/Operator? | Shared with other companies? | Required / optional | Purpose |
|---|---|---|---|---|
| Name (display name) | Yes if Together sign-up | No sale; processor Supabase; visible to group members | Optional (Together) | App functionality |
| Email address | Yes if Together | Supabase Auth as processor | Optional (Together) | Account |
| User IDs | Yes if Together (UUID) | Processor only | Optional (Together) | App functionality |
| User-generated content | Yes: prayers (group + anonymous public text copy), group names, custom plan references, checkmarks, invite codes, badge ids | Group members see names if chosen; public Site wall shows prayer text only; processor Supabase | Optional | App functionality |
| Password | Transmitted to Supabase Auth at sign-in; not stored by the App; Play often lists “other user content” / credentials under account | Auth processor | Optional (Together) | Account |
| Phone number | No | — | — | — |
| Approximate location | No in App. Site chat vendor may infer from IP — not App | — | — | — |
| Precise location | No | — | — | — |
| Photos / videos | No | — | — | — |
| Audio files | Not stored by us. Mic audio may go to Android SpeechRecognizer provider during Ask voice | Possibly Google/OEM, not us | Optional mic | App functionality |
| Messages (Ask chats) | No (on-device encrypted). If user enables LMCloud, messages go to the user’s PC, not Operator servers | No (unless user pastes into Site chat) | Optional | App functionality |
| Installed apps | No | — | — | — |
| Crash logs | No Operator SDK | — | — | — |
| Diagnostics (our store) | On-device only, content-free; not sent to us | No | — | Not “collected” |
| Device or other IDs (AAID) | No advertising ID. Optional Gemma 4 E4B download stores a short-lived hash of date+IP on Cloudflare KV for a 2/day cap — not an advertising ID | Cloudflare as processor for that download | Optional E4B | App functionality / abuse prevention |
| Health / finance | No | — | — | — |
Data sharing (Play definition)
Mark shared only if another company can use the data for its own purposes (ads, etc.). Supabase as your backend processor is typically not “shared” if used solely to provide the App, but you still list it under collection and in the privacy policy. Hugging Face sees IP on download (third-party host). Cloudflare sees IP on the gated E4B Worker (processor for that file). Tawk is Site-only — omit from App Data safety.
Security practices
- Data in transit encrypted: Yes for Operator cloud (Together HTTPS), HF HTTPS, and the gated Cloudflare model Worker HTTPS.
- Users can request deletion: Yes.
- Do not claim “independent review” or “encrypted in transit” for LMCloud HTTP-on-100.x without the privacy caveat.
Ads, IAP, permissions check
| Item | Declare |
|---|---|
| Contains ads | No |
| In-app purchases | No |
| Sensitive permissions | Microphone (optional voice); notifications (optional daily verse); Internet; boot; wake lock; package-install only on non-Play companion builds |
| Privacy policy URL | Hosted privacy.html |
| Account deletion URL | Hosted account-deletion.html |
Common rejection traps this page is meant to close
- Declaring “no data collected” while Together email sign-up exists in the standard APK.
- Declaring “no account” while email/password Auth is in the standard APK.
- Omitting microphone while
RECORD_AUDIOis in the manifest. - Claiming chats are never processed off-device while LMCloud or SpeechRecognizer can send text/audio off the phone (user-directed / OS vendor).
- Using this Site’s Tawk widget as if it were in the APK.
- Claiming F-Droid and Play are the same package id or the same signing key.