Privacy Policy

JC Auto Lights LLC, doing business as Lotwize ("Lotwize", "we"), operates lotwize.ai and the Lotwize application, and is the data controller for the information described here. You can reach us about privacy at support@lotwize.ai.

This policy covers the whole service: the website, the application, and the two services that support it (the eBay connection service and the part-identification service).

Your account. An email address and a password. Your password is verified by Supabase, our sign-in provider, and is never stored by us or visible to us. We do keep a one-way fingerprint of your last few passwords — not the passwords themselves, and nothing that can be turned back into one — so that a new password can be refused if it is one you have used before. Each is deleted with your account. If you sign in with Google or GitHub instead, we receive your email address from them and nothing else: no contacts, no profile information, and no access to anything else in those accounts.

Two-factor authentication. For an authenticator app, the shared secret your app was set up with. Our sign-in provider holds it, and so do we: without our own copy we could not check a code for somebody who is not signed in, which is what lets you reset a forgotten password with your authenticator instead of an email link. For text-message codes, the mobile number you enrol. Turning the feature off deletes both the number and the secret.

What you put into the app. Photos you upload, your listing drafts and their descriptions, your preferences and templates, and information you submit through our contact form.

Your eBay connection. The access and refresh tokens eBay issues when you connect, your eBay username, your business policy names, and a cached copy of your active listings so the app does not have to re-fetch them repeatedly, and, for the Seats page, the title, price, sale date, link and picture address of each listing you sold in the last 90 days, which we delete once it is older than that. For each offer eBay holds for you that was never published, we also keep its offer reference, SKU and title, as eBay reports them, so we can show it in Ended, labelled “Never published”. We also keep a copy of each such offer’s first photo, taken from the photo addresses eBay holds for it, so it can be shown beside it; that copy is kept with your other photos, including in our backups, and is deleted once the offer leaves that list. That list is updated each time Lotwize reads your listings from eBay, except that we keep the previous list when a read looks incomplete; an offer leaves it once you relist it, and the whole list is deleted when you disconnect eBay or switch to another eBay account. When you undo a listing you have just published, we keep a note of its eBay item number, eBay’s offer reference for it, which of your eBay accounts it was on and when you undid it, so that it does not come back in Ended as “Never published”. We never see or store your eBay password.

Corrections and Part # Lookups. Until November 8, 2026, when you fixed one of our identifications and applied it to your listing, we kept what we predicted, what you changed it to, a reference to the photo it came from, and the time. Lotwize no longer records these corrections; the ones recorded before then are kept as this policy describes. We keep no copy of that photo for a correction: it is deleted on the same schedule as your other photos. When Part # Lookup cannot fill a listing, we keep a record of that lookup: the numbers read from your pictures or typed in, which picture each came from, why each was not used, the web searches made for them and the websites they found, what those websites said the part is, and the time. We keep no page address or page title from another website or seller, no picture, and no price, and none of it is shown in the app. We keep each record for 180 days. We review both and use them to improve how Lotwize identifies parts and looks up part numbers, for every seller and not only for you.

How you pay. Which monthly plan your account is on, whether you have started your trial and when it ends, your spending cap, what you have used in each billing month and what each identification and listing was charged, what each bill came to, and what you owe. From Stripe, our payment processor, we keep its reference for your customer record and for each payment, whether a charge was declined or disputed, and, when you start a trial, the fingerprint Stripe gives your card: a code that lets us tell a card that has already had a free trial, which is not the card number and cannot be turned back into it. When you start a trial we also keep a one-way hash of your email address, made with a secret key that stays on our servers, so that the address cannot start a second free trial; it is not the address and cannot be turned back into it. Your card number is not among these: the card form belongs to Stripe and the card never reaches us.

Records of activity. A short log of actions you take in the app, such as a listing published or a draft created, which drives the dashboard counts.

Ended listings. When you end a listing in Lotwize, we save a copy of it first, so you can relist it. We save its photos, its eBay item number, eBay’s offer reference for it, which of your eBay accounts it was ended under, and which person in your business ended it. We also save a copy of its text: the title, price, item specifics, description, condition and eBay’s Seller notes, category, package size and weight, and SKU. With the text we save which business policies and location it used, and the photo addresses eBay held for it. Once eBay ends it, we also record when. We keep all of this even if eBay does not end the listing. We keep it for as long as the business account exists, or until you relist the listing. If you archive a listing, we keep it too: archiving hides a listing, it does not delete it. When eBay accepts a relist, we delete the copy of its text we kept and the listing leaves Ended; its photos are no longer kept for it and are deleted the next time we clear out photos nothing uses.

Technical records. Your IP address, for two purposes. First, rate-limiting abuse, where it is kept about an hour. Second, if you turn on two-factor authentication, recognising a browser you have signed in from before, so that you are not asked for a code at every sign-in; that list holds the networks you signed in from (not your exact address) and is held in a cookie in your own browser, described below, and lasts thirty days. The free identifications offered on the logged-out demo are counted against a random token in your own browser, not against your address, and that count is kept up to two days. Ordinary server logs, which can contain an IP address, a page path and an error reference, and which our host retains for a short period. Separately, which browser and system you signed in from (for example “Chrome on Windows”) and when, so that Settings can list the devices signed in to your account and sign the others out. There is no IP address and no location in it. Each entry is deleted when that browser signs out, when you sign the other devices out, and with your account. An entry not used for thirty days is no longer shown, and is deleted the next time the list is read.

The condition you describe. You write the part’s condition in your description. To compare similar listings with yours, and to fill eBay’s Seller notes, Lotwize reads what you changed or added compared with your description template. When you open similar listings, that text goes to Anthropic, our AI provider, which compares it with the condition each listing states.

Part # title learning, if you use it. Where your account has Part # Lookup, this learns how you title your parts listings. It reads, through your own eBay account, the titles and eBay categories of your parts listings that are live now and of those sold or ended in the last 90 days. How many follows the step you choose before you press it: at Standard up to 1,000 live and 2,000 sold or ended, sending as many titles as fit its budget, and at 10%, 25%, 50%, 75% or 100% that share of them, up to the number the step shows. A category whose eBay name already appears in its titles needs nothing sent. For the others it sends the titles and the names of their eBay categories to Anthropic, which says what you call the part in each category. It sends no prices, descriptions or photos. We keep only what it learns: for each category, the name you use for the part and the order of your titles, and across your store how you write years, capitals and sides. That is kept with your preferences and deleted with your account. The titles themselves are held in memory while it runs and are then discarded.

Learn your style, and the notes you moved, retired November 2, 2026. Lotwize no longer learns where you put condition notes, no longer remembers notes you moved or lines you corrected, and sends nothing to Anthropic for either. A style it learned before then, and the moves and corrections it remembered, are no longer used. They are deleted with your account, and you can ask support@lotwize.ai to clear them sooner. To limit the free style scan to one per internet connection, we kept a one-way hash of the IP address each free scan came from, made with a secret key that stays on our servers. The hash only limits the free scan to one per connection. We keep only the hash, never the address, and the hash cannot be turned back into it. We keep it for as long as the service runs, and it is not deleted with your account.

Other sellers’ listings. The comparison panel shows eBay listings for a part like yours, fetched from eBay’s own APIs when you open it. It shows only listings that are active on eBay right now. We never fetch, show or read sold, completed or ended listings from other sellers, and we hold no history of what anything sold for. That content belongs to the sellers who wrote it and to eBay. We show it and we ask our AI provider to summarise the condition each listing states. So that a listing’s similar listings can be shown again without a second search, we keep that search’s results for that one listing: each listing’s title, price, link, photos and condition notes, and not its seller’s name. They are deleted six hours after the search, and with your account. What we hold is our own one-line summary of that condition, kept in the server’s memory for six hours so the same part is not read twice, and it is not written to disk or attached to your account. We compute nothing from their prices and we never suggest one.

We do not collect payment card information beyond the card fingerprint described under How you pay, and no card number; we collect no government identifiers, and no location beyond what an IP address implies. We do not use tracking or advertising cookies, and we run no third-party analytics.

We use it to provide the service you have requested: identifying the part in your photos, drafting the listing, publishing and revising it on your eBay account, keeping your drafts and preferences, and keeping your account secure.

Your corrections and the Part # Lookups that could not fill a listing improve the tool’s accuracy: we review them, and we may use them to evaluate and improve how Lotwize identifies parts and looks up part numbers. Every correction submitted through Submit anchor before November 6, 2026, and every photo kept for one, has been deleted, and none of them is used to train or evaluate anything. We keep no photo of a listing you publish for training. Aggregate, non-identifying counts tell us whether the service is working.

We do not sell personal data. We do not share it for advertising, we do not use it to advertise to you, and we do not permit our AI provider to use your content to train its models.

Automated identification and writing produce a draft. Nothing is published to eBay until you publish it, and no decision with a legal or similarly significant effect is made about you automatically.

Where the law asks us to name a basis for each use, these are ours.

To perform our contract with you: your account, your photos, drafts, preferences and templates, your eBay connection and tokens, your plan and what you owe, and the mail we send you about your account. Without these there is no service to provide.

Because the law requires it: the billing record that outlives your account, and anything we must keep or disclose under tax, accounting or legal process.

Our legitimate interests, weighed against yours: keeping accounts secure and rate-limiting abuse; the short activity log behind your dashboard counts; reviewing the corrections you applied before November 8, 2026 and the Part # Lookups that could not fill a listing, to improve how it identifies parts and looks up part numbers; aggregate, non-identifying counts telling us whether the service works; keeping the fingerprint of a card, and a one-way hash of an email address, that has had a free trial, so that neither can start a second one; and collecting what an account still owed when it was deleted. We use the least data that answers the question, and you may object, as set out under Your rights.

Your consent, which you may withdraw at any time: text-message two-factor authentication and the mobile number it needs; the photo tools, each off until you switch it on: the stock or SKU number reader, which sends the last picture of a listing to Anthropic, our AI provider, to be read and then discarded, and, with the turn-upright tool also on, to find which way up that picture goes; and the country-of-origin reader and the text-photo sweeps, which read the other pictures on our own servers and send none of them anywhere; and the part number reader, which sends the areas of your other pictures that carry printed text, cropped to that text, to Anthropic to be read, and the text read from them to a web search service and to Anthropic to check it against the web pages the search finds for it. You can switch the photo tools and text-message codes off in Preferences at any time, and switching one off stops it for every draft you save afterwards. Withdrawing consent does not undo what was lawfully done before you withdrew it, and for corrections already used in training, what deletion can and cannot reach is set out below.

We rely on a small set of processors, each for one job. We share only what that job needs.

Supabase. Sign-in, and the database holding your account, drafts, preferences, eBay connection record and corrections, and the messages you send us through the contact form. Also the private storage bucket holding the offsite backup copies of your photos. As our sign-in provider it also keeps its own security log of sign-in events, which records the email address and the IP address each one came from.
Render. Hosting for the website and both background services, and the disk holding your photos, caches and logs. That includes the copy of each photo you publish that our eBay connection service holds until eBay has collected it, described under How long we keep it.
Upstash. The key-value store in which our eBay connection service keeps your eBay access and refresh tokens, indexed by your eBay username.
eBay. Your listings, photos and item labels, sent through eBay’s official APIs so your listing can be published and revised.
Anthropic. For Part # title learning, the titles of your own parts listings and the names of their eBay categories, as described under What we collect. The listing text we ask it to draft or rewrite: your title and item specifics. For similar listings, what you changed or added to your description template to describe the condition, as described there too. One listing photograph is sent whole, and only when the stock or SKU number reader is on: the last picture of a listing, which you have told us is your stock or SKU number, so the number on it, written by hand or printed on a tag, can be read into that field. With the turn-upright tool also on, the same picture is sent turned four ways so Anthropic can say which way up it reads. Whatever else is in that frame is sent with it. When the part number reader is on, the areas of your other pictures that carry printed text are sent, cropped to that text and not as whole pictures, to be read, and the text read from them and the search results found for it are sent to check whether a string is a headlight's part number. The country-of-origin, text-photos-last and turn-upright tools read your other pictures on our own servers and send none of them. Anthropic’s commercial terms state that inputs to its API are not used to train its models. With the stock or SKU number reader off, no photograph leaves our own servers whole; with the part number reader off too, no part of one does. We do not send your account information.
Twilio. Your mobile number, solely to deliver the one-time codes described in our Terms, and only if you turn on text-message two-factor authentication.
Stripe. Our payment processor, which charges your card for your plan and anything past its allowance. The card form is Stripe’s own, so your card information goes to them and never to us. For each monthly charge we send Stripe the amount, a reference to your Lotwize account and to the billing month it is for, and the email address Stripe sends its receipt to. Stripe tells us whether a payment succeeded or was declined, and whether you have disputed one, and gives us its reference for your customer record and for each payment and, when you start a trial, your card’s fingerprint. When you save a new card, the card it replaces is deleted from Stripe. When you delete your account, your saved card is deleted from Stripe, as described under How long we keep it. Stripe keeps its own record of the payments it processed, under its own terms.
SendGrid. The mail we send you (a password reset, a confirmation link, an invitation to a seat) and the address it is sent to. Mail you send us through the contact form does not go this way.
Google. One page, the text-message consent page, loads a font from Google Fonts, which receives your IP address in order to serve it. No other page loads anything from Google. Messages you send through the contact form are stored in our database at Supabase, as above, and we answer them by email from support@lotwize.ai.
Serper. When the part number reader is on, the text read off your pictures is sent as web search queries. A part number you type in for Part # Lookup is sent the same way. For a result page we cannot fetch ourselves, the page address is also sent to Serper’s page reader, which fetches the page for us. No picture and no account information is sent.
Brave. When Serper cannot answer, the same search queries can go to Brave Search instead. No picture and no account information is sent.
Cloudflare. Every request to lotwize.ai passes through Cloudflare’s network, which delivers the site and protects it from attacks. Cloudflare receives your IP address and the information about each request, such as the page asked for and your browser’s user agent, for that purpose only. Separately, when you create an account, with an email address and a password or with Google or GitHub, and before your first try of the demo: the sign-up page, the Google and GitHub buttons on the log-in page and the demo page load Cloudflare Turnstile, which checks that a person, not an automated script, is creating the account or using the demo. It receives your IP address, your browser’s user agent and technical signals from your browser and connection, solely to tell people from bots, and tells us only whether the check passed. To confirm that result, we send Cloudflare the IP address the request came from. Most people see nothing; if Cloudflare is unsure, it shows a box to tick. The bot check does not run on any other page.

These providers are in the United States, and your data is processed there. If you are outside the United States, using Lotwize means your data is transferred there; where the law requires a transfer safeguard, we rely on the standard contractual clauses in our providers’ terms.

We may also disclose information if the law requires it, or to protect the rights and safety of our users or ourselves. If our business is transferred, your data may transfer with it, and we will notify you before that happens.

Traffic is encrypted in transit. The access and refresh tokens eBay issues are held by our connection service, never sent to your browser, and can additionally be encrypted at rest. Passwords are handled by our sign-in provider and never reach us. Two-factor authentication is available on every account, and sign-in attempts are rate-limited. Each seller’s data is separated so one account cannot read another’s.

No system is perfectly secure. If a breach affects your personal data, we will notify you and any regulator we are required to notify, without undue delay.

Your account, drafts, preferences and corrections stay while your account is open. An account with no active subscription for 30 days (cancelled, counted from the end of the last paid month; paused for an unpaid bill; or never subscribed) is deleted no earlier than that, after an email at least 7 days before that names the date in UTC and how to keep it. This does not apply to the owner account, to accounts we have given free use, or to a seat on its own; a seat is never deleted for this reason, but goes with the business account above it. Drafts and their photos also follow any retention window you set yourself in the app. The photo backup keeps a photo you delete for 30 days and then removes it, and the whole backup is removed when you delete your account. Ended listings keep the same retention as the rest of the business account: their text and photos stay for as long as it is open, including after you archive them, until you relist them, and their photos are part of that same backup. Lotwize keeps a record of who in a business published, ended, relisted or revised each listing, or changed its promotion, and when, with a copy of the listing as it was before each revision or promotion change, so that the business can see and undo what a seat did. Each entry is deleted after 15 days. When the administrator deactivates a seat, or a seat deletes its own account, the business account keeps that seat’s name and email address and its part of that record for 7 days, so the administrator can look through what the seat did and undo it, and then deletes them; if the administrator permanently deletes the seat, they are deleted at once. After that the business keeps only how many listings the seat published, and the business’s own copies of listings the seat ended, both labelled “Removed seat” and without the seat’s name or email address. Your eBay tokens are removed when you disconnect eBay, when you delete your account, or when eBay tells us you have closed yours. When you disconnect an eBay account or switch to another one, we keep its account name and a one-way fingerprint of its old sign-in, never the sign-in itself, so that if eBay later tells us that account was closed we can still delete the copies of its ended listings, their photos and its remembered policies. When eBay tells us an eBay account was closed, we also remove the data we hold from that eBay account wherever we can tell it came from that account, apart from the billing record described below. Most rate-limit records are deleted within about an hour, and the demo’s free-identification counter within two days; records of sign-in code attempts, which carry no IP address, are kept for about 24 hours; server logs turn over on our host’s own short schedule.

When you publish a listing, our eBay connection service holds a copy of each of its photos at an unlisted web address until eBay has collected it: that copy is deleted 72 hours after eBay last fetches it, or 60 days after it was made if eBay never fetches it. The copy is not filed under your account, so it is deleted on that schedule even after you delete your account, and not sooner.

Some records outlive the account. The first is your billing record. It lists each charge and when it was made; each identification and listing it was for, by the photo’s file name or the listing’s reference; changes to your plan and your spending cap, and who changed the cap; any dispute and any charge that failed; and Stripe’s reference for your customer record and for each payment. While a charge is still being attempted it also holds the email address that charge’s receipt goes to. It holds no card number. The second is the fingerprint of any card used to start a trial, and the one-way hash of the email address of any account that started one, each with the number of the account it was first used on and when. We keep them with no end date, and only so that the card or the address cannot start a second free trial, on a new account or any other; neither can be turned back into the card number or the address. The third is your saved card at Stripe, and only if you still owe us money, other than a month under dispute. When you delete your account, your saved card is deleted from our payment processor, Stripe, at the same time, unless you still owe us money, other than a month under dispute. In that case your account and data are still deleted straight away, and what you owe remains owed. That is so whether the charge we make when you delete your account is declined, there is no card to charge, or its result cannot be confirmed. If there is a saved card, it stays with Stripe, where we cannot see it, while we try to collect what is owed. We retry after 1, 2, 4 and 8 hours and then once a day, up to 30 attempts in all, which is about 26 days. The card is deleted as soon as the payment goes through or the attempts run out. If we cannot tell what is owed, or whether a payment went through, the card is kept until we have checked by hand. Anything still unpaid after that stays on our billing record, and so does what you owe if there was no card to charge. The fourth is the one-way hash of an IP address kept for the Learn your style limit, described under What we collect. We keep it for as long as the service runs, with no end date, and it cannot be turned back into the address.

Messages you send through our contact form, including a request for help when you are locked out of your account, are kept in our database at Supabase. A message is deleted 24 months after we have answered or closed it, and at once when you delete your account: deleting an account deletes every message sent from it or from its email address. If you tell us why you are leaving when you delete your account or cancel your plan, the reasons you tick and anything you type are kept without your name, email address or account, so they cannot be found as yours afterwards; anything you type is deleted after 12 months, and the reasons you ticked are kept as counts. If you unsubscribe from our optional emails, your address stays on our list of unsubscribed addresses after your account is deleted, so that we never send those emails to it again. Supabase’s own log of sign-in events, described under Where it goes, is not part of your account; when you delete your account we delete your entries in it too where Supabase lets us, and any it still holds are kept under Supabase’s own terms.

If a bill cannot be charged for any reason and is still unpaid 3 days after the first failed charge, we pause the paid tools. If it stays unpaid for 30 days the account is deleted no earlier than that, after the same warning described above. If we suspend an account for a breach of our Terms, we do not delete it for that alone: suspension stops the work, it does not erase the record.

This section states what deleting your data reaches and what it does not.

When you delete your account we remove your corrections and your photos from our database and our storage, and they are excluded from any future training. The records of Part # Lookups that could not fill a listing are removed with them. Each correction recorded before November 8, 2026 was also appended to a working file that the live identifier reads back, and deleting your account removes your rows from that file too. What remains there are rows written without an account attached: corrections recorded before accounts carried an identifier, and the working-file record of which part numbers a person ticked as real, which has never been stored against anyone (its database copy is stored against your account and deleted with it). We cannot tell whose those are, so we neither delete them on your request nor include them when you download your data. They hold the correction and the photo’s filename, and no name, address or sign-in information.

We cannot remove an individual example from a trained model. If a correction has already been used to train a model, that training cannot be individually undone: a trained model does not store your correction as a retrievable record, and no technique available today can remove one example from an already-trained model. Deletion instead removes the source, ends its use, and lets the correction fall out of the model at the next retrain. We do not promise an erasure we cannot perform.

Corrections are stored against your account so that a deletion request can find them.

Some emails we send are optional, such as a note when a seat is added to your account or an invitation to join someone’s account. Each one has an Unsubscribe link, and you can turn them off in Settings under Optional emails. Emails about security, billing and deleting your account still arrive, because they are part of running your account. To make this work we keep a list of the email addresses that have unsubscribed. An address stays on that list after its account is deleted, so that we never send those emails to it again.

We set three cookies. All three are necessary for the service to operate, none is used for tracking or advertising, and we set no third-party cookies.

The sign-in cookie (session) keeps you signed in. It is signed, HTTP-only, and sent only to lotwize.ai. It also carries a random identifier for this browser, against which our server counts the free identifications on the logged-out demo, which is why it is set before you have an account. The count itself is kept on our server, not in the cookie. For our own staff previewing a new version of the site, it can also carry a flag that shows them that version. Once you have used the demo, or ticked “stay signed in”, it lasts thirty days; otherwise only as long as your browser is open.

The device cookie (lw_device) records that this browser has already answered two-factor authentication, so you are not asked for a code at every sign-in. It holds the networks you have signed in from (not your exact address; a second machine on the same office network counts as the same place), up to sixteen of them, and it lasts thirty days. It is signed, so it cannot be altered to let anyone else in, but it is not encrypted: anyone with access to your browser can read the addresses in it. Clearing your cookies revokes it, as does turning two-factor authentication off and on again, which retires every browser you have trusted.

The sign-up cookie (lz_signup) is set when you create an account with an email address and a password. It lets the page you signed up on notice when you have confirmed your email, so it can carry on by itself. It holds a random reference, not your address or your name, is HTTP-only, is sent only to Lotwize's sign-up address, and lasts two hours.

Cloudflare’s check, described under Where it goes, sets no cookies. It does keep one item in your browser’s storage under Cloudflare’s own address (challenges.cloudflare.com), which we cannot read, and only on the sign-up, log-in and demo pages.

Storage in your browser. Lotwize also keeps a few items in your browser’s own storage for lotwize.ai. They stay on your device, and none is used for tracking or advertising. They are your remembered settings (whether the sidebar is collapsed, a notice you have closed or seen, which tools you have switched on or off, the comparison filter, how many dashboard cards to show, and the two-factor method you used last); the email address you signed up with, while it waits for confirmation, removed once the address is confirmed or you sign in; references that stop a retried publish from listing the same draft twice; and, in storage that lasts only as long as the tab, helpers that carry your email address between the steps of signing in and keep track of a relist in progress. Signing out removes all of them except the publish references, and deleting your account removes those too.

You may ask for access to your data, a copy of it, correction of it, or its deletion; you may object to or ask us to restrict processing; and you may withdraw a consent you have given. Write to support@lotwize.ai and we will respond within the time the law allows.

You can exercise two of these rights yourself, in Settings, without writing to us. Download a backup exports your drafts, your preferences, your listing links, and your own corrections and Part # Lookup records as one file. On an employee seat it exports that employee’s own work; the business’s settings are not theirs to take and are left out. On the owner’s own account it also includes any listings you or your seats have ended in Lotwize, and, if you include photos, their photos; those belong to the business, not to a seat, so a seat’s own backup does not carry them. Delete this account removes everything except the records described under How long we keep it. Deletion is complete and irreversible: your drafts, preferences, photos, their offsite backups, your sign-in, your phone number and two-factor settings, and the eBay tokens we hold for you. On an employee seat, your unfinished drafts and their photos move to the business instead, as described for employee seats below. Listings already published to your eBay account belong to you and stay on eBay. Deleting the business account deletes the copies of your ended listings and their photos with everything else; a seat deleting only its own account does not, because those copies belong to the business, not to any one seat. Deleting your account settles what you owe before the account goes: any billing month that has ended and is still unpaid, other than a month under dispute, and the billing month you are in, each at its plan price and anything past its allowance. During your free trial there is no plan price, so only anything past the allowance is charged. If that charge is declined, or there is no card to charge, your account and data are still deleted, and the amount remains owed, as described under How long we keep it. Nothing is refunded. See our Terms. If you have added employee seats, deleting your account deletes theirs too: each seat’s drafts, photos, offsite backups and sign-in go with yours, and that cannot be undone either. Remove a seat on its own first if you want that person’s account to survive your own.

If we refuse a request, we will tell you why and you may appeal it by replying to that answer; we will respond to an appeal in writing, and if we refuse again we will tell you how to complain to your regulator.

If you are in the EU or UK you may complain to your local data-protection authority. We will not discriminate against you for exercising any of these rights: the service you get and the price you pay do not change because you asked.

California, Colorado, Connecticut, Virginia, Texas, Oregon, Montana and a growing list of other states give their residents rights over personal information. Wherever you live in the US, we give you all of them: to know what we collect and why, to get a copy, to correct it, to delete it, and to limit how sensitive information is used. Use Download a backup and Delete this account in Settings, or write to us.

We do not sell personal information and we do not share it for cross-context behavioural advertising, in the ordinary sense of those words or in the broader sense those statutes give them. We have never done either. Nothing is sold or shared, so there is nothing for a Global Privacy Control signal to opt you out of; if that ever changes, we will honour it. We do not use personal information for profiling that produces a legal or similarly significant effect.

Sensitive information. Two things we hold count as sensitive under those laws: your account credentials, meaning your sign-in and your two-factor secret or phone number, and the contents of your account. We use them for one thing — letting you in and running the service — and for nothing else. We do not use them to infer anything about you, and we do not disclose them for any purpose that would give you a right to limit their use.

The categories we collect, where they come from, why, and how long we keep them are set out above under “What we collect”, “Why we are allowed to use it” and “How long we keep it”. Everything in those sections applies to you. An authorised agent may make a request for you if they show us your written permission; we may ask you to confirm it directly.

A business can invite you to work under its account. You get your own sign-in, your own password and your own two-factor settings, and the business never sees any of them.

What the business does see is your work. Your drafts, the photos you upload and the listings you publish belong to its account, and the administrator can open them. The eBay account you publish to is theirs, the plan that pays for your work is theirs, and the settings you list under are theirs to change.

You accept our Terms and this Privacy Policy yourself, when you first sign in and again whenever they change. The business’s acceptance does not stand in for yours, and yours does not stand in for theirs.

Because the work is theirs, so is the responsibility for it. Under our Terms the business answers for what is uploaded and published from your seat — including whether a photo was theirs to use. Ask them what you may upload if you are not sure.

Two consequences worth stating plainly. You can delete your own account whenever you like, in Settings, and doing so takes your sign-in with it; your unfinished drafts and their photos move to the business. And if the administrator deletes the business account, yours goes with it. That is their decision to make, not yours, and we cannot restore it afterwards. The same happens if the business account is deleted because its subscription lapsed; we email you when it does. If the administrator deactivates or deletes your seat, your drafts and any listing you left unfinished move to the business as well. After you delete your account, or the administrator deactivates your seat, the business keeps your name, your email address and its record of what you did to its listings for 7 days, so it can review and undo it, and then deletes them; after that it keeps only a count of the listings you published, under “Removed seat”.

You must be at least 18 to open a Lotwize account, and Lotwize is not directed to children. You must be at least 13 to use a seat a seller adds. When you sign up you tick a box to confirm your age; we keep only whether you confirmed you are at least 18 or at least 13, and when. We do not knowingly collect data from anyone under 13, or from anyone under 18 other than through a seat, and we delete it if we learn we have.

We may update this policy. The date at the top of this page changes when we do, and we will notify you in the application or by email before a material change takes effect.