Short, because there is little to tell.

Who is responsible

Controller: Resonator LLC registered address follows before release
Privacy questions: hello@kontrolator.example (placeholder address)

What the app does not do

• No account, no login, no analytics, crash reporting, advertising or tracking libraries.
• No access to your contacts, files, photos, location or clipboard.
• Nothing you type on a controlled device is stored on the phone; the keyboard does not autocorrect, suggest or learn from it.
• The camera picture you use as your view of a screen is shown, not recorded.

What stays on the phone

• Settings and saved connections: the tentacle or device you last used, and for the developer Wi-Fi mode a host and port.
• The app's Resonator node, on both phones: a key pair generated on the phone that identifies it to peers you pair with, such as your tentacle or, on Android, the assistant service. It is never tied to a name or an account.

What leaves the phone, and when

To the tentacle

Your keystrokes, pointer movements and clicks go to the tentacle, or on Android to a device that paired your phone as a keyboard, and nowhere else. The developer Wi-Fi mode sends the same data over your local network in plain text to the host you typed in.

To the assistant service (Android, only when you use the assistant)

• One downscaled photo of the screen and your instruction per plan, one per step in multi-step tasks. The service returns a plan; the phone runs it.
• The connection travels over the Resonator network, relayed through public servers we do not run and which cannot read what passes through them.
• To produce the plan, the service sends the photo and your instruction to an AI provider. Currently Anthropic (Claude); the provider is configurable.
• The service keeps your instruction and the returned plan as text for 30 days, for debugging and abuse prevention, then deletes them. Usage metrics per phone identity, without text or images, are kept longer for rate limiting. The screenshot is never written to disk.
• If you point the assistant at a service you run yourself, none of this reaches us.

Speech

Where the operating system offers it, speech is recognised on the phone (Android 12 and newer); otherwise Google's speech service processes the audio under its own policy. The app receives only text, and the audio never reaches us.

Permissions

Permission	Why
Camera	To show you the screen you are controlling. Input works without it.
Bluetooth: scan, connect, advertise on Android	To find and talk to tentacles, and on Android to be discoverable as a keyboard. Only our own service is scanned for, never location.
Microphone (Android)	Spoken instructions to the assistant, only while you use it.
Notifications (Android)	One status notification while the phone acts as a keyboard, as Android requires.
Internet (Android)	To reach the assistant service. Not a user prompt.

This website

Static pages, no analytics, no access logs for browsing. The error log, held briefly by the system journal, can contain an IP address when a request fails. Affiliate links on the hardware page are marked with an asterisk; the shop you land on has its own policy.

One exception while the site is invite-only: entering an invite code stores a cookie so the site stays open for you, and logs the code, your IP address, browser and the time, so we can see which invitation reached whom. The site collects no email addresses.

Your rights

Under the GDPR you can ask what we hold about you, have it corrected or deleted, and complain to a supervisory authority. Since there is no account, that is limited to the assistant service's records for your phone's key: the last 30 days of instruction and plan texts, and usage metrics. Write to the address above with the identity shown on the app's Connect screen.

Version: draft, 2026-09-09.