Metadata updates for Play Store distribution

This commit is contained in:
James Babcock committed 2026-11-09 12:08:37 -08:00
1 parent 70ec2a0d6a
commit 8b70585da8
12 files changed
+132 -47

No files matched your search

+10 -4
View File
@@ -264,15 +264,21 @@ if (faceclawVersionFile.exists()) {
faceclawVersionName = faceclawVersionMatch.group(1) faceclawVersionName = faceclawVersionMatch.group(1)
} }
} }
def faceclawBuildRevision = System.getenv("FACECLAW_ANDROID_BUILD_REVISION") ?: "0"
if (!(faceclawBuildRevision ==~ /[0-4]/)) {
throw new GradleException("FACECLAW_ANDROID_BUILD_REVISION must be an integer from 0 to 4")
}
def faceclawVersionCode = { def faceclawVersionCode = {
// Prerelease labels belong in versionName, not the numeric versionCode. // Prerelease labels belong in versionName, not the numeric versionCode.
def parts = (faceclawVersionName.split('-')[0].tokenize('.') + ["0", "0"]).take(3)*.toInteger() def parts = (faceclawVersionName.split('-')[0].tokenize('.') + ["0", "0"]).take(3)*.toInteger()
return parts[0] * 10000 + parts[1] * 100 + parts[2] // Last digit: build revision * 2, plus form factor (phone 0, Wear OS 1).
// Play requires distinct version codes even on separate form-factor tracks.
return (parts[0] * 10000 + parts[1] * 100 + parts[2]) * 10 + faceclawBuildRevision.toInteger() * 2
}() }()
android { android {
compileSdkVersion 35 compileSdkVersion 36
buildToolsVersion "35" buildToolsVersion "36.0.0"
// ndkVersion "" // ndkVersion ""
sourceSets.main { sourceSets.main {
@@ -282,7 +288,7 @@ android {
defaultConfig { defaultConfig {
minSdkVersion 24 minSdkVersion 24
targetSdkVersion 35 targetSdkVersion 36
ndk { ndk {
// The NativeScript platform build.gradle has already added all four // The NativeScript platform build.gradle has already added all four
// ABIs by the time app.gradle is applied, and abiFilters is additive, // ABIs by the time app.gradle is applied, and abiFilters is additive,
+25 -1
View File
@@ -5,6 +5,8 @@ collects and shares information when you use an iOS TestFlight build, even
when Faceclaw statistics are set to None. Information you voluntarily send when Faceclaw statistics are set to None. Information you voluntarily send
us, such as feedback, may also identify you. This policy describes these us, such as feedback, may also identify you. This policy describes these
separate channels and the third-party services you can choose to use. separate channels and the third-party services you can choose to use.
On Android, Google ML Kit also collects SDK diagnostics separately from
Faceclaw statistics, as described below.
## Usage Statistics ## Usage Statistics
@@ -16,7 +18,8 @@ your choice at any time in Settings > Privacy > Faceclaw statistics. Until
you choose, it is None. This setting controls only Faceclaw's own statistics. you choose, it is None. This setting controls only Faceclaw's own statistics.
With None, Faceclaw sends and stores none of its own usage statistics. This With None, Faceclaw sends and stores none of its own usage statistics. This
does not disable Apple's TestFlight reports or services you choose to use. does not disable Apple's TestFlight reports, Google ML Kit diagnostics, or
services you choose to use.
With Minimal, Faceclaw keeps counts on your phone and sends them about once a With Minimal, Faceclaw keeps counts on your phone and sends them about once a
day to stats.faceclaw.org, a server run by Faceclaw's developers: day to stats.faceclaw.org, a server run by Faceclaw's developers:
@@ -48,6 +51,27 @@ phone, and stops all reports; turning them back on starts a new identifier.
The statistics server doesn't record the IP addresses reports come from. The statistics server doesn't record the IP addresses reports come from.
## Android and Google ML Kit
Android translation and language identification use Google ML Kit. The
developer QR-code scanner uses Google's code scanner. Text and scanner
images are processed on-device, but the SDKs send Google diagnostic and
usage metrics over HTTPS: device/app details, installation identifiers,
timings, errors, feature events, input/output sizes, and detected or
configured languages. Translation also uses Firebase installation and
remote-configuration services. This reporting is separate from the
Faceclaw statistics setting; selecting None does not turn it off. Faceclaw
does not provide a switch to disable these SDK diagnostics.
These metrics do not include the text being translated or scanned images.
Cloud transcription and assistant providers are separate, as described below.
For Google's handling of SDK metrics, see:
https://developers.google.com/ml-kit/android-data-disclosure
https://developers.google.com/ml-kit/terms
https://policies.google.com/privacy
## iOS and TestFlight ## iOS and TestFlight
For TestFlight builds, Apple automatically collects crash reports and beta For TestFlight builds, Apple automatically collects crash reports and beta
+1 -1
View File
@@ -39,7 +39,7 @@ The instructions below build the Android app.
If you want to customize faceclaw, the best way to do it is to download the If you want to customize faceclaw, the best way to do it is to download the
source code and using a coding agent such as Codex or Claude Code. source code and using a coding agent such as Codex or Claude Code.
To compile, you will need an Android SDK environment with SDK version 35 To compile, you will need an Android SDK environment with SDK version 36
installed and licenses accepted, and the ANDROID_HOME pointing to the install. installed and licenses accepted, and the ANDROID_HOME pointing to the install.
You will need Nativescript installed, and a JDK environment (v21), with the You will need Nativescript installed, and a JDK environment (v21), with the
JAVA_HOME environment variable pointed at it. You will also need a reasonably JAVA_HOME environment variable pointed at it. You will also need a reasonably
+3
View File
@@ -4,3 +4,6 @@
*/ */
export const IOS_PRIVACY_SUMMARY = export const IOS_PRIVACY_SUMMARY =
"With TestFlight, crash/usage reports continue even with None. See Privacy policy for details."; "With TestFlight, crash/usage reports continue even with None. See Privacy policy for details.";
export const ANDROID_PRIVACY_SUMMARY =
"Google ML Kit diagnostics for translation and QR scanning are separate from this setting. See Privacy policy for details.";
+3 -3
View File
@@ -32,9 +32,9 @@ export class DataCollectionPage implements OnboardingPage {
paint(image: GrayImage, focused: boolean): void { paint(image: GrayImage, focused: boolean): void {
const top = drawPageHeading( const top = drawPageHeading(
image, image,
"Data Sharing", "Faceclaw Statistics",
(global.isIOS ? "If using TestFlight, crash/usage reports cannot be disabled here. " : "") + (global.isIOS ? "TestFlight reports are separate. " : "Google ML Kit diagnostics are separate. ") +
"Choose how much data you want to share. Change later in Settings > Privacy.", "Choose Faceclaw statistics below. Details and controls: Settings > Privacy.",
3, 3,
) + CONTENT_GAP; ) + CONTENT_GAP;
const body = onboardingFont("body"); const body = onboardingFont("body");
+3 -3
View File
@@ -28,7 +28,7 @@ import { LIST_ROW_TEXT_INSET, lineStep } from "./metrics";
import { Layer, type LayerContext } from "./layers"; import { Layer, type LayerContext } from "./layers";
import { GrayImage } from "~/graphics/image"; import { GrayImage } from "~/graphics/image";
import type { DataCollectionLevel } from "../analytics/analytics-store"; import type { DataCollectionLevel } from "../analytics/analytics-store";
import { IOS_PRIVACY_SUMMARY } from "../analytics/privacy-disclosure"; import { ANDROID_PRIVACY_SUMMARY, IOS_PRIVACY_SUMMARY } from "../analytics/privacy-disclosure";
export type NightscoutSettings = { export type NightscoutSettings = {
siteUrl: string; siteUrl: string;
@@ -858,7 +858,7 @@ const DATA_COLLECTION_LABELS: Record<DataCollectionLevel, string> = {
// What each level collects is set out in app/analytics/analytics-store.ts and // What each level collects is set out in app/analytics/analytics-store.ts and
// the privacy policy (PRIVACY); keep these in step with both. // the privacy policy (PRIVACY); keep these in step with both.
const DATA_COLLECTION_SUMMARIES: Record<DataCollectionLevel, string> = { const DATA_COLLECTION_SUMMARIES: Record<DataCollectionLevel, string> = {
none: "Disable all data sharing", none: "No Faceclaw statistics",
minimal: "Version, devices, and connection reliability statistics", minimal: "Version, devices, and connection reliability statistics",
full: "More detailed usage data", full: "More detailed usage data",
}; };
@@ -877,7 +877,7 @@ export const dataCollectionSetting = new ConfigSettingEnum<DataCollectionLevel>(
values: ["none", "minimal", "full"], values: ["none", "minimal", "full"],
formatValue: (value) => DATA_COLLECTION_LABELS[value], formatValue: (value) => DATA_COLLECTION_LABELS[value],
description: description:
(global.isIOS ? IOS_PRIVACY_SUMMARY + " " : "") + (global.isIOS ? IOS_PRIVACY_SUMMARY : ANDROID_PRIVACY_SUMMARY) + " " +
"Optional statistics Faceclaw may send its developers once a day, to help fix problems and improve the " + "Optional statistics Faceclaw may send its developers once a day, to help fix problems and improve the " +
"app. None: no Faceclaw statistics are stored or sent. Minimal: the app version, which devices are " + "app. None: no Faceclaw statistics are stored or sent. Minimal: the app version, which devices are " +
"paired and in use, and how reliable the connection to them is. Full: also settings chosen from fixed " + "paired and in use, and how reliable the connection to them is. Full: also settings chosen from fixed " +
+1 -1
View File
@@ -16,7 +16,7 @@ kotlin {
} }
android { android {
namespace = "com.faceclaw.shared" namespace = "com.faceclaw.shared"
compileSdk = 35 compileSdk = 36
minSdk = 24 minSdk = 24
compilerOptions { jvmTarget.set(JvmTarget.JVM_17) } compilerOptions { jvmTarget.set(JvmTarget.JVM_17) }
withHostTestBuilder {}.configure {} withHostTestBuilder {}.configure {}
+55 -26
View File
@@ -1,7 +1,7 @@
#!/bin/bash #!/bin/bash
# Build signed release APKs at dist/Faceclaw-<version>.apk (phone) and # Build signed release APKs and AABs at dist/Faceclaw-<version>.{apk,aab}
# dist/Faceclaw-Wear-<version>.apk (watch), where <version> comes from # (phone) and dist/Faceclaw-Wear-<version>.{apk,aab} (watch), where <version>
# FACECLAW_VERSION in app/version.ts. Both are signed with the same key: # comes from FACECLAW_VERSION in app/version.ts. All use the same key:
# the Wearable Data Layer only routes between apps with matching package # the Wearable Data Layer only routes between apps with matching package
# names and signing keys. # names and signing keys.
# #
@@ -17,18 +17,20 @@ ROOT="$(cd "$(dirname "$0")/.." && pwd)"
cd "$ROOT" cd "$ROOT"
source scripts/before_build.sh source scripts/before_build.sh
if [ ! -f "$ANDROID_KEYSTORE" ]; then export FACECLAW_ANDROID_BUILD_REVISION="${FACECLAW_ANDROID_BUILD_REVISION:-0}"
echo "Keystore not found: $ANDROID_KEYSTORE (set ANDROID_KEYSTORE in build_paths.sh)" >&2 case "$FACECLAW_ANDROID_BUILD_REVISION" in
[0-4]) ;;
*) echo "FACECLAW_ANDROID_BUILD_REVISION must be an integer from 0 to 4" >&2; exit 1 ;;
esac
if [ ! -f "${ANDROID_KEYSTORE:-}" ]; then
echo "Keystore not found: ${ANDROID_KEYSTORE:-unset} (set ANDROID_KEYSTORE in build_paths.sh)" >&2
exit 1 exit 1
fi fi
# build.sh is the machine-specific wrapper that exports JAVA_HOME/ANDROID_HOME. # before_build.sh loads JAVA_HOME/ANDROID_HOME from build_paths.sh.
# Pick up its exports so keytool and the build use the same JDK.
if [ -f build.sh ]; then
eval "$(grep '^export ' build.sh)"
fi
if ! command -v keytool >/dev/null; then if ! command -v keytool >/dev/null; then
echo "keytool not found; set JAVA_HOME (usually via build.sh)" >&2 echo "keytool not found; set JAVA_HOME and PATH in build_paths.sh" >&2
exit 1 exit 1
fi fi
@@ -52,44 +54,71 @@ if [ -z "$ALIAS" ]; then
printf '%s\n' "$LISTING" >&2 printf '%s\n' "$LISTING" >&2
exit 1 exit 1
fi fi
echo "Signing as '$ALIAS', version $VERSION" echo "Signing as '$ALIAS', version $VERSION, Android build revision $FACECLAW_ANDROID_BUILD_REVISION"
read -r -s -p "Key passphrase for '$ALIAS' (empty = same as keystore): " KEY_PASS read -r -s -p "Key passphrase for '$ALIAS' (empty = same as keystore): " KEY_PASS
echo echo
KEY_PASS="${KEY_PASS:-$STORE_PASS}" KEY_PASS="${KEY_PASS:-$STORE_PASS}"
OUT="dist/Faceclaw-$VERSION.apk" OUT="dist/Faceclaw-$VERSION.apk"
BUNDLE_OUT="dist/Faceclaw-$VERSION.aab"
WEAR_OUT="dist/Faceclaw-Wear-$VERSION.apk" WEAR_OUT="dist/Faceclaw-Wear-$VERSION.apk"
WEAR_BUNDLE_OUT="dist/Faceclaw-Wear-$VERSION.aab"
mkdir -p dist mkdir -p dist
rm -f "$OUT" "$WEAR_OUT" # Keep existing release artifacts until every build and verification succeeds.
STAGING_DIR="$(mktemp -d "$ROOT/dist/.release-XXXXXX")"
trap 'rm -rf "$STAGING_DIR"' EXIT
PHONE_SIGNING_ARGS=(
--key-store-path "$ANDROID_KEYSTORE"
--key-store-password "$STORE_PASS"
--key-store-alias "$ALIAS"
--key-store-alias-password "$KEY_PASS"
)
echo "=== Building Android app ===" echo "=== Building Android app ==="
npx nativescript build android --release \ npx nativescript build android --release \
--key-store-path "$ANDROID_KEYSTORE" \ "${PHONE_SIGNING_ARGS[@]}" --copy-to "$STAGING_DIR/phone.apk"
--key-store-password "$STORE_PASS" \
--key-store-alias "$ALIAS" \ echo "=== Building Android app bundle ==="
--key-store-alias-password "$KEY_PASS" \ npx nativescript build android --release --aab \
--copy-to "$OUT" "${PHONE_SIGNING_ARGS[@]}" --copy-to "$STAGING_DIR/phone.aab"
# Wear app: sign with the same key via AGP's injected signing properties, so # Wear app: sign with the same key via AGP's injected signing properties, so
# no signing config needs to live in the wear build files. # no signing config needs to live in the wear build files.
echo "=== Building Wear app ===" echo "=== Building Wear app ==="
(cd wear && ./gradlew :app:assembleRelease \ (cd wear && ./gradlew :app:assembleRelease :app:bundleRelease \
-Pandroid.injected.signing.store.file="$ANDROID_KEYSTORE" \ -Pandroid.injected.signing.store.file="$ANDROID_KEYSTORE" \
-Pandroid.injected.signing.store.password="$STORE_PASS" \ -Pandroid.injected.signing.store.password="$STORE_PASS" \
-Pandroid.injected.signing.key.alias="$ALIAS" \ -Pandroid.injected.signing.key.alias="$ALIAS" \
-Pandroid.injected.signing.key.password="$KEY_PASS") -Pandroid.injected.signing.key.password="$KEY_PASS")
cp wear/app/build/outputs/apk/release/app-release.apk "$WEAR_OUT" cp wear/app/build/outputs/apk/release/app-release.apk "$STAGING_DIR/wear.apk"
cp wear/app/build/outputs/bundle/release/app-release.aab "$STAGING_DIR/wear.aab"
echo
echo "Built $OUT"
echo "Built $WEAR_OUT"
if [ -n "${ANDROID_HOME:-}" ] && [ -d "$ANDROID_HOME/build-tools" ]; then if [ -n "${ANDROID_HOME:-}" ] && [ -d "$ANDROID_HOME/build-tools" ]; then
APKSIGNER="$(printf '%s\n' "$ANDROID_HOME/build-tools"/*/apksigner | sort -V | tail -1)" APKSIGNER="$(printf '%s\n' "$ANDROID_HOME/build-tools"/*/apksigner | sort -V | tail -1)"
if [ -x "$APKSIGNER" ]; then if [ -x "$APKSIGNER" ]; then
for apk in "$OUT" "$WEAR_OUT"; do for apk in "$STAGING_DIR/phone.apk" "$STAGING_DIR/wear.apk"; do
echo "== $apk" echo "== $apk"
"$APKSIGNER" verify --print-certs "$apk" | head -5 "$APKSIGNER" verify --print-certs "$apk"
done done
fi fi
fi fi
# AABs use JAR signing, not APK signing. jarsigner can return success for an
# unsigned ZIP, so require its explicit verification result too.
for bundle in "$STAGING_DIR/phone.aab" "$STAGING_DIR/wear.aab"; do
echo "== $bundle"
if ! jarsigner -J-Duser.language=en -J-Duser.country=US -verify "$bundle" > "$STAGING_DIR/jarsigner.log" 2>&1 \
|| ! grep -q '^jar verified\.' "$STAGING_DIR/jarsigner.log"; then
cat "$STAGING_DIR/jarsigner.log" >&2
echo "App bundle signature could not be verified: $bundle" >&2
exit 1
fi
echo "App bundle signature verified."
done
mv "$STAGING_DIR/phone.apk" "$OUT"
mv "$STAGING_DIR/phone.aab" "$BUNDLE_OUT"
mv "$STAGING_DIR/wear.apk" "$WEAR_OUT"
mv "$STAGING_DIR/wear.aab" "$WEAR_BUNDLE_OUT"
printf '\nBuilt %s\n' "$OUT" "$BUNDLE_OUT" "$WEAR_OUT" "$WEAR_BUNDLE_OUT"
+4 -1
View File
@@ -102,7 +102,10 @@ Two things must match the phone app or the Data Layer silently won't route:
building both on the same computer just works. For release builds, sign the building both on the same computer just works. For release builds, sign the
watch APK with the same keystore as the phone APK. watch APK with the same keystore as the phone APK.
There's no Play Store listing; sideload. Run `npm run release` from the repository root to build signed phone and Wear
APKs for sideloading and AABs for Google Play. Both apps use the version in
`app/version.ts`, with distinct version codes for the phone and Wear tracks;
see [Android releases](../README.md#android-releases).
## Troubleshooting ## Troubleshooting
+16 -4
View File
@@ -4,9 +4,21 @@ plugins {
id("org.jetbrains.kotlin.plugin.compose") id("org.jetbrains.kotlin.plugin.compose")
} }
// Match the phone's marketing version, with a distinct Play upload code.
val faceclawVersionName = Regex("""FACECLAW_VERSION = "([^"]+)"""")
.find(rootProject.file("../app/version.ts").readText())?.groupValues?.get(1)
?: error("Could not read FACECLAW_VERSION from app/version.ts")
val faceclawVersionParts = (faceclawVersionName.substringBefore('-').split('.') + listOf("0", "0"))
.take(3).map { it.toInt() }
val faceclawBuildRevision = System.getenv("FACECLAW_ANDROID_BUILD_REVISION") ?: "0"
require(faceclawBuildRevision.matches(Regex("[0-4]"))) {
"FACECLAW_ANDROID_BUILD_REVISION must be an integer from 0 to 4"
}
val faceclawVersionCode = (faceclawVersionParts[0] * 10000 + faceclawVersionParts[1] * 100 + faceclawVersionParts[2]) * 10 + faceclawBuildRevision.toInt() * 2 + 1
android { android {
namespace = "com.faceclaw.wear" namespace = "com.faceclaw.wear"
compileSdk = 35 compileSdk = 36
defaultConfig { defaultConfig {
// Must equal the phone app's id (nativescript.config.ts): the Wearable // Must equal the phone app's id (nativescript.config.ts): the Wearable
@@ -14,9 +26,9 @@ android {
// signing key. // signing key.
applicationId = "com.faceclaw.app" applicationId = "com.faceclaw.app"
minSdk = 30 minSdk = 30
targetSdk = 35 targetSdk = 36
versionCode = 1 versionCode = faceclawVersionCode
versionName = "1.0.0" versionName = faceclawVersionName
} }
buildTypes { buildTypes {
+1 -1
View File
@@ -3,7 +3,7 @@
// (for release builds) the signing key, both of which the Wearable Data // (for release builds) the signing key, both of which the Wearable Data
// Layer requires to match the phone app. // Layer requires to match the phone app.
plugins { plugins {
id("com.android.application") version "8.7.3" apply false id("com.android.application") version "8.13.2" apply false
id("org.jetbrains.kotlin.android") version "2.1.10" apply false id("org.jetbrains.kotlin.android") version "2.1.10" apply false
id("org.jetbrains.kotlin.plugin.compose") version "2.1.10" apply false id("org.jetbrains.kotlin.plugin.compose") version "2.1.10" apply false
} }
+10 -2
View File
@@ -27,10 +27,10 @@
<div class="wrap prose"> <div class="wrap prose">
<!-- BEGIN GENERATED: privacy --> <!-- BEGIN GENERATED: privacy -->
<h1>Faceclaw Privacy Policy</h1> <h1>Faceclaw Privacy Policy</h1>
<p>Faceclaw's own usage statistics are off unless you opt in. Separately, Apple collects and shares information when you use an iOS TestFlight build, even when Faceclaw statistics are set to None. Information you voluntarily send us, such as feedback, may also identify you. This policy describes these separate channels and the third-party services you can choose to use.</p> <p>Faceclaw's own usage statistics are off unless you opt in. Separately, Apple collects and shares information when you use an iOS TestFlight build, even when Faceclaw statistics are set to None. Information you voluntarily send us, such as feedback, may also identify you. This policy describes these separate channels and the third-party services you can choose to use. On Android, Google ML Kit also collects SDK diagnostics separately from Faceclaw statistics, as described below.</p>
<h2>Usage Statistics</h2> <h2>Usage Statistics</h2>
<p>The first time you connect your glasses, Faceclaw asks whether to share usage statistics with its developers, to help them fix problems and improve the app. The choices are None, Minimal and Full, and you can change your choice at any time in Settings &gt; Privacy &gt; Faceclaw statistics. Until you choose, it is None. This setting controls only Faceclaw's own statistics.</p> <p>The first time you connect your glasses, Faceclaw asks whether to share usage statistics with its developers, to help them fix problems and improve the app. The choices are None, Minimal and Full, and you can change your choice at any time in Settings &gt; Privacy &gt; Faceclaw statistics. Until you choose, it is None. This setting controls only Faceclaw's own statistics.</p>
<p>With None, Faceclaw sends and stores none of its own usage statistics. This does not disable Apple's TestFlight reports or services you choose to use.</p> <p>With None, Faceclaw sends and stores none of its own usage statistics. This does not disable Apple's TestFlight reports, Google ML Kit diagnostics, or services you choose to use.</p>
<p>With Minimal, Faceclaw keeps counts on your phone and sends them about once a day to stats.faceclaw.org, a server run by Faceclaw's developers:</p> <p>With Minimal, Faceclaw keeps counts on your phone and sends them about once a day to stats.faceclaw.org, a server run by Faceclaw's developers:</p>
<ul class="links"> <ul class="links">
<li>- the Faceclaw version, whether it runs on Android or iOS, and whether it is</li> <li>- the Faceclaw version, whether it runs on Android or iOS, and whether it is</li>
@@ -52,6 +52,14 @@
<li>URLs and names, are never sent.</li> <li>URLs and names, are never sent.</li>
</ul> </ul>
<p>Faceclaw's own statistics never include your name or contact details, your location, Bluetooth device addresses, anything you say or type, or what is shown on your glasses. Each report carries a random identifier, created when you turn statistics on, which links your reports to each other but not to you. Turning statistics off deletes that identifier and everything kept on the phone, and stops all reports; turning them back on starts a new identifier. The statistics server doesn't record the IP addresses reports come from.</p> <p>Faceclaw's own statistics never include your name or contact details, your location, Bluetooth device addresses, anything you say or type, or what is shown on your glasses. Each report carries a random identifier, created when you turn statistics on, which links your reports to each other but not to you. Turning statistics off deletes that identifier and everything kept on the phone, and stops all reports; turning them back on starts a new identifier. The statistics server doesn't record the IP addresses reports come from.</p>
<h2>Android and Google ML Kit</h2>
<p>Android translation and language identification use Google ML Kit. The developer QR-code scanner uses Google's code scanner. Text and scanner images are processed on-device, but the SDKs send Google diagnostic and usage metrics over HTTPS: device/app details, installation identifiers, timings, errors, feature events, input/output sizes, and detected or configured languages. Translation also uses Firebase installation and remote-configuration services. This reporting is separate from the Faceclaw statistics setting; selecting None does not turn it off. Faceclaw does not provide a switch to disable these SDK diagnostics.</p>
<p>These metrics do not include the text being translated or scanned images. Cloud transcription and assistant providers are separate, as described below. For Google's handling of SDK metrics, see:</p>
<ul class="links">
<li><a href="https://developers.google.com/ml-kit/android-data-disclosure">https://developers.google.com/ml-kit/android-data-disclosure</a></li>
<li><a href="https://developers.google.com/ml-kit/terms">https://developers.google.com/ml-kit/terms</a></li>
<li><a href="https://policies.google.com/privacy">https://policies.google.com/privacy</a></li>
</ul>
<h2>iOS and TestFlight</h2> <h2>iOS and TestFlight</h2>
<p>For TestFlight builds, Apple automatically collects crash reports and beta usage information and shares them with us. This includes installations, sessions, crashes, app/build and OS versions, device model and identifier, and language. It is separate from Faceclaw statistics, with no in-app opt-out.</p> <p>For TestFlight builds, Apple automatically collects crash reports and beta usage information and shares them with us. This includes installations, sessions, crashes, app/build and OS versions, device model and identifier, and language. It is separate from Faceclaw statistics, with no in-app opt-out.</p>
<p>Joining only through a public TestFlight link hides your name and email from us, not from Apple. Email invitations can identify you to us. Apple also collects your device's name (not shared with us) and may use your IP address to estimate your region for beta availability.</p> <p>Joining only through a public TestFlight link hides your name and email from us, not from Apple. Email invitations can identify you to us. Apple also collects your device's name (not shared with us) and may use your IP address to estimate your region for beta availability.</p>