Connect your favorite apps to Hands without sharing your password in an AI conversation. You only type your password with the service itself. Hands uses the access you give only to reach that service, and does not pass your sign-in details to the AI.
Example: in Hands you select Connect for Gmail. Hands first shows what your Hand may do, then you sign in with Google itself. Gmail is connected and the access stays shielded with Hands. You ask your Hand to summarize Sanne’s latest email; your Hand retrieves the email and gives a summary. Your password never enters the conversation.
GmailPlug-inConnect
Hands · Google permission
Connect Gmail
Your Hand may read messages and their contents.
Continue to Google
accounts.google.com
Sign in with Googleyou@gmail.com••••••••••
You type your password here, with Google.
Gmail is connectedAccess shielded with Hands, not in the chatConnected
Your request
Summarize Sanne’s latest email.
GmailRead email
Your Hand
Sanne asks whether the quote can be ready by Friday and sends the new quantities.
Recreated view · sample data
In three steps
How a safe connection works
You choose an app
You sign in with the service itself or connect an app through the settings meant for it. You decide which connection you make.
Hands protects the access
Your password never enters the conversation. Hands keeps the access you give shielded and uses it only to reach the service.
Your Hand gets to work
Your Hand can, for example, retrieve events or summarize a document. The AI uses the relevant results to carry out your request.
Want to know more?
Signing in with the service itself. For most Plugins you land on the service’s own sign-in page, for example Google’s. That service shows which access Hands is asking for. Hands then receives a permission or access pass, not your password.
Connecting with a key. Some connections use a key from the service. You enter it in the connection window, not in the chat. Hands stores that key in a protected store on your Hand, separate from your conversations.
Access through Hands. For some connections, Hands keeps the access to the service centrally and your Hand does not receive those access details. Your Hand then requests an action through a separate permission.
Plainly explained
What does your Hand see, and what not?
Sign-in details and the information for your request are two different things. They also take a different route.
Your sign-in details
Don’t belong in your conversation.
You type your password with the service itself. Hands keeps keys and access passes shielded: on your own Hand, or for some connections centrally with Hands. In everything that goes to the AI, they are hidden.
Your Handaccess passGmailDoes not go to your AI
The information for your request
Comes along when your task needs it.
Asking to check your calendar or summarize an email? Then your Hand receives the information needed for that, and it goes to the AI you use. That is different from getting access to your account’s password or secret key.
Summarize Sanne’s latest email.“Can the quote be ready by Friday?”Sanne asks whether the quote can be ready by Friday.To the AI you use
One Hand is one shielded workspace
Every Hand has its own workspace, separate from other Hands. Within that workspace, connections are not shielded from each other once more. So give a Hand only the apps it needs for its work, and use a separate Hand for other work.
Your choices
You decide what your Hand works with
Example of the action rules for Gmail: reading email is allowed, creating a draft may run automatically, sending email asks for your approval every time and changing labels is blocked. Below it, the window to disconnect Gmail.
Gmail · Action rulesWhat may this Hand do?
Read emailAllowed
Create draftAutomatic
Send emailAsk every time
Change labelBlocked
Connector access
Disconnect Gmail?
This removes access and connector-managed credentials from this Hand. Provider access outside this Hand may remain unchanged.
CancelDisconnect
Recreated view · sample settings
Choose your connections
Connect only the apps you want to use.
Set the allowed actions
For each action you choose whether it is blocked, asks for your approval every time or may run automatically.
Remove a connection
You can disconnect a connected app from Hands. For some services, you can also revoke the permission in your account with that service.
Extra protection
More than one layer of protection
Example: your Hand reads a file that contains a secret key. In the result that goes to your AI, the key has been replaced by a marker.
Result that goes to your AI
settings.envWEBSITE=https://yoursite.comSTRIPE_API_KEY=[REDACTED env-secret]
Recreated view · sample data
Shielded accessKeys and access passes are kept apart from your conversations, in protected storage.
Limited actionsHands checks which actions are allowed for a connected app.
Protecting answersHands knows your stored keys and hides them, and other recognizable secrets, in every result before it reaches the AI.
Your approval firstActions you set to ‘Ask every time’ are put to you by your Hand first.
Frequently asked questions
Answers to the questions you may have
Can the AI see my password?
No. With a sign-in connection you type your password with the service itself, not with Hands and not in the chat. With a key-based connection you enter the key in the connection window. Hands keeps the key shielded and hides it in everything that goes to the AI.
Can my Hand just do anything in my account?
No. You choose which apps you connect. The permissions you grant in the app and your action rules in Hands determine what is possible. Actions you set to ‘Ask every time’ are put to you by your Hand first.
Can my Hand read my emails and files?
If you grant access for it and the action is allowed, your Hand can retrieve the information needed to carry out your request. For a summary, for example, that content can also be processed by the AI you use; that service’s terms apply. That is why your sign-in details and the content of your requests are not treated as the same thing.
What happens when I remove a connection?
Hands removes the access and the related sign-in details from your Hand. For some services, you can also check with the service itself which access is still granted and revoke it there.
Does Hands store my password?
Not the password of the app you connect. With a sign-in connection, Hands receives a permission or access pass from the service instead of your password. With a key-based connection, Hands keeps that key shielded.
Can I see which connections are active?
Yes. You see your available and connected apps in your Hands settings. There you can manage and disconnect existing connections.
Working safely together starts with clear choices
Hands is built to help you with your apps, while you decide which connections you use. We keep improving security and ease of use, and explain as clearly as we can how your access works.
