Query++ Data Processing Agreement

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

DRAFT for counsel review. Not in effect.

How this DPA works

  • This Data Processing Agreement ("DPA") is part of the Query++ Terms of Service. It applies automatically when your organization accepts those Terms. No signature is needed.
  • In this DPA, "Provider" means Streama LLC, and "Customer" means the organization that accepted the Terms.
  • This DPA covers personal data that Provider processes for Customer when Customer uses Query++ ("Customer Personal Data"). Our own account, billing and support records are covered by our Privacy Policy instead.
  • This DPA has two parts: this Cover Page, and the Common Paper DPA Standard Terms Version 1.1 at commonpaper.com/standards/data-processing-agreement/1.1 ("DPA Standard Terms"), which are incorporated by reference. We use the DPA Standard Terms without changes. Every change we make is listed on this Cover Page under "Changes to the DPA Standard Terms". If this Cover Page and the DPA Standard Terms conflict, this Cover Page controls.
  • Where the DPA Standard Terms say so, the EU Standard Contractual Clauses and the UK Addendum apply to transfers out of the EEA, the UK and Switzerland. Customer and Provider are treated as having signed them when Customer accepts the Terms.
  • Need a countersigned copy for your records? Email privacy@queryplusplus.app.

Key Terms

Agreement

This DPA supplements the Query++ Terms of Service at queryplusplus.app/terms, as updated from time to time. If Customer and Provider have signed an order form or other agreement that refers to this DPA, this DPA also supplements that agreement.

Approved Subprocessors

The subprocessors listed at queryplusplus.app/subprocessors, with each one's country and processing task. Changes to that list follow "Changes to the DPA Standard Terms", item (a), below.

Security Policy

The security practices described at queryplusplus.app/security, and the measures in Annex II below.

Provider Security Contact

security@queryplusplus.app

Service Provider Relationship

To the extent California Consumer Privacy Act, Cal. Civ. Code § 1798.100 et seq ("CCPA") applies, the parties acknowledge and agree that Provider is a service provider and is receiving Personal Data from Customer to provide the Service as agreed in the Agreement and detailed below (see Nature and Purpose of Processing), which constitutes a limited and specified business purpose. Provider will not sell or share any Personal Data provided by Customer under the Agreement. In addition, Provider will not retain, use, or disclose any Personal Data provided by Customer under the Agreement except as necessary for providing the Service for Customer, as stated in the Agreement, or as permitted by Applicable Data Protection Laws. Provider certifies that it understands the restrictions of this paragraph and will comply with all Applicable Data Protection Laws. Provider will notify Customer if it can no longer meet its obligations under the CCPA.

Other US state privacy laws: see "Changes to the DPA Standard Terms", item (e), below.

Restricted Transfers

Governing Member State

  • EEA Transfers: Ireland
  • UK Transfers: England and Wales

Annex I(A): List of Parties

Data Exporter

  • Name: Customer, the organization that accepted the Terms
  • Address: as given in Customer's account or billing details
  • Contact person: the owner of Customer's Query++ account, or another contact Customer names to Provider in writing
  • Activities relevant to transfer: see Annex I(B)
  • Role: Controller, or Processor acting for its own controller, as applicable

Data Importer

  • Name: Streama LLC (Provider)
  • Address: 813 Oak St Ste 10 - 1131, Conway, AR 72032
  • Contact person: Founder, privacy@queryplusplus.app
  • Activities relevant to transfer: see Annex I(B)
  • Role: Processor

Annex I(B): Description of Transfer and Processing Activities

Service

Query++, a SQL editor for Salesforce Marketing Cloud Engagement.

Categories of Data Subjects

  • Customer's employees and contractors who use Query++ (Customer's Marketing Cloud Engagement users)
  • Customer's end users or customers: people whose records are in Customer's Marketing Cloud Engagement account, such as subscribers and contacts, when Customer's users query those records

Categories of Personal Data

  • Name
  • Contact information: email address
  • User activity: IP address, browser details and actions taken in Query++, in audit logs and server logs
  • Account identifiers: Marketing Cloud Engagement user, account and business unit ids
  • SQL text, query history and run error messages that Customer saves in Query++, and any personal data Customer includes in them
  • Any personal data in Customer's Marketing Cloud Engagement data that Customer's users choose to query. Provider reads it live from Marketing Cloud Engagement to show it to the user and does not store it

Special Category Data

Is special category data Processed? Yes, but only if Customer's Marketing Cloud Engagement data or saved SQL contains it. Customer decides what data it queries. Provider does not ask for or need special category data.

Special Category Data Restrictions or Safeguards

  • Query results are not stored by Provider
  • SQL text and run error messages are encrypted with a separate key for each customer, protected by AWS Key Management Service
  • Access is limited to Customer's own users and business units
  • See Security Policy and Annex II

Frequency of Transfer

Continuous, whenever Customer's users use Query++.

Nature and Purpose of Processing

Provider will Process Customer Personal Data as instructed in Section 2.3 of the DPA Standard Terms. The nature of processing includes:

  • Receiving data, including collection, accessing and retrieval from Customer's Marketing Cloud Engagement account when Customer's users run queries
  • Holding data, including storage of user accounts, saved SQL, query history and audit logs
  • Using data, including consultation and running the queries Customer's users ask for. No automated decision making or profiling
  • Updating data in Customer's Marketing Cloud Engagement account, by writing query results to the Data Extensions and Query Activities Customer's users choose
  • Protecting data, including restricting access and encrypting
  • Sharing data only with Approved Subprocessors
  • Returning data to Customer, including exports of member data
  • Erasing data, including deletion when Customer deletes its account

The purpose of processing is to provide Query++ to Customer: signing users in through Marketing Cloud Engagement, running the queries Customer's users write against Customer's own Marketing Cloud Engagement account, showing results, saving queries and history, keeping audit logs, securing and supporting the Service, and fixing errors.

Duration of Processing

Provider will process Customer Personal Data as long as required (i) to conduct the Processing activities instructed in Section 2.2(a)-(d) of the Standard Terms; or (ii) by Applicable Laws.

Annex I(C)

Competent Supervisory Authority

The supervisory authority will be the supervisory authority of the data exporter, as determined in accordance with Clause 13 of the EEA SCCs or the relevant provision of the UK Addendum.

Annex II: Technical and Organizational Security Measures

See Security Policy, and the measures below.

  • Pseudonymization and encryption of personal data: SQL text, run error messages and Marketing Cloud Engagement sign-in tokens are encrypted with AES-256-GCM. Each customer has its own encryption keys, protected by AWS Key Management Service. Each encrypted value is bound to its customer, so it can't be decrypted under another customer's keys. Plaintext keys are held only in server memory, for at most 20 minutes.
  • Ensuring ongoing confidentiality, integrity, availability and resilience of processing systems and services: Each customer's data is separated in the database by row-level security on customer and business unit. The application's database account can't bypass it, and production won't start if it can. Requests are rate limited. In production, our servers can only connect out to Marketing Cloud Engagement.
  • Ability to restore availability and access in a timely manner after an incident: The database is backed up continuously by our hosting provider, with point-in-time recovery for the last 3 days.
  • Regular testing, assessment and evaluation of security measures: Every code change is scanned for known vulnerable dependencies, leaked secrets and insecure code patterns. Dependencies are also scanned weekly. The application has been tested with an authenticated web security scanner.
  • User identification and authorization: Users sign in through their Marketing Cloud Engagement account. Each Marketing Cloud Engagement call uses the signed-in user's own access, so Marketing Cloud Engagement's own permissions apply. Sessions end after 30 minutes idle or 8 hours in total. Staff access to internal tools needs a named account and two-factor authentication. Sign-up for staff accounts is turned off.
  • Protecting data in transit: All traffic uses TLS. HTTP Strict Transport Security is on for the app and its APIs.
  • Protecting data at rest: Our hosting provider encrypts the database and its backups at rest. The application adds its own encryption, described above.
  • Physical security: Provider has no data centers or offices that hold Customer Personal Data. Data is held at Render and AWS, which hold SOC 2 reports covering physical security.
  • Events logging: An audit log records sign-ins, role and seat changes, saved query changes, folder and sharing changes, Query Activity changes, data exports and billing events, with time, user, and for actions taken by people, IP address and browser. It is kept for 365 days and Customer can export it. Server logs remove SQL, tokens and other secrets before they are written and are kept for 14 days. Staff actions in internal tools are logged separately.
  • Systems configuration, including default configuration: Security headers and a strict Content Security Policy are set on every service. The app can only be embedded in Marketing Cloud Engagement. Production refuses to start with development encryption keys.
  • Certification or assurance of processes and products: Provider holds no certifications yet. Our main subprocessors hold their own, listed on our Subprocessors page.
  • Ensuring data minimization: Query results are shown to the user and never stored by Provider. Error reports keep only an internal user id, with no names, email addresses, IP addresses or SQL.
  • Ensuring data quality: Users' names and email addresses are refreshed from Marketing Cloud Engagement each time they sign in.
  • Ensuring limited data retention: Audit logs: 365 days. Server logs: 14 days. Error reports: 30 days. Temporary tables Query++ creates in Customer's Marketing Cloud Engagement account are deleted by Marketing Cloud Engagement after 1 day (30 days for per-query placeholder tables). All other Customer Personal Data is deleted within 30 days after Customer's account is deleted.
  • Ensuring accountability: Staff actions are logged. Staff who can access Customer Personal Data are bound by confidentiality.
  • Allowing data portability and ensuring erasure: Account owners and admins can download a copy of a member's data from Query++ settings. When an account is deleted, its encryption keys are deleted too, so any copies left in backups can no longer be read.

Changes to the DPA Standard Terms

The following change the DPA Standard Terms. Where they conflict with the DPA Standard Terms, they control.

(a) Changes to Approved Subprocessors. In Section 2.6(a) of the DPA Standard Terms, and in Clause 9 of the EEA SCCs as completed by Section 3.2(c)(ii), "10 business days" is replaced with "30 days". Provider will give notice by email to the owner of Customer's Query++ account and to anyone who has subscribed to subprocessor updates, and will update the Approved Subprocessors list. If Customer objects on reasonable data protection grounds within 30 days of notice, and the parties can't resolve the objection in good faith, Customer may end the Agreement by written notice, and Provider will refund any prepaid fees for the period after it ends. If Provider must replace a Subprocessor urgently, for example because a Subprocessor fails or for security reasons, Provider may do so with shorter notice. Provider will then notify Customer as soon as possible, and Customer's right to object and to a refund still applies.

(b) Audits. Provider does not yet hold a Report. Until it does, Section 5.2 of the DPA Standard Terms does not apply, and Provider meets its information duties through Section 5.3, the Security Policy and this DPA. Provider will list any Report it obtains on its Security Policy page. Section 5.1 does not limit any audit right that the EEA SCCs or UK Addendum give Customer. Customer will exercise any such right as follows: Customer first asks for information under Section 5.3. If the answers don't reasonably show compliance, Customer may audit, on 30 days' written notice, during business hours, no more than once a year, under a confidentiality agreement, without unreasonably disrupting Provider's operations, and at Customer's own cost. An auditor acting for Customer must not be a competitor of Provider. The once-a-year limit does not apply after a Security Incident affecting Customer Personal Data, or when a supervisory authority requires the audit.

(c) Deletion. Customer gives the instruction to delete under Section 7 of the DPA Standard Terms when the owner of Customer's Query++ account asks Provider to delete the account, as described in the Agreement. Before deletion, Customer may ask for a copy of its data. Provider will then delete all Customer Personal Data within 30 days, unless Applicable Laws require Provider to keep it. Encrypted copies in backups become unreadable when the account's encryption keys are deleted, and are removed within 7 days. Provider will confirm deletion in writing on request.

(d) Personnel. Provider will ensure that everyone it authorizes to Process Customer Personal Data has committed to confidentiality or is under an appropriate legal duty of confidentiality.

(e) US state privacy laws. Where the CCPA or another US state privacy law applies to Customer Personal Data, Provider acts as Customer's service provider, contractor or processor under that law. In addition to the Service Provider Relationship terms above, Provider will:

  1. not combine Customer Personal Data with personal data it receives from anyone else or collects itself, except as those laws allow;
  2. not use Customer Personal Data for any commercial purpose other than the purposes in Annex I(B), or outside its direct business relationship with Customer;
  3. give Customer Personal Data the same level of privacy protection those laws require of Customer;
  4. let Customer take reasonable and appropriate steps to confirm that Provider uses Customer Personal Data in line with those laws, and, after notice, to stop and fix any unauthorized use;
  5. help Customer respond to consumer requests under those laws, taking into account the nature of the Processing;
  6. bind each Subprocessor by written contract to the same obligations; and
  7. delete or return Customer Personal Data when the Service ends, as described in item (c).

Any right those laws give Customer to assess Provider's compliance is exercised as described in item (b).

(f) Switzerland. For transfers subject to the Swiss Federal Act on Data Protection, the EEA SCCs apply as adjusted by Section 3.4 of the DPA Standard Terms, and also as follows. The Swiss Federal Data Protection and Information Commissioner is the competent supervisory authority, alongside any EEA supervisory authority where the GDPR also applies. The term "Member State" in the EEA SCCs does not prevent data subjects in Switzerland from bringing claims in their place of habitual residence under Clause 18(c).

Acceptance

Provider and Customer have not changed the DPA Standard Terms except as set out on this Cover Page. This DPA takes effect when Customer accepts the Query++ Terms of Service, and lasts as long as the Agreement, as described in Section 10 of the DPA Standard Terms. Accepting the Terms has the same effect as signing this Cover Page. For a countersigned copy, email privacy@queryplusplus.app.


Based on the Common Paper Data Processing Agreement (Version 1.1), free to use under CC BY 4.0. We completed and adapted the Cover Page. The DPA Standard Terms are unchanged.