Privacy Policy

Last Updated: October 11, 2026

Who we are

Our website address is: https://querystreams.com. Query Streams provides data integration, query, alerting, and automation services that let you send queries to your own databases and data sources and retrieve results into spreadsheets, applications, AI tools, and reports. Our Service includes add-ons for Google Sheets and Microsoft Excel, a web portal with a query builder, a REST API for programmatic access, the Model Context Protocol (MCP) for AI assistants such as Claude and ChatGPT, our own AI assistant ("Nova"), alerting and scheduled reporting, and a Network Agent that you install on your own systems (available for Windows, macOS, and Linux).

For the purposes of data protection law, Query Streams is the controller of your account, billing, and website data, and acts as a processor (or service provider) on your behalf for the contents of the databases and data sources you connect. A Data Processing Addendum is available on request for customers who require one.

Information we collect

Account and organization information. When you create an account we collect your name, email address, password (stored hashed) or single-sign-on identity, organization name, role, and any profile details you choose to provide. If you sign up with Google or Microsoft, see the dedicated sections below.

Billing information. Subscription plan, invoices, and payment status. Card details are collected and stored by our payment processor (Stripe); we do not store full card numbers.

Usage and telemetry. Information about how the Service is used: which features, connectors, and channels are used; query counts, execution times, error states, data-transfer sizes; Network Agent version, operating system, and health/heartbeat status; and the identity of the client (add-on, portal, API key, MCP key, or connected AI client) that made each request. We use this to operate, secure, bill for, and improve the Service.

Support communications. Messages you send to support, and the account context needed to help you.

Website visitor data. When you browse querystreams.com we collect standard web logs (IP address, browser, pages visited, referrer) and first-party analytics about how visitors use our site. See "Cookies, analytics, and advertising" below.

How your database data is handled

The Network Agent runs on your own systems, holds your database credentials locally, and executes your queries there. By default, Query Streams acts as a secure conduit: query results pass through our relay and real-time servers only while they are in transit to the destination you chose (a spreadsheet, the portal, an API caller, or an AI client) and are discarded once delivered. We monitor traffic patterns and transfer sizes for service quality and billing, but we do not build a copy of your databases on our servers.

Some features you may choose to use necessarily process, and in some cases retain, a limited amount of your data so that the feature can work. Where that is the case we say so here:

Schema Capture (optional, per database connection) stores database structure metadata — database, table, and column names, data types, indexes, and foreign-key relationships — so that the query builder, Nova, and MCP clients can offer autocomplete and schema navigation. Schema Capture does not store row data.
Semantic Intelligence (optional, per database) builds on Schema Capture by profiling your tables. Profiles may include column statistics (row counts, null rates, distinct counts), detected data types and enumerations, inferred relationships, and a small number of sample values per column. These profiles are stored so that Nova and AI clients can write better queries. Do not enable Semantic Intelligence on databases containing data you do not want profiled; you can disable it and delete stored profiles at any time.
Alerts and scheduled reports execute saved queries on a schedule, evaluate the results against your rules, and deliver the output (for example, by email or to a connected destination). To do this we process the results on our servers and may retain the values needed to evaluate alert conditions, detect changes, and show alert history, as well as copies of generated reports for the period needed to deliver them and show delivery history.
Nova AI assistant processes the natural-language prompts you type, the schema metadata and profiles for the databases you are working with, and — when you ask it to run or explain a query — the SQL and a bounded excerpt of the results. See "Nova AI assistant" below.
Federated (cross-source) queries combine results from more than one connection. The combination step runs on our servers and the intermediate results are held in memory only for the duration of the query.
Query history and saved queries store the SQL text, parameters, and execution metadata (timing, row counts, status) for queries run through the portal, API, or MCP, so that you and your teammates can review and reuse them. History does not store result rows except where a feature above says otherwise.
Spreadsheet add-on streaming may buffer chunks of a result on our relay for a few seconds so that large results can be reassembled reliably in Excel or Sheets. Buffers are discarded when the transfer completes or fails.

Except as described above, we do not store, sell, or use the contents of your databases for any purpose other than providing the Service to you.

Nova AI assistant

Nova is Query Streams' built-in AI assistant. When you use Nova, the content you provide (your prompt, the conversation so far, the schema metadata and Semantic Intelligence profiles for the databases in scope, and, when you ask Nova to run or interpret a query, the SQL and a bounded excerpt of its results) is sent to the large-language-model providers we use to power Nova. Our current AI providers are listed in "Who we share your data with" below. We use these providers under business API terms under which they do not use your content to train their models. We may also run some models on infrastructure we operate.

We retain Nova conversation history so that you can return to earlier conversations, and we record usage metrics (tokens, cost, latency, model) for billing and service improvement. We may also retain verified query patterns that Nova learned to be correct for your organization (for example, that a particular join or filter produced the result you accepted) in order to improve Nova's future answers for your organization only; these records contain SQL and schema references, not result rows. Nova features can be disabled for your organization, and you can delete conversation history from the portal or by contacting support.

Website assistant

querystreams.com offers a chat assistant ("Ask about Query Streams") that answers questions about the product. It is an AI assistant, not a live chat and not Nova: it only has access to our public documentation, pricing, and the page you are reading, and it never connects to your databases or to any account data. When you use it, the messages you type, the address and title of the page you are on, and your browser language are sent to the AI provider that powers it (Anthropic, under business API terms under which your content is not used to train their models). Cloudflare Turnstile runs when you open the assistant to tell people from bots.

We store each conversation (your messages, the assistant's replies, the pages it linked to), the page it started on, the language, the country derived from your IP address, a one-way hash of your IP address (never the address itself), and a random reader identifier that the website keeps in your browser's local storage so that your visits can be joined up; the same identifier is used by our first-party website analytics described below. If you choose to leave your email address in the chat, we store it with a short summary of the conversation so that we can follow up, and we may match it to an existing account to route the reply. We read conversations to improve the assistant's answers and our documentation.

Message text and marketing attribution are removed from a conversation 180 days after it started; the remaining record (topic, outcome, cost, timings) is deleted after two years. Email addresses left in the chat are deleted 90 days after we close them, or earlier on request. If you prefer not to use the assistant, every page also offers an email form, and you can clear the reader identifier by clearing your browser's site data for querystreams.com.

Cookies, analytics, and advertising

Service cookies. Query Streams uses cookies and similar storage to maintain authentication sessions and remember your preferences in the portal. These are essential for the functioning of the Service. For users of our add-ons, authentication tokens may be stored locally within your spreadsheet application to maintain the connection to our service and your Network Agent.

Website analytics. On querystreams.com we use first-party analytics operated by Query Streams to understand which pages are visited, how visitors arrive, and which features generate interest. We also use Cloudflare in front of our website and services for security, caching, and bot protection, which processes IP addresses and request metadata.

Advertising and conversion measurement. We run advertising campaigns on platforms such as Google Ads and Reddit Ads. To measure whether those campaigns work, we may use those platforms' conversion-tracking technologies (such as tags or pixels) on our website and may report conversion events (for example, "started a trial") back to them, including click identifiers from the ad you arrived through. These platforms may set their own cookies, which are governed by their privacy policies. We do not sell your personal information to advertisers, and we do not use advertising technologies inside the authenticated portal, add-ons, or Network Agent. You can opt out of interest-based advertising through your browser settings, the platforms' own controls, or industry opt-out tools.

Google Account Authentication

Query Streams uses Google OAuth to provide a convenient and secure login option for the web portal. When you sign in with Google, we request the following permissions:

openid - Enables basic OpenID Connect authentication to verify your identity.
email - Provides access to your Google email address to create and identify your Query Streams account.
profile - Provides access to your basic profile information (name and profile picture) for display in the Query Streams portal.

What Google Data We Store

When you authenticate with Google, we store the following information in our database:

Email address: Used to create your Query Streams account, identify you when you log in, and send service-related communications.
Name and profile picture: Displayed in the Query Streams portal interface for personalization.
OAuth tokens: Encrypted and stored securely to maintain your authenticated session.

We do not sell, rent, trade, or otherwise disclose your Google data to third parties for marketing, advertising, or any other purpose not directly related to providing the Query Streams authentication service.

Revoking Google Access

You can revoke Query Streams' access to your Google account at any time by visiting your Google Account Permissions page and removing Query Streams from your list of connected apps.

Microsoft Account Authentication

Query Streams uses Microsoft OAuth to provide a convenient and secure login option for the web portal. When you sign in with Microsoft, we request the following permissions:

openid - Enables basic OpenID Connect authentication to verify your identity.
email - Provides access to your Microsoft email address to create and identify your Query Streams account.
profile - Provides access to your basic profile information (name and profile picture) for display in the Query Streams portal.

What Microsoft Data We Store

When you authenticate with Microsoft, we store the following information in our database:

Email address: Used to create your Query Streams account, identify you when you log in, and send service-related communications.
Name and profile picture: Displayed in the Query Streams portal interface for personalization.
OAuth tokens: Encrypted and stored securely to maintain your authenticated session.

We do not sell, rent, trade, or otherwise disclose your Microsoft data to third parties for marketing, advertising, or any other purpose not directly related to providing the Query Streams authentication service.

Revoking Microsoft Access

You can revoke Query Streams' access to your Microsoft account at any time by visiting your Microsoft Account App Permissions page and removing Query Streams from your list of connected apps.

AI Assistant Access (MCP) and API

In addition to our spreadsheet add-ons and portal, Query Streams offers two ways to access your data programmatically: a REST API for direct programmatic access, and the Model Context Protocol (MCP), which lets AI assistants such as Claude and ChatGPT connect to Query Streams and run queries or read schema on your behalf. Both operate through the same conduit described above: queries execute locally on your Network Agent, and results pass through our servers only during active transmission and are not stored except as described in "How your database data is handled".

Authentication and Credentials

MCP and API access are authorized using credentials you create and manage in the portal:

API keys and MCP keys: Keys that you generate and can revoke at any time. We store these keys only in hashed form, never in plain text.
OAuth authorization (one-click connect): When you connect an AI client such as Claude or ChatGPT using our one-click OAuth flow, you are first shown a consent screen that lists exactly which organization and permissions you are granting. We then record a grant for that client and issue a short-lived access token and a rotating refresh token, all stored only as hashed values. We do not store the AI provider's client secrets, and we do not store any of your query results.

What We Log

For security, troubleshooting, rate limiting, and billing, we record metadata about MCP and API activity — such as which tool or endpoint was called, the SQL text of the query, timestamps, the calling client's identity, data-transfer sizes, and success or error status. These logs do not contain the actual rows returned by your queries.

Data Sent to AI Providers

When you use a third-party AI assistant with Query Streams through MCP, the query results you request are returned to that assistant and are therefore transmitted to the AI provider you have chosen — for example, Anthropic for Claude or OpenAI for ChatGPT. Once your data reaches that provider, it is handled under that provider's own privacy policy and terms, which Query Streams does not control. You decide what to ask the assistant and, consequently, what data is shared with it. We recommend reviewing your chosen AI provider's privacy practices and connecting only data you are comfortable sharing with that provider.

Revoking AI and API Access

You remain in control of every connection. You can revoke any API key, MCP key, or connected AI client at any time from the portal — for MCP and OAuth connections, use the MCP / Connected Apps section of your account. Revoking a credential immediately invalidates its tokens and prevents any further queries from that client.

Who we share your data with

Query Streams does not sell, rent, or trade your personal information. We share data only with service providers (subprocessors) that help us run the Service, under contracts that restrict their use of the data to providing services to us, and otherwise as required by law. Our current categories of subprocessors are:

Hosting and infrastructure: DigitalOcean (application servers, relay, and databases) and Cloudflare (DNS, security, caching, and bot protection).
Payments: Stripe (subscription billing and card processing).
Identity: Google and Microsoft (optional single sign-on, as described above).
AI model providers (Nova and the website assistant): Anthropic and OpenAI, and open-weight models run on infrastructure we operate. Which provider handles a given request depends on the model configured for your organization and the task; the website assistant uses Anthropic.
Add-on marketplaces: Google Workspace Marketplace and Microsoft AppSource, whose platform policies apply in addition to ours when you install our add-ons.
Email delivery and error monitoring: providers that deliver transactional email (alerts, reports, notifications) and collect application error reports. Error reports contain technical context and may include the SQL text of a failing query, but are configured not to include result rows.

We may also disclose information if required by law, subpoena, or court order; to protect the rights, property, or safety of Query Streams, our customers, or others; or in connection with a merger, acquisition, or sale of assets, in which case we will notify you before your information becomes subject to a different privacy policy.

Legal bases for processing

Where the GDPR, UK GDPR, or similar laws apply, we process personal data on the following bases: performance of a contract (providing the Service you signed up for); legitimate interests (securing and improving the Service, preventing abuse, measuring our marketing, and communicating with you about your account), balanced against your rights; consent (where required, for example for non-essential cookies or marketing email); and legal obligation (tax, accounting, and responding to lawful requests).

International data transfers

Query Streams is based in the United States and our servers are hosted by DigitalOcean in the United States. If you access the Service from outside the United States, your account data and any data that passes through our servers will be transferred to and processed in the United States. Where required, we rely on appropriate safeguards such as Standard Contractual Clauses. Because the Network Agent runs on your own systems and query results travel only through our relay, we recommend installing the agent on the same network as your database to minimize data movement.

How long we retain your data

We retain account information for as long as your account is active. After an account or organization is closed, we delete or de-identify its data within a reasonable period, except for billing records we must keep for tax and accounting purposes, security logs retained for a limited period, and information we need to enforce our agreements or resolve disputes.

Usage metadata and activity logs (query timing, transfer sizes, connection status, SQL text) are retained for a limited period for security, troubleshooting, and billing, and are then aggregated or deleted. Schema Capture and Semantic Intelligence data is retained until you disable the feature or delete the database connection. Alert history, report copies, and Nova conversation history are retained for as long as they are useful to you in the product and can be deleted on request. Website assistant conversations follow the periods stated in the "Website assistant" section above.

Your rights and choices

You can access, correct, or delete your account information at any time through your account settings, and you can enable, disable, or delete Schema Capture, Semantic Intelligence, alerts, reports, Nova history, and connected credentials from the portal. You may request a copy of your account data and usage history by contacting support.

Depending on where you live, you may have additional rights, including the right to access, correct, delete, or port your personal data; to object to or restrict certain processing; to withdraw consent; and to lodge a complaint with a supervisory authority. Residents of California and other U.S. states with comprehensive privacy laws have the right to know what personal information we collect and how we use it, to delete it, to correct it, and not to be discriminated against for exercising those rights. We do not sell personal information and do not share it for cross-context behavioral advertising, other than the advertising conversion measurement described above, which you can opt out of using the controls described there. To exercise any right, contact [email protected]. We will verify your identity before acting on a request and will respond within the time required by applicable law.

The contents of the databases you connect remain under your control. If you are an end user of a Query Streams customer (for example, an employee of an organization that uses Query Streams) and have questions about data that organization processes through the Service, please contact that organization first; we will assist them in responding.

Children

The Service is intended for business use and is not directed to children under 16. We do not knowingly collect personal information from children. If you believe a child has provided us with personal information, contact us and we will delete it.

Security

Query Streams uses industry-standard measures to protect data, including TLS encryption for all traffic between the add-ons, portal, Network Agent, and our servers; hashed storage of passwords, API keys, MCP keys, and OAuth tokens; encryption of stored credentials; access controls and audit logging on our systems; and network-level protection through Cloudflare. The Network Agent keeps your database credentials on your own systems and executes queries locally, so they are never transmitted to us.

No method of transmission or storage is completely secure. If we become aware of a security incident that affects your personal data, we will notify you and the relevant authorities as required by applicable law.

Data usage and subscription

Query Streams offers subscription plans with different usage allowances. We measure the data transferred through our servers, the number of queries, API and MCP calls, AI usage, and other usage metrics for billing purposes, as described in our Terms of Service. Usage beyond your plan's allowance may result in additional charges or reduced service depending on your plan.

Changes to this policy

We may update this Privacy Policy from time to time. When we make material changes we will update the "Last Updated" date above and, where appropriate, notify you through the Service or by email. Your continued use of the Service after a change takes effect means you accept the updated policy.

Contact information

If you have questions or concerns about this Privacy Policy or our data handling practices, or wish to exercise your rights, please contact us at [email protected].