Privacy Policy. This page is ready
Last updated: 2026-11-06
Orderly Rescue helps Shopify merchants identify checkout problems, understand recurring issues and assist with purchases. It is operated by Quarata Consulting LLC, a Florida limited liability company, at 7901 4th St N Ste 300, St. Petersburg, FL 33702, United States. Contact info@orderlyrescue.com about privacy.
This notice covers shoppers and visitors to stores using the app, and merchants and their staff. The merchant's own privacy notice also applies to shopping at its store.
For store shopping and checkout data, the merchant decides the purposes and we process data on its instructions. Our Data Processing Addendum explains that relationship; our merchant terms also apply. Merchants can adapt our shopper-notice template for their own store.
We separately handle information needed to administer our merchant relationships, support the service, protect it, meet legal duties and keep agreement evidence. For those purposes we determine how information is used. Shopify has its own roles and privacy terms, which vary by service.
We do not sell shopper data, use it for advertising, train AI models on it or create cross-store shopper profiles.
When enabled, the app receives supported page-view, cart and checkout events from Shopify's pixel runtime. Collection can occur on the storefront as well as at checkout. It helps merchants understand the path to checkout and diagnose problems such as address errors, delivery restrictions or failed payments.
Events can include:
We discard unrestricted journey-event payloads, keeping only the product title. We do not deliberately collect payment card numbers, security codes, bank credentials or special-category information, and we keep street-address fields only in the shipping-address error case described above. Diagnostic messages, typed field values or product titles can incidentally include personal information; automated scrubbing reduces this risk but cannot recognise every possible detail.
When a merchant opens an error's details, the app also reads the store's own shipping settings and product details from Shopify and, for a checkout that ended in an error and was not completed, the recovery link Shopify creates for that abandoned checkout. It does this only to show them to the merchant. They are read from Shopify at that moment and are not stored; the recovery link is not stored, logged or put in any email. Opening a recovery link resumes that checkout with the shopper's saved details, so the app shows it only to the merchant. The app never sends the link or any message to shoppers; a merchant may choose to.
Optional checkout guidance gives general tips. It does not make payment decisions, correct addresses or determine whether someone can buy. Reports describe observed activity and estimates, not guaranteed causes or outcomes.
Older records collected before the 2026-10-04 revision may contain fuller URLs or journey payloads. They remain subject to applicable detail-access controls, erasure and retention; the minimisation changes apply to new collection.
The pixel requires Shopify's analytics-processing permission and checks changes to that permission for all events. Events without permission are discarded, not held for later transmission by our pixel. The only events the pixel holds are checkout and error events it was permitted to send and our server did not accept, as described under privacy choices below. Shopify determines the permission signal using customer choices and the store's configuration; in some regions this may permit analytics without a consent prompt. Each stored event records the permission state Shopify reported when it was captured; events stored before 2026-10-24 have no such record.
Merchants must establish the applicable lawful basis and provide required notices and choices. Depending on the processing and applicable law, that may involve consent or a documented legitimate interest. A merchant setting or our geographic estimate does not itself establish consent, legal necessity or compliance.
You can use the store's privacy controls to change your choices and contact the merchant about information already held. The app uses Shopify-provided identifiers; we do not set our own browser cookies. While analytics permission is given, the app's pixel keeps a small record of the privacy choices it saw (up to ten, with times) in the browser's local storage for the store's site and sends it with events; it deletes the record when analytics permission is withdrawn, and otherwise the record remains until the browser's storage is cleared. If our server does not accept a checkout or error event (a network error, a server error or a rate-limit answer), the pixel keeps that event in the same local storage (key orderly_rescue_outbox_v1) and sends it again on a later event or page load, for at most 24 hours, 5 attempts and 20 events. It keeps it only while analytics permission is given, checks the permission again before each resend, and removes the kept events when permission is withdrawn. Browsing events are never kept. The pixel also sends Shopify's identifier for each event, which we use only to drop a duplicate delivery. This does not mean the service is anonymous or outside tracking rules.
Merchants can stop accepting new events and remove the pixel, limit new customer details, select finite retention or delete stored events. Detail limits leave event records and identifiers in place; they do not erase old records. Already-open browser sessions may still attempt delivery after collection is stopped, but the server rejects storage. Uninstall notifications and privacy-control changes must reach the app to take effect.
We hold the store domain, app settings, the list of up to five notification recipient addresses and the weekly-summary switch, the store's current Shopify plan and billing state (a plan handle, status and dates, read from Shopify), whether we have granted the store a complimentary plan (with its dates and our internal note) and which of our staff made each change, Shopify session credentials, and staff identity information Shopify supplies. We use this to authenticate, deliver and administer the service. Account and billing processing relies on our contract with an individual merchant where applicable; business-contact and staff administration ordinarily relies on our legitimate interests in operating the service. Legal obligations apply where required.
Support messages are used to answer the enquiry. Please avoid sending unnecessary shopper information or credentials. Our legitimate interests in security and resolving disputes support limited access logs and agreement records, with rights balanced against those purposes.
Access records contain the store, available staff identifier, operation, row identifiers or counts and field names, never the protected field values. Agreement records contain the store, document version and fingerprints, date and available accepting/acknowledging staff identifier. Acknowledging a notice is recorded separately from accepting an agreement.
We disclose information to the merchant and authorised staff, configured notification recipients and merchant-chosen webhook destinations. Merchants control their own downloaded or delivered copies.
Railway Corporation hosts the app, database and operational logs in the United States. Plus Five Five, Inc., trading as Resend, delivers merchant notifications, a weekly summary email to the merchant's recipients (counts and amounts, with no shopper personal data) and data-request notices. Emails may include shopper contact details, error context and details from the store's own shipping and product settings, but never a recovery link. They are not direct marketing messages sent by us to shoppers. Functional Software, Inc., trading as Sentry, receives technical error and performance reports from the app server and the merchant admin pages, processed in the United States. Before sending, the app removes request contents, cookies, headers and query strings and masks email addresses, long numbers and identifiers. An error message can name the store's myshopify.com domain.
Shopify supplies events and hosts the merchant platform under its own terms. We may disclose information when legally required, to protect rights and security, or to a successor that assumes the relevant privacy obligations in a business transfer. We restrict disclosures to their necessary purpose.
Information is processed in the United States. Where required, our DPA incorporates EU standard contractual clauses and the UK Addendum, with Swiss adaptations and applicable safeguards for onward transfers. Error reports go to Sentry in the United States, which relies on its Data Privacy Framework certification, with the standard contractual clauses as fallback. Quarata is not Data Privacy Framework certified. A provider's certification is used only within its verified scope and does not cover transfers to Quarata automatically. Contact us to request information about the safeguards or a copy, subject to appropriate redactions.
| Information | Retention |
|---|---|
| Shopping and checkout events | Set by the merchant's plan: Free 7, Starter 30, Growth 90, Pro 365 days, or a shorter window the merchant chooses, except that browsing events (page, cart and add-to-cart steps) are kept at most 30 days on every plan; expired records removed by daily cleanup. Until Shopify first confirms a store's plan, cleanup uses a 30-day window for the first 30 days after install and the Free window after that, unless the merchant chose a window. When a lower plan takes effect, events outside its window are deleted 72 hours later, with an in-app notice. Details a plan does not display are still stored within the window and are included in a data return on every plan |
| Store settings and linked notification records | While installed; events and dependent records may be deleted earlier |
| Uninstalled store data and sessions | Sessions are removed on uninstall processing; store data (except the complimentary plan records in the next row) on Shopify erasure, ordinarily requested after about 48 hours, with daily fallback cleanup after seven days inactive. If the store reinstalls the app before that request arrives, its data stays with the reinstalled installation and is erased after a later uninstall |
| Complimentary plan records | Kept as our own records of the grant, including after uninstall and after Shopify erasure, for as long as needed to administer and evidence it |
| Security access records | 90 days, followed by daily expiry cleanup |
| Acceptance and acknowledgement records | Six years from each record, followed by daily expiry cleanup |
| Support correspondence | Until the enquiry is resolved and for up to 12 months afterwards, unless needed for a documented dispute or legal obligation |
| Non-identifying daily totals | While the store remains installed; removed with the store |
| Recovery backups, if enabled | At most 90 days; restricted to recovery/security; deletion instructions reapplied before restored data is used |
These periods do not authorise unrestricted use. A specific legal hold may require longer retention of relevant records. Copies in merchant inboxes or exports follow the merchant's retention rules. Railway (hosting logs), Resend (email) and Sentry (error reports) delete their copies under their own terms; our own records follow the periods above. We avoid writing customer field values to application audit logs and store access/agreement evidence in the database with explicit expiry.
Depending on your location and the processing, you may request access, correction, deletion or portability, restrict or object to processing, withdraw consent where relied on, and complain to your data-protection authority. Withdrawal does not change processing lawfully performed before withdrawal. Applicable US state rights may also include an appeal of a denied request and protection against unlawful discrimination.
For shopping data, contact the merchant first so it can verify and coordinate the request. We support Shopify's access and deletion workflows and provide additional assistance. Automated matching uses supplied identifiers and associated checkout context; mistyped or unlinked identifiers may need further investigation.
Contact info@orderlyrescue.com for our own merchant, staff, support or security processing, an unresolved routing question or an applicable appeal. We may request information reasonably necessary to verify authority. We do not sell or share personal information for cross-context behavioural advertising, or make automated decisions with legal or similarly significant effects about shoppers.
We publish the revision date above. Material changes affecting merchants are posted here and announced in the app under the Terms and DPA. Changes do not retroactively authorise a new use of previously collected data. Merchants should update their own notices when their use of the service changes.