Skip to main content

InventoryPath Proof Approvals privacy notice

Last updated: October 31, 2026.

InventoryPath Proof Approvals is operated by AvanSaber Inc. Read this app-specific notice alongside the AvanSaber company privacy policy. The InventoryPath website privacy supplement covers public website analytics and newsletter subscriptions.

Contact [email protected] for app privacy questions.

What the app processes

When a merchant installs the app, Shopify authenticates the merchant and authorises recent-order access. We process the shop’s domain and identifier, installation and authorisation state, encrypted app access tokens, limited authorised staff identifiers and permission or owner status, Shopify subscription eligibility and aggregate app usage.

For orders the merchant chooses, we process order identifiers and numbers, creation and cancellation or refund eligibility, selected line-item identifiers, titles, SKUs, variants, quantities and customisation attributes, the recorded customer email, merchant production notes, uploaded artwork and safe rendered previews, revision identifiers and hashes, and the customer’s approval or change-request comment and time.

Artwork, customisation text and comments may contain personal information entered by the merchant or customer. Merchants should include only what is needed for the proof.

The app requests Shopify order access and the protected email field. It does not request customer names, phone numbers, mailing addresses, customer lists or all historical orders. Artwork or customisation fields can still contain those details when supplied by a merchant or customer.

Why we use it

We use this information to prepare and show the exact artwork revision, send transactional invitations, verification codes and opted-in reminders, authenticate access, record the response to that revision, check whether selected order details changed, administer Shopify app billing, prevent misuse, support the service and fulfil privacy requests.

Buyer information is not used for marketing, personalised advertising or cross-app customer acquisition. No Brevo marketing list receives proof customer data.

Access and service providers

Authorised Shopify users can view their own store’s retained proof records. A customer must verify the recorded inbox before seeing artwork or responding; a forwarded link alone is insufficient.

Shopify provides authentication, order access and app billing. AWS hosts the app and its private storage. Zoho ZeptoMail carries transactional messages and necessarily receives the destination email and message content. Messages contain an opaque access link or a short-lived code, rather than attached artwork or full order details.

Customer proof screens contain no analytics pixels, advertising tools or third-party images or fonts. They use a secure, HttpOnly browser cookie for verification and request protection. Public InventoryPath website pages use their separate website consent and privacy controls.

Retention and deletion

Proof records and rendered artwork expire ninety days after the proof job was created. Customer invitations expire at the earlier of fourteen days or the order’s accessible 59-day horizon. Verification codes expire after ten minutes and are single-use. Verified access grants expire after thirty minutes.

Raw uploads are normally removed after rendering; abandoned uploads are cleaned up by the worker. Archiving revokes links immediately and queues deletion of the retained proof.

Uninstall revokes app access, invitations and queued work immediately after the authenticated lifecycle event is recorded, and queues deletion of app-held proof content. Reinstallation starts a new installation epoch and does not resume old links or jobs.

Shopify customer redaction requests remove related artwork, recipients, comments and access records. Deletion takes precedence over approval history. Shop redaction removes inactive shop data. Privacy events are authenticated without depending on a still-valid store token. Aggregate usage can remain without readable erased order identifiers.

Protection and recovery

We encrypt private artwork, proof details and app tokens, limit hosted services to their app-specific access, and authenticate private asset delivery.

Encrypted local backups use a fourteen-day rotation and a separate encrypted deletion journal kept for fifteen days. Quarantine recovery reapplies later erasures before any reactivation; a populated restore and deletion replay were tested. Off-server replication remains an operational follow-up, rather than a verified independent recovery guarantee.

Email provider acceptance does not guarantee inbox delivery. An already-dispatched invitation or reminder may arrive after a customer response or revocation; its access link still follows the app’s current authorisation state.

Requests and contact

Customers should contact their merchant to exercise access or deletion rights or correct the order’s email or customisation. Shopify’s privacy workflow notifies the app.

The authorised store owner can inspect an app-specific related-record report in Usage & plans. Prepared reports expire after seven days. Reports list retained artwork page references; contact support for help securely retrieving related artwork or a report that requires regeneration. Privacy reports are not published or automatically emailed to an unverified address. Requests must follow the merchant’s verified privacy process within Shopify’s required timeframe.

For app privacy questions, contact [email protected]. Include the shop domain and request context, never an access token, password or verification code. We update this notice when the service’s actual processing changes.

AvanSaber Inc. operates InventoryPath Proof Approvals.

App terms · Support · Merchant guide

Optional merchant setup tips

Optional setup tips are available. The full guide and core app work without email enrollment. Only the authenticated store owner can separately opt in and verify an eligible individual inbox. Buyers, suppliers and reps are not enrolled by receiving operational messages, and Shopify customer emails are not imported into marketing lists for this feature.

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.

Zoho Campaigns delivers optional educational setup tips. Zoho CPaaS/ZeptoMail delivers requested setup-tip verification codes under a separate transactional purpose. These services receive the supplied help inbox, generic app help content and the delivery or subscription identifiers needed for that purpose. They do not receive Shopify access tokens, artwork, customer proof comments, order contents or shipping addresses from the optional setup-tip service. Brevo is retained only where needed for previous withdrawals, late-event handling and historical message/resource cleanup; it is not selected to send new tips for this app. Migration never reenrolls withdrawn or completed sequences.

The apps share a sending connection, but have separate setup-tip topics and app-specific preferences. Current installation, consent, completion and withdrawal checks still apply before educational dispatch. Stopping one app’s tips does not subscribe, unsubscribe or enroll the inbox in unrelated brand newsletters. The portfolio stop-all control and provider unsubscribe/suppression settings also apply.

Email providers process delivery and subscription events. Educational email may include provider-managed open or link tracking. Opens and clicks do not determine whether setup is complete. This feature adds no tracking to the embedded app, private proof screens or artwork. Requested verification uses a separate transactional purpose; the Zoho CPaaS verification route has open and click tracking disabled.

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. Do not interpret expiration of a login code as immediate deletion of 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.

Use an individual inbox without a + tag for optional tips. Zoho Campaigns rejects tagged addresses and some role addresses such as support@, info@ and admin@. The app explains this before requesting a verification code. Enter an eligible individual inbox yourself; operational email can still use supported role addresses.

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