Skip to content
Guth

Trust

Privacy and security

You approve what matters, your work stays yours, originals are kept, and synced means synced.

Guth is built on a few plain rules: you approve what matters, you can see what an action sends and to whom, your work stays yours, originals are kept, and "synced" means synced. This page explains each rule and says honestly which parts are still being built.

You approve what matters

Agents can read, organize and draft on their own. Actions with consequences wait for your approval
i

Your yes or no before an agent takes an action with consequences, like sending, publishing, paying or deleting. It shows what will happen first.

Read more

, for example:
  • sending a message or email on your behalf,
  • publishing or posting something,
  • spending money or making a purchase,
  • deleting something for good,
  • changing an account, a password or a security setting.

An approval shows what will happen before it happens. Saying yes to one action does not approve the next one.

You see what an action sends, and to whom

Before an action leaves Guth, the approval names the information it will send and where it is going: which service, which person, which address. If an agent cannot tell you that, it should not do it.

Your work stays yours

Work you make with an agent is your work. Private files, memory, passwords and history stay separate between accounts. When you share something with another person, who owns it is stated clearly.

Originals are kept

Guth keeps the original of what you bring in: the file, the page, the conversation
i

The file, page or conversation as it first came in. Guth keeps originals; summaries and indexes are built from them.

Read more

. Summaries and search indexes
i

A helper that makes your sources quick to search. It is built from the originals and can be rebuilt; it never replaces them.

Read more

are helpers built from originals. If a helper is wrong, it can be rebuilt; the original is not overwritten.

Training is your choice

Using your data to train or improve a model is opt-in
i

Your choice to let your examples help train or improve a model. It is off unless you turn it on, and a bug report does not count as consent.

Read more

. Reporting a problem is separate from agreeing to training: sending a bug report does not sign you up. Personal training itself is in development In development.

Passwords and secrets

GuthVault
i

A planned protected store for passwords, keys and other secrets, so an agent can use an approved secret without the AI model seeing it.

Read more

is planned Planned: a protected place for passwords, keys and other secrets, so an agent can use an approved secret without the AI model ever seeing it. Until GuthVault exists, do not paste passwords, card numbers or keys into a chat.

Honest status, including sync

Guth tries never to show progress it has not made. Work is labelled running, paused, completed, held or failed. When sync across devices arrives In development, each change will show as local, queued, synced, stale or failed
i

Whether a change is local, queued, synced, stale or failed. 'Synced' is shown only after the other device confirms it. Sync is in development.

Read more

, and "synced" appears only after the other device confirms it.

The same rule applies to this website: every product carries a label, live, private preview, in development or planned. See release status.

Public tools and your data

The public MCP server Live only reads. What you type into one of its tools is sent to Guth's server so it can answer. Do not put private information into public tools.

Reporting a security problem

If you find a security problem, write to services@getguth.com with the details. Please do not include other people's personal data in the report.

Where to go next

  • Agents: permissions and receipts.
  • AgentNotebook: how notes, suggestions and instructions stay apart.
  • FAQ: quick answers.