Privacy Policy

1. What this policy covers

Modura Waitlist ("the App") is a Shopify app by Modura Apps ("Modura", "we"). It lets Shopify merchants ("Merchants") show a waitlist form for sold-out product variants in their online store and collect requests from shoppers ("Shoppers").

This policy explains what information the App processes, why, and for how long. The Merchant decides which fields its waitlist form collects and how it uses the requests; Modura processes that information to provide the App to the Merchant.

2. Information we process

Merchant / store information

• Shop domain and App configuration (form fields, texts, settings).
• Shopify session data needed to run the embedded admin, including information about the staff member using the App.
• Billing usage records (shop, billing cycle, request-volume threshold). They contain no Shopper information.
• If the Merchant connects a CRM (section 4): the connection's access credentials (stored encrypted) and the Merchant's CRM settings, such as field mappings.

The App does not request access to Shopify customer or order data. Its Shopify access is limited to reading products and operating the App Proxy.

Waitlist request information

Depending on the fields the Merchant configures, a waitlist request can contain:

• name, email address and/or phone number;
• answers to additional (custom) form fields;
• the product and variant requested and the product URL;
• the date and time of the request.

Email addresses and phone numbers may be normalized internally (for example lowercased, or reduced to a standard phone format) to recognize repeated requests and to answer privacy requests.

Security and rate limiting

To protect waitlist forms against abuse, the App counts recent requests. The Shopper's IP address is not stored in plain text: it is only used as a keyed hash inside short-lived rate-limiting records.

3. How we use information

• To show the waitlist form and record Shoppers' requests.
• To show the Merchant its requests, product demand information and CSV exports.
• To calculate usage-based billing. Billing itself is processed by Shopify; Modura only reports usage volumes and receives no payment details.
• To protect the service against abuse.
• When the Merchant connects a CRM: to send new waitlist requests to that CRM on the Merchant's instruction (section 4).

The App does not send back-in-stock notifications to Shoppers. A waitlist request is not treated as consent to marketing.

We do not sell personal information.

4. CRM integrations

• Connecting a CRM is optional. The App currently supports RD Station CRM and Bevean CRM; a Merchant may connect either or both. Nothing is sent to a CRM unless the Merchant connects and configures it.
• Once connected, new waitlist requests of that store may be sent to the Merchant's CRM account. When both CRMs are connected, each new request is sent to each of them independently. Requests created before a connection are not sent automatically.
• Data that may be sent to Bevean CRM: the Shopper's name, email address and phone number (filled only where the Bevean customer has no value yet), and Modura-named fields on the customer with the request context (product, variant, product URL, request date and time, source "Modura Waitlist") and the custom form answers of the latest request. To update a customer safely, the App reads the customer's existing fields and sends them back unchanged.
• Data that may be sent to RD Station CRM: the Shopper's name, email address and phone number (on an existing contact, the name only where the contact has none, and the email address or phone number only where it is not already on the contact), and — only for the RD Station CRM contact fields the Merchant explicitly maps — the request context (product, variant, product URL, request date and time, source "Modura Waitlist", latest waitlist request) and the custom form answers of the latest request; mapped fields are updated with the latest request. To find and update a contact safely, the App searches RD Station CRM by email or phone, reads the existing contact and sends its other data back unchanged. The App does not create custom fields in RD Station CRM.
• RD Station CRM is connected by the Merchant's authorization in RD Station (OAuth); Bevean CRM with an API key the Merchant creates. The App stores these access credentials encrypted and uses them only to send the Merchant's waitlist requests and to check the connection; for RD Station CRM it renews the access periodically while the connection exists. Disconnecting (or uninstalling the App) deletes the stored credentials.
• The App does not create or change marketing consent, opt-in fields or legal-basis records in the CRM, and does not create a deal or opportunity because of a waitlist request. Any use of the data inside the CRM is the Merchant's decision and responsibility.
• Disconnecting the CRM stops new requests from being sent. Data already sent stays in the Merchant's CRM: deleting data in Modura (a deletion request, the retention period, or shop deletion) does not delete it automatically.
• The CRM provider processes the data under its own terms with the Merchant.

5. Service providers and sharing

Information may be processed by or shared with the following service providers as needed to operate the App:

• Shopify — the platform the App runs on (admin, App Proxy, billing).
• Railway — hosting of the App and its database.
• Cloudflare — DNS, proxy, and security services for the App's web address.
• The CRM chosen by the Merchant — only when the Merchant connects it (section 4).

6. Data retention

• Waitlist requests: up to 24 months from the request date, then deleted automatically; earlier when a deletion request applies (section 9).
• CRM delivery records contain no Shopper contact data and are deleted with their request.
• Rate-limiting records: up to about 24 hours.
• CRM credentials: removed when the Merchant disconnects the CRM, and on uninstall.
• After uninstall, the store's data is deleted when Shopify sends its shop deletion request (about 48 hours after uninstall), unless the App was reinstalled in the meantime.
• Data already sent to a Merchant's CRM follows the Merchant's own policies.

7. Security

• Access to a store's data is limited to authenticated admins of that store.
• CRM credentials are encrypted at rest (AES-256-GCM), used only on Modura's servers and never shown in the App.
• Secrets are kept in the hosting platform's configuration, not in code.
• We limit application logging and do not intentionally log CRM credentials or waitlist form contents.
• The App is served over HTTPS.

8. Merchant responsibilities

The Merchant chooses the fields of its waitlist form, informs its Shoppers as required, and is responsible for how it uses the requests — including any use in a connected CRM and any marketing communication.

9. Data rights and requests

Shoppers should contact the Merchant (the store where they joined the waitlist). Through Shopify's privacy webhooks, the App:

• deletes the matching Shopper's waitlist requests on a customer deletion request (matched by email address or phone number);
• lets the Merchant find and export a Shopper's requests in the admin for a customer data request;
• deletes all of a store's data on Shopify's shop deletion request.

Questions about privacy: [email protected].

10. International processing

Our service providers may process information outside the Shopper's or Merchant's country.

11. Children's privacy

The App is a tool for Shopify merchants and is not directed to children.

12. Changes to this policy

We will update this policy when the App changes how it processes information, and change the effective date above.

13. Contact

Modura Apps — Modura Waitlist
Privacy and support: [email protected]