Public checks
We use submitted store and contact details to run the check you request.
Privacy
This page explains how Autonomous Path handles information submitted through product-data checks, qualified audits, scanners, contact forms, public business outreach, purchases, reports, and customer accounts.
Last updated:
At a glance
The short version
Business outreach
Reviewed messages use public business sources and include a direct opt-out path.
Private audit files
Raw audit uploads are scheduled for deletion 30 days after report delivery.
Optional measurement
Analytics and campaign attribution load only after you allow measurement.
Jump to a privacy section
Information you provide
We collect the details you submit through the site, including contact information, website URLs, commerce platform context, catalog samples, scanner inputs, audit qualification details, purchase details, and messages you send to us.
Public business outreach
For a small, reviewed business-outreach program, we may use contact details a business publishes for commercial inquiries and public information from its store, product pages, policy pages, or an authorized advertising source. We record the source, date checked, business role, jurisdiction, and evidence used to prepare the message. We do not use private customer data, account pages, checkout pages, purchased consumer lists, or access-restricted sources for this outreach.
Every exported message identifies Autonomous Path, includes a physical mailing address, and provides a signed unsubscribe link plus a reply-based opt out. An opt-out creates a one-way hashed suppression record so the address can be screened from later exports without putting the address in the public unsubscribe token. Suppression and related compliance records may be kept as needed to honour the request and demonstrate compliance.
The review is limited to public evidence and is not a full audit. It does not mean we accessed a merchant system or made a decision about platform approval, eligibility, or inclusion.
How we use it
We use submitted information to run scanners, prepare reports, respond to questions, support purchases, provide requested services, improve the site, and keep account or workflow history available to the right customer.
Optional analytics and advertising measurement
If you choose Allow measurement, the site loads Google tags for page views and selected funnel events such as scanner starts and completions, sample-report views, accepted or saved leads, and checkout starts. Google may receive a shortened page path and title, whitelisted campaign values, and browser or device context. We do not send scanner inputs, catalog files, email addresses, names, form messages, access tokens, or business prefill values through those tags. Internal and token-gated delivery routes are excluded, and advertising user-data and ad-personalization consent remain denied.
Campaign attribution
With measurement permission, we keep first-touch and last-touch landing pages, referring pages, UTM campaign values, and advertising click identifiers so a submitted lead can be connected to the campaign that produced it. Query strings and fragments are removed from stored landing and referring URLs. Attribution is attached only to scanner or contact records you choose to submit; choosing Necessary only clears browser attribution and stops new attribution capture.
Browser storage and retention
The browser stores your measurement choice. Our Free Product Mismatch Check also uses a necessary signed, opaque browser identifier to apply fair-use limits without storing an email address in the cookie.
Kept only in the current tab when email verification is required.
May be reused to avoid recrawling the same public pages.
Stored as a pseudonymous fair-use record.
Stored only when measurement is allowed or a lead is submitted.
Used for fair-use limits; the cookie does not store your email.
Pending form data is cleared when it is restored, when the check completes, or when the tab session ends. Requester emails, free-text notes, and pathway selections are not included in the shared public-evidence snapshot.
Purchase, delivery, security, and account records may need different retention periods for operational or legal reasons.
Private Root-Cause Audit uploads
After a qualified Root-Cause Audit is paid, you may submit one source catalog or export, one target feed or diagnostic export, and optional screenshots through the private audit workspace. These files are used to verify product-data discrepancies and prepare the requested report.
Raw audit uploads are scheduled for deletion 30 days after report delivery. You may ask for earlier deletion, subject to payment, security, dispute, delivery, or legal records we still need to keep. Limited attachment metadata, file hashes, delivery history, findings, and payment records may be retained separately for those purposes.
Staging review environment
Pre-release staging is intended only for owned or synthetic test information. It uses separate storage and workflow records, redirects test email to a controlled sink mailbox, disables advertising measurement and outbound prospect delivery, and is not a production service. Reviewers should not submit a real business catalog, customer list, credentials, or other production data to staging.
Service providers
We may use trusted service providers for hosting, storage, payments, email delivery, scanner workflows, and, when you allow it, analytics or advertising measurement. Those providers support the services requested through Autonomous Path or the optional measurement choice you make.
Your choices
You can ask us to review, correct, or delete information tied to your inquiry or account, subject to records we need to keep for payment, security, delivery, or operational reasons.
Contact
Questions about privacy or site data can be sent to support@autonomouspath.ai.