This is the previous Privacy Notice. Read the current notice, including browser-only comparison and the public contact address.
What the account stores
FeedGuard stores the email address you enter, a password hash, a hash of your recovery key, account dates and the version of terms accepted. Raw passwords and recovery keys are not stored in the account database. A recovery key is shown when you register and replaced after successful recovery.
Your email identifies your account. Confirmation and recovery by email are available when the account security sender is enabled. Marketing messages remain disabled. We store hashed session tokens and their expiry times to keep you signed in.
If you add a passkey, we store its public key, credential identifier, your chosen name, device transport and backup metadata, verification counter and use dates. Your private key and biometric data are not sent to FeedGuard. Device verification is required. Short-lived challenges expire after five minutes; enrollment challenges are bound to your current session and password hash. Recovery removes all passkeys and signs out all sessions. Removing a passkey also signs out other sessions.
Email confirmation and recovery use short-lived, one-use hashed tokens. Confirmation requires the same signed-in account; email recovery is available only after confirmation. When account email sending is enabled, Resend processes your email address and a security message containing the link. The application stores token hashes and a limited delivery history, not raw links or message bodies. Delivery records last until account closure; new requests replace previous links. Verification links expire after 24 hours and password-reset links after 15 minutes. Email recovery replaces the recovery key, removes passkeys and signs out all sessions.
The service owner can view account registration and last sign-in dates, email confirmation, connected shop, usage totals and support-request counts in a private per-product account view. No subscription revenue is inferred from free accounts.
What happens to a catalog
Choosing a file reads it in your browser. Running a check sends the catalog and the context you supplied to our application server. The server checks the file and saves the successful report, the original catalog and the latest revised version in your account. This file workflow does not send your catalog to an AI model, Shopify or Google Merchant Center.
The connection is limited to the approved development store. Its basic permission reads product and variant data. Sales & actions can additionally request Shopify aggregate sales reports and product-edit permission, after your separate approval. Sales queries request product IDs, quantities, revenue and recorded-cost totals, not customer or order identifiers. Shopify still requires protected-data approval for its reporting API. We store the shop domain, encrypted access and refresh tokens, requested and granted permissions, connection metadata and hashes of short-lived authorization state.
Only upload product information you are authorized to process. Do not include buyer records, personal information, passwords, access keys or confidential information that does not belong in a product catalog. The credential detector can reject recognized secrets; it is not a guarantee that every kind of sensitive data will be detected.
Saved reports are scoped to your account. Operational service administrators may access the underlying systems when necessary to maintain the service and handle incidents. Do not use the service for regulated or highly sensitive data.
Scheduled checks are off until you enable them. They refresh available data on your selected 6-, 12- or 24-hour interval and save the result in your account; they do not edit the store or send email. Separately opting in to the in-app digest saves a summary when findings change; unchanged checks do not create another notification. Product changes require an exact preview and a separate confirmation. Shopify receives only the selected supported fields or existing-media association. A network interruption can leave a result unconfirmed; the work history records that uncertainty.
How long information stays
The file workspace retains one original and one current catalog/report, plus up to 20 recent change summaries. Sales & actions retains a current product/aggregate snapshot, exact short-lived change previews and a work ledger with outcomes and report observations. The interface shows the 30 latest runs; the account ledger remains until account closure or a verified shop-data erasure request. You can delete the report or close the account; there is no automatic inactivity deletion in the current service. A verified Shopify shop-data erasure request also removes the linked imported catalog, connection, commerce snapshot, previews and work ledger. You can download the current catalog and report from your workspace.
Disconnecting Shopify clears local connection credentials, cancels monitoring and removes pending previews, but keeps saved reports and work history. Deleting a report does not disconnect Shopify. A Shopify uninstall notification clears local credentials without removing the saved catalog.
Closing an account removes active catalog, aggregate reports, previews, work history, monitoring preferences, passkeys, account-linked challenges, email-action and delivery records, session, support and Shopify connection data. If the free check was used, we retain a one-way hash of the normalized email and the time the trial was consumed to prevent repeated free trials. This limited record is retained to enforce the one-free-check allowance. It does not contain your catalog, password or readable email.
Security rate limits use counters keyed by hashed request identifiers. Hosting and database providers process connection and operational metadata. Their logs and backups can retain information after it is removed from the active application database; closing an account does not erase these immediately.
The service uses Vercel for hosting and Neon for PostgreSQL storage. Infrastructure retention and access are governed by their configurations and policies. Downloads remain on your device until you remove them.
Cookies, browser storage and images
FeedGuard uses an essential, HTTP-only session cookie for sign-in. That sign-in cookie is Secure and SameSite=Strict in Production, with a 24-hour session lifetime. Signing out invalidates that session. Passkey verification uses a separate essential HTTP-only, SameSite=Strict cookie for up to five minutes, also Secure in Production. Shopify authorization uses a separate essential Secure, HTTP-only, SameSite=Lax callback cookie for up to 10 minutes. No advertising pixels, marketing cookies or optional analytics are added by the FeedGuard interface.
Catalog editing state and unsaved changes live in the current page. Browsers may restore page state when navigating back. Refreshing reloads the saved server version; it does not restore the free allowance.
Product thumbnails can load directly from image URLs in your catalog. The image host then receives an ordinary browser request, including network information such as an IP address. We set no-referrer on these images. Displaying a thumbnail does not mean the server inspected or verified its contents.
Questions and data requests
FeedGuard is presented under the Agentos brand. Use the private account help area for product questions and privacy requests; do not include passwords or recovery keys. There is no guaranteed response time or outbound email notification at present.
You can remove your saved report in the workspace or close the account yourself. Paid services are not open. Seller details and any additional terms will be provided before a paid offer is introduced.
Open account & data controls