Data and Privacy FAQ

Common privacy, security, and data-handling questions. If yours isn't here, email support@regiostech.com.

How does Regios handle customer information?

By default, no personal data about your customers will be stored in our database. For example, if you use the "Specific customers" eligibility option, which allows you to select a finite list of specific individuals for a discount, as long you have "Settings > Use compact format enabled" (default), our app will only store Shopify IDs rather than other personally identifiable information (PII).

When our analytics feature is implemented, the following customer information may be stored in our database:

• Shopify ID, ex. gid://shopify/Customer/123456789.
• List of tags, ex. ["gold", "vip"]
• The values of metafields that your discount configuration depends on. For example, a "VIP tier" discount might require us to store the value of the customer's custom.vip_tier_name metafield.

We do not store free-form PII (name, email, address).

Server location and data retention

• Location: United States.
• Retention: Deleted discounts are soft-deleted to enable backups/restore. With Compact Format enabled (on by default), the discount config holds no PII besides the Shopify customer ID.
• On uninstall: Store info is deleted within a few hours. Discount configs are retained as backups so they can be restored if you reinstall.
• Third-party access: None.

What permissions does your app require?

• Required: read_cart_transforms, read_customers, read_discounts, read_locales, read_products, read_shipping, read_themes, write_cart_transforms, write_discounts, read_publications, and write_publications.
• Optional scopes include read_locations, read_markets, read_companies, read_orders, read_marketing_events, and write_app_proxy.

We do not request or hold scopes that would let our app edit customer records or product records.

Can the Regios app edit customers?

No.

Can the Regios app edit products?

No.

Information security certifications

None currently (no ISO 27001 / SOC 2 Type II).

Updated on: 06/06/2026