Skip to content
Security & trust

A capable teammate, on a short leash you control.

Tend teammates can browse, write and work on a computer of their own. That’s exactly why the rules are enforced by our servers — not by the AI — and why you can see and stop everything.

You approve what happens

  • Approvals bind to exact content

    An approval covers one specific account, recipient list, message, attachment set, form or invoice — fingerprinted when you approve it. If anything material changes, the approval no longer applies and you’re asked again. Approvals expire and can only be used once.

  • Proposing is separate from doing

    Your teammate can only propose actions. Trusted server code checks the policy, your approval and the current account before anything runs. Emails, web pages and model output can never count as an approval.

  • Reuse only what you approved

    After you approve an outreach email or invoice, you can let your teammate reuse it. Only a new email that closely follows it (same wording and links, one person, no attachments) or an invoice with exactly the same items and prices goes out without asking. Each one is still checked by server code against its exact content, daily limits apply, and you can stop it any time in Settings.

  • Stop, pause and emergency stop

    Stop a task, pause your teammate, or hit emergency stop to revoke its ability to act. We’re upfront that nothing can undo an action a provider has already accepted — like a sent email.

Separate places for separate jobs

  • Public research browser

    Used for reading the open web. It holds no logged-in sessions, and its network access is restricted — private networks, cloud metadata and Tend’s own systems are blocked.

  • Authenticated browser

    Signed-in sessions live in a separate, restricted runtime. Only reviewed site integrations and approved actions can use it; unfamiliar logged-in workflows stay manual.

  • Code and file sandbox

    Generated files are created away from your accounts — no mailbox tokens, no logged-in browsers, no access to Tend’s control systems. Downloads and previews go through size, type and isolation checks.

Your credentials stay sealed

  • Never shown to the model

    Passwords, OAuth tokens, cookies and one-time codes are encrypted with keys kept outside the database. The AI model works with opaque references and never sees the values. We never ask for passwords in chat.

  • Least-privilege connections

    Gmail connects through Google’s official sign-in with the narrowest scopes needed, and sending is a separate permission you switch on. Disconnecting revokes access and blocks queued work immediately.

  • Payments handled by Stripe

    Identity verification and bank linking happen on Stripe-hosted onboarding. Tend never stores card or bank credentials, and your teammate has no ability to withdraw, refund or change payout details.

Web and email content is data, not instructions

  • Prompt-injection stance

    A web page or email that says “ignore your instructions” or “the owner already approved this” changes nothing: permissions are enforced by server code, not by what the model reads. Detectors flag suspicious content, but they are a second line, not the gate.

  • No quiet data leaks

    Private mailbox content can’t be placed into public URLs or research searches, and links in model output are never fetched automatically.

You can always take over

  • Human takeover

    Take control of your teammate’s computer at any time. Automation stops, stale work is fenced out, and nothing resumes until you hand control back.

  • Secure login mode

    When you sign in somewhere, your teammate stops taking screenshots, reading the page or recording until you explicitly return control. CAPTCHAs, identity checks, passkeys and payment steps are always yours to complete.

Your data, your call

  • Deletion and retention

    Delete chats, memories, files, screenshots, browser sessions and sandbox snapshots — or your whole teammate. Retention is configurable; we document how long backups and providers keep copies. Financial records are kept as the law requires.

  • Inspectable memory

    See, edit, export and delete everything your teammate remembers. It never remembers passwords, codes or payment details, and outside content can’t quietly become one of your preferences.

  • Sensible defaults

    Computer recording is off by default, and your content isn’t used to train models by default.

Honest status

Tend has not yet been independently security-audited. Our automated tests cover approvals, tenant isolation, prompt injection, takeover and payments, but passing tests aren’t an audit. An external review is a prerequisite for public launch, and live payments and public multi-tenant access stay switched off until it’s complete.