Privacy policy

T3 for Pebble · G-Cyrille · Effective 8 November 2026

The app connects directly from the Pebble phone companion to the T3 server address you choose. The developer operates no relay and receives no app analytics, conversation content, or account data.

Data on your devices

The companion stores the server address, a bearer token, chosen permissions, language, local read state, a pending reply while its delivery is uncertain, and the latest thread-creation receipt. An unconfirmed creation retains its draft so it can be retried with the same request ID; after confirmation, the receipt retains the title and target but discards the draft. The next creation replaces it. Thread metadata and opened conversations are held in memory for display. Watch language is also persisted on the watch. The existing bearer token is never passed to the settings page.

Data sent to your T3 server

Pairing sends a one-time code, permissions, and an OAuth PKCE challenge. Reading fetches thread metadata and messages, including those on machines linked in T3. Replies, including saved prompts and requested summaries, are sent to your T3 server and may be handled by your configured AI providers. Creating a thread sends the confirmed dictated request to the selected machine and project and can start an agent using your T3 settings. Settle and snooze modify the selected thread. Your T3 server and provider policies govern their processing and retention.

Dictation and other services

Voice input uses Pebble's system dictation. Audio may be processed by the phone app and its speech provider under their policies. T3 for Pebble receives the resulting text and displays a draft before sending it. The developer runs no speech service. The Pebble app and Appstore have their own network and account behavior.

Control and deletion

Use the lowest permissions you need. Forget connection removes the saved connection, pending reply, and creation receipt from the companion. It retains the language and local read-state preferences. Revoke the corresponding session in T3 to invalidate server access. Removing the app and its companion data removes its local preferences, subject to phone/app backup behavior. Server conversations are not deleted by uninstalling.

Contact

Contact oiawo.cir@gmail.com. Report security issues privately. GitHub issues and pull requests are public; remove private logs, addresses, and conversation text before posting. GitHub handles that data under its own policies.

Source and changes · Setup guide