Privacy
Effective 2026-09-28
dossier shows your upcoming meetings with AI-generated personality estimates. This page describes exactly what it does with data.
What it collects
Signing in with Google links your email address and a read-only calendar token. Both live only in an encrypted cookie in your browser — there is no server-side account database. Your meetings are fetched from Google Calendar when you open the meetings page — and once on the key form, to show your next meeting and estimate what the coming week's research would cost — and are not stored on our servers.
Notes you save about an attendee are kept encrypted on our server under your account (never in the shared estimate cache), for up to a year after they were last saved or shown to you — opening the meetings page may renew the ones it shows. Stored key names and the per-account index reveal how many notes an account keeps and when they were last active, never who they are about or what they say. A "Not them?" hint — a detail you save to say which person with that name you meet — is kept exactly like a note and counts toward the same limit.
Text you save about yourself ("About you") is kept the same way — encrypted on our server under your account, for up to a year after it was last saved or used. Save it empty to remove it. Text dossier drafts about you automatically (see below) is kept the same way while it waits for your review, together with a small record that a draft was attempted, saved, or retired — that record is what keeps the automatic draft to one per account.
When you tell dossier whether an email domain that looks like yours is your team too, it keeps your answer encrypted on our server under your account, for up to a year after it was last saved or used, so it doesn't ask again. The stored key shows only that an account has saved or removed an answer at some point, never which domains (removing every answer leaves an empty record until it expires).
Your xAI API key, which you provide, is kept in that same encrypted cookie and — so it can follow your account across devices — as an encrypted copy on our server bound to your account. You can delete it any time with "Remove key from account"; copies unseen for a year expire on their own.
What it shares
To produce an estimate, an attendee's name and email address are sent to xAI (Grok) under your own API key, and Grok may search public sources about that person. Meeting titles, descriptions, and other calendar contents are never sent. If you saved a note about that attendee, the note's text is sent to xAI inside that one person's estimate — describe observed behavior, not medical claims — and an estimate informed by your note may reflect its content. If you saved "About you" text, it is sent to xAI inside every estimate while it stays saved, so results can name genuine things you have in common; those personalized results are never stored in the shared cache or served to other accounts. The first time you open the meetings page with no "About you" text saved and no earlier profile on the account, your own name (as it appears in your email address) and email address are sent once to xAI under your key to research your public footprint and draft that text for you; you can edit or remove it any time. A saved "Not them?" hint is sent inside that one person's estimate, like a note. Nothing is sold, and there are no advertising or third-party analytics trackers: dossier keeps only anonymous daily totals — landing-page views, meetings-page visits and return visits, sign-ins, keys saved, first fully prepared meetings, free lookups and "Was this right?" answers — as plain counts, with no names, email addresses, account identifiers or cookies attached.
To show profile photos, your browser sends an unsalted one-way hash (SHA-256) of each attendee's email address to Gravatar (Automattic) to look up a public avatar. The raw address is not sent to Gravatar (attendee addresses already go to xAI) and cookies are withheld, but like any direct image fetch the request reveals your IP address to that service, and hashes of registered addresses are linkable by it. Attendees without a public avatar get locally drawn initials, and no request is made for attendees with no email address.
What it stores
Finished estimates are cached in your browser session and in an encrypted shared server cache under hashed keys for up to 30 days, so a person already researched is not re-billed — including when a different signed-in user looks up the same person.
If you set a spending limit, this browser keeps the amount — or that you removed it — for your account until you sign out (as far as the browser allows), plus a flag, with no account or amount attached, that stops a limit an older version kept in a single tab from coming back. The limit is never sent to our server.
If you hide scores on the meetings page, this browser remembers that for your account until you sign out (as far as the browser allows). It is never sent to our server.
This browser also keeps small records of its own: the day you last opened your meetings, whether a meeting was fully prepared here, which automatic About-you draft it already announced, and each researched meeting with a set time that you haven't declined — its title, the attendees researched for it and the short read dossier showed for each — until 48 hours after it ends, so dossier can ask how it went. An expired meeting record is deleted the next time dossier opens in this browser (when the browser allows it). "Sign out" clears them all and leaves one note — the time it happened, with no account attached — that pages opened earlier check before writing again, all as far as the browser allows (plus the spending-limit flag above). Your "Was this right?" answers are stored on our server only as the anonymous counts above.
Cookies
One session cookie keeps you signed in: it lasts up to 30 days without a visit, 180 days at most, and "Sign out" deletes it. There are no tracking cookies.
Services used
Google (sign-in and read-only Calendar), xAI (estimates, under your key), Gravatar/Automattic (public avatar lookup by email hash), Vercel (hosting), Upstash (the encrypted cache and key store).
Your choices
Sign out to clear the browser session; use "Remove key from account" to delete the server copy of your key; clear a note by saving it empty, or a hint with "Remove hint", or remove every note and hint at once with "Remove all notes" on the meetings page; clear your "About you" text by saving it empty; remove a saved team answer under Settings → Your team; remove a saved spending limit with "Remove limit" ("Sign out" removes it too); show hidden scores again with "Show scores" ("Sign out" forgets that choice too, as far as the browser allows); revoke calendar access any time at myaccount.google.com/permissions. Cached estimates expire within 30 days — for earlier removal, contact us.
Contact
Use the support email shown on the app's Google sign-in screen.