Your data

Pepper is useful because it remembers things and can reach the accounts you've given it. That only works if you can see what it keeps and take any of it back, so this page is the plain-language version of both: what's stored, who else ever touches it, and every control you have over it.

Two things shape everything below. Pepper starts out able to see nothing — signing in grants no access to your mail or calendar, and each connection after that is a separate decision you make. And nothing here is one-way: every connection can be cut, most content can be deleted, and anything that isn't handled by a button is handled by an email to a person.

The full legal version is the Privacy Policy — this page doesn't replace it, it just tells you where the controls are.

What Pepper keeps

• Your account — your name, email, picture, phone numbers, time zone, and preferences, plus a record of the choices you've made: which channels you agreed to, which terms you accepted, when you opted out of something.
• Your conversations — the messages you send on every channel, Pepper's replies, and any files, images or audio that went with them. It's one continuous conversation, so this is the long one: older stretches get condensed into daily, weekly and monthly summaries rather than dropped. See Memory & preferences.
• What Pepper has worked out about you — your dossier, the durable facts it keeps, and the search indexes that let it find an old conversation by meaning. This is the part people most want to inspect, and you can: the Dossier section in Settings shows both halves, the notes you wrote and what Pepper inferred.
• The things Pepper makes and holds for you — artifacts, generated images, todos, reminders and scheduled tasks, meal plans and recipes, workouts, feed and podcast subscriptions, booking pages, saved skills.
• The keys to your connected accounts — not your password, which Pepper never sees, but the access Google or GitHub issued in its place, kept encrypted. Alongside it, a record of exactly which capabilities you granted.
• What it fetched to answer you — an email it read, an event it looked up, a page it searched. Those results land in the conversation like everything else, which is why "what did that message say?" still works an hour later.
• Operational records — sign-ins, delivery status, errors, usage. The unglamorous rows that keep the service running, secure, and debuggable.

Pepper does not hold your Google or GitHub password, and it can't reach any account you haven't connected — an unconnected inbox is invisible to it, not merely unused.

Who else ever sees it

• Model providers. Pepper is an AI assistant, so answering you means sending the context needed for that request to the model provider it's configured to use. Production runs on paid API terms with no-product-improvement treatment, meaning your conversations aren't used to train their models.
• Delivery providers. Your texts, emails and push notifications pass through the companies that carry them, which is unavoidable for anything that arrives on a phone.
• Anyone you point Pepper at. A person you ask Pepper to email, a website it fetches, a tool server you connected — those receive what the request needs and are governed by their own terms.
• Google Workspace data gets stricter treatment than the rest. Anything Pepper reads from Gmail, Calendar, Contacts or Drive is handled under Google's Limited Use requirements, which is why it never feeds model training in any form, including summarized or derived forms.

Every provider is named on the public Vendors page, with what each one handles. Nothing is sold, and there's no advertising or cross-site tracking — Pepper uses only the cookies sign-in and the chat page actually need.

Improving Pepper, and how to object

Eligible Pepper conversations and your 👍/👎 feedback may be used to develop and evaluate Pepper's own models. These are never used for that, whether or not you object:

• anything from your connected accounts — Gmail, Calendar, Contacts, Drive, GitHub, MCP tool servers — and anything derived from it;
• anything that didn't start in your own Pepper conversations or your feedback on them, such as something imported or restored from elsewhere;
• rooms, and anything shared with you or that you've shared with others;
• credentials, tokens, keys, and financial or payment details;
• sensitive information such as health, precise location, biometrics, or immigration status;
• content about people who don't have a Pepper account, and content about children;
• anything you've deleted or asked to have restricted;
• anything a provider or contract says can't be used this way.

You can object at any time, and the two routes differ in how fast they take hold. Where Settings shows an Improving Pepper section, that's one button and it takes effect the moment you press it. Mailing privacy@vycari.ai also works and is the route when Settings doesn't show that section — it's handled by a person, who may need to check the request is really from you, so it takes effect once it's processed rather than instantly. Objecting applies going forward and changes nothing else about the product — no feature gets worse, and nothing already written while you hadn't objected is retroactively swept in either direction.

Taking access back

Connected accounts. In Settings → Accounts, Disconnect removes an account, Revoke Google access withdraws the permissions, and the per-account Access checklist switches off one capability — reading mail, adding events — without touching the rest. If several accounts are connected there's a single button to revoke all of them at once. Pepper tells Google to cancel the access rather than just forgetting its own copy, and your data stays in Google. See Connecting your accounts.

Connectors. Under Settings → Connectors, disconnecting a server deletes its stored credentials as well as stopping its tools. Nothing on a connected server is exposed until you tick the specific tools Pepper may use, and a server that changes what a tool does has to be re-approved. See Connectors.

Command-line tokens. Access tokens issued for the pepper CLI are listed in Settings and can be revoked individually. A token that was created while signed in through another token is marked "created from" that token, and revoking the original revokes it too. See The command-line app.

Signing out ends your Pepper session and touches nothing else.

Turning off the ways Pepper reaches you

• SMS — text STOP from that phone and Pepper stops texting it. Each number tracks its own opt-in, so this doesn't affect your others, and START opts back in. You can also remove a number entirely in Settings → Phones. Stopping SMS does not delete your account.
• Email — the Notification email chooser in Settings → Notifications decides where anything Pepper sends on its own initiative goes.
• Push — browser notifications are per-browser and off until you enable them. By default a push shows the specifics — the task name, or the sender and first line of a group message — on your lock screen; Notification previews in Settings → Notifications is the one setting that controls this, for task updates and group messages alike. Turn it off and a push only says that something happened, with the specifics held back until you open Pepper. To quiet one room without touching the rest, use the Notifications setting on that room's room info page — @mentions only or Muted; it's saved to your account, so it applies on every device. (Sending a recipe or workout to your Watch is different: that handoff always names what you're sending, previews setting or not — it's your own data you just chose to hand off, not something Pepper wrote.)

Deleting what's in there

Most things Pepper holds for you can be deleted where you find them: an artifact, a generated image, a skill, a scheduled task, a booking page. A todo you dismiss and a feed you unsubscribe from come off your lists the same way. Artifacts and images stay recoverable for a while after you delete them and are then gone for good.

Your dossier works differently, because correcting it is usually what you actually want: your own notes are editable in place, and what Pepper has inferred sits below them, readable, with anything you say yourself taking priority over anything it guessed.

A copy of everything. In Settings → Your data, Download your data gives you a zip of what Pepper holds about you — conversations, memories, files, schedules and other records. It leaves out your sign-in credentials and connected-account tokens; the archive lists which accounts and MCP servers you had connected, and which of those servers' tools you had approved, so you know what to reconnect. If you use the Pepper command-line tool, pepper takeout downloads the same archive. One export runs at a time, and there is an hourly cap generous enough for a few retries; past either, Pepper asks you to try again shortly.

Deleting your account. In Settings → Your data, Delete account opens a page that lists what is kept afterwards and for how long, and gives the date your data will be erased, 30 days after you confirm. Messages you sent in shared rooms stay there under your name marked "(deleted)". Rooms you are the only owner of are deleted for everyone on that date. Consent records are kept for 6 years, and backups age out about 60 days later. The page offers Download your data first, because once you confirm you can't sign in to get it. It also names what you have to revoke yourself: connected tool servers at the provider, and the Chrome extension. To confirm, sign in again — with Google or Apple, whichever you use — and type DELETE. The account closes at once: you are signed out everywhere and an email confirms the date. There is no undo.

For anything the download doesn't cover, or for the whole account to go, email privacy@vycari.ai — access, a formal copy request, correction, deletion, restriction and objection all start there, and closing your account is a distinct request from stopping a channel. Where EEA, UK or Swiss law applies you'll generally get a response within a month. One honest caveat: deletion clears the live service, while residual copies in backups persist until the ordinary backup cycle overwrites them.

Room threads

A room is its own thread, separate from your one-on-one chats, and the other people in it see what's said there — not your private conversations with Pepper, your dossier, or your other rooms.

Scheduling is the case worth understanding, because it's the one place a room learns something from your calendar. By default a room sees busy times only — never the title, location or attendees of an event — and only from calendars you own, so a shared team calendar or a partner's calendar you subscribe to isn't counted as your time. You choose per calendar under Rooms see in Manage calendars (Nothing, Free/busy, Titles and times, or Everything), and each room can override that on its own info page. Pepper asks anyone whose calendar it can't see directly instead. See Rooms.

In the web app's sidebar, a room nobody's posted in for a week tucks itself under a quiet "Show inactive" row instead of crowding your active ones — it's a display fold, not an archive, and one new message brings it right back.

Acting in your name

Control over data isn't only about storage — it's also about Pepper not doing things in your name. Changing your calendar — adding, moving or cancelling an event — is confirmed with you first. Mail is normally confirmed too, but treat that as how Pepper usually works rather than a rail that can never be crossed: read what it tells you it's about to send, especially the first few times. Background work is held to a stricter line than you are — a scheduled task that would send mail as you writes a draft instead, so nothing can slip out of a turn you weren't present for. Pepper also can't do a number of things by design: it can't change who has access to a file, and its Drive access is read-only, so it can't edit, move or delete anything there.

The fine print, if you want it

All four pages are public and need no account:

• Privacy Policy — the full account of what's processed, why, and for how long.
• Terms
• Vendors — every provider, what it handles, and what it keeps.
• For people who aren't users — for someone who appears in your calendar or inbox without an account of their own.

Privacy questions and requests go to privacy@vycari.ai. Anything that looks like a security problem goes to security@vycari.ai — the team would much rather hear about it early. See Who makes Pepper.