Privacy Policy
01 What This Policy Covers
This single policy applies to three surfaces:
- The JASS Query website — the marketing pages at
jassquery.com, including this page, the product pages, and any form submissions on them. - QueryVault — our free browser extension for saving Keepa Product Finder queries (Chrome and Edge).
- QueryForge — our SaaS service for scheduling and running Keepa Product Finder queries on your behalf and delivering results to your chosen cloud storage.
Where a section applies only to one surface, it is tagged with a colored pill at the top of that section.
02 The JASS Query Website Website
What we collect
Essentially nothing directly. We do not set advertising cookies, we do not run third-party analytics, and we do not embed tracking pixels or advertising scripts. The only information we actively collect on the marketing site is what you voluntarily submit through a form — for example, a product signup or a contact message.
Hosting and request logs
Our website is hosted by us on Microsoft Azure (see §09 for location). As part of normal web-server operation we maintain standard request logs (IP address, timestamp, user agent, requested URL) for security, abuse prevention, and basic traffic statistics. We do not access or analyze these logs for marketing purposes, and we do not share them with third parties except where required by law or to defend against an abuse incident.
Fonts
The site loads web fonts (Syne and DM Sans) from Google Fonts. When you view the site, your browser requests the font files from fonts.googleapis.com. Google may log these requests per its own privacy policy. No other data is sent to Google from the marketing site.
Cookies
The marketing site does not set tracking or advertising cookies. It may set a small number of strictly-necessary cookies required to remember your display preferences (for example, light/dark theme). These are stored in your browser only.
03 QueryVault (Browser Extension) QueryVault
What QueryVault stores locally in your browser
- Saved Keepa Product Finder query configurations (form field names and values)
- Query metadata (names, creation/update timestamps, favorite status)
- Extension preferences (license expiration date, UI preferences)
- If you choose to register for the optional free upgraded tier: your name and email address, submitted to us for account creation
What QueryVault does NOT do
QueryVault does not collect, store, or transmit your browsing history, cookies, or activity on any website other than Keepa Product Finder pages that you actively interact with. It runs no analytics, no telemetry, and no usage tracking.
External network requests
QueryVault is local-first. The only outbound network requests the extension makes are:
- If you choose to register for the free upgraded tier, your name and email address are transmitted via HTTPS directly to our own servers and stored in our backend system, hosted on Microsoft Azure and subject to the same security measures described in this policy. We use this information to create and recognize your registration and to contact you about the products you registered for. The data is not handed to any third-party form or delivery service.
- If you are signed in with a paid or registered account, the extension may periodically verify your license status with our servers.
- During license activation (comped or internal access only), an email address is entered to validate a license key. This email is used solely for cryptographic validation within the browser and is immediately discarded — it is never saved, stored, or transmitted anywhere.
- Interactions you initiate with Keepa (for example, running a saved query) go directly from your browser to Keepa, as if you had filled out the form manually.
We do not sell or rent any information transmitted to us, and we do not share it with third parties for advertising.
How the stored data is used
Your saved queries are used exclusively to:
- Store your Keepa Product Finder search configurations on your device
- Restore saved configurations when you load a query on a Keepa page
Storage technology
Query definitions are stored locally in your browser using the browser's built-in Extension Storage API (chrome.storage.local). This data stays on your device; QueryVault does not write it to Chrome Sync or any other cross-device storage.
Chrome Web Store Limited Use disclosure. QueryVault's use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. We do not transfer or sell user data to third parties for advertising, analytics, or unrelated purposes; do not use user data to determine creditworthiness or for lending; and do not allow humans to read user data except as necessary for security, to comply with applicable law, for operations where we have user consent, or where data has been aggregated and de-identified.
04 QueryForge (SaaS Service) QueryForge
What QueryForge does
QueryForge is a subscription service that runs Keepa Product Finder queries on a schedule you define and delivers the resulting CSV files to a cloud storage location you own and control (Google Drive, Microsoft OneDrive, or Azure Blob Storage). Your account, queries, and run history are hosted by us in Microsoft Azure.
Account and authentication data
When you create a QueryForge account, we collect:
- Identity. Your name, email address, and a unique user identifier supplied by our identity provider (Microsoft Entra External ID). Entra supports sign-in via Google, Amazon, or email/password — the details of that sign-in flow are governed by your chosen provider and by Microsoft.
- Account metadata. A generated account ID, your subscription tier, billing status, and a small set of preferences (for example, notification settings).
We do not receive or store your identity-provider password. We never see your Google/Amazon/Microsoft account password.
Query and run data
- Query definitions. The Keepa Product Finder parameters you save (the same form-field values you could fill out manually on Keepa).
- Schedules. The cadence and timing you assign to each query.
- Run history. A record of each scheduled execution: timestamps, result counts, status, and any errors encountered. This is retained to show you your history and to support credit accounting.
We do not retain a copy of your result CSVs on our servers once they have been delivered to your cloud storage. The authoritative copy of your results lives in your storage, not ours. Delivery logs contain metadata (file name, row count, delivery status) but not row-level content.
Keepa API credentials (BYOK tiers)
If you are on a "bring-your-own-key" (BYOK) tier, you provide your own Keepa API key. The key is stored encrypted at rest in Microsoft Azure Key Vault. It is used only to execute the queries you scheduled, and is decrypted in memory only at the moment a run executes. We never display the key back to you in plaintext after you submit it, and we never share it with any third party.
If you are on a bundled-credits tier, we use our own Keepa credentials to run your queries and deduct credits from your subscription allowance.
Results-storage integration (Google Drive, OneDrive, Azure Blob)
You configure exactly one results-storage channel:
- Google Drive. You authorize QueryForge via Google OAuth using the
drive.filescope. This scope is per-file: QueryForge can only create files in, and manage files in, a folder you specifically choose through Google's picker. It cannot see or access any other file in your Drive. We store the OAuth refresh token encrypted at rest in Azure Key Vault. We use the access this grants solely to write result CSVs to the folder you selected and to read back metadata about the files we wrote (for example, to confirm a file exists). See §05 for our detailed Google user-data handling disclosures. - Microsoft OneDrive. You authorize QueryForge via Microsoft OAuth. The OAuth refresh token is stored encrypted at rest in Azure Key Vault. We use the access solely to write result CSVs to the folder you selected.
- Azure Blob Storage (customer-owned container). You supply a Shared Access Signature (SAS) URL that points at a container in your Azure subscription. We store the SAS URL encrypted at rest in Azure Key Vault and use it only to write result CSVs to that container. We do not receive any credentials for your Azure account beyond that SAS URL, and the SAS URL is scoped to the permissions you granted when you generated it.
In all three cases, you can disconnect the integration at any time from the QueryForge portal. Disconnecting revokes our stored credentials immediately on our side; you should also revoke the grant at the provider (Google Account permissions, Microsoft account permissions, or by rotating the SAS) to be fully thorough. Disconnecting does not delete CSVs that have already been delivered to your storage — those are yours and remain yours.
Billing data
Paid subscriptions are processed by Stripe. When you enter payment information, it is submitted directly to Stripe from your browser; we do not receive or store credit card numbers, CVV codes, or bank account numbers. We receive and store only the billing metadata Stripe returns to us: your customer ID, subscription ID, plan, status, and a token representing your payment method (used only to charge renewals through Stripe). Stripe's handling of your payment information is governed by Stripe's privacy policy.
Transactional email
We send transactional email (account confirmations, run-completion notices, billing receipts, and similar) through Resend. Resend receives your email address and the contents of the message in order to deliver it. Resend is used for transactional email only; any marketing email is governed by the Communications and Marketing section below (§07) and always carries an opt-out.
Diagnostics and logs
We maintain operational logs in Azure Application Insights and related Azure services to monitor the health of QueryForge and to debug issues. These logs may include your account ID, request paths, response codes, and error messages, but do not contain row-level query results or your Keepa API key. Operational logs are retained on a rolling 90-day window unless a longer retention is required to investigate a specific incident.
05 Google User Data (QueryForge + QueryVault) QueryForge
What Google data we access
QueryForge accesses Google user data only when you explicitly connect your Google Drive as your results-storage channel. When you do, you authorize QueryForge via Google OAuth using the drive.file scope. This is a per-file scope: QueryForge receives access only to files it creates in the folder you pick through Google's Drive Picker, plus the folder itself. We cannot see, download, or modify any other file in your Drive.
How we use it
- To write CSV result files for your scheduled queries into the folder you selected.
- To read back metadata about files we have written (for example, to confirm a file was created successfully, to display file details in your run history, or to update a file we previously wrote).
- To list, rename, or delete files within the folder we write to, if you ask us to do so through the QueryForge portal.
We do not use Google user data for any purpose other than providing the user-facing features you asked for.
How we store it
The OAuth refresh token that lets us write to your Drive folder is stored encrypted at rest in Microsoft Azure Key Vault. Access to it is restricted to the QueryForge service workers that execute your scheduled queries. We do not copy or cache Drive file contents on our systems beyond what is strictly necessary to produce and upload the result CSV.
How we share it
We do not transfer Google user data to any third party, except as necessary to provide the QueryForge feature you requested (for example, the Azure infrastructure that runs the service), to comply with applicable law or legal process, or with your explicit consent.
How you remove it
You can disconnect QueryForge from your Google account at any time by (a) removing the integration from the QueryForge portal, which deletes our stored refresh token, and/or (b) revoking QueryForge's access from your Google Account permissions page. Revoking either way stops any further access. CSVs we have already delivered to your Drive folder remain in your Drive under your control — they are your files.
Google API Services User Data Policy — Limited Use disclosure. QueryForge's use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Specifically, we affirm that QueryForge does not:
- transfer Google user data to third parties, except as necessary to provide or improve user-facing features of QueryForge that are prominent in the product's user interface, to comply with applicable law, or as part of a merger, acquisition, or sale of assets with appropriate notice to users;
- use Google user data for serving advertisements, including retargeting, personalized, or interest-based advertising;
- use Google user data to determine creditworthiness or for lending purposes;
- allow humans to read Google user data, except (i) with your explicit affirmative consent for specific messages, (ii) as necessary for security purposes (such as investigating abuse), (iii) to comply with applicable law, or (iv) where the data has been aggregated and de-identified for internal operations.
06 Microsoft User Data (Sign-in and OneDrive) QueryForge
What Microsoft data we access
QueryForge uses Microsoft services in two distinct places, and it is important to keep them separate:
- Sign-in (always). We authenticate every QueryForge user through Microsoft Entra External ID, our identity provider. When you sign in, Microsoft shares a minimum profile (your name, email, and a unique identifier) and issues us a short-lived token. This is not OneDrive access — it only confirms who you are. Entra External ID supports sign-in using Google, Amazon, or email/password; your choice of method is governed by the provider you pick plus Microsoft.
- OneDrive results storage (only if you opt in). If you choose OneDrive as your results-storage channel, you additionally authorize QueryForge via Microsoft OAuth against Microsoft Graph. We request only the scopes needed to read and write files within the folder you designate for QueryForge output.
How we use it
- Sign-in data is used to create and authenticate your QueryForge Account, to show your name and email in the portal, to associate runs and billing with you, and to send you transactional email.
- OneDrive access is used solely to write result CSVs to the folder you designate, to read back metadata about files we have written (for example, to confirm a file exists), and to list, rename, or delete files within that folder when you ask us to from the portal.
We do not use Microsoft data for advertising, for training machine-learning models, or for any purpose other than providing the user-facing features of QueryForge.
How we store it
The OAuth refresh token that lets us write to your OneDrive folder is stored encrypted at rest in Microsoft Azure Key Vault. Sign-in claims (name, email, identity-provider ID) are stored in your QueryForge account record in Azure Cosmos DB. We do not cache OneDrive file contents on our systems beyond what is strictly necessary to produce and upload a result CSV.
How we share it
We do not transfer Microsoft user data to any third party, except as necessary to provide the QueryForge feature you requested (for example, the Azure infrastructure that runs the service), to comply with applicable law or legal process, or with your explicit consent. Sharing Microsoft user data for advertising, resale, or unrelated analytics is not allowed and we do not do it.
How you remove it
You can disconnect QueryForge from your Microsoft account at any time by (a) removing the OneDrive integration from the QueryForge portal, which deletes our stored refresh token, and/or (b) revoking QueryForge's access from your Microsoft Account or, for Entra work/school accounts, your organization's admin "My Apps" page. Revoking either way stops any further access. CSVs we have already delivered to your OneDrive remain in your OneDrive under your control — they are your files. If you delete your QueryForge Account, your sign-in record and any stored tokens are deleted as described in §12.
Publisher identity and consent
QueryForge's Microsoft Entra application is registered under a publisher domain we control (jassquery.com). The consent screen Microsoft shows when you first authorize QueryForge identifies us as the publisher and links to this Privacy Policy and to our Terms of Service, so you can review how we handle your data before granting access.
07 Communications and Marketing
When you give us your contact details — by registering for a QueryVault tier, joining a list, creating a QueryForge account, or contacting us — we use them to operate the Services and to stay in touch with you about JASS Query.
- Service (transactional) messages. We send messages you need in order to use the Services: account confirmations, security and account notices, run-completion notices, billing receipts, and policy or service-change notices. These are not promotional, and you cannot opt out of them while you have an active registration or account, because they are part of the Service.
- Product and marketing messages. We may also contact you about updates and new features, upgrades, and our own complementary products and services that relate to the ones you registered for or use. We do not send third-party advertising, and we do not market other companies' products to you — every marketing message is from JASS Query, about JASS Query. You can opt out at any time using the unsubscribe link in any such message or by emailing privacy@jassquery.com, and we will stop sending marketing email promptly. Opting out of marketing does not stop the service messages above.
Where the law requires consent for marketing email (for example, in parts of the European Economic Area and the United Kingdom), we rely on your consent or on the "soft opt-in" available for our own similar products, and you may withdraw consent at any time.
08 Legal Basis for Processing (GDPR)
If you are located in the European Economic Area, the United Kingdom, or Switzerland, we rely on the following legal bases under the GDPR / UK GDPR:
- Contract. Most processing we do (running your queries, storing your account, delivering your CSVs, billing you) is necessary to perform the subscription contract you enter into with us.
- Legitimate interest. Operational logging, fraud and abuse prevention, and securing the service rely on our legitimate interest in running a safe and reliable product, balanced against your privacy interests.
- Consent. If we ever ask you to receive marketing communications, or otherwise process data where consent is required, we rely on your consent, and you may withdraw it at any time.
- Legal obligation. Where we are required to retain information for tax, accounting, or regulatory purposes.
09 Subprocessors and Third-Party Services
We do not sell or rent your personal information. We use the following subprocessors to operate JASS Query, QueryVault, and QueryForge. Each has signed (or operates under) a data processing agreement or equivalent contractual terms where applicable.
| Subprocessor | Purpose | Data category | Location |
|---|---|---|---|
| Microsoft Azure | Hosting, storage, compute, Key Vault, logging (QueryForge) | All QueryForge account, query, run, credential, and log data | United States |
| Microsoft Entra External ID | Identity provider and authentication (QueryForge) | Name, email, identity-provider ID, tokens | United States |
| Stripe | Subscription billing and payments (QueryForge) | Name, email, billing address, payment method (held by Stripe; not by us) | United States |
| Resend | Transactional email delivery | Email address, message contents | United States |
| Keepa GmbH | Executes the Product Finder queries you scheduled | Query parameters and (on bundled-credit tiers) our own Keepa API key | Germany |
| Google (Drive + OAuth) | Delivers result CSVs to your Drive if you connect Google Drive; also powers Google Fonts on the website | OAuth tokens; file metadata and contents we write to your folder | United States |
| Microsoft (OneDrive + OAuth) | Delivers result CSVs to your OneDrive if you connect OneDrive | OAuth tokens; file metadata and contents we write to your folder | United States |
We will update this list as subprocessors change. Material changes will be reflected in the "Last Updated" date at the top of this page; subscribers on enterprise terms, if any, may also be notified directly.
10 International Data Transfers
JASS Query is operated from the United States and the primary QueryForge infrastructure runs in Microsoft Azure US regions. If you access our products from outside the United States, you acknowledge that your information is transferred to and processed in the United States, and that U.S. law may apply to it. Where required for transfers of personal data out of the European Economic Area, the United Kingdom, or Switzerland, we rely on the European Commission's Standard Contractual Clauses, the UK International Data Transfer Addendum, or equivalent transfer mechanisms with our subprocessors.
11 Your Rights
Depending on where you live, you have some or all of the following rights regarding your personal information:
- Access. Ask what personal information we hold about you and receive a copy.
- Correction. Ask us to correct inaccurate or incomplete information.
- Deletion. Ask us to delete your personal information (subject to legal retention obligations).
- Portability. Receive your personal information in a structured, machine-readable format.
- Restriction or objection. Restrict or object to certain processing (GDPR/UK GDPR).
- Opt out of sale or sharing. Direct us not to "sell" or "share" your personal information under the California Consumer Privacy Act / California Privacy Rights Act (CCPA/CPRA). We do not sell or share your personal information as those terms are defined under CCPA/CPRA, and we have not done so in the preceding twelve months. You may still make this request.
- Limit use of sensitive personal information. Direct us to limit our use of sensitive personal information to what is necessary to provide the service (CCPA/CPRA).
- Non-discrimination. We will not deny service, charge a different price, or provide a different quality of service because you exercised any of these rights.
- Withdraw consent. Where we rely on consent, you may withdraw it at any time without affecting the lawfulness of prior processing.
- Complaint. Lodge a complaint with your local data protection authority (for example, your EU member-state supervisory authority, the UK ICO, or the California Attorney General).
To exercise any of these rights, email privacy@jassquery.com. We will respond within the timeframes required by applicable law (for example, within 30 days under GDPR, or 45 days under CCPA, with extensions only as the law permits). We may need to verify your identity before acting on a request — typically by confirming control of the email address tied to your account.
Authorized agents may submit CCPA/CPRA requests on your behalf with written permission that we are allowed to verify.
12 Data Retention
We keep information only as long as we need it for the purpose it was collected for, or as required by law. In practice:
- QueryVault local data. Persists in your browser until you delete it or uninstall the extension. We have no copy and cannot remotely access or delete it. If you opted into the registered tier, the name/email you submitted through QueryVault is retained in our backend system so we can recognize your registration and contact you about the products you registered for, until you ask us to delete it.
- QueryForge account data. Retained while your account is active and for up to 90 days after cancellation so you can reactivate without losing your query history. After that window, your account is archived. Archived account data — including your account metadata, query definitions, schedules, run history, and integration credentials — is retained until you submit a deletion request to privacy@jassquery.com. We will delete or anonymize your archived data within 30 days of receiving a completed request, except where we are required to retain specific records for billing, tax, or legal purposes. There is no self-service account-deletion button in the current version of the product; the portal surfaces a Request Data Deletion link that opens a support email to that address.
- QueryForge run history. Retained for the life of the account, subject to reasonable storage limits per tier. You can delete individual run records from the portal.
- Result CSVs. We do not retain copies on our servers after delivery. The copies in your cloud storage are controlled by you.
- Keepa API keys and OAuth tokens. Retained in Azure Key Vault until you disconnect the integration or delete your account, at which point they are deleted (subject to the vault's soft-delete period).
- Operational logs. Typically retained for up to 90 days, longer only where needed to investigate a specific incident.
- Billing records. Retained for at least seven (7) years to meet U.S. tax and accounting obligations, regardless of account closure.
- Marketing signup data. Retained until you ask us to remove it or the list is retired.
13 Security
We take the security of your information seriously, and in particular, of the OAuth tokens, SAS URLs, and Keepa API keys you entrust to us. We apply the following measures:
- All traffic to and from our services is encrypted in transit using TLS 1.2 or higher.
- Secrets (OAuth tokens, SAS URLs, Keepa API keys, webhook signing secrets) are stored encrypted at rest in Microsoft Azure Key Vault. Application code fetches them at the moment they are needed and does not write them to logs.
- Application data (accounts, queries, run history) is stored in Azure Cosmos DB and Azure Table/Blob Storage, encrypted at rest with Microsoft-managed keys.
- Access to production systems is restricted to authorized personnel and authenticated via Microsoft Entra with multi-factor authentication.
- We log security-relevant events and monitor them for anomalies.
No system is perfectly secure. If we learn of a personal-data breach that affects you, we will notify you as soon as reasonably possible and in any event within the timeframes required by applicable law (for example, within 72 hours of awareness where GDPR applies).
14 Third-Party Sites and Integrations
Our products and website may link to third-party sites (for example, Keepa, Stripe's billing portal, or the Google and Microsoft account pages). We are not responsible for the privacy practices of those third parties. Once you leave our site or enter a third-party integration flow, that third party's privacy policy applies.
15 Children's Privacy
Our products and website are designed for Amazon resellers running a business. They are not directed to children. We do not knowingly collect personal information from children under 13 (or under the equivalent age in your jurisdiction — for example, 16 in parts of the EU). If you believe we have inadvertently collected information from a child, contact privacy@jassquery.com and we will delete it.
16 "Do Not Track" and Global Privacy Control
Because we do not engage in cross-context behavioral advertising and do not sell or share personal information for advertising purposes, we do not respond differently to browser Do-Not-Track signals. Where required, we honor the Global Privacy Control (GPC) signal as an opt-out request for California consumers.
17 Changes to This Policy
We may update this policy from time to time — for example, when we add or change a subprocessor, launch a new feature that handles data differently, or adapt to new legal requirements. Changes will be reflected in the "Last Updated" date at the top of this page. Material changes will be highlighted or emailed to account holders. Continued use of our products or website after the effective date of a change constitutes acceptance of the updated policy.
18 Jurisdiction
JASS Query is operated by JASS Pet Services LLC d/b/a JASS Query, a limited liability company organized in the United States. This policy is written to comply with applicable U.S. privacy laws and, where relevant, with the GDPR / UK GDPR. If you are accessing our products or website from outside the United States, you acknowledge that any information you provide is transmitted to and processed in the United States.
19 Contact
For privacy questions, data-access or deletion requests, or to exercise any of the rights described in §11:
- Email (privacy): privacy@jassquery.com
- Email (general support, as a fallback): help@jassquery.com