Privacy Policy

What we collect

• Account details you give us: name, email address, the name of your newsroom, and a password, which we store only as a one-way hash.
• Workspace details: who is in your workspace, their roles, invitations you send (the invitee’s email address), and billing contact details.
• What you create: alert keywords and filters, saved beats, notes, drafts, files you upload, and the questions you ask the assistant.
• Billing: Stripe handles payment. We store the Stripe customer and subscription identifiers, your plan, its status and renewal dates, and the billing email address. Card numbers never reach our servers.
• Sign-in security: for each signed-in device we keep the IP address, browser description, and when the session started and was last used, so you can see and sign out your devices.
• Email records: which account and alert emails we sent you and when, and whether you unsubscribed.
• Server logs: requests to the service with timestamps and IP addresses, kept for security and debugging.

Public-record content

The meetings themselves are public records. Recordings, agendas, minutes and the transcripts and briefs we make from them name public officials, staff and people who spoke in public session. That material comes from the public bodies and the platforms they publish on, not from you. If something about you in that material is wrong, write to support@retriever.dog and we will look at it.

How we use it

• To run the service: sign you in, show your workspace its content, deliver the alerts and digests you set up.
• To send account email: verification, password reset, invitations, trial and billing notices. Alert email carries a one-click unsubscribe; account email about your subscription cannot be turned off while it is active.
• To bill your workspace and keep records the tax authorities require.
• To keep the service secure: detect abuse, stolen sessions and fraud.
• To answer support requests and to understand, in aggregate, which features are used.

AI processing

Transcription and brief writing use machine-learning models run by our providers. When you ask the assistant a question, your question and the meeting content it refers to are sent to Google’s Gemini API to produce the answer. Meeting audio is transcribed on Modal’s infrastructure and, where captions exist, with Google’s API. We use these providers under their business API terms, which do not permit them to train models on this data, and we do not train models on your content ourselves.

Who else sees it

• Your workspace. Owners and admins can see members’ names, emails, roles and last sign-in. Alerts, beats, notes and drafts belong to the workspace and stay with it if you leave.
• Service providers that process data for us, in the United States: Stripe (payments), Resend (email), Neon (database), Railway and Vercel (hosting), Cloudflare (file storage), Modal (transcription) and Google (AI). Each is bound to use the data only to provide its service to us.
• The law. We disclose information when a valid legal process requires it, and we will tell you unless we are legally prevented from doing so.
• A successor, if Retriever is acquired or merges, under this same policy.

We do not sell personal information, and we do not share it for cross-context behavioural advertising.

Cookies and browser storage

We set one strictly necessary cookie, retriever_refresh, which keeps you signed in. It is HttpOnly, sent only to our API, and expires after 30 days of inactivity or 90 days at most. Your browser’s local storage holds a marker that a session exists, your theme and layout preferences, notices you have dismissed, recent searches, and your saved briefs and reading history, all of which stay on your device and are never sent to us. There are no advertising or analytics cookies.

How long we keep it

• Account and workspace data: while the account exists, and for 30 days after you ask us to delete it, so a mistaken request can be reversed.
• Sign-in sessions: until they expire or are revoked, then 90 days for security review.
• Billing records: as long as tax and accounting law requires, typically seven years.
• Server logs: 30 days. Backups expire on a rolling basis.

Security

Traffic is encrypted in transit. Passwords are hashed with bcrypt. Access tokens expire after minutes and every signed-in device can be revoked from Settings. Card data is handled entirely by Stripe. No system is perfectly secure; if we learn of a breach affecting your data we will tell you without undue delay.

Your choices and rights

You can edit your profile and notification settings, manage devices, and leave or delete content in the app. For anything else, including a copy of your data, correction, or deletion of your account, write to support@retriever.dog from the address on the account. We honour the rights state privacy laws give you, including those of California residents, and we will not treat you differently for exercising them. Deleting your account removes your personal details; content that belongs to a workspace you were part of stays with that workspace.

Children

The service is for working newsrooms and is not directed to anyone under 16. We do not knowingly collect information from children.

Changes

We will post changes here and update the date at the top. For material changes we will email workspace owners before they take effect.

Contact

Retriever Technologies, [Mailing address]. Privacy questions: support@retriever.dog. See also our Terms of Service.