Listwright™
Menu

Last updated 17 October 2026

Your data, explained.

This privacy notice explains what Listwright stores, how product data is used and how to request a copy, correction or deletion.

What is collected

Your account. An email address, the shop name you chose, and your password stored as an argon2id hash. The password itself is never written down anywhere and cannot be recovered from what is kept. A forgotten password has to be replaced, not looked up.

What you upload. The rows of every spec sheet you submit are stored as the canonical record of each product, along with a fingerprint of each row. That fingerprint is what lets an unchanged product be skipped instead of regenerated, so the sheet contents are kept rather than read and discarded.

Sales you record in Telematics. When you enter a sale, import a sales CSV, request a shop import or enable automatic shop updates, we store the sale reference, product key, marketplace, date, quantity, currency, gross sales, refunds and fees in your account. These records power your sales charts and tables. Do not include customer names, email addresses, payment details or other customer information in references or product keys. Direct shop imports also retain shop and order-line identifiers to update repeat imports and honor marketplace deletion requests. Sales are not sent to the listing generator. You can delete individual records in Telematics; deleting your account also deletes its sales records.

Automatic sales updates. These are off until you enable them for a connected shop. You can choose hourly or daily updates, which refresh a rolling 30-day window of sales and available refunds even while this site is closed. We store the schedule, update times, counts and status with the shop connection. You can pause updates; an update already in progress may finish. Deleting an imported sale does not delete the order from your shop, and the record can return on a later import.

What is generated. Every version of the copy written for a product is kept, along with the run that produced it: title, description, tags and sku. Older versions are never overwritten.

Runs. When each batch was submitted, how many products it covered, how many credits it cost, which items failed and the rules they broke.

Paid shop audits. When you request an audit of a connected shop, we read a sample of its listings and save the shop URL and identity, listing identifiers and titles, scores, recommendations, audit date and credits charged. These reports remain available after you disconnect the shop. Account deletion and applicable marketplace privacy erasure remove them. Audits use content checks on our server and do not send listing content to an AI model. The free pasted-listing and CSV checks do not save audit reports.

Sessions. When you log in, a record is stored holding your account, the expiry, and a SHA-256 of the session token. The token itself is not stored, so the records cannot be read to impersonate you.

Server logs. Requests are logged with a request identifier, the method and path, the response status, and the account and user the request acted as. These are ordinary operational logs.

A connected shop, if you connect one. Connecting is optional and available for the marketplaces shown on the shops page. If you connect one we store the shop's identifier, its name, the permissions you granted, and the access and refresh tokens the marketplace issued. Those two tokens are encrypted before they are written down, with a key held in this server's configuration and not in the database, so a copy of the database on its own does not open them. We never receive, ask for, or store your marketplace password: you approve the connection on the marketplace's own site and it hands us a token instead.

What a connected shop means

There is a section for this on its own because it is the one part of this service that reaches outside it, and because you should be able to check the claim rather than take it.

Reading. Imports store product information such as titles, descriptions, tags, SKUs, prices, quantities and categories. Shopify imports active products and reads variant facts. EBay imports items managed through its Inventory API. Other eBay listings may need migration first. Amazon connections, when available, use existing seller listings. Sales imports require read access to Etsy transactions, Shopify orders or eBay fulfillment orders. Marketplace responses may contain customer fields; we do not retain customer names, contact details, addresses or payment credentials in Telematics. Shopify queries request only the order and product fields needed for analytics. Product image URLs may be returned by marketplaces. We do not download the images for generation.

Writing. You choose when to send a product's copy back. Shopify updates its title, description and tags. EBay updates its inventory title and description while retaining the other inventory fields. Existing products keep their price, quantity and photographs. Creating an Etsy or Shopify draft or an unpublished eBay inventory item also sends required product facts that you supplied. New items stay off sale until you publish them in the marketplace. Amazon supports title and description updates to existing imported listings. Amazon validates and processes submissions.

Ending a connection. Disconnecting deletes our saved access tokens. Imported products, generated copy, sales and paid audit reports remain in your account. We retain their marketplace source so an authenticated marketplace privacy request can remove those products, their generated copies, sales, audit reports and connection data, including after disconnection. Shopify app removal deletes connection tokens, and its later shop-data deletion request removes imported data. EBay account-deletion requests remove the associated data and prevent reconnection of that deleted eBay identity. A product that combines imported data from multiple shops is removed as a whole if one of those shops requests erasure. Your separate ListWright account and products that have no imported data from that shop remain.

What leaves this server

Generating listing copy can involve sending the contents of a product's row to Anthropic's API, which is the model that writes it. It is sent as text with no tools and no access to anything else, and it carries no account details, no email address and no password. Just the product row and the instructions for writing a listing.

The other place data leaves this server is a marketplace you have connected, and only in the two directions described above: reading your listings when you import or request a shop audit, reading sales when you request an import or enable automatic sales updates, and sending copy and the product facts needed for your requested update or creation when you press publish. With no shop connected, that never happens.

An instance can instead be run with a deterministic generator that builds the copy from your fields on this server, in which case nothing is sent anywhere. If it matters to you which one this instance uses, ask whoever operates it.

There is no analytics service, no advertising, no error-reporting service and no embedded fonts. The scripts this site runs are served from here and not from a content network, specifically so that loading a page does not tell somebody else who is reading it.

One exception, on two forms. The demo on the home page and the sign-up form each load a bot check from Cloudflare, which sees your IP address and enough about your browser to judge whether you are a person. It is not used to identify you afterwards, and no other page loads it. Those two carry it because they are what a stranger can set running without an account: one writes a listing and sends an email, the other opens an account with free credits on it. Both cost us money, and a script can ask for either over and over.

Cookies and browser storage

Four, all HttpOnly and SameSite=Lax, and none of them used to track you across sites or to build a profile of you.

CookieHoldsLasts
lw_session An opaque identifier for a login held on the server. Not a credential on its own. Until the session expires, or you log out
lw_form A token the login and signup forms echo back, so another site cannot post them on your behalf. 30 minutes
lw_last_run The identifier of the last run you started, so the dashboard can link back to it. 7 days
lw_src A short label naming the advertisement you arrived from, when you arrived from one, so we can count how many accounts a campaign produced. It holds nothing about you, only which link was clicked, and it is deleted the moment an account is created. 30 days, or until you sign up

lw_src is the one that deserves a sentence of its own, since it exists because we buy advertising. It is written by this server, read by this server, and never sent anywhere. There is no advertising pixel on this site and no third-party script that could see it, which is the whole reason it works this way: the alternative is the ad network watching you read, and counting our own signups is not worth that.

Because none of these follow you to other sites or build a profile, there is no consent banner to click through.

Sales targets saved in your browser. The Telematics goal planner saves only your chosen target amount in this browser's local storage. A hashed key separates targets by account, currency, marketplace and report length without storing your account identifier or login token. Targets are not sent to the API or synced across devices. Changing the report end date or sales page reuses the target for that report length. Use Clear target to remove the selected target, or clear this site's browser storage to remove all saved targets. They can remain after logout or account deletion until you clear them. If browser storage is unavailable, a target lasts only for the current page visit.

Before & After change journal. Experiment names, notes, dates, comparison lengths, currencies and marketplace selections stay in this browser's local storage under a separate hashed key for each account. Names and notes are not sent to our servers. When you compare a change, we read your account's saved sales for the chosen dates, currency and marketplace. Comparisons do not modify sales or contact your marketplace. Notes do not sync across devices and can remain after logout or account deletion. Remove a change in Telematics or clear this site's browser storage to erase them. If storage is blocked, the journal says that changes last only for the page visit.

Who can see your data

Every record carries the account it belongs to, and every query is restricted to that account. Ask for another account's product or run and you do not get a filtered result. You get nothing at all, and it reads as though the thing was never there. Signing up creates an account of its own. It gives you access to nothing that already existed.

Whoever operates this instance has access to the database and can read what is in it. That is unavoidable for anyone running a service on their own infrastructure, and it is stated here rather than left implied.

How long it is kept

Products, runs and generated copy are kept until they are deleted. Sessions stop working at their expiry and are cleared out afterwards. A revoked session stops working immediately. A shop connection is kept until you disconnect it. An authorisation you started and did not finish is deleted within half an hour.

You can delete your account yourself, from the account page. It removes the account's stored data from our service immediately: products, runs, generated copy, sales, API keys, shop connections and sessions all go together. There is no grace period and nothing kept back to restore from, so it cannot be undone. A paid subscription is cancelled as part of it. Browser-saved sales targets and change journals are separate and must be cleared in the browser as described above.

One record outlives the account, deliberately: which payment events have already been processed, kept without the account it belonged to. It holds no personal data, and it is what stops a payment notification arriving afterwards from being acted on a second time.

Asking about your data

Requests for a copy of your data, a correction, or a deletion go to [email protected].

Depending on where you and the operator are, you may have rights over this data under local law that go beyond what is described here.

Changes

The date at the top is when this was last changed. It describes how the software behaves as of that date. If the behaviour changes, this should change with it.