Security at Query++

Last updated: 2026-11-21

Query++ is a SQL editor that runs inside Salesforce Marketing Cloud Engagement. This page explains how we protect your organization's data, what we store, and how to report a security problem.

The short version

  • Query results aren't stored. They pass through our servers on their way to your screen and are never saved.
  • Your SQL and Marketing Cloud Engagement sign-in tokens are encrypted with keys unique to your organization, protected by AWS Key Management Service.
  • Each organization's data is kept separate inside the database, not just by our application code.
  • You sign in with Marketing Cloud Engagement. Query++ only does what your own Marketing Cloud Engagement permissions allow.
  • Found a security problem? Email security@queryplusplus.app. See Reporting a vulnerability.

What we store, and what we don't

What we don't 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, job queue, logs or error reports. Our API also tells browsers not to cache it.
  • Marketing Cloud Engagement passwords. Users sign in through Marketing Cloud Engagement. We receive a sign-in token, never a password.
  • Card numbers. Stripe collects card details directly. They never reach our servers.

What we store, encrypted with your organization's own keys

  • SQL in saved queries, versions, snippets, run history and published Query Activities.
  • Error messages from query runs.
  • Marketing Cloud Engagement sign-in tokens. They stay on our servers and never reach the browser.
  • The secret for a security-event webhook, if you set one up.

What we store without that extra layer (our database host still encrypts it at rest; see Encryption)

  • Each user's Marketing Cloud Engagement user ID, name and email address.
  • The names you give queries, folders and snippets, and the names of the Data Extensions and Query Activities you work with.
  • Your company name, roles, seats, settings and billing records.
  • An audit log of actions in your account, with the IP address and browser details of each request.

What stays in your Marketing Cloud Engagement account

To run a query, Query++ writes the results to Data Extensions in your own Marketing Cloud Engagement account. The temporary ones it creates expire on their own within 30 days. Data Extensions you pick as targets stay until you delete them.

How Query++ connects to Marketing Cloud Engagement

  • Your admin installs it. Query++ is added to your Marketing Cloud Engagement account as an installed package. The package settings decide what Query++ can access.
  • Users sign in with Marketing Cloud Engagement. Sign-in uses the standard OAuth authorization-code flow. Users enter their credentials on Marketing Cloud Engagement's own sign-in page, never in Query++.
  • Each user acts as themselves. We keep a separate sign-in token for each user in each business unit. Every request to Marketing Cloud Engagement uses the signed-in user's own token, so Marketing Cloud Engagement applies that user's permissions. Query++ can't reach data the user couldn't reach on their own.
  • Requests go only to Marketing Cloud Engagement. Before our servers send one, they check that the address is a Marketing Cloud Engagement API domain. Anything else is blocked.
  • Signing out of Marketing Cloud Engagement signs you out of Query++. It ends your Query++ session as well.

Encryption

  • In transit. All traffic to Query++ uses TLS. HTTP Strict Transport Security is on for the app and its APIs, so browsers refuse to connect without it.
  • At rest. Our hosting provider, Render, encrypts our database and its backups with AES-256.
  • A second layer for your sensitive data. SQL, run error messages, Marketing Cloud Engagement sign-in tokens and webhook secrets are encrypted again by Query++ itself, with AES-256-GCM.
    • Each organization has its own keys. Those keys are protected by AWS Key Management Service (KMS), which sees only internal account IDs, never your data.
    • Each encrypted value is bound to its organization, so it can't be decrypted under another organization's keys.
    • Readable keys exist only in server memory, for 20 minutes at most. We store keys only in their KMS-protected form.
    • The database rejects any value in these fields that isn't encrypted.
    • Production won't start with development keys.
  • Deleting your account deletes your keys. Any encrypted copies left in backups can no longer be read.

Keeping organizations separate

Many organizations share our database. Each one's data is kept apart by the database itself, not only by our application code.

  • Row-level security. PostgreSQL row-level security is on for every table that holds an organization's workspace, user or billing data. Each request is tied to one organization and, for workspace data, one business unit. The database then returns only that organization's rows.
  • It fails closed. If a request isn't tied to an organization, it fails instead of returning data.
  • The app can't switch it off. The database account our app uses has no permission to bypass these rules. Our servers check this at startup and refuse to run in production if that account, or any role it belongs to, could bypass them.
  • Separate keys too. Even inside the database, each organization's sensitive data is encrypted with its own keys (see Encryption).

Who can access what

Your users

  • Users sign in through Marketing Cloud Engagement. Query++ has no separate passwords.
  • Each organization has one owner, plus admins and members. Owners and admins manage users, seats and billing.
  • A user can only work in business units they have a seat for, and only within their Marketing Cloud Engagement permissions.
  • Sessions end after 30 minutes without activity and after 8 hours at most. We can end every session for a user at once.

Our staff

  • Only Streama staff who need it for their work have access to production systems.
  • Every staff account is a named account, protected by multi-factor authentication. That includes our hosting, cloud, code, payment and monitoring providers.
  • Our internal support tool has no public sign-up, requires an authenticator app, and locks accounts after repeated failed sign-ins. It can't sign in as your users, and it can't decrypt your SQL or sign-in tokens.
  • We review who has access every quarter and remove access the same day someone no longer needs it.
  • Staff actions in our support tool are logged.

Building it securely

  • Checks on every change. Before code is merged, it's scanned for known-vulnerable dependencies, leaked secrets and common coding flaws. We also rescan our dependencies every week.
  • Fixes on a deadline. Security findings get a fix deadline based on how severe they are, with the most serious fixed first.
  • Browser protections. A strict Content Security Policy and security headers are set on every service. The app can only be embedded inside Marketing Cloud Engagement.
  • Request protections. Every request that changes data needs a valid anti-forgery token, and requests are rate limited.
  • SQL checks. Query++ checks your SQL before sending it and blocks statements that change data, such as UPDATE or DELETE. Marketing Cloud Engagement's own validator has the final say, and the query runs with the signed-in user's Marketing Cloud Engagement permissions.
  • Testing the running app. We have scanned Query++ with an authenticated web application scanner.

Logging and monitoring

  • An audit log you can see. Query++ records important actions in your account: sign-ins, role and seat changes, changes to saved queries, folder and sharing changes, publishing Query Activities, data exports and billing changes. Each entry shows who, what and when. Actions people take in Query++ also show the IP address and browser of the request. Owners and admins can view and export it, or send it to their own security tools through a webhook. We keep it for 365 days.
  • Server logs without your content. Our server logs leave out SQL, sign-in tokens, cookies and Marketing Cloud Engagement responses. We keep them for 14 days.
  • Error reports with minimal data. Error reports include only an internal user ID, not names, email addresses, IP addresses or request contents. We keep them for 30 days.
  • Alerts. We're alerted to errors, unusual failure rates and service problems, and we investigate them.

Where Query++ runs

  • Hosting. Our servers and database run on Render, in Virginia, United States.
  • Key protection. AWS Key Management Service protects your organization's encryption keys, in AWS's US East region.
  • Their certifications, not ours. Render and AWS each hold SOC 2 Type II reports and ISO 27001 certification. Those cover their own systems. Streama doesn't hold these certifications itself (see Certifications).
  • Every provider is listed. Our Subprocessors page lists every company that handles your data, what each one handles and where.

Backups and recovery

  • Continuous backups. Our database is backed up continuously, so we can restore it to any point in the last 3 days.
  • Encrypted. Backups are encrypted by our hosting provider. Your SQL and sign-in tokens are also encrypted inside them with your organization's own keys.
  • Restores never overwrite. A restore creates a separate copy of the database. We check it before switching over.
  • Deletions stay deleted. If we ever restore from a backup, we delete again any accounts and users that were deleted after that backup was taken.
  • Tested. We test restoring from backup at least once a year.

Keeping and deleting data

  • How long we keep things. Our Privacy Policy lists how long we keep each kind of data.
  • Deleting your account. Your account owner can ask us to delete your organization's account (see our Terms, section 18). Access ends right away. We permanently erase your data within 30 days. Your encryption keys are deleted, so copies left in backups can no longer be read, and those copies are gone within 7 days. We'll confirm the deletion in writing if you ask.
  • Removing a user. 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.
  • Getting a copy first. Owners and admins can download a copy of a user's data from Query++ settings.
  • Cancelling isn't deleting. Cancelling a paid plan or uninstalling Query++ doesn't delete your data. Only a deletion request does.

If something goes wrong

We have a written plan for security incidents. If one happens, we:

  1. Contain it. For example, we end sessions, change secrets, or turn off the affected feature.
  2. Investigate. We work out what happened, which organizations are affected and what data was involved.
  3. Tell you. If a security incident affects your organization's data, we email your account owner without undue delay, and within 72 hours of becoming aware of it, as our Data Processing Agreement says. We tell you what happened, what data was involved, what we've done, and what you may need to do.
  4. Keep you updated as we learn more.
  5. Learn from it. We review every incident and fix what allowed it.

We keep a record of every incident, including ones that turn out not to affect anyone's data.

Payments

Stripe handles all payments. You enter card details on Stripe's own checkout and payment forms, so they go straight to Stripe and never reach our servers. We keep Stripe's IDs for your customer record and subscription, plus your plan details, but never card details. Stripe is certified as a PCI DSS Level 1 Service Provider, the highest level for payment processors.

Certifications and reviews

  • No certifications of our own yet. Streama doesn't hold a SOC 2 report or ISO 27001 certification. The certifications on this page belong to our providers and cover their systems, not ours.
  • Data protection terms. Our Data Processing Agreement is part of our Terms. It includes the European Commission's Standard Contractual Clauses and the UK Addendum for transfers out of Europe.
  • Security questionnaires. We answer security questionnaires from customers and prospective customers. Email security@queryplusplus.app.

Your part

Security is shared. These steps on your side make the biggest difference:

  • Manage Marketing Cloud Engagement access. Query++ follows your users and permissions there. Give each user only the access they need there.
  • Remove people who leave. Deactivate them in Marketing Cloud Engagement, which stops them signing in to Query++, and take back their Query++ seat.
  • Review your audit log. Check it now and then, or send it to your own security tools through the webhook.
  • Keep secrets out of SQL. Don't put passwords, API keys or other secrets in queries, snippets or their names.
  • Tell us about anything odd. Email security@queryplusplus.app if you see something unexpected.

Reporting a vulnerability

If you find a security problem in Query++, please tell us. We welcome reports from everyone.

How to report

Email security@queryplusplus.app with:

  • what you found and where;
  • steps to reproduce it; and
  • what an attacker could do with it.

What we'll do

  • Confirm we got your report within 3 business days.
  • Keep you updated while we investigate and fix it.
  • Thank you publicly once it's fixed, if you'd like. We don't offer paid rewards.

In scope

queryplusplus.app and its subdomains, and the Query++ installed package in Marketing Cloud Engagement. Problems in Marketing Cloud Engagement itself belong with Salesforce.

Please don't

  • access, change or delete other people's data. Test only with accounts and data you own;
  • disrupt the service, including denial-of-service testing;
  • use social engineering, phishing or physical attacks; or
  • send reports from automated scanners without showing a real problem.

Disclosure

Please give us 90 days to fix the problem before you share it publicly. We'll work with you on timing, and we may agree to publish sooner once it's fixed.

Safe harbor

If you make a good faith effort to follow this policy, we will consider your research authorized. We won't take or support legal action against you for it, including under anti-hacking laws, and we waive our Terms where they would otherwise restrict your research. If someone else takes legal action over research you did under this policy, we'll make it known that you acted with our authorization. If you're unsure whether something is allowed, ask us first at security@queryplusplus.app.

Contact

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