What Grenier can and can't see

When you connect Gmail, Grenier reads your messages so it can work out who matters to you and when you last spoke. It reads the full text — but it doesn't keep it. From each message it saves who wrote to whom and when (plus, from LinkedIn and Facebook notification emails, the job changes and birthdays of people in your contacts; and, for a sender not yet in your contacts, just their address and how many of their messages were held back); the text itself is not saved (the one exception is an opt-in debugging log, described in the privacy promise).

Your mail goes to an AI model only when you ask for something built from it: a person's relationship profile (including when you sync one person from their page, which rebuilds it), a draft to them, or a check on what kind of contact someone is when you ask Grenier to look for people you could bring in. The AI provider keeps nothing: it processes that one request, then lets it go. It doesn't store your email or use it to train anything.

The main things Grenier stores: your contacts, a who-and-when record of each message, the text of LinkedIn messages you import, the relationship profiles and commitments it builds when you ask, the drafts it writes for you, and any notes you write. We don't keep the text of your emails, your attachments, or your calendar event descriptions — and the privacy promise has the full field-by-field breakdown.

Grenier's access is read-only, unless you choose to use “Create draft in Gmail” — a separate permission Grenier uses only to add drafts. It never sends or deletes your email, and never changes anything else in your inbox.

We never sell or share your data — not to advertisers, not to data brokers, not to train anyone's AI. And you stay in control: from Settings you can export everything, delete it all (gone for good after 30 days), or disconnect Gmail in one tap, anytime.

The technical details, for the curious: the AI runs at an external inference provider under a zero-data-retention, no-training contract for our account — every provider we use is named at /legal/subprocessors; your Google sign-in tokens, the drafts Grenier writes, the sender and recipient addresses of your messages, voice-recording summaries and meeting titles are encrypted with AES-256 at rest under a key that belongs to your account alone; LinkedIn message text is encrypted with AES-256 at rest under one key shared by every account; the relationship profiles Grenier builds are stored unencrypted; and the Gmail connection uses Google's read-only permission, so Grenier cannot change your mailbox — apart from the separate, optional permission behind “Create draft in Gmail”, which it uses only to add drafts.