Privacy approach

Current status

Listing SEO Auditor is in private development and is not currently accepting public users. The landing page itself does not collect account information, set marketing cookies, or provide an Etsy login.

Data an audit processes

One audit processes:

• The public Etsy listing URL the user confirms they own, manage, or are otherwise authorized to audit, plus the buyer query they submit.
• Official Etsy Open API fields for that listing, where authorized.
• Keyword terms the seller supplies or approves for the audit.
• Report preferences, warnings, stage timings, and technical error details.
• An optional customer-supplied AI API key, handled as a secret.

The service does not request Etsy passwords, orders, receipts, buyer information, private sales data, or permission to edit listings.

How evidence is collected

Version 1 collects Etsy data through the official Etsy Open API and no other route. It does not screen-scrape, crawl, or otherwise sidestep the API to obtain Etsy data, and it uses no browser automation, headless browser, or proxy pool against Etsy.

Collection is started by hand, once, by the seller running the audit, and covers the single listing they confirm they are authorized to audit. It is a snapshot, not a feed: nothing runs on a schedule, in the background, or after the audit ends. Requests stay within Etsy's published rate limits.

Retention and expiry of Etsy content

Etsy's API Terms of Use limit how stale displayed Etsy content may be: listing content may not be shown more than six hours older than it is on Etsy, and other Etsy content not more than twenty-four hours older. A timestamp alone does not satisfy that rule, so the service expires the content rather than merely labelling it:

• Raw Etsy API responses exist only for the duration of the run and are discarded once the report is written.
• A stored report carries the time its Etsy data was retrieved and an expiry six hours later. After that point the report is no longer presented as Etsy content: the Etsy-derived fields are withheld and the report offers a re-run instead.
• Stored reports embed no Etsy images. Images are analyzed during the run and described by measurement, not copied into the saved output.
• Etsy content is deleted from run storage on the shorter of the configured retention window or a deletion request, and no standing cache, mirror, index, or database of Etsy listings is built.
• Etsy data is not sold, redistributed, shared with other users, or used to train a model.

The seller's own analysis—scores, findings, and suggested copy—is the seller's to keep. The expiry applies to content retrieved from Etsy, not to conclusions drawn about the seller's own listing.

Where this description and Etsy's API Terms of Use differ, Etsy's terms govern and the service will be changed to match them.

AI processing of Etsy content

Stated plainly, because it is material: at the seller's request, content retrieved from the Etsy Open API for the audited listing—its title, tags, description, and derived measurements—is sent to a third-party AI provider, which returns the wording of the recommendations. This happens on every audit that produces suggested copy.

• Only the audited listing's own content is sent. No other member's listing content is included.
• Routing is configured so request content is not used to train the provider's models, and provider-side retention is set to the minimum the provider offers.
• Model web search and grounding stay disabled, so the model cannot pull in evidence from outside the audit.
• The model may only organize evidence already gathered. Its output is mechanically checked, and any keyword it invents is rejected before the report is written.
• A seller may supply their own AI provider key, in which case the request goes to their account under their own terms.

A seller who does not want AI processing can use the deterministic findings, which are produced without any model call. The production audit form will provide a clear AI-processing control, and turning it off will prevent any request to OpenRouter or a model provider.

Why the data is used

Submitted and captured evidence is used only to validate the request, produce the listing audit and report, prevent unsupported keyword recommendations, diagnose failures, and control usage and billing.

Service providers

The service relies on:

• Apify for Actor execution, storage, and billing.
• Etsy for authorized Open API data.
• OpenRouter and a selected model provider for constrained report generation.

Production AI routing will be configured to avoid model training on request content. Web search and grounding will remain disabled so they cannot introduce unrelated evidence.

Secrets and retention

API keys will not be printed in logs, reports, datasets, exceptions, or diagnostic snapshots. A customer-supplied AI key will override managed keys and will be used only for that request.

The application is not planned to maintain a separate customer database. Audit inputs and outputs may remain in the user's Apify run storage under the retention and deletion controls of that account. Operational logs will be minimized and must not contain credentials.

Etsy member content

Version 1 reads one listing: the one the seller confirms they own, manage, or are otherwise authorized to audit. Listing text, images, and public counters may belong to Etsy members, change over time, and are used only to produce that seller's own report.

Reports are not published, shared between users, or resold as a dataset, and the service will not reproduce another shop's protected creative work.

Your choices

Before public beta, users will receive clear information about stored outputs, optional bring-your-own-key processing, and how to delete their run data through Apify. Requests or privacy questions can be sent to digitasfortuna@gmail.com.