Google Play declarations

Aligned with app version 1.3.19 / versionCode 34 · 18 August 2026. Use this page with the Privacy Policy and Data safety worksheet when filling Play Console.

This page is a good-faith map of the shipped Android app so the store listing, this website, and the Play Console checkboxes match the APK. It is not a lawyer’s opinion and it is not a substitute for the Google Play Developer Policy Center or the U.S. Bureau of Industry and Security encryption rules.

Contents 1. Confirm Developer Program Policies 2. Store listing copy (paste into Play Console) 3. Accept US export laws 4. What encryption the app actually uses 5. Other App content answers 6. Play APK checks before you tick the boxes

1. Confirm the app meets Developer Program Policies

Play Console asks you to confirm that the application meets the Developer Program Policies, and it points to tips on policy-compliant app descriptions. Those tips are about honesty, not marketing volume.

This product is a Christian Bible study app. Religious teaching is allowed. The listing and this website must still be accurate, suitable for a general audience, and free of impersonation, ranking claims, and deal language.

Policy area	How this app meets it
Accurate metadata	Title, short description, full description, screenshots, and this website describe the same app: 1611 KJV reading, optional Together account, optional Cloud Ask, no ads. They do not claim “no accounts” while Together email sign-in exists.
No ranking or deal language	No “#1,” “best,” award badges, “popular,” “free for a limited time,” or “No Ads” in the title. The full description may say the app does not contain ads as a fact, not as a sale badge.
No anonymous testimonials	Listing and site do not quote unnamed reviewers.
Impersonation	The app is not Adrian Rogers, Love Worth Finding, or Bellevue Baptist Church, and is not endorsed by them. That disclaimer is on the listing, the site, and in the app.
Deceptive behavior	Ask is disclosed as cloud composition when Online Mode is on. Together is disclosed as optional email sign-in. Chats are saved on the device; they are not a secret Operator transcript store.
User data	Hosted privacy policy, account-deletion URL, and Data safety answers match the APK. HTTPS for Operator cloud paths. No ads, no advertising ID, no analytics SDK.
User-generated content	Together prayers and group names are optional UGC. Groups are invite-only. Admins can kick or ban. Public website wall shows prayer text only, with no name. Together is 13+.
AI-generated content	Ask Scripture is generative text grounded in retrieved KJV. It is a study helper, not a general chatbot, and it does not speak as God. Users must check claims against the in-app Bible text.
Restricted permissions	Microphone is optional voice input. Notifications are optional Daily Verse. `REQUEST_INSTALL_PACKAGES` is for private LMCloud APK updates and must not be in a Play-uploaded build.
Children / Families	Not Designed for Families. Target age 13 and up because Together has UGC. Core reading does not require an account.
Ads and IAP	Contains ads: No. In-app purchases: No.

You may tick “The application meets Developer Program Policies” when the listing you paste matches section 2, the privacy and deletion URLs resolve on HTTPS, Data safety matches data-safety.html, and the Play AAB follows section 6.

2. Store listing copy

Paste these into Play Console → Grow → Store presence → Main store listing. They also live in fastlane/metadata/android/en-US/. Title ≤ 30 characters. Short description ≤ 80. Full description ≤ 4,000. Default language: English (United States).

Field	Paste this
App name	King James 1611 Assistant
Short description	Christ-centered offline King James Bible study and teaching
Full description	Use the text in `fastlane/metadata/android/en-US/full_description.txt` (also summarized below).
App category	Books & Reference (primary purpose is Bible reading and study, not a social network)
Tags	Only words that describe the app (Bible, King James, Christian study). Do not paste a keyword block.
Contact email	The developer email on the Play developer account (also named as contact in the Privacy Policy)
Privacy policy URL	https://kingjames1611assistant.pages.dev/privacy.html
Account deletion URL	https://kingjames1611assistant.pages.dev/account-deletion.html

Full description (same as fastlane)

King James 1611 Assistant helps you read and study the 1611 King James Bible on Android. The app is Christ-centered and offline-first: the Bible text, search, notes, and reading plans stay on your phone.

Read Scripture book by book, including the Apocrypha as printed in 1611. Display spelling is eased for reading; the wording used for study and citations is the 1611 text. Search the Word, keep bookmarks, highlights, and notes, follow reading plans, open Easton’s Bible Dictionary, and view offline maps. Listen can speak Scripture with a male voice on the device.

Ask Scripture retrieves verses on the phone, then composes a teaching answer. In the standard Android app, that composition uses a gated HTTPS connection when you turn Online Mode on. Saved chats stay encrypted on the device. Ask is a Bible-study helper, not a general chatbot, and it is not the voice of God. Check every claim against the King James text in the app.

Together is optional. Invite-only groups can share a reading plan and prayer. Together uses an email sign-in. You do not need a Together account to read the Bible. Published prayer request text also appears on the public website prayer wall without a name.

Online Mode is off by default. When it is off, Together, model downloads, and remote pairing stay blocked. The app does not contain ads, in-app purchases, or analytics SDKs.

This app is not Adrian Rogers, Love Worth Finding, or Bellevue Baptist Church, and is not endorsed by them.

The program source is licensed under the GNU GPL v3. The King James text is public domain in most countries. In the United Kingdom, Crown printing rights for the Authorised Version may still apply to commercial printing.

Graphics

Icon, screenshots, and feature graphic must show the real app, not another product, and must be suitable for a general audience.
Do not overlay “#1,” “FREE,” sale badges, or fake notification dots on the icon.
Do not use Adrian Rogers, Love Worth Finding, or Bellevue artwork or names as if this were their official app.
Scripture includes historical accounts of war and judgment. Store art should not turn that into graphic violence or a combat game.

3. Accept US export laws

Play Console requires this acknowledgment because Google hosts the app on U.S. servers. A download by someone outside the United States is treated as an export, even if you are not a U.S. person. The certification is:

You acknowledge that the software may be subject to United States export laws, including rules for software with encryption functions, and you certify that the application is authorized for export from the United States under those laws.

You may accept that declaration for this app on the following facts (not legal advice):

The app is a mass-market Bible study product. Information security is not its primary function.
Encryption is ordinary commercial cryptography: HTTPS/TLS for network paths we operate, and AES-256 via Android platform APIs (AndroidX Security Crypto + Android Keystore) for chats and secrets at rest.
The app does not implement a custom or proprietary cryptographic algorithm, does not include a standalone crypto toolkit for others to build with, and does not add encryption beyond those standard libraries.
Program source is published under GNU GPL v3 (publicly available software). Model files you may download remain under the model publishers’ licenses.
Google Play already blocks distribution to U.S.-embargoed destinations. Users must not evade that block.

Those facts are the usual path for a consumer Android app that only uses OS TLS and OS-provided AES, often discussed as mass-market / Category 5 Part 2 encryption under the Export Administration Regulations (including License Exception ENC, 15 C.F.R. § 740.17) and, where it applies, publicly available encryption software. Classification and any SNAP-R reporting are the publisher’s duty. See Play export compliance and BIS mass-market encryption.

4. Encryption inventory

Use this table if Console or a reviewer asks what encryption the app uses.

Where	What	Purpose
Together (Supabase)	HTTPS / TLS 1.2+	Account, groups, prayers in transit
Cloud Ask (Cloudflare Worker)	HTTPS / TLS 1.2+	Grounded prompt and answer in transit
Hugging Face catalog models	HTTPS / TLS 1.2+	Optional model file download
Gated Gemma 4 E4B Worker	HTTPS / TLS 1.2+	Optional model file download
Ask chats on the phone	AES-256-GCM EncryptedFile, Android Keystore MasterKey	Confidentiality at rest on device
Together session tokens	EncryptedSharedPreferences (AES-256-SIV keys, AES-256-GCM values)	Keep the user signed in on that phone
LMCloud pairing secret	Same EncryptedSharedPreferences / Keystore	Pairing token at rest
LMCloud to your PC	HTTPS when you use HTTPS; HTTP only on private LAN/CGNAT addresses gated in-app	Your PC, not Operator servers. Do not mark this path as “all traffic encrypted” without the privacy caveat.

Play Data safety “encrypted in transit?” Yes for data the Operator collects (Together, Cloud Ask, HTTPS model hosts). See Data safety for the LMCloud caveat.

Export questionnaire, typical answers

Question (wording varies)	Answer for this app
Does the app use encryption?	Yes
Only authentication / digital signature?	No — it also uses TLS and AES for confidentiality
Standard HTTPS and OS crypto libraries only?	Yes — Android TLS, AndroidX Security Crypto, Android Keystore. No custom cipher.
Proprietary or non-standard crypto?	No
Primarily an information-security product?	No — Bible study
Authorized for export from the United States?	Yes, as mass-market / publicly available standard encryption as described above. You still must not distribute to embargoed destinations.

5. Other Play Console → App content answers

Console item	Answer
Privacy policy	Required. URL in section 2.
Ads	No
In-app purchases / Play billing	No
Target audience	13–15, 16–17, and 18+. Not Designed for Families. Together accounts are 13+ (or the higher digital-consent age).
News app	No
COVID-19	No
Government	No
Financial features	No
Health	No. Bible teaching is not medical advice. Crisis copy points people to local emergency help.
Data safety	Follow data-safety.html. The Play flavor includes Together and Cloud Ask, and omits `REQUEST_INSTALL_PACKAGES`.
Account deletion	Yes, in-app and on this site. URL in section 2.
User-generated content	Yes, optional Together. Invite-only groups; 13+ sign-up gate; in-app Report; local Block; admin kick/ban; public wall is anonymous text only.
AI-generated content	Yes. Ask Scripture is text-to-text, KJV-grounded. In-app Report on answers is sent to the Ask host when Online Mode is on. Declare it. Keep the in-app teaching disclaimers.
Content rating (IARC)	Complete honestly. This is a Bible, not a game. The text includes historical violence. Together has user prayer text. Do not mark the app as a social network as its main purpose.

6. Before you upload a Play AAB

Build the Play flavor: gradlew.bat :app:bundlePlayRelease (or assemblePlayRelease for an APK). Do not upload assembleStandardDebug. The standard flavor keeps REQUEST_INSTALL_PACKAGES for private LMCloud updates.
Confirm the merged Play manifest does not declare REQUEST_INSTALL_PACKAGES (app/src/play/AndroidManifest.xml removes it). The F-Droid flavor also removes it.
Use a release AAB signed for Play App Signing, not a debug APK from a private phone install.
Package id for this Play product is com.example.kingjames1611assistant unless you create a new Play application id. The F-Droid id org.kingjames1611assistant is a different app.
Screenshots should match the uploaded version (reader, search, Ask, Together if present).
If you add ads, analytics, a new account type, or a new cloud host, update this page, privacy, Data safety, and the listing in the same release.

Official policy tips Play itself cites for this checkbox: Best practices for your store listing.