Files
faceclaw/PRIVACY
T

202 lines
9.5 KiB
Plaintext

# Faceclaw Privacy Policy
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.
## Usage Statistics
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 > Privacy > Faceclaw statistics. Until
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
does not disable Apple's TestFlight reports or services you choose to use.
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:
- the Faceclaw version, whether it runs on Android or iOS, and whether it is
an official release or a build someone compiled themselves;
- whether glasses and a ring are paired, and which devices (glasses, ring,
Wear OS watch) were in use each day;
- counts of connection events: connection attempts, disconnections and
their causes, message timeouts and retries, Bluetooth error codes, and
how long connections lasted.
With Full, it also sends:
- which kinds of API key are set (for example, that an Anthropic key is
set), but never the keys themselves;
- how many terminal and T3 Code connections are set up, and which of
Faceclaw's built-in fonts is in use;
- the values of settings chosen from fixed options, such as on/off
switches and pick-one lists. Settings you type in, such as addresses,
URLs and names, are never sent.
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.
## iOS and TestFlight
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.
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.
Feedback is optional. Comments, screenshots and diagnostics submitted
through TestFlight go to Apple and us. Public-link testers can omit their
email in the feedback form. Email sent directly to us reveals your email
even after public-link enrollment, but is not shared with Apple. Check
screenshots and comments for private content; feedback can include device
state such as battery level, free storage and network type.
Faceclaw has no public iOS API to switch off TestFlight's automatic reporting.
Its statistics setting and iOS tracking permissions do not control it. To
leave, select Stop Testing on Faceclaw's TestFlight information page, then
stop using and uninstall the beta. This does not erase previous reports.
Self-built installations do not use TestFlight reporting.
For ordinary iOS analytics, use iPhone Settings > Privacy & Security >
Analytics & Improvements, including Share With App Developers. Faceclaw
cannot change these system settings. TestFlight crash reporting applies
regardless of those settings. See https://www.apple.com/legal/privacy/data/en/app-analytics/.
We use TestFlight reports only to improve Faceclaw, not for advertising or
sharing with third parties. Apple retains feedback for one year and may keep
crash/usage reports until bugs are resolved. For access/deletion requests,
contact us using the developer email in TestFlight; manage Apple's data at
https://privacy.apple.com/.
Apple's details: https://www.apple.com/legal/privacy/data/en/test-flight/
and https://testflight.apple.com/.
## Audio
Faceclaw allows users to transcribe audio (for use with the voice assistant,
the Transcribe app, typing into Terminal, and other apps). The default setting
is that this is done using an on-device model running on your phone. If an
on-device model is selected, audio never leaves your device, and is not stored
after it is processed.
Users can also provide their own API key for a third-party transcription
service such as OpenAI Whisper, ElevenLabs, or Soniox, which may offer better
accuracy.
Faceclaw never transmits audio to any party other than a user-selected
transcription service. If a third-party transcription service is selected,
audio will be sent to that third party, is linked to the account with which
that API key was created, and is subject to that party's privacy and retention
policies:
OpenAI: https://openai.com/policies/row-privacy-policy/
ElevenLabs: https://elevenlabs.io/privacy-policy
Soniox: https://soniox.com/policies/privacy-policy
Third party data retention and privacy policies may differ based on the API
key provided. API keys are part of a relationship between the user and the API
provider; Faceclaw does not manage accounts or process billing information.
## AI Assistant Transcripts
Faceclaw has a builtin AI voice assistant. Using a cloud model requires
providing an API key for a model provider such as Anthropic, OpenAI, or Venice,
or configuring an OpenAI-compatible endpoint such as a private Open WebUI
server. Prompts and responses are subject to the selected provider or server
operator's privacy policy:
OpenAI: https://openai.com/policies/row-privacy-policy/
Anthropic: https://www.anthropic.com/legal/privacy
Venice: https://venice.ai/privacy
With an OpenAI-compatible provider, the configured server receives the
assistant system prompt, conversation history, available tool definitions, and
tool results needed to answer. Its URL, model ID, and optional API key are
stored on the phone. Faceclaw does not operate that server and cannot make
representations about its logging or retention; for a private Open WebUI
server, the server's operator controls those policies.
AI conversation histories and memory files may be stored on your phone.
Faceclaw does not transmit voice-assistant prompts or responses to any party
other than a user-selected AI model provider. The voice assistant is given
tools with which it is able to access most things on the user's phone,
including all content displayed on the glasses, location, notifications, and
content accessible through the Terminal app.
The AI assistant can take actions on the user's behalf, including sharing any
information it has access to. The user is responsible for any instructions
they give it.
## Location
Faceclaw has a builtin Navigate app, which provides turn-by-turn directions.
Using the Navigate app requires providing an API key for Mapbox. While the
Navigate app is active, the user's exact location and selected destination are
transmitted to Mapbox, and are subject to Mapbox's privacy policy.
Mapbox: https://www.mapbox.com/legal/privacy
The Weather app will retrieve the user's coarse location, and will use it to
query a third-party weather information provider: the US National Weather
Service, then Open-Meteo if the location is outside the US. Outside the US, it
also asks the phone's built-in geocoder (Google's on most Android phones,
Apple's on iOS) for the name of the place.
Open-Meteo: https://open-meteo.com/en/terms
## Spotify
On iOS, the Music app, Glanceboard and the voice assistant can show and
control Spotify through Spotify's Web API, once the user has created their own
Spotify developer app and signed in. Signing in happens on Spotify's website in
the system's sign-in sheet; Faceclaw never sees the password, and stores the
resulting sign-in tokens on the phone. While Spotify is shown or used,
Faceclaw requests the user's playback state, queue, library and search results
from Spotify and sends it playback commands, directly from the phone. This is
subject to Spotify's privacy policy.
Spotify: https://www.spotify.com/legal/privacy-policy/
## EvenHub
The EvenHub app store is subject to Even Realities' privacy policy:
https://support.evenrealities.com/hc/en-us/articles/14127464826511-Privacy-Policy.
Apps downloaded from the EvenHub app store come with their own privacy
policies.
## Wear OS Watch
The optional Faceclaw watch app (wear/) talks to the phone over Google Play
services' Wearable Data Layer, the same channel the watch uses for
notifications and other companion apps. Gestures, commands, the watch's own
speech-recognition results, and the mirrored glasses status and assistant
replies travel between your watch and your phone over their Bluetooth (or,
when paired that way, Wi-Fi) link; Faceclaw does not send any of it to a
server. Speech recognized on the watch uses the watch's system speech
recognizer, which may send audio to Google under Google's privacy policy:
Google: https://policies.google.com/privacy
The phone does nothing watch-related on phones without Google Play services.