Find the thread.
Find the email you need. Get a reply ready. Move the conversation along.
GMAIL / SEARCH & SENDPersonal AI, private by design
A little help with your inbox, your plans,
and everything you’d rather not keep in your head.
In development · Try it with sample data.
One less loose end
Alex Morgan asked about Thursday.
You’ve got a reply ready to review.
A little room in your day
A catch-up with Sam Rivera.
The event details, ready for your review.
No need to repeat yourself
You prefer afternoon meetings.
Useful context for the next conversation.
Sample details only. No accounts connected.
A little less life admin
Starting with Gmail and Google Calendar, through a conversation in Telegram.
What’s built, what’s nextFind the email you need. Get a reply ready. Move the conversation along.
GMAIL / SEARCH & SENDCheck your calendar and prepare an event. Less back-and-forth, fewer tabs.
GOOGLE CALENDAR / READ & CREATECarry useful preferences into the next conversation. Pick up where you left off.
MEMORY / ON YOUR INFRASTRUCTUREA closer look
Help that keeps you
in the picture.
From request to reply
Drafting an email and sending it are different decisions. Carte Blanche’s approval step puts the second one in your hands.
Interactive illustration · no email is sent
“Let Alex know that Thursday works.”
I’ve drafted a reply. Ready to send?
Hi Alex,
Thursday works for me. Looking forward to it!
The draft waits here until you decide.
A record you can inspect
See what the agent read, what it changed, and where it stopped for approval. Filter this example log, then open an entry to inspect it.
Interactive illustration · fictional activity
Request: Find Alex’s email about Thursday.
Outcome: The search returned three matching messages. No email was sent.
Change: Saved “I prefer afternoon meetings” to the agent’s memory.
Outcome: Local memory changed. Memory updates appear in the activity log too.
Proposed action: Send Alex the reply “Thursday works for me.”
Outcome: Waiting for your decision. Preparing a draft does not authorize sending it.
Your decision: Don’t send.
Outcome: The proposed send was denied. No email was sent.
Showing all 4 example entries. Open any entry for details.
Control over what stays
Revoking a connection and deleting stored data are separate controls. Try both to see exactly what each changes.
Interactive illustration · only sample data changes
Stored by your agent
This clears its memories, conversations, log entries, and stored tokens, and revokes connected access.
Google is connected. The agent holds 9 sample records.
Local deletion does not erase Google mail or events, Telegram messages, provider records, or separate backups.
A different starting point
Instinct and OpenClaw take different approaches to personal agents. Here’s where we’re choosing to focus.
INSTINCT
Instinct connects across your digital life. Its terms reviewed September 7 allow continued use of indexed data after disconnection unless you separately request deletion.
The terms also permit model training, with opt-out rights, a safety-review exception, and a separate exclusion for Vault materials. Its privacy policy excludes Google Workspace API data from model training.
Terms, section 3 ↗Privacy policy ↗OPENCLAW
OpenClaw is open source and runs on your own hardware. It offers configurable tool policies, approvals, and sandboxing.
Its documented trust model is one trusted operator or team per gateway. Security posture depends on configuration; sandboxing is off by default.
Security model ↗Architecture & defaults ↗CARTE BLANCHE IN DEVELOPMENT
We’re starting with Gmail and Google Calendar through Telegram, with approval gates for sending email and creating events.
Separate local stores per user, an inspectable activity log, and revoke-and-purge controls make data control part of the core experience.
Our controls & current limits ↓Based on the linked first-party documentation, reviewed September 7, 2026. Products and defaults change. This compares approaches, not independent security ratings.
Why these boundaries matter
Recent scrutiny of personal agents makes three questions unavoidable: who authorizes an action, what remains after disconnecting, and what can a compromised agent reach?
Oasis Security’s February 2026 OpenClaw research demonstrated a website-to-agent takeover. The team shipped a fix within 24 hours. That history is a reason to examine boundaries and maintenance, not to label a patched issue a current vulnerability.
Instinct: August 24 reporting · TechCrunch ↗OpenClaw: research & remediation · Oasis Security ↗The details matter
The current code includes approval gates for email sending and calendar creation, per-user local storage, activity logging, Google access revocation, and local data purge. Carte Blanche is in development; hosted access and public source release are planned. These controls have not been independently security-audited.
The agent’s stores live on the infrastructure running it. Data can still go to the model provider and services you configure, including Google and Telegram. Their processing and retention rules apply. Self-hosting alone is not a guarantee that data never leaves your machine.
Disconnecting Google revokes the connector token. Purging removes the agent’s local user directory, including its memory, conversation history, activity log, and stored tokens. This does not erase mail or events at Google, messages in Telegram, provider records, or separately retained backups.
Separate user directories provide application-level separation, not separate operating-system sandboxes. Optional vector and graph memory have different isolation limits, and group chats share an approval context. Deployment, provider choice, and enabled tools matter. The initial experience is designed around private use.
Capable AI. Private by design.
IN DEVELOPMENTWe’re building Carte Blanche.
Know someone who’d get it?