1. Information you provide
When you use a research input, you may provide an Amazon ASIN or public Amazon product URL and choose a marketplace. These inputs are used to validate the request and show the requested AsinSeed page or result state.
If you are signed in and already have an active AsinSeed profile, a Reverse ASIN request creates an owner-bound query record containing the normalized marketplace, ASIN, locale, processing state, and bounded result or failure. The raw idempotency key is not stored; AsinSeed stores only its SHA-256 digest and a digest of the normalized request. Anonymous requests and signed-in identities without an active profile remain transient.
When your current access includes live Reverse ASIN queries, AsinSeed sends the selected marketplace, normalized ASIN, partner code, and a derived request signature to the server-to-server AsinSeed Partner API. We do not send your Clerk identity, local profile ID, email address, session token, locale, plan details, or raw idempotency key with that provider request.
If you create an AsinSeed profile after signing in, we store an opaque profile ID, your language preference, account state, and the verified identity-provider issuer and subject needed to reconnect you to that profile. If paid subscriptions become available and you purchase one, AsinSeed would also store the opaque Stripe customer, price, subscription, checkout, status, billing-period, and event references needed to provide and reconcile access. The AsinSeed database does not store your password, full card number, card security code, bank password, or Stripe-hosted billing contact details.
When you submit the correction form, we receive the selected issue category, language, public AsinSeed page path, and the report detail you enter. The form does not ask for your name, email address, attachments, or account details. Do not place personal, confidential, payment, or credential information in the report.
When you email support@asinseed.com, we receive the information in your message and any attachments you choose to send. Please do not send passwords, payment-card details, secret credentials, confidential customer records, or other information that is not needed to answer your request.
2. Information handled automatically
Like most websites, the hosting and security infrastructure may process technical request information such as IP address, browser and device type, requested URL, referring page, timestamp, and security signals. This information is used to deliver pages, prevent abuse, troubleshoot reliability, and protect the service.
On eligible public pages, Vercel Web Analytics records anonymous aggregate page views, and Vercel Speed Insights samples 10% of Core Web Vitals measurements. AsinSeed also records a limited set of product interactions: a valid Reverse ASIN request starting or reaching a terminal outcome, an approved sample-result filter, selection or successful copy, a reviewed SellerSprite call to action becoming visible, and a qualified manual-reentry fallback being issued. The event values are fixed categories or buckets, not user-entered text.
Before a measurement is sent, AsinSeed removes every query string and page fragment. Account, sign-in, administration, API, and preview page views are excluded, and product-result page views containing an ASIN are suppressed. For an approved result-workspace event, the ASIN path segment is replaced with the fixed label “result-workspace.” Custom event properties do not contain a user or account ID, Clerk fact, request ID, ASIN, keyword, research input, URL query, correction report, credential, payment detail, or free text.
These measurement services do not use third-party analytics cookies. Vercel may process the sanitized or redacted page URL, referring page, approximate location, browser, device, operating system, event category, and performance values with a short-lived anonymous visitor session. Vercel states that the visitor-session seed is discarded after 24 hours.
The identity provider uses cookies and related security data to keep you signed in, prevent session misuse, and complete sign-in, sign-up, recovery, and sign-out flows. The current AsinSeed application does not intentionally set advertising cookies or operate cross-site behavioral advertising.
After an active signed-in profile submits a query, AsinSeed sets one first-party HttpOnly Cookie containing only the random opaque query ID. It is limited to that exact clean result path, expires within two minutes, and lets the destination read the already saved owner result instead of executing the query again. It does not contain the ASIN, result, identity claim, idempotency key, or session token.
3. How information is used
We use information to provide and secure the website, respond to support and correction requests, understand and fix errors, preserve URL continuity, and improve the clarity and accessibility of public content.
For signed-in customers, we use the verified identity key to retrieve only that customer's AsinSeed profile and to prevent another signed-in identity from reading it.
For an active signed-in profile, we also use that same owner boundary to execute a query once, replay the exact saved outcome, list a bounded set of recent query summaries, let the owner retrieve one opaque query ID, download eligible saved keyword rows, and accept an owner deletion request. AsinSeed does not expose another customer's query record.
When that owner chooses to continue a completed saved request in SellerSprite, AsinSeed verifies the profile, ownership, query state, and any selected saved-row identifiers. The response contains only a registry-controlled SellerSprite tool URL and the names of fields to enter again; it does not disclose the query ID, marketplace, ASIN, keywords, identity, token, code, or free text.
Authorized AsinSeed administrators may protect and stage records from the former service solely for a later, separately controlled reconciliation. Staging does not create a current account or automatically link an identity by email address or other contact detail.
We do not sell personal information. We do not use support messages to create advertising profiles.
4. Service providers and external links
AsinSeed is proudly powered by SellerSprite. This relationship does not automatically transfer an AsinSeed query, ASIN, keyword, account, identity, or token to SellerSprite; current continuation links require manual re-entry.
AsinSeed is hosted on Vercel infrastructure. Vercel may process request, security, anonymous page and product analytics, performance, and operational data as necessary to host, secure, measure, and deliver the website under its own applicable terms and privacy practices.
Clerk, installed through Vercel Marketplace, provides sign-in and session services and processes authentication details under its applicable terms and privacy practices. AsinSeed reads only the verified issuer and subject for its own profile mapping.
AsinSeed does not currently provide paid checkout or subscription management on this production site. If Stripe-hosted checkout becomes available, Stripe would process payment method, billing contact, invoice, tax, fraud-prevention, and transaction information under its applicable terms and privacy practices. AsinSeed would send only an opaque AsinSeed profile ID, selected offer, language, and operational metadata, and would not receive or store full card details.
Correction reports and their receipt history are stored in the project's Neon database obtained through Vercel Marketplace. Application rate controls use one-way pseudonymous request keys and do not add the raw network address to the correction Case.
Current AsinSeed profiles and their verified identity mappings are stored in the same restricted Neon environment. Account events are limited to redacted operational facts and do not contain contact details or session tokens.
Owner-bound authenticated query records are stored in the restricted Neon environment for up to 30 days. They reference the opaque local profile ID rather than storing Clerk identity claims, contact details, the raw idempotency key, a session token, network address, or user agent.
Live Reverse ASIN queries are not currently offered on this production site. If they become available for your access, the AsinSeed Partner API would process the marketplace, ASIN, partner code, and derived request signature needed to return live product and keyword fields. The partner credential and signature would stay on the server and would not be included in the saved result or browser response. The Partner API's own retention and deletion periods have not been provided to this website; contact support@asinseed.com if you need more information before using a future live query.
Historical customer staging also uses the project Neon database. Legacy identifiers are stored as keyed one-way digests, record payloads are encrypted with authenticated encryption before persistence, and the public website cannot read these staging records.
The website links to Amazon, SellerSprite, and other external sources. When you follow an external link, the destination receives normal browser request information and applies its own privacy policy. AsinSeed does not control those external sites.
The browser-extension page links to the current Chrome Web Store and Firefox Add-ons listings. The stores deliver the packages and your browser presents the permissions requested before you enable them. The Chrome listing currently discloses personally identifiable information, authentication information, user activity, and website content; Firefox lists tab access and access to AsinSeed, Amazon marketplace, and WeChat hosts.
This policy describes the current AsinSeed website. It does not replace the extension data disclosure or developer privacy policy shown by a browser store, and AsinSeed has not independently audited the listed packages or their runtime data handling.
4. Service providers and external links (continued 2)
The saved-query SellerSprite continuation is a manual re-entry link. AsinSeed does not create a handoff record, one-time code, SSO or OIDC exchange, parameter prefill, cookie, browser-storage item, or destination-consumption proof, and does not place query context in the destination URL. After a qualified fallback is returned, AsinSeed may record only the fixed task intent, destination-tool category, manual-reentry fallback label, and fallback status in Vercel Web Analytics; it does not send the query ID, ASIN, marketplace, keyword selection, identity, or a cross-domain handoff identifier.
5. Retention and security
Current profiles are retained while the account remains active and as reasonably needed to secure, close, or document the account. Correction report text and optional context are retained for up to 180 days. A daily process then removes that content and its linkable digests, while limited non-content Case and receipt/state evidence may remain to document how the report was received and handled. Pseudonymous correction rate-limit buckets expire after one day and are removed by the same process. Protected historical customer staging records are retained for up to 90 days. A daily deletion process removes protected staging payloads when that period ends unless they have already been reconciled; limited import and deletion evidence may be retained to document the operation. Other information is retained only for as long as reasonably needed for the purpose described, to resolve a support request, or to meet applicable legal obligations.
Authenticated Reverse ASIN query records expire after 30 days. The signed-in owner can view a minimized recent-history list and delete a record before expiry, and closing the local AsinSeed profile deletes its current query records. One authenticated daily Vercel retention task invokes bounded Neon deletion functions for expired query records, protected historical staging, and correction content. The history list does not contain keyword rows, full results, failure detail, identity data, or idempotency material. If the current Plan Catalog grants CSV access, a fresh owner and row-limit check can return saved keyword rows directly; AsinSeed does not retain a separate export file.
Deleting an AsinSeed query record removes the mapped result from the AsinSeed application database, but it cannot by itself delete provider-side request records. The Partner API's provider-side retention and deletion behavior remains unspecified.
Resolving a manual SellerSprite continuation does not create a separate AsinSeed handoff record or retain transferred context. The bounded fallback analytics category is not a cross-domain context and cannot prove that SellerSprite consumed or activated a task. After navigation, the browser and SellerSprite control any information you enter there under SellerSprite's own policies.
Anonymous page, product-event, and performance aggregates are retained in Vercel according to the project plan and settings and are not written to the AsinSeed application database. The current Vercel Pro reporting window is 12 months; Vercel may retain provider data longer under its applicable terms. Because AsinSeed does not attach these measurements to an account or user ID, it generally cannot identify or retrieve an individual measurement by your identity.
Automated public-service monitor runs and component checks are retained in the project Neon database for up to 90 days, and resolved incident history for up to 365 days. These records contain fixed component identifiers, bounded outcome and timing fields, and generic error codes; they do not contain user input, account data, request or response content, credentials, network addresses, or third-party availability data.
When you close an AsinSeed profile, we mark the local profile closed, revoke its AsinSeed identity connections, and disconnect any current historical-customer link. We retain the opaque profile and identity mapping, closure timestamp, and limited immutable lifecycle and historical-link evidence as needed to prevent silent recreation, protect the service, and document the action. Closing the AsinSeed profile does not delete the separate Clerk login account or information retained by Clerk, Vercel, backups, or law.
We use reasonable technical and organizational safeguards, but no internet service can guarantee absolute security. You are responsible for avoiding sensitive information in public inputs and support messages.
6. Your choices and rights
Depending on where you live, you may have rights to request access, correction, deletion, restriction, objection, or a copy of personal information associated with you. You may also ask a question about how a request was handled.
If you have an active profile, the Your account page lets you view recent query summaries, delete an individual query record, download a JSON copy of the local AsinSeed profile and redacted connection/lifecycle facts, or close the local profile after an explicit confirmation. When the current Plan Catalog grants it, you may also download saved keyword rows from a completed query as a CSV file. The downloaded file is then controlled by your browser, device, and chosen destination. These self-service controls do not include or delete authentication-provider, hosting, backup, support-email, or legally retained records.
When the current first-party query interface creates a saved query, it returns an opaque query ID that only the signed-in owner can use to retrieve or delete that record. The private history list exposes only minimized request and lifecycle fields; closing the local profile deletes all current query records for that profile.
Email support@asinseed.com with the subject “Privacy request.” We may need enough information to understand and verify the request, but we will not ask you to send a password or full payment-card number.
7. Children
AsinSeed is a business research service and is not directed to children. Do not submit personal information about a child through the research input or support channel.
8. Changes and contact
We will update the date on this page when this Policy changes. If a change materially affects how information is handled, we will provide an appropriate notice on the website before or when the change takes effect.
For privacy questions or requests, contact support@asinseed.com.
Applicable boundary
This policy records current product disclosures and handling boundaries; rights and duties required by applicable law remain controlling.
Questions?
Contact support@asinseed.com.