Sub-processors
Who else sees your content
Grenier sends your content to a small number of external services to do the work you asked for. This page names every one of them and what each receives, and for the AI providers, what each is allowed to do with it.
Inference providers
Profiles, drafts, labels, summaries and suggestions are produced by language models running at external providers. We send them the text needed for that specific job and nothing else.
Every provider listed in this section operates under zero data retention for our account: your content is not stored after the response is returned, and each is contractually barred from using it to train or fine-tune any model. We do not add a provider to this list without those terms in place, and we do not route your content to a provider before it appears here.
Groq
Used for: Relationship profiles, drafts, introductions, the kind-of-contact check, voice-note transcripts and summaries, follow-ups found in notes, topics after a “Not now”, interests from captured LinkedIn profiles, checks for duplicate interests, referral invitations, closeness suggestions, company-news relevance, and, in the browser extension, share messages and page summaries
What we send: One person's recent messages, with quoted replies stripped, the names and email addresses of the people in your contacts swapped for placeholders, and any other email address, phone number or card number swapped too. For a draft, some of: how you know them, the language, formality and tone of your exchanges and their interests; what they care about and how they like to be written to; a captured LinkedIn profile or headline; their country; when and where you last spoke; how many addresses you have for them; the relationship's health, rhythm and pattern; titles, dates and topic tags of up to three recent meetings; a recent news item about them or their company; the start of your notes on them; and your instruction, your own news, the tone you pick, their first name and your own name, pronoun, location and meeting tool. For a share from the extension: the page's text, title and address, the contact's company and title, the pattern of your exchanges and when you last spoke, the dates and direction of up to five recent exchanges, titles, dates and topic tags of up to three recent meetings, a captured LinkedIn profile, and your first name. For an introduction: each person's company, role and interests and the interests they share, never names. For a referral invitation: a fixed request only, nothing about you or the person invited. Also: voice recordings you upload; notes you save; LinkedIn profiles you capture; interest labels; contacts' job titles and companies with message counts, or with a company news headline and summary. Each is sent only to produce the result it is for
Retention: Zero data retention — not stored after the response is returned
Training: Contractually barred from training or fine-tuning on it
Applies to: All accounts
Anthropic
Used for: Drafts, introductions and extension share messages on an advanced model
What we send: The same inputs the Groq row lists for a draft, an introduction or a share from the extension, sent to produce that one message
Retention: Zero data retention — not stored after the response is returned
Training: Contractually barred from training or fine-tuning on it
Applies to: Grenier staff accounts only today. This row is published in advance of the wider rollout so the disclosure never lags the routing.
There is no fallback provider
If the provider handling a request is unavailable, the request fails and can be tried again later. Your content is not re-routed to some other service to get the job done, and there is no provider outside this list. One narrow exception stays inside it: on the staff accounts that use the second provider above, a draft or introduction that provider refuses because of a problem with our own account there (a missing credit or a bad key) is sent to the first provider instead.
Which model, and why it can change
Which provider handles a given request depends on your plan and on the kind of request. That routing changes as models improve — we treat it as an engineering decision, not a promise. What does not change is the rule above: any provider Grenier sends your content to is under zero retention and no-training terms, and is named on this page before it receives anything.
When our team reads logged text
If you let Grenier keep the text of your AI requests in its log (see the privacy promise), our team can copy that text out of the log to look into a problem or to test a change to how Grenier asks a model. The team works with an AI coding assistant, Anthropic's Claude Code, and text read or tested that way can pass through it. The terms above cover the requests Grenier itself sends; this use is under the terms of the team's own account with that tool instead, and a copy made this way is not erased when you turn the setting off or after 30 days.
Infrastructure
Grenier also relies on these services to run the application, hold its data and deliver its email. They are not AI providers: the zero-retention and no-training terms above are about AI providers only. What Grenier stores, and how it is protected, is in the privacy promise.
Vercel
Used for: Runs the application, stores files, and counts visits to public pages
What it receives: Every page and request passes through it. It stores contact photos, and a voice recording you upload until it has been transcribed. Its visit counter sees only the public pages, never a page you open while signed in
Neon
Used for: Hosts Grenier's database
What it receives: Everything Grenier stores about your account and your contacts, as the privacy promise describes it
Oracle Cloud Infrastructure
Used for: Hosts the database of Grenier's preview site, and the mail server for @grenier.app addresses
What it receives: Accounts and data created on preview.grenier.app. Mail you send to an @grenier.app address, such as [email protected], which it passes on to the team's own mailbox at Google
Resend
Used for: Delivers the emails Grenier sends
What it receives: Each email and its recipient's address: account emails, reminder digests, team and referral invitations, introductions, and the messages you send to a contact from Grenier or the browser extension
Postmark
Used for: Delivers the emails Grenier sends, in place of Resend when we switch to it
What it receives: The same as Resend. Only one of the two delivers Grenier's email at any time
Sentry
Used for: Reports errors and slow pages so we can fix them
What it receives: Error reports from our servers and from your browser, with internal identifiers of your account and of the records involved, such as a contact, and the address of the page or request; on an error in your browser, a replay of the screen with all text, typing and images masked; and timings for about one page or request in ten
Upstash
Used for: Limits how often a request can be made, and runs mailbox syncs in steps
What it receives: Counters keyed by internal identifiers of your account and, for some limits, a contact, or by a fingerprint of your IP address; and, for each sync step, the sync job's internal identifier and step counters. No message or contact details
Stripe
Used for: Takes payment for the Pro plan
What it receives: Your email address, and the payment details you enter on Stripe's own checkout page