• TROUBLESHOOTING AND FAQS • SETUP GUIDE

Understanding Data Access, Security, and Privacy

By Rivio Support Team
2 min read

What you will achieve in this guide

Follow this step-by-step documentation to configure custom B2B registration forms, approval workflows, and customer tagging.

EXPECTED SETUP TIME 5-10 Minutes
COMPATIBILITY All Shopify Themes & Plans
TECHNICAL DIFFICULTY Zero Code Required

Rivio B2B Registration Forms uses Shopify customer, company, and file access for application onboarding and protects integration credentials.

Before you begin

Record the affected store, form name, slug, application reference if available, and approximate time. Reproduce the issue once with dummy data and note the exact message before changing settings.

Understand access and handling

The documented app uses Shopify session tokens in admin, signed App Proxy requests on the storefront, HTTPS, and encrypted secret storage. Its documented permissions cover the customer/company/file workflow rather than orders, payments, or checkout.

API keys, SMTP passwords, reCAPTCHA secrets, and webhook secrets should stay in credential fields. Exports and application records can contain personal information, so use role/form scope and authorized sharing. Email and webhook logs are documented as retained for seven days.

Reference and examples

Control What it protects Merchant action
Admin session tokens Embedded app session Use authorized Shopify accounts.
App Proxy signature Storefront requests Use the intended storefront app block.
Encrypted secrets/HTTPS Stored credentials and transport Keep secrets out of chat, screenshots, and hidden fields.
Scoped keys/team roles API and human access Limit scope and revoke obsolete access.
Shopify privacy requests Customer export/deletion and shop deletion Use the appropriate privacy workflow and support where needed.

Example

Use dummy business records, controlled test inboxes, and a dedicated test integration. Redact key-management and credential screens from any walkthrough.

Expected result

The demo teaches the workflow without exposing customer records or reusable secrets.

Limits and important behavior

  • The documented app permissions do not access orders, payments, or checkout.
  • The app supports Shopify customer-data export/deletion and shop-deletion requests.
  • Documented email and webhook logs are retained for seven days.
  • Security controls do not replace your responsibility for how your business uses applicant information.

If you still need help

For a data or deletion request, contact support with the relevant store and record reference using the available privacy workflow. Do not send full applicant files, API keys, or SMTP credentials in a general screenshot. Restrict exported data to the people who need it.

Screenshots to add

Screenshot placeholder: Capture the app screen or test result described in “Understanding Data Access, Security, and Privacy”. Include the relevant saved settings and the example outcome so readers can connect the explanation to the interface. Use dummy applicant details and mask any secrets.

Related guides

If these checks do not resolve the issue, contact RivioApps Support with the form name, application reference where relevant, error, and time. Do not include passwords or access keys.