Privacy Policy

Last updated: November 7, 2026

For how this works in practice rather than in legal terms (what Quay reads, what it stores, and what is deleted when you leave), see the security page.

1. Who we are

Quay is currently operated by Andrei Markov, an individual entrepreneur registered in Georgia, trading as “Simple Business”. Contact for privacy questions: support@quayhq.com.

For your store's data being processed by an app you've installed: you, the merchant, are the data controller for your buyers' personal data; Quay is the data processor, acting on your instructions as set out in our Terms of Service and this policy. Quay is also bound by the Shopify Partner Program Agreement.

These Terms of Service together with this Privacy Policy constitute the written processing agreement required under GDPR Article 28 between Quay (as processor) and you (as controller). If your business requires a separate bilateral Data Processing Agreement, contact us at support@quayhq.com.

By accepting these terms, you authorize Quay:

Quay personnel with access to your data are bound by confidentiality obligations consistent with GDPR Article 28(3)(b). On request, we give you the information you need to check that we meet our duties as your processor. We allow and help with reasonable audits, including inspections, by you or an auditor you appoint (GDPR Article 28(3)(h)).

Quay is operated from Georgia and complies with the Law of Georgia on Personal Data Protection (No. 3144/2023, in force since 1 March 2024), overseen by the Personal Data Protection Service (PDPS). Because your store and your buyers may be located in the European Economic Area or the United Kingdom, we also process personal data in line with the EU GDPR and the UK GDPR; where those apply, the Article 28 commitments above govern our role as processor.

2. Data we read from Shopify

When you install Quay, the app calls Shopify's Admin API to read the following. We request only the scopes the service needs. One of them (read_all_orders) is a scope Shopify gates behind explicit justification; Quay requests it solely to read your full B2B order history (see Orders below), not just the most recent 60 days. We do not request scopes unrelated to credit management, such as write_payment_mandate or storefront pixel-tracking scopes.

3. Data we write back to Shopify

Quay writes the results of its analysis to company metafields under the $app:billing namespace. These remain in Shopify while the app is installed:

The $app: prefix means only Quay can write to these metafields, and they are set merchant-readable. On uninstall, Shopify's standard dialog offers a checkbox to delete the app's metafields with the app's data.

4. Data we store in our own database

To operate Quay, we maintain a Postgres database hosted by DigitalOcean (United States). For each shop, we store:

We do not store your buyers' postal addresses, payment information or browsing behavior. A phone number or email address for a company's statement block is stored only if you type it in. An email address Quay reads from Shopify is kept only inside the copy of a reminder email, for 30 days. We do not store any data about visitors to your storefront. Conversations in the support chat are not stored in our database either: they stay with Crisp (Section 6).

Buyer-facing banner. Quay's Customer Account UI Extension shows the authenticated buyer a single banner on their Shopify customer account page when their company is over its limit or on credit hold, explaining the restriction and who to contact. The banner is composed at the company level: it does not list individual invoices, balances, or another contact's orders. Healthy accounts and direct-to-consumer buyers see nothing. It is shown only to the buyer through Shopify's Customer Account authentication, scoped to their own company, never another company's.

Pages a reminder links to. Two links in a payment reminder open pages on app.quayhq.com: the company's statement, and a page that stops the emails. Each opens only its own company's page and needs no sign-in, so anyone the email is forwarded to can open it too. The statement link works for 30 days, and stops working sooner if you change who gets the company's emails; the stop link does not expire. A link to pay an order opens Shopify's checkout for it. Quay sets no cookies on its two pages, and they load no chat or analytics. The statement page loads its font from Shopify's servers, as Quay's pages in your admin do.

5. Marketing site (quayhq.com)

The marketing site at quayhq.com uses Cloudflare Web Analytics: a cookie-free, privacy-first analytics service that aggregates page views and referrer data without setting tracking cookies and without persistent visitor identifiers. We use it to understand traffic sources and content effectiveness. No personal data is collected. We believe no consent banner is required because the marketing site uses no cookies or persistent identifiers; if your jurisdiction's regulator takes a different view on cookie-free analytics, contact us at support@quayhq.com.

The app itself (everything under app.quayhq.com) uses no analytics. Besides Shopify's own App Bridge script, which every app in the Shopify admin loads, the one third-party script its pages load is the Crisp support chat window (Section 6). Once you first open the chat, and where your browser allows it, Crisp keeps a cookie in your browser; it lasts six months, is renewed each time you come back, and is limited to app.quayhq.com. Inside the Shopify admin some browsers, Chrome among them, refuse it; your conversation is then found again through the code described in Section 6.

6. Subprocessors

Data we entrust to operational vendors:

Why Shopify isn't on this list. Shopify is your own platform: you signed up with Shopify, and Shopify looks after your store's data under its agreement with you. Shopify doesn't process your data on Quay's behalf. Quay reads your store's data from Shopify and writes its results back into your store, under the rules Shopify sets for every app (the Shopify Partner Program Agreement and API terms).

Quay does not sell your data, serve advertising, or share your data with advertising networks or third-party product-analytics services. If we take on a new subprocessor, we will add it to this list and tell installed merchants first, as Section 1 describes.

What the support chat sends to Crisp. Each time a Quay page loads, your browser downloads the chat button from Crisp, so Crisp sees your IP address and browser even if you never open the chat. Nothing about your store is sent until you open it. Then the chat window tells Crisp which store it is (your myshopify address), your Quay plan and its status, and a code that keeps each person's conversation separate for each store; only we can tell which staff member a code belongs to. It sends nobody's name or email address, and no company names, amounts or balances. When you write to us, Crisp also receives your messages, any file you attach, and your email address if you type it in so we can answer by email. Crisp's chat window also records by itself your IP address and the rough location it points to, your browser and device, and the address of each Quay page you open, which can include a company's numeric Shopify ID. Crisp acts on our instructions under the data processing agreement in its terms of service.

Telegram is not on the same footing as the others. DigitalOcean, Cloudflare, Crisp, Resend and Sentry are contracted subprocessors: we use them under their data processing agreements, and the Article 28 commitments in Section 1 rest on those. We have no data processing agreement with Telegram. The Quay bot is used under Telegram's ordinary public terms, and it carries your data only because you chose to connect a chat. If that is not acceptable for your business, do not connect one: the feature stays off and nothing reaches Telegram.

What an alert contains. Once you connect a chat, each alert carries the order number and a link to that order in your Shopify admin, the order amount and currency, the company name, the reason the order should have been blocked (for an overdue invoice: the invoice number and how many days late it is; for a manual hold: the reason text you typed, word for word; for an order edited upward: the amount it grew by), the company's available credit before the order whenever a credit limit is set, the sales channel, and the person who placed the order (their name, or the email address if that is what our staff cache holds, or their Shopify staff ID if we have no name at all). The one-off message our bot posts when you first connect a chat names your store. We do not send your buyers' names or contact details, their addresses, or the order's line items, though a manual-hold reason is free text, so whatever you wrote there travels with the alert.

Telegram's own privacy policy governs what Telegram does with a message once it arrives. That policy states the service is provided by Telegram Messenger Inc., with group companies Telegram Group Inc and Telegraph Inc in the British Virgin Islands and Telegram FZ-LLC in Dubai, and names the European Data Protection Office, Avenue Huart Hamoir 71, 1030 Brussels, as its representative for EU data-protection matters. Disconnecting the chat in Quay's settings stops all further messages immediately and our bot leaves the chat; alerts already delivered remain in your Telegram chat and cannot be recalled by us.

7. Data retention

While Quay is installed, we retain operational data for as long as needed to run the service.

On app uninstall, Shopify revokes our access token and fires the app/uninstalled webhook. We delete your access tokens and session rows immediately, and we schedule the rest of your shop data for deletion 30 days later.

The 30-day grace window exists so an accidental uninstall (or a reinstall while you evaluate Quay) does not lose your configuration. If you reinstall within 30 days, the pending deletion is canceled and your policies, company assignments, and history are preserved. If you do not reinstall, a daily cleanup job permanently and irreversibly deletes all of your shop's data once the window elapses, including the audit log, the order-invoice projection, your policies, and every operational cache and queue listed in Section 4. Your statement settings, the uploaded logo with them, and the per-company statement contact details go with it. Nothing is retained indefinitely, except two do-not-email lists. Your store's list (Section 8) holds a code for each buyer who asked to be erased, stopped your reminders or marked one as spam. The code is made from their email address and is never the address itself. It is kept with your store's Shopify address and the date, so Quay never emails them for your store again. Quay's shared list holds the same kind of code for an address that bounced or was marked as spam from any store's reminder, so no store's reminders go to it. When any store presses Try again for a bounced address in Quay, Quay checks the address with Resend and, if it only bounced, takes it off both lists. Resend keeps a list of its own (Section 6).

Payment reminders. The full copy of a reminder email, the address included, is deleted 30 days after the email was written. The buyer's Shopify customer ID and the address code kept with it are deleted 12 months after the email was written. Resend deletes its own copies on its own schedule (Section 6). Everything else Quay stores for reminders, such as each email's date, type and outcome, is deleted with the rest of your shop data under the rules above.

Support chat. Your conversations with us are kept in Crisp so we can see what we already told you. When your shop data is deleted under the rules above, we delete your conversations in Crisp, and the contact profile Crisp keeps for you, within 30 days. That step is done by hand, because the cleanup job does not reach Crisp. You can ask us to delete them sooner at support@quayhq.com.

Your stored data is accessible only to Quay operations staff and is never shared with anyone except the subprocessors in Section 6 and your own Shopify store, where Quay writes its results. If you want your data deleted sooner than the 30-day grace window, contact us at support@quayhq.com. We will acknowledge your request within 30 days and purge promptly.

Cache refresh schedules: the KPI cache refreshes hourly; the Shopify staff identity cache refreshes every 24 hours.

Telegram data. A one-time connection code stops working as soon as it is used or after 15 minutes, whichever comes first, but the hashed row itself stays in the database until you generate the next code for your store (which clears every code row we hold for you) or until your shop data is deleted. Your chat connection, the connection codes, and the blocked-order records all go with the rest of your shop data under the same 30-day uninstall rule above, or immediately if you uninstall with Shopify's "delete this app's data" option (Section 8). Messages already delivered to your Telegram chat are outside our control and stay there until you delete them.

8. Shopify GDPR webhooks

Every Shopify app must implement three GDPR-related webhooks. Quay implements them as follows:

We keep the record of each buyer privacy request until 30 days after we answered it or carried it out, and never longer than your shop's data.

9. Your rights

As a merchant, you can:

As one of a merchant's buyers: make data-subject requests to the merchant. When your request reaches Quay through Shopify, Quay sends the merchant what it holds about you, or carries out your erasure (Section 8). For anything else that touches Quay, the merchant can contact us and we help them respond. Every payment reminder has a "Stop these reminders" link. Once you confirm, the store sends no more reminders to your address. A reply to a reminder goes to the store.

10. Security

The following applies to the Quay application at app.quayhq.com. The marketing site at quayhq.com is a static site hosted on Cloudflare Pages with no servers or PII storage.

Security incidents. If we become aware of a security incident affecting your data, we will notify you in writing without undue delay, and in any event within 72 hours of becoming aware for incidents involving EU/UK data subjects, so you can meet your own GDPR Article 33 obligations toward your supervisory authority. We will include details of the incident, its scope, and the steps we are taking to mitigate it.

11. International transfers

Our database is hosted by DigitalOcean in the United States. If you are based in the European Economic Area, the United Kingdom, or another jurisdiction with cross-border data-transfer restrictions, your data is transferred to and processed in the United States. Data that stays in Shopify is covered by Shopify's own Data Processing Addendum, which you accepted as a Shopify merchant and which Quay is not a party to. For the data Quay receives and stores, we rely on:

12. Children

Quay is a business tool intended for use by merchants and their B2B customers. We do not knowingly collect data from anyone under 16. If you believe we have, contact support@quayhq.com.

13. Changes to this policy

We will post material updates to this page and update the "Last updated" date. For substantive changes that affect installed merchants, we will notify you directly (by email to the contact address on file for your store) before the changes take effect.

14. Contact

For privacy questions, data-subject requests, or to inquire about retained records: support@quayhq.com.