Effective date: May 18, 2026 · Last updated: November 21, 2026
This Privacy Policy describes how Quiriz ("we," "us," or "our") collects, uses, stores, and shares information when you use the Quiriz platform at quiriz.co (the "Service"). Quiriz is operated by Quiriz Systems Inc., a British Columbia corporation, 16469 109A Avenue, Surrey, BC V4N 5B7, Canada, which is responsible for the personal information described in this Policy. By using the Service, you agree to the practices described in this Policy.
We may update this Policy from time to time. We will post the revised Policy with a new effective date. Continued use of the Service after changes are posted constitutes your acceptance of the updated Policy.
We collect information in the following categories:
| Category | Examples | Source |
|---|---|---|
| Account information | Name, email address, authentication credentials | Provided by you at registration (via Clerk) |
| User Data | Datasets, CSV/Excel files, and other content you upload | Provided by you |
| Usage data | Pages visited, features used, queries submitted, report history | Automatically collected |
| Third-party integration data | Google account tokens, Microsoft account tokens, email metadata; for connectors (HubSpot, Google Ads, Google Search Console, Google Analytics, Meta Ads, Shopify, QuickBooks, Stripe), the account name and the records or reports you choose to import | Collected when you authorize integrations |
| Technical data | IP address, browser type, device information, error logs | Automatically collected |
We use collected information to:
We do not use your User Data to train AI models, and we do not sell your personal information to third parties.
All data collected and processed by Quiriz is stored on servers located in the United States, hosted through Render (render.com), a US-based cloud infrastructure provider. Every sub-processor listed in Section 6 processes data in the United States. Optional chat integrations you turn on yourself (Section 7) are the exception: they carry your questions and answers to the chat service you chose, which may process them elsewhere.
By using the Service, you acknowledge and consent that your data will be transferred to, stored in, and processed in the United States. The United States may have data protection laws that differ from those in your country. Your use of the Service is subject to applicable US federal and state law.
Quiriz does not currently maintain data residency options outside the United States. If your jurisdiction requires data to be stored locally, you should not use the Service.
Quiriz is a general-purpose data analysis platform. It is expressly not designed, audited, or compliant with the following regulatory frameworks:
You must not upload datasets containing any of the following:
If you upload such data, you do so in breach of our Terms of Service and solely at your own risk. Quiriz accepts no liability for any harm resulting from your upload of sensitive or regulated data.
We share data with trusted third-party sub-processors only as necessary to operate the Service. These include:
| Provider | Purpose | Location |
|---|---|---|
| Render | Cloud infrastructure and database hosting | United States |
| Clerk | User authentication and account management | United States |
| OpenRouter / AI model providers | AI inference for data analysis and report generation | United States |
| OAuth authentication and optional Google Drive / Google Sheets, Google Ads, Google Search Console and Google Analytics integrations | United States | |
| Microsoft | OAuth authentication and optional OneDrive integration | United States |
| Nango | Connector sign-in: stores the access tokens for the HubSpot, Google, Meta, Shopify, QuickBooks and Stripe connections you make and relays Quiriz's read requests to those services; it does not log the data those requests return | United States |
| HubSpot | Optional CRM connector: source of the deals, contacts and companies you choose to import | United States |
| Resend | Delivery of scheduled reports, notifications, and system email | United States |
| PostHog | Product analytics — usage events and page views, plus anonymized session recordings of the homepage and demo page (typed text masked); not dataset contents | United States |
| Google Analytics | Website traffic and advertising measurement — page views and sign-up events, not dataset contents or email addresses | United States |
| Discord | Internal error alerts to the Quiriz team — the error type, location and a short excerpt of the error message, which can occasionally include a fragment of the data being processed | United States |
Each sub-processor is bound by data protection agreements consistent with applicable law. We do not authorize sub-processors to use your data for their own purposes.
If you choose to connect a Google or Microsoft account, we will request only the permissions necessary for the features you activate (such as reading a Google Drive or Google Sheets file you select for ingestion). OAuth tokens are stored securely and used solely to perform the actions you authorize.
Connectors. A company admin can connect HubSpot, Google Ads, Google Search Console, Google Analytics, Meta Ads, Shopify, QuickBooks or Stripe. Quiriz then reads the data you choose (for HubSpot: deals, contacts and companies; for Google Ads: the reporting data of one ad account you pick; for Google Search Console: the search performance of one site you pick; for Google Analytics: the reports of one GA4 property you pick; for Meta Ads: the reporting data of one ad account you pick (campaigns, ad sets and ads, with spend, impressions, clicks, purchases and leads); for Shopify: the orders, refunds, products and customer purchase totals of one store, without customer names, emails, phone numbers or addresses; for QuickBooks: the profit and loss, balance sheet, general ledger and open invoices and bills of one company; for Stripe: the payments, refunds, fees, payouts, invoices, subscriptions and customer names and countries of one Stripe account, without emails, phone numbers, addresses or card numbers) and stores it as datasets in your company's workspace, refreshed once a day. Connectors only read: Quiriz never creates, edits or deletes anything in HubSpot, Google, Meta, Shopify, QuickBooks or Stripe. The sign-in tokens for these connections are held by our sub-processor Nango, not in Quiriz's own database. When you disconnect, Quiriz deletes the connection and stops the daily refresh; you choose whether the imported datasets are kept or deleted.
Chat integrations. A user can choose to ask Quiriz questions from Slack or, through Mobile Chat, from Telegram. When a user turns one on, the questions they send and the answers Quiriz returns, which can include figures from your company's datasets, pass through that chat service and are stored there under its own terms. Slack processes data in the United States; Telegram processes data outside the United States. These integrations are off until a user links them, and a user can unlink them at any time.
You may revoke these permissions at any time through your Quiriz account settings or through your Google, Microsoft or HubSpot account settings, or your Facebook settings (Settings & privacy → Business integrations). Revoking access will disable the corresponding features but will not affect your other data on Quiriz.
When you connect a Google account, Quiriz requests the following Google API scopes only for the features you choose to use:
| Scope | Why Quiriz requests it |
|---|---|
| Google Drive — read-only ( drive.readonly) |
To let you import spreadsheets and files from your Google Drive into Quiriz as datasets. |
| Google Ads ( adwords) |
To import reporting data from the one Google Ads account you choose (campaigns, ad groups and keywords, with their impressions, clicks, cost and conversions) into your Quiriz workspace as datasets, refreshed daily, and to list the ad accounts your Google sign-in can reach so you can pick one. Quiriz only reads reporting data: it never creates, changes or pauses campaigns, ads, budgets or bids, although Google grants this scope as read and write. |
| Google Search Console — read-only ( webmasters.readonly) |
To import search performance data (clicks, impressions, click-through rate and average position by day, search query and page) for the one Search Console site you choose into your Quiriz workspace as datasets, refreshed daily, and to list the sites your Google sign-in can reach so you can pick one. |
| Google Analytics — read-only ( analytics.readonly) |
To import reports (sessions, users, engagement, key events and revenue by day, channel and landing page) for the one Google Analytics 4 property you choose into your Quiriz workspace as datasets, refreshed daily, and to list the properties your Google sign-in can reach so you can pick one. |
Separately, the Quiriz Editor add-ons — Quiriz for Google Sheets™, Quiriz Presentations (Google Slides™) and Quiriz Documents (Google Docs™) — are Google Workspace Marketplace Editor add-ons. Each requests the following Apps Script scopes, granted when you install that add-on. Every add-on requests only the per-file scope for its own host application, and never the per-file scope of the other two:
| Scope | Why Quiriz requests it |
|---|---|
| See and edit only the current spreadsheet ( spreadsheets.currentonly) |
Quiriz for Google Sheets™ only. To read the cells of the active
spreadsheet so the =QUIRIZ() function can answer your question in-cell, and so
you can push the active sheet into Quiriz as a dataset. This per-file scope never accesses
any other file in your Drive. |
| See and edit only the current presentation ( presentations.currentonly) |
Quiriz Presentations only. To insert the answer to your question onto the slide you have open — as a chart image, a table or a note — and to re-read those objects Quiriz itself inserted so they can be refreshed in place. This per-file scope never accesses any other file in your Drive. |
| See and edit only the current document ( documents.currentonly) |
Quiriz Documents only. To insert the answer to your question into the document you have open — as a chart image, a table or a written analysis — and to re-read those objects Quiriz itself inserted so they can be refreshed in place. This per-file scope never accesses any other file in your Drive. |
| Connect to an external service ( script.external_request) |
To send your question, and the rows needed to answer it, to the Quiriz API at app.quiriz.co and return the answer. No other endpoints are contacted. |
| Display a sidebar and menu ( script.container.ui) |
To render the Quiriz menu and the sidebar used for API-key entry, for typing your question, and for the insert and refresh controls. |
Limited Use. Quiriz's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Specifically, data obtained from Google APIs (including Google Ads, Google Search Console and Google Analytics reporting data and Google Drive, Google Sheets, Google Slides and Google Docs content):
You can review and revoke Quiriz's access to your Google account at any time at myaccount.google.com/permissions.
Who receives Google user data. Google Ads, Google Analytics and Google Search Console data, and answers derived from it, are shared only as needed to run the features you use:
Quiriz never sells Google user data or shares it with advertisers, ad networks, data brokers or any other party.
How Google user data is protected. It travels only over encrypted connections (HTTPS/TLS) and is stored in databases encrypted at rest. The Google sign-in token is held by Nango, not in Quiriz's database. Every query is limited to the datasets of the signed-in user's own company, and only a company admin can connect or disconnect a Google account. Access to production systems is limited to authorized Quiriz personnel using individual accounts.
How long Quiriz keeps Google user data, and how to delete it. Imported Google data is kept as datasets while the connection is active, and each daily refresh replaces it with the latest reporting window (13 months for Google Ads and Google Analytics, 16 months for Search Console). Disconnecting a Google connector deletes the stored token at once; choosing Disconnect and delete the datasets also deletes the imported data at once (see 7c). Revoking Quiriz at myaccount.google.com/permissions stops all further access. If you delete your account, or email privacy@quiriz.co, we delete your Google user data within 30 days.
When a company admin connects Meta Ads, Quiriz requests one read-only permission. Quiriz uses data from Meta only to show the connected company its own advertising reports, never sells it, never uses it for advertising, never uses it to train AI models, and follows the Meta Platform Terms.
| Permission | Why Quiriz requests it |
|---|---|
| Meta Ads — read-only ( ads_read) |
To import reporting data from the one Meta ad account you choose into your Quiriz workspace as datasets, refreshed daily, and to list the ad accounts your Facebook login can reach so you can pick one. |
To delete data Quiriz imported through a connector, a company admin opens Manage Connections, chooses Disconnect on that connector, then Disconnect and delete the datasets. Disconnecting also deletes the stored sign-in token at our sub-processor Nango.
To delete all your Quiriz data, or if you removed Quiriz from your Facebook or Google settings and want the imported data deleted, email privacy@quiriz.co from your account's email address. We confirm and complete the deletion within 30 days.
When a company admin connects a Shopify store, Quiriz requests read-only access to orders (including order history older than 60 days), products, inventory and customers. Quiriz imports order amounts, line items, refunds, products and each customer's id, order count and total spent. It never imports customer names, email addresses, phone numbers or addresses, never changes anything in the store, and uses the data only to show the connected company its own reports.
When a store uninstalls Quiriz, Shopify notifies Quiriz 48 hours later, and Quiriz then deletes that store's connection and the datasets imported from it.
When a company admin connects QuickBooks Online, Intuit's sign-in asks the admin to choose one company and grant accounting access (Intuit offers no read-only option). Quiriz only reads: it imports that company's profit and loss and balance sheet by month, its general ledger lines for the current and two prior fiscal years, and its open invoices and bills. These records include customer and vendor names, document numbers and transaction memos. Quiriz does not import payroll, employee or bank sign-in data, never changes anything in QuickBooks, and uses the data only to show the connected company its own reports.
Disconnecting in Quiriz, or from the Apps page in QuickBooks, stops the daily refresh. The imported datasets are kept or deleted as described in section 7c.
When a company admin installs the Quiriz app on a Stripe account, Stripe's install screen lists the read-only permissions Quiriz asks for. Quiriz imports that account's balance transactions (charges, refunds, disputes, fees and payouts), charges including failed attempts, invoices, subscriptions and prices, and each customer's name and country. It never imports customer emails, phone numbers, addresses, card numbers or bank details, never changes anything in Stripe, and uses the data only to show the connected company its own reports. Quiriz removes email addresses from transaction descriptions before storing them.
Disconnecting in Quiriz stops the daily refresh and removes Quiriz's access. The app stays listed under the account's installed apps until it is uninstalled there. The imported datasets are kept or deleted as described in section 7c.
When a company admin connects PostHog, the sign-in screen lists the read-only permissions Quiriz asks for: running queries, and listing the organizations and projects the admin belongs to. Quiriz reads daily totals only: sessions, page views, bounces, signups and other event counts by day, channel, page, country and device, the number of distinct people active in each period, and signup-week cohort counts (how many people activated or came back). It never imports individual events, person identifiers, email addresses, IP addresses or person properties, never changes anything in PostHog, and uses the data only to show the connected company its own reports. The admin chooses which event names count as signup, activation and paid events; event names are stored as part of the connection settings.
Disconnecting in Quiriz stops the daily refresh and removes Quiriz's access. The imported datasets are kept or deleted as described in section 7c.
When a company admin connects Bing Webmaster Tools, the admin pastes an API key generated in their own Bing Webmaster Tools account and chooses one verified site. Quiriz stores the key encrypted and uses it only to read statistics for that site: clicks and impressions by day, the search queries and page addresses Bing already aggregates by week, average positions, and crawl counts. It reads nothing about individual visitors, never submits or changes anything in Bing Webmaster Tools, and uses the data only to show the connected company its own reports. Quiriz keeps the statistics it has received for up to 25 months so history can grow beyond what Bing still shows.
Disconnecting in Quiriz stops the daily refresh and deletes the stored key. The imported datasets are kept or deleted as described in section 7c. The admin can also generate a new key in Bing Webmaster Tools at any time, which stops the old one from working.
When a company admin connects Klaviyo, the admin creates a read-only private API key in their own Klaviyo account with access to account details, campaigns, flows and metrics only, and pastes it into the connection screen of Quiriz's connection provider. Quiriz reads totals only: email and SMS sends, unique opens and clicks, unsubscribes, bounces and spam complaints, subscribes and unsubscribes by day, and the orders and revenue Klaviyo attributes to each campaign, flow and channel. It never reads customer profiles, email addresses, phone numbers or message content, never changes anything in Klaviyo, and uses the data only to show the connected company its own reports. The admin can delete the key in Klaviyo at any time, which stops the connection.
Disconnecting in Quiriz stops the daily refresh and removes the stored key. The imported datasets are kept or deleted as described in section 7c.
When a company admin connects Harvest, the admin signs in to Harvest through Quiriz's connection provider (OAuth) and chooses the Harvest account to connect. Harvest does not offer a read-only permission, so reading only is Quiriz's own commitment: Quiriz never creates, changes or deletes anything in Harvest. Quiriz reads the names of people, clients and projects, hours tracked by day and task, billing and cost rates (used only to compute billable and unbilled totals, and cost and margin totals by client and project, never by person; individual rates are not stored), weekly capacity, invoice and expense amounts and dates, and project budgets. It never imports time-entry or expense notes or receipts, and uses the data only to show the connected company its own reports. The admin can remove Quiriz from their Harvest ID account at any time, which stops the connection.
Disconnecting in Quiriz stops the daily refresh and removes the stored sign-in. The imported datasets are kept or deleted as described in section 7c.
When a company admin connects a WooCommerce store, the admin creates a read-only REST API key in their own store and enters it, with the store's address, in the connection screen of Quiriz's connection provider. Quiriz reads orders, refunds and products: order dates, statuses, amounts, coupons, shipping and taxes, products and quantities, prices and stock, and each order's billing country. It never keeps customer names, email addresses, phone numbers, street addresses or refund reasons, and never changes anything in the store. To count returning shoppers who check out as guests, Quiriz turns each shopper's email address into a one-way code while it reads the order and keeps only that code: the email itself is never stored, and the code cannot be turned back into an email or matched to another store. The data is used only to show the connected company its own reports.
Disconnecting in Quiriz stops the daily refresh and removes the stored key. The imported datasets are kept or deleted as described in section 7c. The admin can also delete the key in WooCommerce at any time, which stops the connection.
When a company admin connects GitHub, the admin installs the Quiriz GitHub App on the repositories they choose. The app asks for read-only repository permissions: metadata, pull requests, and contents (used only to read commit history). Quiriz reads repository names, pull request titles, file paths, GitHub usernames and git author names, and counts and timestamps. It never stores code, diffs, pull request descriptions, commit messages or email addresses, and never changes anything in GitHub. Pull request titles, the first line of commits pushed directly to the main branch, and file paths are sent to Quiriz's AI provider to label the type of change. The data is used only to show the connected company its own reports.
Disconnecting in Quiriz stops the daily refresh and removes the stored connection. The imported datasets are kept or deleted as described in section 7c. The admin can also uninstall the app on GitHub at any time, which stops access.
Files you upload are held only while Quiriz converts them into structured data, then the source file is deleted. Quiriz keeps the converted data, a small data sample, and basic metadata such as the file name. Your original file is never placed in third-party cloud storage.
We retain your account information and User Data for as long as your account is active. If you delete your account, we will delete your personal information and User Data within 30 days, except where retention is required by applicable law or for the resolution of disputes.
Certain anonymized or aggregated usage statistics may be retained indefinitely as they do not identify you personally.
We implement industry-standard technical and organizational measures to protect your data against unauthorized access, disclosure, alteration, or destruction. These include encrypted data transmission (HTTPS/TLS), access controls, and regular security reviews.
However, no method of transmission over the Internet or electronic storage is 100% secure. We cannot guarantee absolute security. You are responsible for maintaining the security of your account credentials and for the data you choose to upload.
Quiriz may occasionally receive a request from a government, law enforcement agency or court for data we hold on your behalf. We handle every such request as follows:
Data obtained through third-party integrations (section 7), including Meta Platform Data and Google user data, is handled the same way.
Depending on your jurisdiction, you may have rights regarding your personal data, including:
To exercise any of these rights, contact us at privacy@quiriz.co. We will respond within 30 days. We may need to verify your identity before fulfilling any request.
The Service is not directed to children under the age of 13. We do not knowingly collect personal information from children under 13. If you believe a child has provided us with personal information, please contact us at privacy@quiriz.co and we will delete it promptly.
Quiriz is operated by a corporation incorporated in British Columbia, Canada. All data is stored and processed on servers located in the United States. By using the Service, you consent to your data being transferred to and processed in the United States. Data protection laws in the United States may differ from those in Canada or your country of residence.
Canadian users: the Service is subject to applicable Canadian federal privacy law (PIPEDA and any applicable provincial equivalents). By using the Service, you consent to the collection, use, and disclosure of your personal information as described in this Policy.
Users in the European Economic Area (EEA), United Kingdom, or other jurisdictions with heightened data protection requirements: our Data Processing Agreement forms part of the Terms of Service and covers transfers to the United States with the EU Standard Contractual Clauses and the UK Addendum. Quiriz does not maintain EU-specific data residency.
The Service uses session cookies and local storage to maintain your login state and preferences. We use PostHog for privacy-friendly product analytics (aggregate usage and page views); it is configured to store its identifier in your browser's local storage rather than in cookies.
On our homepage and on the public demo page we also use PostHog to record anonymized sessions (clicks, scrolling and page changes) so we can see where visitors get stuck and improve those pages. Text you type into fields on those pages is masked in the recordings. The questions you type into the demo are stored with the visit, so we can improve our sample questions. Sessions are never recorded on signed-in pages or in the upload demo, where you try Quiriz with your own file. We do not record sessions for visitors in the European Economic Area, the United Kingdom, Switzerland or Canada. Recordings use your browser's local storage, not cookies.
We also use Google Analytics to measure website traffic and the performance of our
advertising, including Google Ads. Google Analytics sets cookies on quiriz.co and
app.quiriz.co (such as _ga) that recognize a returning browser; it does not
receive your email address or the contents of your datasets. In the European Economic Area,
the United Kingdom, Switzerland and Quebec, these cookies are off: Google receives only
cookieless measurement signals. You can block Google Analytics with your browser's cookie
settings or Google's
opt-out add-on.
Browser telemetry may be collected for performance monitoring and error diagnosis.
For privacy-related questions or to exercise your data rights, contact us at:
privacy@quiriz.co
For general support: support@quiriz.co