Trace one task from start to finish
Take a simple task, such as comparing travel options. Your request might contain dates, a budget and a destination. The assistant may send part of that request to a search service, retain a preference or pass a chosen option to a booking provider.
Ask the service to explain that journey in plain language. Which information stays on the device? Which reaches its servers or another provider? Which parts are optional? “We value privacy” is a principle; you also need concrete answers.
| Part of the task | Question to ask |
|---|---|
| Information you provide | What is collected, and can I give less? |
| Processing | Which services receive it and for what purpose? |
| Memory and history | What persists, for how long, and who can see it? |
| Actions | What may the assistant send, change or purchase? |
| Removal | What does disconnecting or deleting actually remove? |
Separate reading from changing
An assistant may need to read a calendar to find a free afternoon. That does not automatically justify permission to edit every event. Separate access to information from authority to act on it.
Start with a narrow connection or a single shared item when the task allows it. If a service requests broad access, ask why the task needs it and whether a more limited option exists. A useful explanation connects each permission to a real function.
Treat memory as something you can inspect
Useful memory might be a preference for train travel or a standing limit on spending. It should be possible to distinguish those preferences from a conversation transcript, temporary working context and a guess the assistant made.
Ask how to correct a mistaken detail. Then ask whether deleting a conversation also removes saved preferences, uploaded files and information already shared with a connected service. Those can be different operations.
Review the phone and the service
Apple lets you review app access by information category in Settings, under Privacy & Security. App Privacy Report can also show how granted permissions and network access are being used.
That is one view of the system. An assistant may also hold an online account connection or retain information on its own servers. Read the service’s policy and connection controls alongside the phone settings.
Reference: Apple: review app permissions and activity
Check the connection you mean to remove
For a connected account, distinguish signing in from granting access to information. Google’s linked-app controls separate Sign in with Google, linked accounts and access to your Google Account. Review the specific connection and its details before removing it; an app can have more than one kind of link.
Google says removing an app’s Google Account access prevents that access and may disable related features. Removing a Sign in with Google link stops automatic sign-in but does not delete your data from the app. Treat disconnecting and deleting stored information as separate questions.
Before ending a trial, note which routines or tasks depend on the connection. Use the service’s controls to stop work you no longer want, review account access, and read its history, file and memory removal options. A revoked connection is not evidence that a copied document or an earlier completed action has been undone.
| What you want to change | What to check separately |
|---|---|
| Stop future routine work | The assistant’s task or schedule controls and any action already attempted. |
| Remove account access | The exact provider connection and access details. |
| Remove retained information | The assistant’s own history, upload, memory and deletion policy. |
| Change phone permissions | Device permissions for the relevant app and information category. |
Check app activity after a small trial
Try one task with made-up details, such as dictating a grocery list. Before you start, open Settings → Privacy & Security → App Privacy Report and turn it on. Apple starts collecting report activity from that point. Write down when you run the test so you can look for the app around that time.
After the trial, look under Data & Sensor Access for the app. An entry for the microphone around the time you dictated is consistent with the task. If you see access you did not expect, check which permission the app has and review why it needs it before trying again.
The report can also show network domains the app contacted. A domain entry shows a connection. To find out what the provider stores or which online accounts it can reach, check the service’s privacy policy and account connection settings.
Reference: Apple’s guide to App Privacy Report
Try a small privacy check
Before connecting an important account, ask the assistant what it knows about you. Correct one harmless preference and see whether the correction appears in later work. If there is a removal control, check what its explanation says will be removed.
Use invented or low-sensitivity details for a trial. You do not need to disclose a private document just to understand how a product handles permissions. If a claim is unclear, ask before expanding access.
Twin’s boundaries and current policy
Twin’s product direction calls for chosen context, reviewable permissions, correction and removal. Those are requirements for the assistant being developed, not proof that every future control is available today.
The public site has its own privacy policy covering the website experience. The early-access invitation reaches the team; it does not silently connect your accounts or authorize background work. Review the current policy and ask about any connection before sharing more.
Reference: Twin’s website privacy policy