Privacy

Privacy policy.

Overlay is a multi-tenant platform for independent retail. This policy describes what data we collect from merchants who use Overlay, how we handle the customer data their POS syncs into our system, and the rights everyone involved has.

Effective · 2026-09-28 Last updated · 2026-10-21 Contact · team@overlaypos.com

1Who this covers #

Overlay ("we", "us") operates this platform from Chicago, Illinois. This policy describes how we handle personal information for three groups of people:

  • Merchants — the businesses that sign up for Overlay and their staff who log in.
  • Merchant customers — the shoppers who buy from a merchant's Overlay-powered storefront or receive their marketing emails. We handle this data as a processor on the merchant's behalf; the merchant is the controller.
  • Visitors — people who browse overlaypos.com, read this policy, or start a signup.

If you are a customer of a merchant that uses Overlay and want to exercise a data right, contact that merchant first — they control your data. If they don't respond, or you can't reach them, email us and we will route the request.

2What we collect #

From merchants at signup

  • Business name and merchant contact name.
  • Email address and password (stored hashed with scrypt).
  • Business address, phone number, and the domain the storefront will run on.
  • POS provider and API credentials the merchant chooses to connect (Square access token, Shopify admin token, WooCommerce keys).
  • Payment method for Overlay's subscription billing (handled by Stripe; we receive metadata only — no card numbers).

From merchants during normal use

  • Content the merchant creates in Overlay: marketing campaigns, product descriptions, design settings, wine-club rosters, waitlist rules.
  • Server logs of API activity (request path, method, tenant, timestamp, response code).
  • Support conversations at team@overlaypos.com.

From the merchant's POS (about the merchant's customers)

When a merchant connects a POS, Overlay reads the following on their behalf:

  • Customer name, email, phone (where the merchant has collected them).
  • Order history: items, quantities, totals, dates.
  • Product catalog and inventory.

We do not read or store full card numbers or card security codes from any POS. Payment authorization stays on the POS provider's side. Some features do keep payment-provider tokens and card details that are not the card number: for example, club records keep the card brand, last four digits and expiry, and a card fingerprint issued by Stripe is kept against the customer's name, email and phone. Features that connect a bank (Plaid, Teller) read the merchant's bank transactions.

From visitors to overlaypos.com

  • Basic server access logs (IP address, user agent, referring URL, timestamp).
  • Anything a visitor submits through a form (name, email, business name, comments).

3How we use it #

We use the information above to:

  • Provide the service — run the merchant's storefront, deliver marketing emails, sync inventory, process club billing.
  • Authenticate merchants and secure their accounts (session tokens, admin keys, rate limits).
  • Bill merchants for the Overlay subscription and reconcile disputes.
  • Send transactional email to merchants: signup confirmation, billing receipts, security notices, service announcements.
  • Send Overlay product marketing to merchants (only to the merchant contact — never to the merchant's customers). Merchants can opt out of Overlay product marketing at any time.
  • Debug production issues (error monitoring with redacted headers, described in Security).
  • Detect abuse and enforce our Terms of Service.
What we don't do We do not sell merchant data. We do not sell merchant-customer data. We do not use merchant-customer PII to train models. We do not market Overlay to the merchant's customers — reaching those inboxes is the merchant's decision and stays under their control.

5Sharing & subprocessors #

Overlay shares data with the third-party services required to run the platform. Each merchant chooses their POS and payment provider; the remainder are Overlay's operator-side infrastructure.

Recipient Purpose Data
RenderApplication hostingAll application data
AWS SESTransactional and marketing email deliveryRecipient email, subject, HTML body
StripeOverlay subscription billing, and payments taken on a merchant's own connected Stripe accountMerchant name, email, payment metadata
Square / Shopify / WooCommerceMerchant-selected POSMerchant catalog, orders, customer records
AnthropicAI drafting and editing (emails, club plans, event pages, site edits, product descriptions), plain-English search, and reading supplier invoices, P&L files and bank transactionsPrompts, photos and PDFs a merchant or staff member provides, and the shop data each feature reads (for example catalog and sales summaries, supplier invoices, bank transactions)
SentryServer error reportingRedacted request metadata, stack traces
EasyPostShipping labels (for tenants who ship)Recipient name, address, package weight
DoorDash DriveLocal delivery (for tenants who deliver)Recipient name, address, phone, order items
Twilio, Inc.Text messages, for merchants who turn on SMSRecipient phone number, message text
Lob CorporationPrinting and mailing checks, for merchants who pay distributors by checkPayee name and address, amount, memo
Plaid Inc. and TellerBank connection for a merchant's profit-and-loss view, for merchants who connect a bankThe merchant's bank transactions
HubSpot, Inc.CRM sync, for merchants who connect itContact and order records
Slack Technologies, LLCBusiness alerts, for merchants who connect itEvent summaries the merchant chooses
Xero Limited and Intuit Inc. (QuickBooks)Accounting export, for merchants who connect oneOrder and invoice totals
Google LLCAnalytics, Search Console and product feeds, for merchants who connect themSite visit events, product data
GitHub, Inc.Hourly backup copy of each shop's data files, in a private repositoryThe data files Overlay keeps for each shop, including customer records. Encrypted only when a backup encryption key is set; every version is kept (see Retention)
Neon, Inc.Postgres database hosting for Overlay's subscription-billing records and for the inventory registerBilling records (tenant id, plan, invoices, Stripe identifiers); register data for shops that use the register database
Resend; Google (Gmail)Email delivery for marketing campaigns (Resend) and for transactional email (Gmail SMTP), and reading bounce notices (Gmail, read-only), where Overlay has configured themRecipient email, subject, body; bounce notices
Microsoft (Clarity)Session recordings on a shop's pages, only for a shop that sets a Clarity project idPage interactions of visitors to that shop
Meta Platforms; TikTokServer-side conversion events, only for shops that set them upOrder value and a hashed email address and phone number
ipwho.is; ip-api.comLooking up the city and country of a visitor's IP address, for Overlay's traffic monitorVisitor IP address
PagerDuty, Inc.; DiscordOperator alerts, only where Overlay has configured themAlert title, message and context (such as a tenant id)
Google LLC (Fonts)Web fonts loaded by overlaypos.com pagesThe visitor's IP address and browser details, as for any web request

Beyond these, Overlay shares personal information only when required by law (subpoena, court order, tax authority) or when necessary to protect the safety of a person. Overlay does not sell personal information.

6Cookies & tracking #

Overlay's own pages use one first-party cookie, and a shop's pages use a few more:

  • ovs — signed session token used to keep users logged in (30 days). HTTP-only, SameSite=Lax, and Secure in production.
  • overlay_cart, ov_ref, cs_age — on a shop's storefront: the shopper's cart, a referral code from a referral link (90 days), and a confirmation that the visitor answered the shop's age check.

Overlay does not run third-party analytics, ad-network trackers, or cross-site cookies on overlaypos.com. The pages load web fonts from Google Fonts, so Google receives the visitor's IP address. Each merchant may configure their own storefront analytics (for example Google Analytics, Microsoft Clarity, Meta or TikTok); that is their choice and appears in their own privacy notice.

Marketing emails sent through Overlay use a tracking pixel and wrapped links to record open and click events, so merchants can see engagement. Recipients can disable open tracking at the email-client level; every marketing email includes an unsubscribe link and a List-Unsubscribe header.

7Merchant-customer data #

Data about the merchant's own customers is handled differently from data about the merchant. Overlay is a processor for this data; the merchant is the controller. The rules are set out in our Data Processing Agreement, which is binding on every merchant account.

In practice:

  • When a merchant keeps its own POS (Square, Shopify or WooCommerce), Overlay reads customer records from it and keeps copies of the fields its features need, such as names, emails, phone numbers, addresses and order history for marketing sends and club rosters. When a merchant runs Overlay's own register and storefront, the customer records are kept by Overlay on the merchant's behalf.
  • Overlay does not currently have a tool that removes a customer from all of the copies it keeps; see Retention.
  • Merchant-customer data is never sold, rented, or used for cross-tenant analytics. Overlay's cross-tenant analytics measure Overlay usage (AI credits consumed, campaigns sent), not customer identities.
  • If a data-subject request reaches us but names a merchant we host, we forward it to the merchant and CC the requester.

8Retention #

  • Active merchant accounts — data is retained for the life of the subscription.
  • Closed merchant accounts — Overlay deletes the files it keeps for the shop from its live system within 30 days of closure, by a tool Overlay's operator runs by hand. That does not reach the backup copy, databases such as billing records, or copies held by third parties (see Backups). Merchants can request an export at any time before closure.
  • Server logs — held at Render for the log retention of Render's plan, which Overlay has not confirmed.
  • Billing records — retained for 7 years to satisfy tax obligations.
  • Backups — every hour Overlay copies each shop's data files to a private GitHub repository. That repository keeps every version and nothing is deleted from it, so data erased from the live system remains in earlier versions of the backup copy. The copy is encrypted only when a backup encryption key is set. Render, the hosting provider, may also keep its own disk snapshots; Overlay does not control or promise their retention.

9Your rights #

Depending on where you live, you may have the right to:

  • Access the personal information we hold about you.
  • Correct inaccurate information.
  • Delete your information (subject to legal-retention requirements).
  • Export your data in a portable format.
  • Object to processing or withdraw consent where consent was the basis.
  • Not receive marketing — unsubscribe links are on every Overlay marketing email, and you can email us to opt out of all future contact.
  • Lodge a complaint with a supervisory authority (for EU/UK residents) or your state Attorney General (for US residents in states with privacy laws).

To exercise a right, email team@overlaypos.com from the address on file with the wording Data request in the subject. We respond within 30 days. We do not charge a fee for the first request in a 12-month period. We may need to verify your identity before acting.

Merchant customers who want to exercise a right about data held by a merchant should contact that merchant directly. Overlay will support the merchant in responding.

10Security #

Personal information handled by Overlay is protected by tenant-level isolation, HTTPS in transit, scrypt-hashed passwords, and layered access controls. Overlay does not encrypt the files it keeps on the hosting disk as a whole; individual secrets, such as two-step sign-in secrets, are stored encrypted. The full description — including our known limitations and security roadmap — lives on the Security page.

If you find a vulnerability, please email team@overlaypos.com instead of posting publicly.

11International transfers #

Overlay processes and stores data in the United States. If you are outside the US, using Overlay means data is transferred to and processed in the US. For merchants and customers in the European Economic Area, the United Kingdom, or Switzerland, transfers are made under the European Commission's Standard Contractual Clauses (SCCs), incorporated by reference in the Data Processing Agreement.

12Children #

Overlay is a B2B platform for retail operators. The service is not directed at children under 16 and we do not knowingly collect personal information from them. If you believe a child has provided information to us, email us and we will delete it.

Where merchants sell age-restricted products (alcohol, cannabis), it is the merchant's responsibility to enforce age gates and verify identity at delivery.

13Changes to this policy #

If we make a material change to how we handle personal information, we will email active merchants at the address on file at least 30 days before the change takes effect and update the "Effective" date at the top of this page. Non-material changes (typos, clarifications) may take effect immediately with an updated "Last updated" date.

14Contact #

Privacy questions, data requests, or complaints:

Overlay — Privacy
Overlay
1128 W Armitage Ave
Chicago, IL 60614
United States
team@overlaypos.com