Privacy policy

Quiver sits between the AI client a person uses (Claude, ChatGPT, Cursor, VS Code, Codex and other MCP clients) and the systems their company connects: MCP services, files the company uploads, S3 buckets the company owns, and, optionally, the person's own Gmail, Google Calendar, GitHub and Slack accounts. When the AI asks a connected system a question, Quiver fetches the result, holds any large result in memory, computes figures over it in code when the AI asks, and returns a card that shows what was computed and from what. Every call and computed answer gets a signed receipt.

Quiver is a business tool. Companies sign up, invite their people, and decide which connections those people may use.

A group label or a filter value is part of a derivation, so it appears in the log and the receipt. If someone asks for "messages per sender", the sender addresses are in the computed result and therefore in the log. That is by design (a receipt has to show what was computed), and it means the log is not free of business data.

We do not store your prompts to your AI, your AI's answers, or the credentials your AI client holds for its own provider.

A Gmail connection lets a person link one or more of their own Google accounts so that their AI can search and read that mail through Quiver. A Google Calendar connection does the same for calendars and events. The two are separate: an account linked to one grants nothing to the other. This section describes exactly how Quiver accesses, uses, stores and shares Google user data. Quiver's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

What we ask Google for

• openid and email: to know which Google account you linked and to show you its address.
• https://www.googleapis.com/auth/gmail.readonly, for Gmail connections only: to search and read mail, labels and attachment names in that account. This scope cannot send, delete, modify or label mail, and Quiver has no tool that tries.
• https://www.googleapis.com/auth/calendar.readonly, for Google Calendar connections only: to list the calendars in that account and read their events (times, titles, locations, descriptions, attendees and their responses, conference links) and busy times. This scope cannot create, change, delete or respond to events, and Quiver has no tool that tries.

Each connection asks for openid, email and its own scope, nothing more. These read-only scopes are what a company's Google app asks for at the read-only level described next.

Your company's own Google app

Quiver does not link Google accounts through an app of its own. A company that wants Gmail or Calendar connections creates its own Google OAuth client, in its own Google Cloud project, and gives it to Quiver under Company settings. Its people link their accounts through the company's app: Google's consent screen shows the company's app, and the company decides what it may ask for. Until a company adds one, nobody in it can link a Google account. A company admin chooses one of two levels:

• Read-only: the two read-only scopes above.
• Full access: https://www.googleapis.com/auth/gmail.modify for Gmail, to also send mail and replies, create, send and delete drafts, add and remove labels (which is how mail is archived or marked read), create labels, and move mail to and from Trash. It cannot delete mail permanently. And https://www.googleapis.com/auth/calendar for Calendar, to also create, change and delete events and answer invitations. Quiver makes such a change only when your AI calls the tool that makes it, on your behalf, and records it in your company's activity log. A company admin can hold those tools for approval or turn on read-only mode under Controls.

The company's client secret is encrypted like the keys in section 2 and used only to sign that company's people in and refresh their tokens. When the company replaces or removes its app, Quiver deletes the accounts linked through the old one and asks Google to revoke them. If Quiver adds another Google service, this page will name its scopes before the connection is offered, and Google will ask you for consent again.

How we access it

You link an account from a connection page in the portal. Google shows its consent screen; you may decline. If you grant access, Google gives Quiver a refresh token, which Quiver encrypts and stores as described in section 2. Quiver uses it to obtain short-lived access tokens, held in memory, only when your AI calls a Gmail or Calendar tool. Quiver never accesses your mail or calendars on a schedule, in the background, or for any purpose other than answering a request your AI made on your behalf. Every such request is recorded in your company's activity log under your name.

How we use it

• To return search results, messages, threads and labels, or calendars, events and busy times, to your own AI client, in response to a question you asked it.
• Where your company gave full access: to send, draft, label, archive or trash mail, or create, change, delete or answer events, as you, when your AI asks to.
• To compute over those results in code when your AI asks (for example, count messages per account or per sender, or add up meeting hours per calendar) and to return the computed figures.
• Nothing else. We do not use Google user data for advertising, for profiling, to train or improve machine-learning or AI models, to build or sell datasets, or for any purpose unrelated to the feature you are using.

Where it goes (sharing)

• Your AI client and its model provider. Mail or calendar data that answers your question, or a small sample of a large result, is returned to the AI client you installed Quiver in. That client sends it to its model provider (for example Anthropic or OpenAI) under that provider's terms. You choose the client; Quiver sends Google data nowhere else. This is the only transfer of Google user data Quiver makes, and it exists solely to provide the feature you asked for.
• Your company's activity log. Only what section 2 describes: hashes, row counts, the derivation and the computed result. Never message bodies or event details, and never the raw result rows. Company admins and managers can see the log for the whole company; users see only their own.
• Your approval email. When approval by email is on and your AI asks to send mail or change an event, Quiver emails you, and only you, a one-line summary: the recipients and subject, or the event's title, time and invitees. Never a message body or event description. The full call is shown only on the approval page, after you sign in.
• Our infrastructure providers (section 8) process data on our behalf as described there. Google user data held in gateway memory is on a server we rent; the refresh token is in the database in encrypted form.
• We do not sell Google user data, and we do not share it with anyone else, except if the law requires it or to investigate abuse or a security incident.

How long we keep it

• Mail and calendar content: in the memory of one gateway process, for up to 45 minutes after it was fetched, or until the process stops, whichever is first. It is never written to disk, the database, logs or receipts.
• Refresh token, account email and Google account id: until you remove the account, the connection is deleted, or you leave the company.
• Access tokens: in memory, until they expire (about an hour).

Human access

No person at Validus Business Solutions reads your mail or calendars. We do not have a tool that displays Google user data, and refresh tokens are unreadable without the gateway's master key. We will only read Google user data with your explicit consent (for example, to help with a problem you report), when necessary for security or to investigate abuse, to comply with law, or after it has been aggregated so it does not identify anyone.

Removing access

• On the connection page, remove a Google account. Quiver deletes the stored token immediately and asks Google to revoke its grant.
• Or revoke Quiver at myaccount.google.com/permissions. Quiver will then fail to reach that account and will tell you to reconnect or remove it.
• Leaving a company removes every Google account you linked under it.

A GitHub connection lets a person link one or more of their own GitHub accounts so that their AI can read repositories, issues, pull requests, commits and files, and propose changes to them, through Quiver. It is handled the same way as Google data in section 3, with these differences.

What we ask GitHub for

Quiver signs you in through a GitHub App. The app is registered with read and write access to repository contents, issues and pull requests, and read access to metadata, and it works only on the accounts and organizations that installed it, on the repositories they chose. You also see and change only what your own GitHub account can already see and change; GitHub's branch protection and organization rules apply as they would to you. Quiver never gets access to any other user's repositories through your link, and nobody else's link reaches yours.

What your AI can change is limited to proposals made as you: creating a branch, committing to a branch other than the repository's default branch, opening or editing a pull request, requesting reviewers, opening an issue and adding a comment. Quiver has no tool that commits to the default branch, merges, closes, deletes or changes settings. Company admins can require approval before any of these run, or switch them off with read-only mode. The content your AI writes is sent to GitHub, recorded by GitHub under your account, and is not kept by Quiver beyond the hash of the call in the activity log.

How we access, use, share and keep it

• You link an account from a connection page. GitHub shows its authorization screen; you may decline. If you authorize, GitHub gives Quiver an access token and, for apps that issue them, a refresh token. Both are encrypted and stored as described in section 2, and rewritten each time GitHub rotates them.
• Quiver calls GitHub only when your AI calls a GitHub tool, never on a schedule or in the background, and records every such call in your company's activity log under your name.
• Repository data is used only to answer your AI's request and to compute over the rows it asked for (for example, open issues per repository or commits per author), and is returned only to your own AI client. It is held in the memory of one gateway process for up to 45 minutes and is never written to disk, the database, logs or receipts. It is not used for advertising, profiling or training models, and it is not sold or shared with anyone else, except if the law requires it or to investigate abuse or a security incident.
• Tokens, your GitHub login and account id are kept until you remove the account, the connection is deleted, or you leave the company. Removing an account deletes the tokens immediately and asks GitHub to revoke the grant; you can also revoke Quiver under your GitHub account's Applications settings, after which Quiver will tell you to reconnect or remove it.
• No person at Validus Business Solutions reads your repositories through the Service, and tokens are unreadable without the gateway's master key.

A Slack connection lets a person link one or more of their own Slack workspaces so that their AI can read the channels, messages, threads and people they can already see there, through Quiver. It is handled the same way as Google data in section 3, with these differences.

What we ask Slack for

Quiver signs you in through a Slack app and asks only for user-token read scopes: channels:read, channels:history, groups:read, groups:history, im:read, im:history, mpim:read, mpim:history, users:read, and for search search:read.public, search:read.private, search:read.im and search:read.mpim, which you may decline. It asks for no bot and no write scopes, and has no tool that can post, edit, delete, react, upload, or join or leave a channel. Because the token is yours, it reaches only the public channels of your workspace and the private channels, direct messages and group messages you are already a member of. Workspace admins who require approval for apps approve Quiver before a link completes.

How we access, use, share and keep it

• You link a workspace from a connection page. Slack shows its authorization screen; you may decline. If you authorize, Slack gives Quiver an access token and, if the app uses token rotation, a refresh token. Both are encrypted and stored as described in section 2, and rewritten each time Slack rotates them.
• Quiver calls Slack only when your AI calls a Slack tool, never on a schedule or in the background, and records every such call in your company's activity log under your name.
• Messages and member details are used only to answer your AI's request and to compute over the rows it asked for (for example, messages per channel or per person), and are returned only to your own AI client. They are held in the memory of one gateway process for up to 45 minutes and are never written to disk, the database, logs or receipts. They are not used for advertising, profiling or training models, and are not sold or shared with anyone else, except if the law requires it or to investigate abuse or a security incident.
• Tokens, the workspace's name, domain and id, and your Slack user id and name are kept until you remove the workspace, the connection is deleted, or you leave the company. Removing a workspace deletes the tokens immediately and asks Slack to revoke them; you can also remove Quiver from your workspace's app settings, after which Quiver will tell you to reconnect or remove it.
• No person at Validus Business Solutions reads your Slack messages through the Service, and tokens are unreadable without the gateway's master key.

A file connection gives your company's AI a set of files: either files a company admin uploads in the portal, or files in an S3 bucket (or S3-compatible store) your company owns. When the AI reads a table from one of them, Quiver reads the rows, computes figures over them in code, and the card names the exact file, version and SHA-256 fingerprint the figures came from.

Files you upload

• Only a company admin (or, for a personal connection, its owner) can upload or delete files. Everyone who gets the connection can have their AI list, read and search them; nobody can change or delete a file from an AI client.
• Uploaded files are stored in object storage we operate with Amazon Web Services, encrypted at rest, under a location unique to your company and connection. Uploading a file with the same name adds a new version and keeps the earlier one, so figures computed from it can be traced to the bytes they came from.
• We keep each file until a company admin deletes it (which deletes every version), the connection is deleted, or the company is deleted. When a connection is deleted, its files are removed from storage within minutes. The fingerprint, name and size of a file may remain in your company's receipts, which are kept as section 11 describes; the contents do not.
• When your AI reads a file, its contents are handled like any other result: held in the memory of one gateway process for up to 45 minutes and never written to the database, logs or receipts.

S3 buckets you connect

• A company admin chooses the bucket and the folders Quiver may read, and gives access either through a role Quiver assumes (with an external id unique to that connection) or through an access key, which is encrypted as section 2 describes. We recommend a role, and a role or key that can only list and read.
• Quiver reads the bucket only when someone's AI calls a file tool, only under the chosen folders, and never writes, moves or deletes anything in it. It keeps no copy: file contents are held in memory for the answer, as above.

name.com accounts you connect

• A Name.com connection lets your AI read the domains, DNS records, forwarding, orders and transfers in a name.com account, check availability and pricing, and change DNS records, nameservers, auto-renew, the transfer lock and WHOIS privacy. It has no tool that can buy, renew or transfer a domain, change contacts or spend money.
• A company admin (for a shared account) or each person (for their own) enters the account's API username and token in the portal. Quiver checks them against name.com once, then encrypts them together as section 2 describes; nobody can read them back. A username ending in -test is sent to name.com's sandbox instead of the live service.
• Quiver calls name.com only when your AI calls a Name.com tool, never on a schedule, and records every call in your company's activity log. Results are held in memory for the answer, as above, and never stored. The username and token are kept until the key is removed, the connection is deleted, or the person leaves the company; name.com's own privacy policy applies to the account.

Alpaca accounts you connect

• An Alpaca connection lets your AI read an Alpaca brokerage account's balances, positions, orders, portfolio history and activity, and market data (quotes, trades, bars, snapshots, news), and place, replace and cancel orders and close positions. It has no tool that can deposit, withdraw or transfer money, change account settings or read account documents.
• A company admin (for a shared account) or each person (for their own) enters the account's API key ID and secret key in the portal. Quiver checks them against Alpaca once, then encrypts them together as section 2 describes; nobody can read them back. A key ID starting with PK is sent to Alpaca's paper-trading environment, where no real money is traded; one starting with AK is sent to the live environment.
• Quiver calls Alpaca only when your AI calls an Alpaca tool, never on a schedule, and records every call in your company's activity log. Results are held in memory for the answer, as above, and never stored. The key pair is kept until the key is removed, the connection is deleted, or the person leaves the company; Alpaca's own privacy policy and customer agreement apply to the account.

Use and human access

Files are used only to answer your company's AI requests. They are not used for advertising, profiling or training models, and are not sold or shared with anyone else, except if the law requires it or to investigate abuse or a security incident. No person at Validus Business Solutions opens your files except with your company's explicit consent (for example, to help with a problem you report), when necessary for security or to investigate abuse, or to comply with law.

Every dataset, log row, receipt, connection and control is owned by one company. The portal's tables are under row level security and the gateway checks the company on every request, so no company can read another's data. Companies share our gateway processes and one database; the separation is logical and tested, not physical. Our security page, in the project documentation, describes this in more detail.

• Supabase: authentication (passwords, second factors, single sign-on) and the PostgreSQL database that holds companies, connections, encrypted keys and tokens, the activity log and receipts.
• Our hosting provider: the virtual server that runs the portal and the gateway, where results are held in memory.
• Amazon Web Services: object storage for the files your company uploads, encrypted at rest. When your company connects its own S3 bucket, Quiver reads it through AWS under your company's agreement with AWS.
• Google: when you link a Google account to a Gmail or Calendar connection, Quiver calls Google's APIs as you. Google's own privacy policy applies to that account.
• GitHub: when you link a GitHub account to a GitHub connection, Quiver calls GitHub's API as you. GitHub's own privacy statement applies to that account.
• Slack: when you link a Slack workspace to a Slack connection, Quiver calls Slack's API as you. Slack's own privacy policy and your workspace's agreement with Slack apply to that workspace.
• name.com: when your company enters a name.com API username and token in a Name.com connection, Quiver calls name.com's API with them. name.com's own privacy policy and your agreement with name.com apply to that account.
• Alpaca: when your company enters an Alpaca API key ID and secret key in an Alpaca connection, Quiver calls Alpaca's Trading API and Market Data API with them. Alpaca's own privacy policy and your customer agreement with Alpaca Securities apply to that account.
• Resend: delivers the portal's email, such as invitations and the approval emails described in sections 2 and 3, to your address.
• Your AI client's provider: chosen and installed by you; receives what Quiver returns to that client.

We do not use advertising or analytics trackers on the portal.

The portal sets only the cookies Supabase Auth needs to keep you signed in. There are no advertising, analytics or third-party cookies.

Connections to Quiver use TLS. Keys, sign-ins to MCP services and Google, GitHub and Slack tokens are encrypted at rest with AES-256-GCM under a master key kept only in the gateway's environment, bound to their owner so a sealed value cannot be moved to another connection or person. Fetched results never leave process memory. Uploaded files are encrypted at rest in object storage, and each file's SHA-256 fingerprint is checked every time it is read, so a stored file that changed is refused rather than used. Two-step sign-in is available to everyone and a company admin can require it. Every administrative action is recorded before it takes effect. No outside security review has been completed yet; we say so plainly in our security documentation.

• See and export: your company's activity and receipts are available in the portal to your company's admins and, for your own activity, to you.
• Remove: remove a Google account, a GitHub account, a Slack workspace, an API key, a sign-in to an MCP service, an S3 access key or an uploaded file at any time from the connection page. Signing out of an MCP service also asks that service to end the sign-in, where it supports that. Leave a company from your company's People page (an admin can also remove you). A company admin can delete connections and the company.
• Delete your account: email us at matt@techvalidus.com from the address on the account. We delete the account, its memberships and every key and Google, GitHub and Slack token it held within 30 days, and we revoke Google, GitHub and Slack grants when we delete their tokens.
• Receipts: log rows and receipts your actions created are part of a hash chain your company relies on for evidence, so we do not edit or delete individual entries. They contain no message, event or file content; they contain your user id, the tool names, hashes, and the derivations and computed results described in section 2.
• Access, correction, portability and objection: where the law gives you these rights, write to us and we will respond within 30 days.

Quiver is for businesses and is not directed at anyone under 16. We do not knowingly collect data from children.

If we change how we handle Google user data, GitHub data, Slack data, files or anything else material, we will update this page, change the date at the top, and tell company admins by email before the change takes effect. Continued use after that date means you accept the updated policy.

Validus Business Solutions, operator of Quiver. Privacy and security questions: matt@techvalidus.com.