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.
Quick summary. Quay is a B2B credit management app for Shopify wholesale stores. We process two kinds of data: Shopify data we read through the Admin API (your companies, orders, payment terms) and operational data we store ourselves (your app settings, the AR aging projection, our audit log, your subscription state, and a record of each privacy request about your buyers that Shopify sends Quay).
We do not sell your data, run ads, or share it with advertising networks, and the Quay app itself runs no third-party analytics or advertising trackers. Besides writing results back into your own Shopify store, we share data only with the operational vendors (subprocessors) listed in Section 6 below.
Support chat. Every page of the Quay app in your Shopify admin has a chat button that reaches us directly. It runs on Crisp, a support-chat service based in France that stores conversations in the EU. Your browser downloads the button from Crisp, so Crisp sees your IP address and browser whenever you open Quay. Nothing about your store is sent until you open the chat. Then Crisp receives what you write to us, your store's myshopify address and your Quay plan, plus what its chat window records by itself: your IP address, your browser, and which Quay pages you open. The chat window sends no company names, amounts or balances of its own. See Sections 5, 6 and 7.
Telegram alerts. Quay can send you a Telegram message when an order gets past one of your credit blocks. Nothing is sent to Telegram until you connect a chat yourself from Quay's settings page. The record of the blocked order is kept in our own database either way, whether or not you ever use Telegram. If you do connect a chat, each alert carries the order and its amount, the company, why the order should have been blocked, and who placed it. See Sections 4, 6 and 7.
Payment reminders. Reminders aren't open to every store yet, and none of this happens for your store until you turn them on. Once you do, Quay emails the companies you choose about their unpaid invoices, in your store's name. The emails go out through Resend, an email service in the United States, from Quay's address reminders@notify.quayhq.com. Replies go to your buyer contact email. Each email goes to one person per company: the accounts email you typed into Quay, the company's main contact in Shopify, or a contact you picked. It carries what a statement carries: your logo and letterhead, the company's name, and its unpaid orders with amounts, due dates and, where they matter, location names. It also carries the company's store credit, your payment details, your note and signature, and links to pay an order or view the statement where they apply. Every email has a link the buyer can use to stop them. Quay keeps a copy of each email for 30 days so you can open it. See Sections 2, 4, 6 and 7.
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:
- To process your store's personal data only as needed to provide the service described in our Terms of Service §2.
- To process data only on your documented instructions, which are these Terms and this Privacy Policy (GDPR Article 28(3)(a)).
- To engage the subprocessors listed in Section 6 of this Privacy Policy (GDPR Article 28(3)(d), which incorporates the conditions of Article 28(2)). We will notify you in writing at least 14 days before any change to the subprocessor list takes effect, so you have a reasonable opportunity to object. You don't need to reply: a change you don't object to in writing before the date in the notice takes effect on that date. If you do object, we will look for a way to resolve it, such as keeping your store's data away from that subprocessor. If we can't find one, you can uninstall Quay before that date: Shopify stops billing you, and your store's data is deleted as Section 7 describes, or sooner if you ask. The 14-day notice doesn't apply to a subprocessor used only by a feature you turn on yourself, such as Resend for payment reminders. Turning such a feature on is your consent to Quay using that subprocessor for it.
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.
- Companies: names, IDs, payment terms, contact information. Required to compute and assign credit policies per company. When a statement is rendered, Quay also reads the billing address, or failing that the shipping address, of the company's first location (street, city, region, postal code, country) to print the buyer's address block; it is read at that moment and not stored.
- Customers: the link between a buyer (a company contact) and their B2B company (the customer ID and the company it maps to), used to apply the right company's credit at checkout and in the buyer's account banner. If you turn on payment reminders, Quay also reads the contacts of each company it emails: their email addresses, job titles and the locations they buy for. That lets you pick who gets the emails, and lets the emails reach them. Quay never reads a buyer's name. It reads an email address when it needs it and keeps it only in the copy of a reminder email (Section 4). Quay also receives a buyer's email address when Shopify forwards that buyer's privacy request. Quay turns it at once into a code that can't be turned back into the address, and does not keep the address (Section 8).
- Orders: line items, totals, payment status, and
fulfillment status, used to compute the outstanding-balance projection
per company. Because B2B net terms can run to Net 90 and overdue
invoices stay unpaid well beyond Shopify's default 60-day order window,
Quay requests the
read_all_ordersscope so the one-time history import at install and the daily reconciliation can see your full B2B order history; day-to-day updates come from order webhooks. - Payment terms (net-30, net-60, etc.). Required to determine when invoices are overdue.
- Staff identity (
currentStaffMember): name and email of the merchant staff member currently using the Quay admin UI. Used to show "who made this change" in the in-app audit log, and to name the person who placed an order in a blocked-order record, which means it can travel to Telegram in an alert if you have connected a chat (Sections 4 and 6). - Shop name, address and contact email: read to prefill the statement letterhead in Document settings (display name, address lines, email). You can change what prints; the saved values live in the statement settings described in Section 4.
- Store owner email: read when we answer a buyer's data request, to send the answer to you (Section 8). If you turn on payment reminders, Quay also reads it, together with your store's contact email, to make sure no reminder goes to your own addresses. Quay stores neither address for this.
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:
credit_limit: the credit limit you set for each company.available_credit: the computed amount the company can still charge.-
enforcement_state:off/hide_net_terms/hard_block, the runtime authoritative state read by checkout enforcement. enforcement_reason: human-readable cause of the current state.in_plan: whether the company is covered by your current subscription cap.
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:
- Sessions: your Shopify offline access tokens, managed by Shopify's official session-storage adapter. Encrypted at rest by DigitalOcean's managed Postgres disk encryption.
- Shop settings: your in-app preferences (display name, your buyer contact email (reminders show it to your buyers, and their replies go to it), AR aging window, etc.).
- Statement settings: the letterhead printed on statements: display name, address lines, phone, email, registration number; the payment details you choose to print (a heading, bank name, account name and number, SWIFT/BIC, IBAN, routing or sort code, branch), a payment note, a footer note, and an uploaded logo (PNG or JPEG). Stored because they print on every statement. The first time you open Document settings, Quay prefills the display name, address lines and email from your shop's own name, address and contact email in Shopify; everything you save there afterwards is yours, and a saved field is never overwritten by a later prefill.
- Statement contact details per company: an optional phone number and email address you enter for a company's address block on its statement. That email is also the accounts email a payment reminder can go to. These are the only two statement fields with no source in Shopify; the company's address is read from Shopify when the statement is rendered and is not stored for statements.
- AR aging projection: a per-order outstanding-balance record computed from your Shopify orders. Not authoritative: refreshed from Shopify on each order webhook.
- Policy assignments: which credit policy (Standard, Trusted, VIP, Probation, or High Risk) applies to each company.
- Audit log: append-only record of policy edits, credit limit changes, and manual enforcement toggles. Records the Shopify staff user ID that made each change or, for a change no person made, that Shopify or Quay made it.
- Applied suggestions: a record of each set of suggested limits and policies you apply, for a group or for one company: when, the Shopify staff user ID that applied it, and, for each company in it, the payment group it was suggested for, the amount its suggested limit was built from, and its limit and policy before and after. Quay uses it to offer Undo for 30 days and to say why it suggests a later change; it stays until your shop data is deleted (Section 7).
- Staff identity cache: names and emails of Shopify staff members who made audit-logged changes. Refreshed every 24 hours from Shopify.
- Subscription state: your Quay plan, status, and billing-period dates. Synced from Shopify's Billing API.
- Webhook deduplication table: Shopify webhook IDs we've already processed, to prevent double-counting under Shopify's retry behavior.
- Net Terms suspension state: for each company location Quay has placed on pay-on-order (because it is over its limit, overdue, or manually held), we record the original Shopify payment-terms template so we can restore it later.
- Dashboard metrics cache: a cached snapshot of your AR aging figures and the names of your top companies by outstanding balance, used to render the dashboard quickly. Derived from your Shopify data and refreshed hourly; never authoritative.
- Operational caches and a background-job queue: which of your companies are within your plan's limit, and a transient queue of background recompute/sync jobs. These hold only shop and company identifiers plus job bookkeeping (including the staff user ID that triggered a job), and are reconstructed from Shopify on demand.
- Payment reminders: if you turn them on, Quay stores when you turned them on, and whether they are paused and why. For each company, it stores whether you stopped its reminders and who should get them; for a contact you picked, that is the contact's Shopify ID, kept while your choice stands. For each reminder email, sent or not, it keeps a full copy as written, including the address it went to, for 30 days so you can open it. After those 30 days Quay keeps the email's date and type, what happened to it (delivered, bounced, and so on) and which orders and warnings it named, so it does not repeat a warning. For 12 months it also keeps the buyer's Shopify customer ID and a code made from the address that can't be turned back into it, so it knows whether the same person was already told. Quay also keeps a copy of the logo your emails carry, and a record of each test email you send yourself. When a buyer uses a reminder's stop link or marks one as spam, a code made from their address goes on your store's do-not-email list. When an address bounces or is marked as spam, the same kind of code also goes on Quay's shared do-not-email list (Section 7).
- Buyer privacy requests: one record for each privacy request Shopify sends Quay about one of your buyers (Section 8): Shopify's ID for the request, the buyer's Shopify customer ID, the IDs of the orders it names, and a code made from their email address that can't be turned back into the address. When a buyer asks to be erased, that code also goes on your store's do-not-email list (Section 8).
- Blocked-order records: when an order gets past one of your credit blocks, we record what happened: the order's Shopify ID and number, the company's Shopify ID and name, whether the block was passed as the order was placed or when it was later edited upward, why the order should have been blocked (for an overdue invoice, that invoice's number and how many days late it was; for a manual hold, the reason text you typed; for an edit, the amount the order grew by), the order amount and currency, the company's available credit and credit limit at that moment, the sales channel the order came through, and the Shopify staff user ID and cached name of the person who placed it, which may be that person's email address, because the staff cache falls back to the email when no name has been stored. Alongside each record we keep the delivery state of its Telegram alert (queued, sent, failed or skipped, the number of attempts, the last error, and when it was sent). These records are written for every store, whether or not you use Telegram.
- Telegram connection: if you connect a Telegram chat, we store that chat's Telegram ID, its type (group or private chat), its title, whether the connection is active or revoked and why it was revoked (you disconnected it, the bot was removed from the chat, or you replaced it with a different chat), and the times it was connected, revoked, and last delivered to. If you connect a private chat rather than a group, the chat ID we store is the Telegram user ID of the person who set it up, which is a personal identifier for that individual. Our bot acts only on the connect command you send it; we do not read, store, or use anything else posted in the chat.
- One-time connection codes: the short-lived codes used to link a chat, stored only as a one-way hash, valid for 15 minutes and a single use. See Section 7 for how long the hashed row is kept.
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:
- DigitalOcean (United States): application hosting and managed Postgres database. Disk encryption at rest; TLS in transit.
- Cloudflare (US/global): DNS, CDN, and cookie-free Web Analytics for the marketing site.
- Crisp (Crisp IM SAS, Nantes, France): the support chat inside the app. Crisp keeps conversations on servers in the EU (the Netherlands and Germany), with encrypted backups in Ireland. The companies running its servers (DigitalOcean), backups (Amazon Web Services), network (Cloudflare), email relay (Vultr) and mobile push notifications (Google) are US companies; Crisp lists them at crisp.chat/en/sub-processors.
- Resend (Resend, Inc., United States): sends payment reminder emails, only for stores that turn reminders on. Turning reminders on is your consent to Quay sending them through Resend. Resend receives each email as written: the buyer's email address and everything the email carries (the summary at the top of this page lists it). It keeps the emails, the record of whether each one was delivered, and its logs for 30 days, and its backups for 7 days. An address that bounced or was marked as spam stays on its do-not-send list until that entry is removed. Resend lists its own subprocessors at resend.com/legal/subprocessors.
- Sentry (Functional Software, Inc., United States, with data kept in its EU region): error reports, so we can find and fix problems in Quay. A report says what failed, where in Quay's code, on which Quay page and for which store. Quay asks Sentry not to keep IP addresses. A buyer's browser sends Sentry nothing from the pages a reminder links to. If your store objects to Sentry (Section 1), Quay sends Sentry no reports about your store.
- Telegram (Telegram Messenger Inc.): used only if you connect a Telegram chat to Quay, and only to deliver the blocked-order alerts described below.
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:
-
customers/data_request: when one of your buyers asks for the data your store holds about them, Shopify forwards the request to Quay, and Quay records it (Section 4). Within 30 days we email you what Quay holds about that buyer, so you can pass it on. It lists each reminder email from the last 12 months that Quay can still link to them, with what happened to it, and the full text of those from the last 30 days. It lists each company, by name, where the statement email you typed in is theirs, with that email and the phone number beside it. It also says whether they stopped your reminders, marked one as spam, or were put on your do-not-email list by an earlier erasure request. We send it to your store owner email in Shopify or, if Shopify has closed your store, to an email address you typed into Quay, if you typed one. If you have uninstalled Quay, we send nothing, and the request is deleted with your shop's data. -
customers/redact: when one of your buyers asks for their data to be erased, Shopify forwards the request. While Quay still holds your shop's data, it records the request the same way and erases at once, on every company where the statement email you typed in is the buyer's, that email and the phone number beside it. It also deletes the copies of every reminder email to the buyer, with the address and the code stored with them. Quay stops sending to them: a company where you picked that buyer, or whose accounts email was theirs, gets no reminders until you choose someone else. Whenever Shopify's request carries the buyer's email address, a code made from it goes on your store's do-not-email list, so Quay never emails that address for your store. The list stays after your shop's data is deleted. -
shop/redact: when you uninstall and opt into deleting the app's data, Shopify fires this webhook approximately 48 hours later. We immediately and irreversibly delete all of your shop's stored data across every table except the do-not-email list described above (access tokens, audit log, order-invoice projection, policies, and every operational cache) rather than waiting out the 30-day grace window in Section 7. If you reinstall Quay before then, we keep your data instead, as Section 7 describes. Your support chat conversations and contact profile live with Crisp, not in those tables, and are deleted by hand within 30 days (Section 7).
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:
- Access your data inside Shopify at any time: we write results back to your metafields.
- Export records through Shopify's standard reports.
- Request deletion of your stored data sooner than the 30-day post-uninstall grace window by emailing support@quayhq.com.
- Lodge a complaint with your local data-protection authority.
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.
- All data in transit is encrypted with TLS. HTTPS-only, with HSTS enabled.
-
Postgres connections use TLS (
sslmode=require) over a private VPC network between the app and database. - Postgres disk is encrypted at rest by DigitalOcean's managed Postgres service.
- Application database queries are scoped by shop ID through a Prisma client extension that throws when the scope is missing; the few low-level maintenance queries are explicitly shop-scoped. One merchant's data cannot be queried by another merchant. That is a constraint built into how the database client is constructed.
- Shopify webhooks are verified by HMAC signature before any processing.
- Embedded admin requests are verified by Shopify session token (JWT).
- Secrets are stored only in DigitalOcean's encrypted environment variables. Never in source code, never in logs.
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:
- For onward transfers to our subprocessors (DigitalOcean, Cloudflare, Crisp, Resend, Sentry), we rely on their published Data Processing Agreements, which include Standard Contractual Clauses or equivalent transfer mechanisms. Standard Contractual Clauses are not signed bilaterally between Quay and individual merchants.
- DigitalOcean's and Cloudflare's published security and compliance posture.
- Crisp stores support chat conversations in the EU (the Netherlands and Germany, with backups in Ireland). The companies running Crisp's servers, backups, network, email relay and mobile push notifications (DigitalOcean, Amazon Web Services, Cloudflare, Vultr, Google) are US companies, which Crisp engages as its own subprocessors under its data processing terms.
- Resend sends payment reminders from the United States. Its data processing agreement covers transfers from the EEA and the UK with the EU Standard Contractual Clauses, the UK Addendum, and the EU-U.S. Data Privacy Framework with its UK Extension.
- Sentry keeps Quay's error reports in its EU data region. Sentry is a US company, and its data processing agreement lets it process data outside Europe under the EU-U.S. Data Privacy Framework, with the EU Standard Contractual Clauses and the UK Addendum as the fallback.
- If you connect a Telegram chat, the alert messages are delivered through Telegram's infrastructure. Telegram's privacy policy states that if you signed up for Telegram from the UK or the EEA, your data is stored in data centers in the Netherlands, and it names the European Data Protection Office in Brussels as its EU representative. That is Telegram's own statement about Telegram account data; we do not offer it as an assurance about where an alert is routed or stored, and we hold no transfer agreement with Telegram (Section 6). This transfer happens only because you chose to connect a chat, and only for the alert content described in Section 6.
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.