Privacy Policy

DMly is a Shopify app that lets merchants add a contact widget (WhatsApp, email, callback request, and direct call) to their storefront. This page explains what data we collect, why, where it lives, and how to remove it. We collect the minimum needed to make the product work — no advertising, no resale, no tracking across stores.

1. Data we collect from merchants

When a merchant installs DMly we store:

• Shop domain (e.g. example.myshopify.com) and Shopify-issued OAuth access token, used only to read product metadata for dynamic message templates and to write the widget configuration metafield.
• Widget settings entered by the merchant — channel toggles, phone numbers, email address, button text, display rules.
• Aggregated analytics: per-day counts of widget views and clicks per channel.

2. Data we collect from storefront visitors

• Anonymous events. When a visitor sees or clicks the widget we record an event row containing: event type (view/open/click), the channel clicked, the page type (home/product/collection/cart), the product ID if on a product page, and a random session ID generated in the visitor's own browser. We do not store IP addresses, names, emails, or cookies tied to identity.
• Callback submissions. If a visitor submits the "Request a callback" form we store the name and phone number they typed, plus an optional message. This data is only ever shown to the merchant inside their DMly admin and is treated as a customer-support record owned by the merchant.

3. What we do not collect

• No order, payment, or revenue data.
• No customer profile data from Shopify (no email, address, order history).
• No third-party analytics or advertising trackers.
• No cross-store identifiers — every shop's data is fully isolated.

4. How we use the data

Strictly to operate DMly: render the widget with the merchant's settings, deep-link clicks to WhatsApp/email/phone, persist callback requests for the merchant to follow up on, and show aggregated click analytics in the admin dashboard.

5. Where the data lives

All data is stored on a PostgreSQL database hosted on a private VPS in the EU. Backups are encrypted at rest. Access is limited to the DMly maintainers and is audited.

6. Sharing

We do not sell, rent, or share merchant or visitor data with any third party. Shopify itself receives the requests it routes through the App Proxy (this is unavoidable — they own the storefront). No other processors are involved.

7. Retention and deletion

• When a merchant uninstalls DMly the shop is immediately marked inactive — public endpoints stop accepting traffic from that store at once.
• 48 hours after uninstall Shopify fires theshop/redact webhook, which triggers permanent deletion of the shop record and every associated row (settings, events, daily analytics, callback requests).
• Merchants can also delete an individual callback request from the Callbacks page in the admin, which removes it from our database immediately.

8. GDPR compliance

DMly responds to Shopify's three mandatory GDPR webhooks:

• customers/data_request — we acknowledge the request and confirm that no customer-identifiable data is held.
• customers/redact — no action is required because no customer-tied data is stored. The request is logged and acknowledged.
• shop/redact — all data for the uninstalled shop is permanently deleted.

9. Cookies

The DMly widget does not set any cookies on the storefront. It uses a singlesessionStorage key (dmly_sid) and a singlelocalStorage key (dmly_visited) so click events can be linked into a session and so we can hide the widget from repeat visitors if the merchant configures that. Both keys are purely local to the visitor's browser and contain no PII.

10. Children

DMly is a B2B product for Shopify merchants. It is not directed at children under 13.

11. Changes to this policy

We may update this policy as the product evolves. Material changes will be communicated to merchants by email at the address on file with Shopify, and the "Last updated" date above will be revised.

12. Contact