InventoryPath Price Scheduler privacy notice
Last updated: October 23, 2026
InventoryPath Price Scheduler 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 support and privacy requests.
Information the app uses
When a merchant installs the app, we process the Shopify shop identifier and domain, default currency, product and variant identifiers, titles and optional SKUs, price and compare-at snapshots, selected targets, scheduling times and campaign execution history.
We retain limited staff identifiers and product-edit permission metadata to record authorised actions. Staff names and email addresses supplied through authentication are removed from stored sessions. Authentication and refresh tokens are encrypted at rest.
The app requests Shopify’s write_products scope to read product information and make approved variant price and compare-at changes. It does not request order or customer scopes, or collect buyer names, addresses, phone numbers or emails.
CSV files are parsed under size and row limits. Normalised campaign rows are retained rather than the uploaded file. Unsubmitted browser selections are not saved as campaign history.
How information is used
These records allow the app to authenticate access, preview and schedule merchant-approved product-price changes, verify results, restore eligible changes, enforce plan limits, diagnose failures and respond to support requests.
Installing the app does not subscribe the merchant or its customers to marketing. Public website subscriptions remain separate and require their own opt-in.
Service providers and data protection
Shopify provides the platform, authorisation and subscription billing. App services and the application database are hosted on AvanSaber’s AWS Ubuntu infrastructure. Support emails are handled through AvanSaber’s support email services.
No advertising pixels or marketing analytics are added to authenticated app screens. Public website analytics, where present, follow the website’s consent and privacy controls.
HTTPS protects app transmission. Authentication and permission checks control access to connected store records. Authentication tokens and operational email addresses are encrypted at rest.
Optional operational email
The store owner approves an operational email recipient and enables messages only after verifying the selected inbox. The address is encrypted at rest. Verification codes expire in ten minutes, work once, and are stored only as a digest.
We use Zoho ZeptoMail for minimal campaign start, completion and review updates, without product prices or buyer data in the messages. Delivery receipts retain state and time without provider diagnostics or plaintext recipient addresses. Minimal hashed delivery receipts contain no raw buyer or shop contact fields.
Email verification and delivery are separate from price restoration. Owners can disable emails; an email already being sent may still arrive. Marketing remains separate and requires its own opt-in.
Optional setup help and Brevo
For requested setup help, we process the merchant-entered help address, authenticated owner/store context, consent version and timestamps, verification state, store time zone and minimal app progress/recovery status. The help address is encrypted in our database. Generic help copy excludes customer details, product prices and exports. A verified subscriber can receive up to four help emails over fourteen days. Email is optional and separate from operational notifications and other newsletters.
Sender, Reply-To and optional-help contact are Inventory App at [email protected]. Brevo processes requested verification, optional email delivery, recipient information and delivery/open/click events. Our app does not use opens or clicks to advance the sequence or provide an engagement dashboard. Some links may be routed through Brevo and marketing messages may include its tracking pixel. Tracking has not been disabled across the shared provider account. The in-app consent explains this processing before the owner chooses whether to subscribe.
Verification codes expire after ten minutes with at most five failed attempts. Local cleanup clears expired codes, removes never-verified preferences after thirty days, removes detailed dispatch history ninety days after the fourteen-day program ends, and removes the latest verified preference 365 days after that window. The current consent record stores the latest request and verification rather than an archive of every previous request.
Hourly cleanup removes this app’s Brevo recipient lists once they are no longer needed after withdrawal, uninstall, store erasure, replacement or the program’s end. Unsent drafts are deleted; sent campaigns are archived because Brevo does not allow deleting a campaign once scheduled. Archiving does not erase historical delivery records. An in-flight provider queue or failed cleanup is held and retried. Requested-verification provider logs and previews are deleted by their individual message IDs within thirty days, or sooner after withdrawal or store erasure. Cleanup never deletes all logs for an email address.
Contacts created exclusively for this program can be deleted after its recipient lists are removed. A contact also used by another brand or purpose, or kept on a provider suppression list, is preserved for that separate purpose. Stopping these tips does not resubscribe anyone or override global opt-outs. Historical marketing delivery records, provider backups and legally retained service records follow Brevo’s applicable retention terms. Contact [email protected] for an erasure request requiring provider assistance. Archiving does not delete history, and removal from every backup is not immediate.
We keep minimal pseudonymous inbox/program hashes, closed-window/slot fences and durable withdrawal markers to prevent repeat sequences or recontact after restoration. These are not anonymous. A restored database is quarantined and reconciled with the latest independent withdrawal and store-erasure journals before optional sending resumes. Store erasure removes private local enrollment data; provider cleanup can continue without a live installation.
Use Help and setup tips in Shopify or the app-specific stop control in an email to stop only this sequence. Brevo’s separate provider unsubscribe can also block other marketing from the same provider account. Contact [email protected] for optional-help access, erasure or preference issues; never send credentials.
Shared portfolio controls
Price Scheduler’s optional setup emails use the shared InventoryPath sending limiter and stop-all controls below. Optional education is capped at one message per rolling 24 hours and three per rolling seven days to the same verified inbox across our apps. A Price Scheduler subscriber may receive up to four setup emails over fourteen days; the limits are maximums, not delivery promises. Requested verification and security messages have a separate purpose.
The private limiter uses keyed pseudonymous inbox indexes, app and dispatch identifiers, minimal timestamps and withdrawal evidence. These indexes are not anonymous. It receives no Shopify tokens, underlying product/customer/order records, campaign prices or other business content.
The owner can stop this app’s setup tips or all InventoryPath app setup tips for the verified help inbox. Brevo’s separate unsubscribe and account-wide suppression also apply and take priority. Installation and existing verified operational recipients do not automatically enroll in this program.
Current independent withdrawal and dispatch journal evidence must be retained during recovery. Restored optional preferences remain held until reconciled so an older database does not restart contact. A previously accepted or uncertain send continues to consume frequency capacity and is not automatically resent. This disclosure adds no new retention period or change to the Brevo processing and archival boundaries above.
Retention, deletion and recovery
The intended retention period for settled campaign and journal history is 90 days. Unresolved price obligations can require longer retention while the app remains installed.
Mandatory Shopify shop-redaction requests take priority and remove tenant tokens, campaigns, price journals and quota records. Customer privacy webhooks are authenticated and acknowledged without retaining customer payloads because the app stores no buyer records.
Encrypted backups support recovery. Recovered databases remain isolated with access and jobs disabled while later deletion and access events, and outstanding requests, are reconciled before any reactivation. Minimal hashed store and event deletion markers remain separate from database dumps so recovery does not reactivate a later-deleted tenant.
Requests and contact
Contact [email protected] about access, correction, deletion or other privacy questions. Do not include access tokens, API secrets, private keys or buyer details in an ordinary support email. The company privacy policy describes the general request process and rights alongside this app-specific notice.
AvanSaber Inc. operates InventoryPath Price Scheduler.