Who we are
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).
What we collect
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, if you turn it on. 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, the condition notes you write, your listing drafts, your preferences and templates, and details 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. We never see or store your eBay password.
Corrections you make. When you fix one of our suggestions, we keep what we predicted, what you changed it to, a reference to the photo it came from, and the time. Submitting a correction sends it for review and gives us permission to use it, including the photo it refers to, to improve how the tool identifies parts, for every seller and not only for you. Editing the field on the listing without submitting it contributes nothing and gives us no such permission.
How you pay. Which monthly plan your account is on, whether you have started your trial and when it ends, what you have used in the current billing month, and what you owe. Your card details are not among these: the payment page 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.
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 of addresses 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.
We do not collect payment card details, government identifiers, or location beyond what an IP address implies. We do not use tracking or advertising cookies, and we run no third-party analytics.
What we do with it
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 improve the tool’s accuracy, and we may use them and their photos to train and evaluate the models behind identification. 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 it goes
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. Also the private storage bucket holding the offsite backup copies of your photos.
Render. Hosting for the website and both background services, and the disk holding your photos, caches and logs.
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 details, sent through eBay’s official APIs so your listing can be published and revised.
Anthropic. The listing text we ask it to draft or rewrite: your title, your condition notes and item specifics. If you turn the part-number reader on, we also send photos in which our own server could not read any text, so it can look for hand-written markings; those are usually the wider shots, and whatever else appears in the frame is sent with them. We do not send your account details.
Twilio. Your mobile number, solely to deliver a sign-in code, and only if you turn on text-message two-factor authentication.
Stripe. The monthly subscription charge for your plan, and anything past its allowance. The payment page is Stripe’s own, so your card details go to them and never to us; what we send is the amount and your account number, and what we get back is that the payment succeeded.
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. The contact form reaches us through Gmail, and our pages load fonts from Google Fonts, which receives your IP address in order to serve them.
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.
How we protect it
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.
How long we keep it
Your account, drafts, preferences and corrections stay while your account is open. Drafts and their photos also follow any retention window you set yourself in the app. The photo backup mirrors what is on the service and is removed when you delete your account. Your eBay tokens are removed when you disconnect eBay, when you delete your account, or when eBay tells us you have closed yours. Rate-limit records are deleted within about an hour, and the demo’s free-identification counter within two days; server logs turn over on our host’s own short schedule. One record outlives the account: your billing record, which states what your subscription was charged and when. It holds no card number.
Corrections, models and deletion
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. One copy is not reached by that: each correction is also appended to a working file that the live identifier reads back. That file records the correction and the photo’s filename without any account attached, so a deletion request cannot single it out. We are changing that.
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.
Cookies
We set two cookies. Both are necessary for the service to operate, neither is used for tracking or advertising, and we set no third-party cookies.
The sign-in cookie keeps you signed in. It also carries the count of free identifications on the logged-out demo, which is why it is set before you have an account.
The device cookie 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 addresses you have signed in from, up to eight 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.
Your rights
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 and your listing links 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. Delete this account removes everything. 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. Listings already published to your eBay account belong to you and stay on eBay. If your account has used more than its plan allows, deleting it charges that overage before the account goes; nothing else is charged, and 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 you are in the EU or UK you may complain to your local data-protection authority. If you are in California you have the rights above plus the right to know what we collect and to opt out of the sale or sharing of personal information. We do neither. We will not discriminate against you for exercising any of these rights.
If you are an employee seat
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.
Two consequences worth stating plainly. You can delete your own account whenever you like, in Settings, and doing so takes your drafts, photos and sign-in with it. 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.
Children
Lotwize is for sellers aged 18 and over and is not directed to children. We do not knowingly collect data from anyone under 18, and we delete it if we learn we have.
Changes to this policy
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.