Query++ Privacy Policy

Version: 2026-11-21
Effective date: 2026-11-21
Earlier versions: queryplusplus.app/privacy/archive

DRAFT for counsel review. Not in effect.

The short version

  • Query++ reads your Marketing Cloud Engagement data to show it to you. Query results aren't stored on our servers.
  • We store what your workspace needs: users' names and email addresses from Marketing Cloud Engagement, your saved SQL (encrypted) and an audit log of actions.
  • We don't sell personal data. We don't run ads, analytics or tracking.
  • Stripe handles card payments. We never see full card numbers.
  • Questions: privacy@queryplusplus.app.

The rest of this policy explains each point in detail.

1. Who we are and what this policy covers

Query++ is made by Streama LLC, an Arkansas limited liability company. Our mailing address is 813 Oak St Ste 10 - 1131, Conway, AR 72032. "We", "us" and "Streama" mean Streama LLC.

This policy explains what personal data we collect, why, who we share it with, how long we keep it and what choices you have. It covers:

  • the Query++ app, which runs inside Salesforce Marketing Cloud Engagement;
  • this website, queryplusplus.app; and
  • our support, by email.

Query++ is for business use by adults, and isn't meant for anyone under 18.

It doesn't cover how Salesforce handles data in your Marketing Cloud Engagement account. Salesforce's own privacy policy and your agreement with Salesforce cover that.

Our Terms of Service and Data Processing Agreement also apply. If your organization has its own agreement with us, that agreement explains how we handle your organization's data, and this policy fills in the details.

2. Three kinds of data, and our role

Marketing Cloud Engagement data that passes through. When a user runs a query, Query++ reads data from your Marketing Cloud Engagement account, such as Data Extension rows and query results, and shows it to that user. We handle it only while showing it, on your organization's behalf. We don't store it on our servers (see section 3).

Your workspace. This is what your organization creates and manages in Query++: SQL, saved queries and their versions, snippets, folders, run history, your users' names and email addresses, and the audit log of actions in your account. We process it on your organization's behalf and follow its instructions. In privacy law terms, your organization is the controller, and we are its processor (a "service provider" under US state laws). Our Data Processing Agreement covers this data.

Our business data. This is data we use to run our own business: billing contacts and invoice details, support emails, security logs and error reports, and visits to this website. For this data we are the controller. We decide how it's used, as this policy describes.

If you use Query++ through your organization and have a question about your workspace data, ask your organization's Query++ owner or admin first. We'll help them answer it.

3. What we never store

  • Query results and Data Extension rows. Each page of results is read from Marketing Cloud Engagement when a user asks for it and sent straight to their browser. It isn't saved in our database, our job queue, our logs or our error reports. Results do stay in your Marketing Cloud Engagement account, in the Data Extensions that hold them (see our Terms, section 4).
  • Marketing Cloud Engagement passwords. Users sign in through Marketing Cloud Engagement. We receive a sign-in token, never a password. We store those tokens encrypted, and they never reach the browser.
  • Card numbers. Stripe collects card details directly. They never touch our servers.
  • Readable SQL on our servers. We store SQL only in encrypted form.
  • Tracking data. We don't use analytics, advertising or tracking tools, in the app or on this website.

4. What we collect and why

To sign you in. When a user signs in, Marketing Cloud Engagement sends us their user ID, name and email address, plus the IDs of your enterprise account and business unit. We also receive sign-in tokens, which we store encrypted. We use these to know who the user is, which account and business unit they're working in, and what they're allowed to do.

To run your workspace. We store:

  • SQL, saved queries and their versions, snippets and run history, all with the SQL encrypted;
  • the names you give queries, folders and snippets, and the names of the Data Extensions and Query Activities you work with;
  • roles, seat assignments and settings, such as a security-event webhook you set up; and
  • an audit log of actions in your account: who did what and when, with the IP address and browser details of the request.

We use this to provide Query++ and to let your owner and admins see what happened in your account.

To bill you. We keep your company name, Stripe customer and subscription IDs, plan, seat and business unit counts, and billing dates. Stripe collects card and billing details at checkout, including your company name, which it passes to us. If you ask to pay by invoice, we collect your company name, billing contact names and email addresses, PO number and any notes you add.

To keep Query++ secure and working. Our servers log requests, including IP address, browser details and internal account and user IDs. Our error reports include only an internal user ID. We use these to find and fix problems and to detect misuse.

To help you. If you email us, we keep your message and our reply.

On this website. We don't set cookies or run analytics on queryplusplus.app. Our hosting provider may log IP addresses and browser details to keep the site secure.

For your workspace data, your organization decides the legal basis, and we process the data on its instructions (see section 2). For our business data, these are our legal bases under the GDPR and UK GDPR:

What we do Legal basis
Billing, invoices and payment Performing our contract with your organization
Keeping billing and tax records Complying with the law
Answering your support emails Our legitimate interest in helping customers
Security logs, error reports and preventing misuse Our legitimate interest in keeping Query++ secure and working
Records of who accepted our Terms and when Our legitimate interest in proving our agreements
Product news and offers by email, which you can unsubscribe from at any time Your consent, or our legitimate interest in telling customers about Query++ where the law allows

We don't:

  • sell or rent personal data;
  • show ads or share data with advertisers;
  • use your data to train AI models; or
  • make automated decisions about people that have legal or similar effects.

6. Who we share data with

We don't sell personal data. We share it only in these cases.

Companies that help us run Query++. These are our subprocessors. Each one gets only the data it needs for its job:

  • Render hosts our servers, database and backups.
  • AWS Key Management Service protects the encryption keys for your data. It sees only internal account IDs, never your data.
  • Stripe handles payments. Stripe also uses payment data for its own fraud prevention, under its own privacy policy.
  • Sentry receives error reports, which include only an internal user ID.
  • Grafana Cloud stores our server logs.
  • Cloudflare runs DNS for our domain.
  • Google Workspace hosts our email, including support messages.

Our Subprocessors page lists each one, with what it does and where it stores data. It also explains how we tell you about changes.

Salesforce. Query++ works inside your Marketing Cloud Engagement account and uses each user's own sign-in to read and write data there. Salesforce handles that data under your agreement with them. We also use our own Salesforce account as our sales system. If you ask to pay by invoice, we send your company name, billing email, plan details and PO number to it.

Places you choose. If your organization sets up a security-event webhook, we send audit log events to the address you give us, including user email addresses and IP addresses.

When the law requires it. We disclose data to authorities only when we receive a valid legal request, such as a subpoena or court order. Unless the law forbids it, we tell your organization first.

If our business changes hands. If Streama is merged, acquired or sells its business, personal data may transfer to the new owner. This policy will continue to apply to it, and we'll tell you.

7. Where data is stored

We store and process data in the United States. Our servers and database run on Render in Virginia, and AWS manages our encryption keys in its US East region. A few subprocessors may process some data in other countries. Our Subprocessors page shows where.

If you are in the European Economic Area, the UK or Switzerland, your data is transferred to the United States. For workspace data, our Data Processing Agreement includes the European Commission's Standard Contractual Clauses and the UK Addendum to them. Several of our subprocessors are also certified under the EU-US Data Privacy Framework.

8. How long we keep data

Data How long
Saved queries, versions, snippets, folders and run history Until your users delete them, or until your account is deleted. Run history and versions have no time limit while your account exists
Users' names, email addresses and sign-in tokens Until the user is removed from your account, or the account is deleted
Audit log 365 days
Sign-in sessions End after 30 minutes without activity, and after 8 hours at most
Server logs 14 days
Error reports 30 days
Backups 7 days
Records of Terms acceptance At least 5 years after your account closes
Payment and invoice records Stripe keeps them for as long as tax and financial law requires
Support emails As long as we need them to help you

When a user is removed, we delete their name, email address and sign-in tokens, and remove them from the audit log. Their saved work stays with your organization.

When your account is deleted, access ends right away, and we permanently erase all your data within 30 days. Our Terms (section 18) explain how to ask for this. Cancelling a paid plan or uninstalling Query++ doesn't delete anything.

In your browser, Query++ keeps copies of open editor tabs for up to 30 days and clears them when you sign out (see section 11).

9. How we protect data

  • In transit. All traffic to Query++ uses HTTPS, and browsers are told to never connect without it.
  • At rest. Our database and its backups are encrypted.
  • A second layer for your SQL. Your SQL, run errors and Marketing Cloud Engagement sign-in tokens are encrypted again, with a key unique to your organization. That key is protected by AWS Key Management Service.
  • Separation between customers. The database itself checks which organization each request belongs to, so one customer can't read another's data.
  • Staff access. Only Streama staff can use our internal admin tools. Each person signs in with a password and a second factor, and their actions are logged.

No system is perfectly secure. If a security breach affects your data, we'll tell you without undue delay, as our Data Processing Agreement describes.

Our Security page has more detail. To report a vulnerability, email security@queryplusplus.app.

10. Your rights

You can ask us about your personal data at any time. It's free, and we honor these requests for everyone, wherever you live.

You can ask us to:

  • show you the personal data we hold about you, and send you a copy;
  • give you that copy in a common format you can move to another service;
  • correct anything that's wrong;
  • delete your data;
  • limit how we use it.

You can also object to how we use your data, for example in our security logs. We'll stop unless we have a strong reason to continue, such as keeping Query++ secure, and we'll explain that reason.

If you've agreed to receive product emails, you can withdraw that at any time. Every email has an unsubscribe link.

How to ask

Email privacy@queryplusplus.app. To protect your data, we'll check that the request really comes from you, usually by replying to the email address we have for you. Someone you trust can also ask for you, with your signed permission.

We'll reply within 30 days. If a request is complex, it can take up to two more months. If so, we'll tell you why within the first 30 days.

If you use Query++ through your employer

Your employer runs your Query++ workspace, so they decide what happens to the data in it. You can still get help quickly. Your workspace owner or admin can download a copy of your data from Query++ settings. Your name and email address come from Marketing Cloud Engagement, so if you update them there, Query++ updates the next time you sign in.

You're also welcome to email us. We'll pass your request to your employer and help them answer it.

If you're not happy with our answer

Reply to our email and ask us to look again. We'll review the decision and answer within 60 days. Using these rights will never affect how we treat you.

If you're in the EU, you can complain to your local data protection authority. In the UK, that's the Information Commissioner's Office (ico.org.uk). We hope you'll talk to us first, but you don't have to.

We don't sell your data

We don't sell personal data, and we don't share it for targeted advertising.

11. Cookies and browser storage

Cookies. Query++ uses two cookies, both strictly necessary, so there's nothing to opt into. One keeps you signed in and ends when you close your browser. The other only exists while you sign in, to protect the return trip from Marketing Cloud Engagement, and lasts at most 15 minutes. Both are encrypted and only our server can read them. Your session also ends after 30 minutes without activity, and after 8 hours at most.

Stripe handles card payments inside Query++. Stripe may set its own cookies to prevent fraud. Its cookie policy explains them.

Our website, queryplusplus.app, sets no cookies.

Storage in your browser. To make Query++ faster and keep your work safe, it stores some things on your own device:

What Why How long
Open editor tabs, including their SQL So you don't lose work if the page reloads Up to 30 days. Cleared when you sign out
Lists of your Data Extensions and fields So autocomplete is fast. No query results are stored 24 hours. Cleared when you sign out
Your name, email, role and current tab So the app knows who's signed in Until you close the tab
Editor preferences and layout So Query++ looks the way you left it Until you clear your browser data

This data stays on your device. Clearing your browser data removes all of it.

No tracking. We don't use analytics, ads or tracking tools, in Query++ or on our website. We don't follow you across other sites. That's why Do Not Track and Global Privacy Control signals don't change anything: there's no tracking for them to turn off.

12. Changes to this policy

We may update this policy. Each version has a date at the top, and earlier versions stay available at queryplusplus.app/privacy/archive.

Small changes, such as fixing typos, updating contact details or making wording clearer, take effect when we post them.

For a material change, such as collecting a new kind of data, using it for a new purpose or sharing it with a new kind of company, we'll email your account owner and show a notice in Query++ at least 30 days before it takes effect. Your users then accept the new version in Query++.

Changes to our list of subprocessors follow the notice on our Subprocessors page.

13. Contact us

Questions about this policy or your data: privacy@queryplusplus.app. A person reads every message, and we'll reply within a few business days.

Other ways to reach us:

By mail: Streama LLC, 813 Oak St Ste 10 - 1131, Conway, AR 72032.