How we improve the product

Tether gets better when it understands how apps are built: what a screen looks like, which button does what, what pop-up tends to appear after an update. This page explains exactly what we collect to learn that, what we never collect, and how to turn it off.

The short version: we learn the shape of app screens, never what is on them. No message text, no names, no photos, no numbers, no codes. Your organisation can turn it off in one click.

1. Two kinds of data, two switches

Your organisation's owner controls both in Settings → Organisation → Help improve Tether.

2. Usage metrics

Examples: "a Flow with 8 steps was created", "a run took 41 seconds and failed at a Tap step", "the template picker was opened", "the agent reconnected 3 times", page load times, error types.

They are tied to a random identifier, not to your name or email, and are reported in aggregate. They do not include Flow names, sheet contents, typed text, screenshots, URLs you configure or anything shown on your phones. They are collected on our servers without cookies.

3. Screen structure (the Screen Graph)

When a Flow runs, the phone reports the screen's structure: a tree of elements such as "a button, here, in this app". From that we build the Screen Graph, a shared map of app screens that helps every customer's Flows find the right button after an app update, handle pop-ups, and need less AI.

What we keep, per screen:

• the app's package name and version, the phone's operating system and its version, screen size and language setting;
• the element types and their positions (for example: a list, a text field, a button, an image), and how they nest;
• developer-assigned element IDs that the app ships with (for example com.example:id/post_button);
• fixed interface labels that the app ships with, such as "Post", "Next" or "Settings", only when the same label is seen on the same element across many unrelated organisations (so it is part of the app, not anyone's content);
• which screen led to which (transitions), and which pop-ups appeared and how they were dismissed;
• a fingerprint of the screen computed from the above.

What we remove before anything leaves your organisation's data:

• all text that is not a fixed interface label, including messages, comments, captions, names, usernames, email addresses, phone numbers, amounts, dates, search terms and anything typed into a field;
• the contents of every text field, and anything in password or secure fields;
• list and feed items (we keep only that a list exists and its rough size);
• images, screenshots and video, and image descriptions;
• the account the phone is signed in to, your organisation, your users, your phones' serial numbers and your location.

The Screen Graph is a combined map from many organisations. It is not linked back to your organisation, cannot be used to see what you did, and contains no personal data by design. Because it no longer identifies anyone, it may be kept after you turn contribution off or close your account.

4. What we never do

• Use your screenshots, screen text, recordings or sheets to improve the product or to train AI models.
• Sell this data or share it with advertisers.
• Use it to profile you or the people who appear on your screens.

5. Turning it off

An owner or admin can turn either switch off at any time in Settings → Organisation → Help improve Tether. From then on we stop collecting that kind of data from your organisation. The change is recorded in your audit log. Turning contribution off does not reduce any feature you pay for: your Flows still benefit from the Screen Graph that others contribute to.

Business customers with a signed agreement can also ask us to turn both off for their organisation at our end.

6. Questions

Write to [email protected]. The Privacy Policy explains the legal basis (our legitimate interest in improving the Service, balanced by these safeguards and the opt-out) and your rights.