Skip to main content

InventoryPath Order Exports privacy notice

Last updated: October 31, 2026.

InventoryPath is a brand of AvanSaber Inc., which operates InventoryPath Order Exports. This notice explains the app’s processing of Shopify merchant, supplier and order information. Read it alongside the AvanSaber company privacy policy. This notice describes the app-specific processing; the InventoryPath website privacy supplement covers website analytics and newsletter subscriptions.

For privacy questions or requests, contact [email protected]. Merchants are responsible for their customer notices and for choosing suppliers authorised to receive the selected information.

Information the app uses

The app reads the order and line-item information needed for configured exports: Shopify order and line identifiers, dates, order statuses and tags, product and vendor details, SKUs, quantities, amounts, currencies, line-item customisation values, order attributes and selected supported order metafields.

It also uses shop identifiers, workflow settings, supplier email addresses, verification records and Shopify subscription eligibility. Raw Shopify order responses are processed transiently rather than stored as complete order records.

This version does not request Shopify buyer name, email, phone or address fields. Customer-entered customisation values and merchant-selected attributes can still contain personal information. Include only the fields your authorised supplier needs.

How information is used and shared

We use this information to preview and generate exports, run schedules, authenticate merchant staff and suppliers, check billing eligibility, troubleshoot the app and respond to privacy requests.

Exports are accessible to authorised app users and the verified supplier configured for the workflow. Supplier notifications contain a private access link rather than a spreadsheet attachment. The approved supplier inbox must verify access before downloading, including when a link has been forwarded.

We do not use exported order data to enrol customers in marketing lists or send it to an advertising service. Installing the app or verifying a supplier inbox does not subscribe anyone to a newsletter.

Service providers

The app runs on AvanSaber’s AWS infrastructure, managed through RunCloud, with Cloudflare serving its HTTPS hostname. PostgreSQL stores app records. Zoho ZeptoMail sends transactional verification and notification emails. Shopify provides authorisation and app subscription billing.

Brevo is used for optional website newsletter subscriptions, separately from app processing. It is not connected to order exports. Export files are stored privately on the app server; S3 and R2 are not used for this deployment.

Data protection

HTTPS protects transmission. Authenticated access and supplier inbox verification control downloads. Export objects, Shopify tokens and privacy-report bodies use application-level authenticated encryption. Export files are held outside public webroots, and database backups are separately encrypted. The app’s database disk is encrypted at rest.

Supplier verification codes expire after ten minutes, are single-use, have attempt and rate limits, and are stored as hashes.

Retention

Information Retention
Export files Access expires after seven days; the worker removes the encrypted file.
Export manifests, source identifiers and diagnostic export records Up to 65 days after processing, with privacy deletion taking precedence.
Data-access reports Up to 30 days after preparation.
Expired supplier verification challenges Cleaned after one additional day.
Shop, workflow and supplier settings While needed to provide the installation, subject to deletion requests and uninstall cleanup.
Database backups, including recovery-test copies Encrypted, with a maximum 14-day retention.

Minimal hashed event receipts may be retained to prevent replaying privacy events; older receipts remove the raw shop value. The 14-day backup retention rule also applies to encrypted recovery-test copies held on operator-controlled storage.

Access, deletion and uninstall

The app authenticates Shopify customer-data request and redaction webhooks. For a data request, it prepares a private report of retained rows requested by Shopify. An authorised merchant can download the report and provide it through the merchant’s verified customer-request process.

When relevant data is redacted, affected files are revoked and deleted. Files containing more than one customer’s data are removed in full. Affected schedules pause, and a future-only recovery boundary prevents erased historical rows from being fetched again.

Uninstalling stops app access and schedules and begins deletion of live app data, with a 24-hour operational target. Failed deletion jobs are retried. Before restoring a backup, later privacy and uninstall events must be reconciled so erased data, revoked downloads and old notifications do not become active again.

Merchants and customers can also contact [email protected] about app processing or to request access, correction or deletion. The rights and request process in the company privacy policy apply alongside this notice.

Changes and contact

We update this notice when app processing or providers change and communicate material changes through the appropriate merchant-facing channel.

AvanSaber Inc. operates InventoryPath Order Exports. Contact [email protected].

App terms · Support · Setup guide

Optional merchant setup tips

Optional setup tips are available. The guide works without email enrollment. Only the authenticated store owner can opt in, and the chosen help inbox must be verified.

If the store owner requests optional setup tips, the optional service processes the deliberately supplied merchant help inbox, verification status, owner-authorised purpose/version/timestamp, preference and withdrawal evidence, confirmed store time zone, installation context and coarse app progress. Onboarding adds no Shopify customer Email access or new Shopify scope.

The optional service is hosted on existing AvanSaber-controlled infrastructure, separately from core app databases and services. It receives a minimal read-only view of readiness, qualifying outcomes and known blockers. It does not receive Shopify access tokens or underlying order/customer details, artwork, supplier files, PO rows, invoices, assignments, commission values or rep credentials.

Optional setup-tip emails require separate consent and verification of an inbox. Zoho Campaigns delivers these tips, and Zoho CPaaS/ZeptoMail delivers requested setup-tip verification codes. These services process the verified inbox and applicable delivery, unsubscribe, complaint, bounce, open and click events. Installing an app or supplying an operational supplier/customer/rep address does not subscribe that address to tips. Opens and clicks do not mark merchant setup tasks complete.

Only the verified help inbox and generic app guidance are used for optional tips. Installing an app, providing a supplier/customer/rep email, or receiving an operational notice does not subscribe that address to marketing. Declining or withdrawing tips does not restrict the app. Opens and clicks do not mark merchant setup tasks complete. Messages already being sent may still arrive after withdrawal.

Brevo is retained only where needed for previous withdrawals, late-event handling and historical message/resource cleanup; it is not selected to send new setup tips for these three apps. Migration does not restart withdrawn or completed sequences. Product support and other operational email routing remain unchanged.

Educational email may include provider-managed open or link tracking. This feature adds no tracking to the embedded app or private buyer, supplier or rep pages.

Keyed pseudonymous inbox indexes and minimal dispatch reservations enforce shared portfolio sending limits and stop-all preferences. These indexes are not anonymous. App credentials and domain databases remain separate; this shared boundary does not let one app browse another app’s domain records. Requested verification and security messages have a separate purpose and do not consume the educational-email allowance.

Incomplete verification preferences and challenges are cleaned within thirty days. Codes expire after ten minutes and are cleared after expiry or attempt limits. Detailed dispatch evidence is normally retained for up to ninety days after the program window; pending external cleanup identifiers remain until resolved. Consent/preference evidence may remain for up to twelve months after the window or withdrawal. Minimal pseudonymous suppression and closed-program records remain to prevent unintended re-enrollment after reinstall or recovery. Restored optional databases are quarantined and current withdrawals and installation state must be reconciled before sending resumes.

We remove app-owned mailing-list memberships and delivery resources when safe, preserve shared profiles and suppression records, and arrange additional provider erasure when required. Historical delivery records and provider backups are not erased instantly. Zoho CPaaS documents sixty-day email-log retention by default; stored message content depends on the account’s content-saving settings. Expiration of a verification code does not immediately delete a provider delivery log. Brevo sent campaigns may be archived where deletion is unavailable; archival is not deletion of historical delivery records.

Uninstall or data erasure stops optional sending once detected, clears current inbox/challenge/guide data and queues provider cleanup. Before education dispatch, current authorisation and installation are checked again. Delayed lifecycle or provider queues can leave a message in flight; it cannot always be recalled immediately. Core app operations are independent of optional-service availability.

The owner may stop this app’s tips or all InventoryPath app setup tips for the verified inbox. Provider unsubscribe and account-wide suppression also apply. No contacts are imported automatically. Choosing not to enroll does not limit the app, and operational recipient verification does not enroll buyers, suppliers or reps. Optional setup-tip sender and Reply-To are Inventory App at [email protected]. Existing product support and privacy requests remain with [email protected]. Both brands belong to AvanSaber Inc.

The postal footer for optional tips is AvanSaber Inc., 1050 Lakes Drive, Suite #225, West Covina, CA 91790, United States.