Subprocessors
These are the companies that help us run Query++. Each one has a written agreement with us that protects your data at least as well as our Data Processing Agreement.
Query results pass through our servers, hosted by Render, on their way to your screen. They aren't saved anywhere, and no other company on this list receives them.
Subprocessors
These companies handle data that belongs to your organization.
| Company | What it does for Query++ | Data it handles | Where |
|---|---|---|---|
| Render Services, Inc. | Hosts our servers, database and backups | Everything Query++ stores: users' names and email addresses, your SQL and saved work, run history, audit logs and encrypted Marketing Cloud Engagement sign-in tokens. Query results pass through but aren't saved | United States (Virginia) |
| Amazon Web Services, Inc. | Protects the encryption keys for your organization's data (AWS Key Management Service). Sends account notices by email (Amazon SES) | For keys: encryption keys and your organization's internal id, never your SQL, tokens or other content. For email: the names and email addresses of account owners and admins, and the notice itself | United States (Virginia) |
| Functional Software, Inc. (Sentry) | Reports errors so we can fix them | Error details, the part of our code where it happened, browser and system versions, and an internal user id. No names, email addresses, IP addresses, SQL or query results | United States |
| Raintank, Inc. dba Grafana Labs (Grafana Cloud) | Stores our server logs | IP addresses, browser details, internal ids and the pages and actions requested. SQL, tokens and other secrets are removed first | United States |
Providers for our own business
These companies handle our own account, billing and support records, such as who pays for Query++ and the emails you send us. They don't handle your organization's data in Query++, so they aren't subprocessors under our Data Processing Agreement. We list them so you can see everyone involved.
| Company | What it does for us | Data it handles | Where |
|---|---|---|---|
| Stripe, LLC | Takes payments and sends invoices. Stripe also uses this data for its own fraud checks and legal duties | Billing contact name, email and address, company name, tax id and invoices. Card details go straight to Stripe. We never see them | United States |
| Google LLC (Google Workspace) | Our email, including support and privacy requests | The emails you send us and our replies | United States and other countries where Google operates |
| Salesforce, Inc. | Our own customer records, for invoice requests | Company name, billing email, plan, seats, payment terms and PO number | United States |
| Cloudflare, Inc. | Runs the DNS for our domain, so browsers can find Query++ | The DNS lookup itself. Cloudflare doesn't see your data or traffic | Worldwide |
Salesforce Marketing Cloud Engagement
Marketing Cloud Engagement isn't our subprocessor. It's your own platform, under your own agreement with Salesforce. Query++ reads from it and writes to it only when your users ask, using their own Marketing Cloud Engagement sign-in and permissions. The Salesforce row above is our separate customer records system, not your Marketing Cloud Engagement account.
Where data is processed
Your organization's data is stored and processed in the United States.
If you're in the European Economic Area, the UK or Switzerland, this means your data is transferred to the United States. Our Data Processing Agreement covers that transfer with the European Commission's Standard Contractual Clauses and the UK Addendum to them. Each subprocessor above has its own data protection agreement with us. Render, AWS and Grafana Labs are also certified under the EU-US Data Privacy Framework, and so is Sentry.
When this list changes
We'll tell you at least 30 days before a new subprocessor starts handling your organization's data. We email the owner of every Query++ account. Anyone else can get the same notice, such as someone on your security team: email privacy@queryplusplus.app with the subject "Subscribe to subprocessor updates".
If you have a reasonable data protection concern about a new subprocessor, email us within those 30 days. We'll work with you to resolve it. If we can't, you can end your subscription, and we'll refund the unused part of any fees you've prepaid.
Rarely, we may need to replace a subprocessor faster, for example if a provider fails or a security issue requires it. If that happens, we'll tell you as soon as we can, and you can still object.
Our Data Processing Agreement sets out these terms in full.
Change log
- 2026-11-21: First published.
Questions
Email privacy@queryplusplus.app. See also our Data Processing Agreement, Privacy Policy and Security page.