Privacy policy

SellFalcon is run by Khizar Hayat, a sole trader established in Pakistan, trading as SellFalcon; he is the data controller for the personal data described here. (This page said "based in the United Kingdom" until 15 August 2026. That was wrong, and it is corrected here rather than quietly: the tool is built for UK eBay sellers, but the person who runs it is in Pakistan, and you are entitled to know who is responsible for your data.) The services that store or process data for us are named in the table below, and where any of them keeps it outside your own browser is said in the section about that service. For anything in this policy, contact support@sellfalcon.com.

Everything SellFalcon works with is stored locally in your browser's extension storage (chrome.storage) on your machine:

• Your settings, including your eBay API credentials and your AI engine key.
• Scraped product data, drafts and listing history.
• Your inventory ledger: published listings with their supplier costs and variant details.
• Orders synced from your own eBay account (these naturally include your buyers' eBay usernames), and the profit figures computed from them.
• From 10 September 2026, if you switch Invoices on under Features: your own AliExpress order history, read from the order pages you are signed in to. That is the order number, date and status, the items, quantities and prices, the seller's name, what you paid, the payment method as the page words it, and the delivery address on the order. The extension keeps the last four months of it on your machine. If you are signed in, each record is also copied to your SellFalcon account, which keeps twelve months so you still have the year after a reinstall or a new computer, and the extension only drops a record from your machine once your account has it. Your AliExpress password never reaches us, and the extension only ever reads pages you are already signed in to; it does not log in for you.
• From 11 September 2026, if Paste the buyer’s address at checkout is on under Features: one delivery address at a time, read off an eBay order page when you press Copy address. That is your buyer’s name, their address and their phone number as eBay shows them to you, plus the order number and which eBay site it came from. It is held so the next press at a supplier’s checkout can type it in, and a new copy replaces the last one. Alongside it the extension keeps the last five run logs: what the automation did step by step, which includes that same address and, on a failure, a snapshot of the supplier form it was filling, so a paste that went wrong can be explained rather than remembered. Both are kept in this computer’s extension storage and never in Chrome’s settings sync, so they do not travel to your other computers. Both are deleted automatically after 30 days, and Settings → Buyer addresses has a Clear now that removes them at once. None of it is ever sent to us, signed in or not, and it is not part of cloud sync. Copying also puts the address on your computer’s clipboard, as any copy would.
• From 11 September 2026, if Save Temu’s own tax invoices is on under Features: nothing is stored beyond the date range you last chose. On a Temu orders page the extension reads the order numbers and dates already shown to you; pressing Save invoice asks Temu, using the session you are already signed in with, for that order’s own tax invoice, assembles its pages into a PDF and saves it to your Downloads folder. The document is Temu’s, unaltered: the extension does not rewrite or recompute any of it. Your Temu password never reaches us, the extension only reads pages you are already signed in to, and no part of this reaches SellFalcon at all, which is why the feature works whether or not you are signed in or on a plan.
• The business details you type for those records (your company name, address, VAT and company numbers, contact details and logo). You type them, we do not collect them, and they are printed on the record and nowhere else.

By default none of this is transmitted to us. If you sign in to your SellFalcon account in the extension's Settings → Account, the extension additionally keeps a copy of the inventory ledger, the synced orders, your staged product drafts (so the web listing editor can open them), the short monitoring/orders preference list and, from 10 September 2026 if Invoices is on, your AliExpress purchase records, in your account (see "Cloud sync" below). The blocked-keyword (VeRO) word list is, from 16 September 2026, your account's own list rather than a copy of the extension's: the web Settings page and the extension both edit it, and the signed-in extension keeps a copy of it on your computer and sends its edits to the account. Neither the copied buyer address, its run logs, nor anything about Temu invoices is in that list, and neither is added to it by signing in. Everything else, including every key, token and credential, stays local no matter what. From 7 September 2026 that is true in a stricter sense as well: the extension keeps its keys and tokens in this computer's own extension storage only, so Chrome's own settings sync (which copies a browser's preferences between the computers signed in to one Google account) never carries them; a second computer needs the keys entered there, or a passphrase-protected backup. If you create a backup, it's a file encrypted with a passphrase you choose (AES-GCM), saved wherever you put it; without the passphrase it cannot be read, by us or anyone else.

The extension only talks to services that are necessary to do what you asked, always directly from your browser:

Accounts on this website

If you create an account (by invitation, or by signing yourself up when open sign-up is switched on) we store your email, your password as a salted one-way hash (never the password itself), and sign-in session tokens, all in our database (Cloudflare D1). From 16 October 2026 we also keep, for each sign-in, the day it was last used (the date only, not the time or what you did), so we can tell a seller who uses the website from one who has stopped; it is deleted with the sign-in it belongs to, within the hour of a sign-out or its end, and with the account. From 7 September 2026 you can also give the tool a display name on Your account ("Sam", say), so it greets you by it; it is optional, stored with your account's settings, shown only to you and your own team, changed or cleared on the same page, and deleted with the account. Disabling an account locks it out immediately (every sign-in and every data request refuses a disabled account); deleting an account removes its data. Ask support@sellfalcon.com to delete your account at any time. From 24 August 2026 there are two doors, and you choose: ask to pause your account and everything is kept as you left it while sign-in is blocked (the time limits on this page still run while you are away: messages, orders, purchase records and the rest still age out on their usual days, and a connected eBay account still syncs), so coming back months later means picking up where you stopped rather than starting again, or ask to delete it and everything goes, permanently, including the messages, orders, reports and files described on this page, plus anything you sent the contact form before you had an account. Pausing is the friendly door for taking a break; deleting means what it says. From 8 September 2026 you can also add a profile photo on the same page: your browser shrinks it to a 96-pixel square of a few kilobytes before anything is sent, it is stored with your account's settings beside the name, shown only to you and your own team, and removed the moment you press Remove photo.

Sign in with Google or Microsoft (optional). When these buttons are switched on, choosing one takes you to Google's or Microsoft's own sign-in page; you never type any password on our pages, and we never see the password you use there. All the provider tells us is which email address you proved you own (plus basic token bookkeeping we do not store), and we use that email for exactly one thing: matching you to your invited SellFalcon account. No account is ever created from it, nothing is posted to your Google or Microsoft account, and we store no extra data about you compared to a password sign-in (an SSO-only account simply has no password hash). During the handoff our sign-in service (which runs on our API's own domain, not sellfalcon.com) sets one short-lived security cookie purely to protect the exchange against forgery; it expires within ten minutes. What Google or Microsoft record about their own sign-in pages is governed by their privacy policies, not this one.

Connecting eBay on the website (optional)

Some accounts can connect an eBay account directly on the Settings page, so the tool works without the browser extension. When you do, you sign in on eBay's own page and approve SellFalcon; we never see or store your eBay password. eBay then gives us a connection token (a "refresh token") that lets us fetch your orders and manage your listings on your behalf. That token is stored encrypted in our database (Cloudflare D1) using AES-GCM with a key that is not kept in the database, so a copy of the database alone cannot read it. We use the connection for one thing: keeping your SellFalcon orders (and, as those features arrive, your listings) in sync, including an automatic refresh about once an hour so your numbers stay current even with no browser open. We do not sell, share or use it for anything else. One addition from 18 August 2026: the connection can also serve your own signed-in extension. If the extension has no eBay developer setup of its own, our server mints a short-lived access token from this connection and hands it to the extension, so the extension can list and manage listings on the same eBay account with nothing to configure. The refresh token itself never leaves the server, the short-lived token expires on its own within minutes, and only the account owner's own sign-in can ask for one; a team member's cannot. From 19 August 2026 the signed-in extension is also told each website connection's display name (the label you set, or the eBay username) and whether it is working, never any token, so its own Settings page can say which eBay account listing runs through instead of claiming no store is connected; the same owner-only rule applies. From 11 October 2026 it is also told the name of the postage policy Settings names as each store's default, so a listing the extension publishes through that store starts on the same policy the website would use. Your synced orders include your buyers' eBay usernames and, since 17 August 2026, the order details eBay already shows you in Seller Hub: the buyer's name, the postage address and phone number they gave eBay, the postage service they chose, eBay's delivery estimate and the paid breakdown, stored in your account's private space so the tool's own order page and packing slip work without a trip to eBay, aged out with the order (roughly the last 45 days). The extension's own sync carries none of that: usernames only. You can disconnect at any time on the Settings page, which deletes the stored connection, the orders and everything else synced from it, and the listings you published from the website through it, and you can also revoke SellFalcon from your eBay account's "connected apps" settings. Deleting your SellFalcon account removes all of this too. One thing is kept aside when you disconnect or remove a store, from 11 October 2026: its listing defaults and default postage policy, for 180 days, under a one-way fingerprint (a SHA-256 hash) of eBay's own id for that account (never the id itself or the username) so they come back if you connect the same eBay account to the same SellFalcon account again. They are deleted when they come back, after the 180 days, when eBay tells us that account has been closed, or with your SellFalcon account, and another eBay account never receives them. If you use the extension instead, nothing changes for you: this section only applies once you connect eBay on the website.

Connecting AliExpress on the website (optional)

You can also connect the AliExpress account you buy from (or several, one per client's eBay account if you run more than one shop) on the same Settings page. You sign in on AliExpress's own page and approve SellFalcon; we never see or store your AliExpress password. If you pair an AliExpress account with one of your eBay accounts, we store that pairing (just the two connection ids) so the daily supplier checks for that shop's listings run through its own account and never through another client's. You can also give each connection a name of your own choosing (AliExpress's autogenerated id tells you little); the name is stored with your account, shown on the owner-only Settings card, and deleted with the connection. AliExpress then gives us a connection token, which we store encrypted in our database (Cloudflare D1) using AES-GCM with a key that is not kept in the database, exactly as we do for eBay. We use it to read product information (prices, stock, photos and variants) for products you ask about, and, as those features arrive, your supplier orders and their tracking. It is never used to buy anything without you asking, and we do not sell or share it.

Ordering at the supplier. From 11 September 2026 the connection can also create an order, and only ever because you pressed a button that showed you what it would buy first. When you do, the delivery details of that eBay order are sent to AliExpress so the parcel reaches your buyer: their name, their address and their phone number. That is the same information you would type into the supplier's checkout by hand, sent to the same supplier, for the same reason. If eBay gave no phone number for the order, the number you put in Settings is used and the order says so; a phone number is never invented. What we keep afterwards is the supplier's own order number and, once it exists, the tracking number, both stored against that eBay order in your account's private space and deleted with it: at most a month after the order itself is no longer held here, unless that supplier order is still under way.

Two things this cannot do, and there is no setting that changes either. It cannot pay: AliExpress's dropshipping API has no payment call at all, so every order it creates is unpaid in your own AliExpress account for you to pay yourself, and AliExpress cancels an order left unpaid for 24 hours. And SellFalcon never holds, stores, enters or uses a card of yours or anybody else's, for this or for anything: the only card details in this product go into our payment provider's own form, as the billing section says. Ordering is OFF unless you switch it on in Settings, and marking the eBay order dispatched when the supplier ships is a separate switch, also off.

Disconnecting on the Settings page deletes the stored connection, and you can also revoke SellFalcon from your AliExpress account settings. Deleting your SellFalcon account removes it too. Connecting AliExpress is entirely optional and nothing else changes if you skip it.

Backing up to your Google account (optional)

From 19 August 2026 you can connect the Google account you own, on the Settings page, and SellFalcon keeps a copy of your records in your own Google Drive: a spreadsheet named "SellFalcon backup" holding your inventory (title, item number, price, your cost, the supplier link) and your orders (order number, date, the buyer's eBay username, item, totals, fees, your cost, supplier order number, tracking, status). You sign in on Google's own page; we never see or store your Google password. Google then gives us a connection token that is stored encrypted in our database (Cloudflare D1) using AES-GCM with a key that is not kept in the database, exactly as we do for eBay and AliExpress. The permission we ask for is deliberately the narrow one (Google calls it drive.file): it lets SellFalcon touch only files SellFalcon itself created; we cannot read, list or change anything else in your Drive, ever. The backup is written when you press Back up now and roughly once a day while you use the tool; nothing about it is sent to anyone but Google, under your own account. Disconnecting on the Settings page deletes the stored connection immediately (the spreadsheet stays in your Drive, because it is yours) and you can also revoke SellFalcon from your Google account's own security settings. Deleting your SellFalcon account removes the stored connection too. Connecting Google is entirely optional: your data lives in SellFalcon either way, and the backup only adds a copy you own. The monthly sheet you build on the Reports page can be saved the same way: pressing "Save to Google Sheets" writes that month's rows (exactly as the page shows them, including any client and expense lines you typed) into a spreadsheet named "SellFalcon report" for that month, one per month, updated in place when you save again.

Users & Team (optional)

Your plan includes a number of team seats. If you invite a team member from Your account, we store their email address, their role (admin or VA), a licence key (every account row has one) and which workspace they belong to, and we email that address, through Resend like the rest of our email, to say how to join (and again if you press Send again on the pending invitation, at most once an hour and within the ten invitation emails a day; an invitation not accepted within 14 days ends, and the account made for it is deleted); once they choose a password, their account works like any other (salted hash, revocable sessions). A team member signing in on sellfalcon.com sees your workspace: the same listings, orders (including your buyers' eBay usernames), drafts, activity, reports and settings you see, and the actions they queue go into the same action queue, so make sure you invite only people you trust with that data, and that they are happy for you to give us their email. Team accounts work on this website only; they cannot connect an extension or push data. Roles limit what they can change (a VA cannot change the extension's settings; only the owner manages the team). Removing a member deletes their sign-in and account immediately; their edits to your workspace stay, because the work is yours. From 18 October 2026, when someone on your team changes a price or stock, ends or brings back a listing, rewrites a title, sets an ad rate, sends a reply or places a supplier order from SellFalcon, the line this leaves in Activity also keeps which person did it (their account number), and your team sees it as their email, "the owner" or "you". Removing a member deletes that mark and leaves the line. Members can also ask us to delete their account at any time: support@sellfalcon.com.

Cloud sync (optional, off until you sign in)

When you sign in to your account inside the extension, it mirrors your inventory ledger (listings, supplier costs, monitor state) and your synced eBay orders (which naturally include your buyers' eBay usernames, but no addresses) to our database (Cloudflare D1), in a space that belongs to your account alone. That is the whole point: the web dashboard at sellfalcon.com/dashboard reads it so you can see your business from any computer. Honest limit: sync is one-way (extension to cloud) today and is not a restore service; to move your data to a new or reinstalled browser, use the encrypted backup file in the extension's Settings. Your eBay connection, your AI key and your account credentials are never included; of the extension's settings, only the short monitoring/orders preference list, the blocked-keyword (VeRO) word list and (from 26 September 2026) your two eBay fee settings, the fee percentage and the fixed fee per order, shown on the web Settings page travel (so you can change those from the web), plus the names you gave your connected eBay stores (name and internal id only, never tokens, so the web tool can say which store is which), the extension's recent-activity feed (short lines like "Daily check finished", shown on the dashboard's Recent activity card) and each product you are preparing to list: since 9 August 2026 this is the FULL draft (title, description, image addresses, prices, quantities, variants, item specifics, eBay category and the supplier product link), because the web listing editor at sellfalcon.com lets you finish and publish these drafts without the extension; before that date only a short summary travelled. If you use the dashboard's action buttons (including Add product by link and settings changes), we also store that small action queue (which listing or link, what to do, and the result your extension reported back) in the same private space. The Orders tab also lets you attach details to an order: the supplier cost, the supplier's order number, a private note, and the tracking number you dispatch with; those are stored in the same private space and feed the profit figures shown across the tool, and are deleted a month after the order itself is no longer held here (it ages out of the order sync and of your extension's copy). Pause sync with one toggle, or sign out to stop it entirely; the extension keeps working exactly the same. Ask support@sellfalcon.com to delete your account at any time: an account is deleted whole, with everything synced to it.

Your AliExpress purchase records (optional, from 10 September 2026)

If you switch Invoices on in the extension's Features tab and you are signed in, each AliExpress order the extension reads is also copied to your account's private space in our database (Cloudflare D1). This is one arrangement with two halves, and the reason for both is the same: only a signed-in browser tab can read your AliExpress order pages, so the extension does the reading and keeps four months, while your account keeps twelve so the year is still there after a reinstall, a cleared browser or a new computer. The extension will not delete a record from your machine until your account has it.

What is copied is the record as read from your own order pages: the order number, date and status, the items with their quantities and prices, the seller's name, what you paid and in which currency, the payment method as the page words it, any tracking number on the order, and the delivery address on the order: which, for a dropshipped order, is your buyer's address. It is stored in your account alone, shown to you at sellfalcon.com/reports under "Purchase records", and never shared with anyone. A record older than twelve months is deleted automatically, judged by the order's own date; a record whose date could not be read is kept rather than guessed at. Switching Invoices off stops new records being read and copied; deleting your account (ask support@sellfalcon.com) deletes what is already there, with the rest of the account. Your AliExpress password never reaches us and we never sign in to AliExpress for you.

One shared sign-in between this website and the extension

From 13 August 2026 the extension no longer asks you to sign in a second time. When you are signed in on sellfalcon.com and the extension is installed in the same browser, the extension reads the sign-in token this website keeps in your browser's own storage for this site, and exchanges it with our API for a separate token of its own. The website's token is never stored by the extension, and the swap is a hand-over, not extra access: it can do exactly what you can already do, for your account only. Because the two tokens are separate, signing out on this website does not silently leave the extension running (we tell it to sign out as well when it is signed in to the account you are signing out of, and signing back in to that account here signs it back in) and changing your password still ends both, like every other signed-in device. An extension signed in to a different account (on a computer two people share) keeps its own sign-in when you sign out here. You can sign the extension in or out yourself at any time on Your account → Your extension, or in the extension's own Settings → Account.

Two small things travel with this. The extension marks the pages of this website so the site can see that it is installed in this browser (that is how the tool can say "your extension is picking it up now" instead of guessing), and when the extension asks our server for queued work (about once a minute while it is signed in) the server records when it last asked, the extension's version number and the random install id it already sends with every sync. It keeps that for the 20 browsers that asked most recently, and deletes a browser's record 90 days after it last asked, except the browser that holds your shop. That is what the "Last asked for work" line on the Settings page and the queued-actions notice on the dashboard are reading. No page addresses, no browsing history, and nothing about any other website: the extension only runs on sellfalcon.com, AliExpress product pages and eBay, exactly as listed above.

Monthly reports and invoices (optional)

The reports page at sellfalcon.com/reports builds monthly sheets and invoices from your synced orders. What you type there is saved to your account's private space in our database (Cloudflare D1): your chosen sheet columns, expense lines, per-order extras (supplier order numbers, postage label costs, refunds, notes), profit-share settings, invoice lines (from 20 August 2026 with an optional unit cost and quantity per line, plus the invoice's due date, purchase order number, currency, tax rate, discount and shipping figures, and, later the same day, an optional small logo image you pick for that one invoice, stored shrunken with that month's report data), and the business details you enter for the invoice (your own and your client's name, address, contact details and, from 20 August 2026, company registration numbers and the bank account details printed in the invoice's payment section; bank details you choose to print on an invoice are, by that choice, shared with whoever receives the invoice). We store the client details exactly as you type them, only so your invoices can show them; it is your responsibility to have your client's OK to use their details this way. Everything is deleted with your account, and what you type there you can change or remove on that page yourself.

Your logo and company files (optional)

From 20 August 2026 you can upload a logo on the Reports page (Business details); it is stored in our database (Cloudflare D1) with your account and printed top-right on your invoices. You can replace or remove it any time, and it is deleted with your account. The same page has a small company file cabinet: up to 15 files of up to 20MB each (contracts, registration papers, past invoices: whatever your business leans on), stored in Cloudflare R2 object storage in our account, indexed against your account alone. Only the workspace owner can see, download or delete these files, team members cannot, and we never read, share or process them; they are stored bytes until you download or delete them. Deleting a file removes it from storage immediately, and deleting your account removes the whole cabinet the same way.

The waitlist (retired 16 August 2026)

This site used to carry a waitlist form. It is gone: accounts are created on the sign-in page (or arranged by email while sign-up is invitation-only), and no new waitlist emails are collected. Emails people typed into the old form are still held only so we can invite them, and each is deleted when its owner is invited, creates an account, or asks: support@sellfalcon.com.

Verification and password-reset codes

When you set your first password, or ask to reset a forgotten one, we email you a 6-digit code and store a one-way hash of it (never the code itself) in our database (Cloudflare D1) alongside your email address, what the code is for, and when it was made. It stops working after 15 minutes, after five wrong tries, or once it has been used, whichever comes first, and asking for a new code cancels the old one. We keep these rows only so a code can be checked once; they are deleted with your account.

Email we send you about your account

When your request to join is approved (or, kindly and once, declined), and for a small number of other account matters (verifying your address, a welcome note when your account is created, resetting your password, and important notices about your account, such as one reminder before a complimentary plan ends), we send you an email. If a seller adds your address to their team, we email you once, saying how to join. If you switch on the daily check email in Settings under Notifications, we email you at most once a day, from 7am UK time, when something is waiting on you: a supplier price change, an out-of-stock or a supplier page that has gone, an order late or due for dispatch within a day, an AliExpress order waiting for your payment, a return or case past eBay's respond-by date, or a buyer who has asked to cancel an order. The email names your listings by title and counts orders and requests, and never gives a buyer's name or address. It carries an Unsubscribe link that works without signing in. These emails are off unless you turn them on and stop the moment you turn them off. If you subscribe to a paid plan, we also send at most two kinds of billing notice: one reminder before a free trial ends (so the first charge is never a surprise), and a note when a subscription payment fails (so you can fix the card while you still have access). Both are service emails about your own account, never marketing. To do that, your email address and the message itself are passed to Resend, the service that delivers our email for us; their servers for our account are in Ireland, inside the EU. We do not use these emails for marketing, we do not send newsletters, and we do not track whether you open them or click their links; link and open tracking are switched off on our account. Support does not run on email: it runs in the chat inside the tool, described below.

Support chat on this website

Support is a chat: if you start a conversation from the support page, we store the conversation (your messages, our replies, the category you picked and, if you are not signed in, the email address you give) in our database (Cloudflare D1), so the answer can appear in the same chat when you come back. It is read only by us, used only to help you, and deleted 30 days after it is resolved, or sooner if you ask: writing in it again before then reopens it, and the 30 days start again only when it is next resolved. A conversation started while signed out is also deleted once nobody has touched it for 90 days. From 6 September 2026 three small things sit beside a conversation: we may write ourselves a private note on it (our own words, stored with the conversation, never shown to you, deleted with it); when a conversation starts, or when you ask for access, a payment of yours fails, your extension has been quiet for two weeks, or a complimentary plan we gave you reaches its last day, one email naming your address goes to the person who runs SellFalcon through the same email service named above, so nothing waits unread; and if you ask for access and we approve or decline, we keep your email address, the decision and the date as a record of it for twelve months, and delete it sooner with your account or when you ask. A conversation started while signed out is tied to a random key kept in your browser; clearing your browser data discards that key, so start a new conversation (or email us) if that happens. Emailing support@sellfalcon.com directly works exactly as well.

Messages in a conversation can carry attachments: pictures, PDFs, plain text files (a CSV sheet goes as one) or a short voice note. They are stored with the conversation, are visible only to you and us, and are deleted with it. A voice note is a recording of your own voice, so send one only if you are happy for us to hear it and store it until the conversation is deleted: 30 days after it is resolved, or after 90 untouched days for one started while signed out.

Feedback

The signed-in feedback page lets you send us bugs, feature requests and suggestions, with optional screenshots or files. We store what you send (message, category, attachments, and which account sent it) in our database so we can read it and improve the tool. Pictures are shrunk in your browser before they are sent, and you can attach a short voice note instead of typing. Feedback is not a conversation, and nothing comes back on the feedback page; if we do answer something you sent, the answer is written into a support conversation of its own inside the tool, which starts with a copy of what you sent, and is kept and deleted like any other support conversation. You can ask us to delete anything you sent at any time.

The extension's own support email can attach optional diagnostics: version numbers, item counts and recent error messages. They never include your API keys, tokens or passphrases.

Error reports from this website

If a page of this website hits a script error, your browser sends us a short technical report: the error message, which script and line it came from, which page it happened on, and the site version. It carries nothing about you: no account, no email, no cookies, and there is no user column in the table it lands in. Identical errors are stored once with a counter, the store is hard-capped, and each entry is deleted about 14 days after the error last happened. Before a report leaves your browser, any web address in it is cut to the page or script it names (nothing after a ? or a #), and anything in it shaped like an email address, a phone or other long number, a postcode or a sign-in token is taken out, with any text the error quoted; our server applies the same rule when a report arrives. A report raised by another browser extension's own script is not sent at all. The same list holds our server's own failures, which name the part of the server that failed and what went wrong in it, never who was using it or what they sent. These reports exist so we can fix bugs before most people ever meet them. The network address a report came from is counted for a day under the limits described next, and is never stored with the report.

Limits on guessing and flooding

So that a password cannot be guessed at machine speed and the forms on this site cannot be flooded, we note some attempts for a short while in our database (Cloudflare D1). For a sign-in that fails, we note the email address that was typed and the network (IP) address it came from; for a one-time code tried or asked for, a request for access, a contact-form message, a support conversation started while signed out and an error report, we note the network address alone. Each note is that address and the time, nothing more: it is tied to no account, counted for that limit and read for nothing else, a successful sign-in clears the notes of the address it used, and every note is deleted within a day. For a team invite emailed from Your account, we note the workspace that sent it and the time, so that one workspace cannot send an endless run of invite emails; that note is counted for that limit alone and deleted within a day too. For Send again we also note, for the person invited, the time of the last invitation email, so that it is not sent twice in an hour; it is counted for that alone, deleted within a day, and deleted with the person if they are removed.

• No analytics or tracking in the extension, and none on this website.
• No cookies on sellfalcon.com. Your light/dark theme choice is kept in your own browser's local storage and never transmitted. (Three exceptions, all named: during an optional Google or Microsoft sign-in, our API's own domain sets a single security cookie for up to ten minutes, described under "Accounts on this website"; while you connect eBay, AliExpress or Google on the Settings page, it sets one more for up to ten minutes, a random value that lets only the browser which started the connection finish it, cleared when it does; and opening the plan card or a Paddle payment link loads Paddle's checkout software into this page, which sets its own cookies to run the checkout: that overlay is how your card details reach Paddle and never us.)
• No selling, sharing or renting of data. What we hold is a waitlist email, an account if you have one, and, only if you use cloud sync, your own listings and orders, visible to nobody but you and us as the operator.
• No access to other sellers' accounts or listings. The extension acts only on your own account. Your order records naturally include your buyers' eBay usernames; they stay in your browser unless you switch on cloud sync, in which case they are also stored in your account's private space.

Chrome will list these permissions when you install. Here's what each is actually for:

Host access is limited to the sites the tool works with: AliExpress and its image hosts, eBay and its API domains, the AI engine's API endpoint, the wsrv.nl image proxy, and SellFalcon's own API (for cloud sync when you sign in, and the sign-up wording question described in the services table above).

• Everything lives on your machine, so you can inspect, back up or delete it at any time. Uninstalling the extension removes its stored data. If you used cloud sync, ask us and we delete your account, and the server copy with it: an account is deleted whole.
• Monitoring, notifications and auto-reprice are all controlled in Settings; destructive actions are off or alert-first by default.
• Under UK GDPR you have rights over personal data a controller holds about you. Our honest position: we hold your waitlist or account email if you gave us one, and your synced listings and orders if you use cloud sync. All of it is deleted on request: an account is deleted whole, with everything this page describes, and a support conversation or a piece of feedback can also be deleted on its own.
• When someone closes their eBay account. eBay tells every app connected to it when a member closes their eBay account, and we act on it. If you close yours, the eBay connection you made on the website is removed with everything synced through it (orders, listings, messages, feedback, returns, traffic, ads), together with that store's copy of your extension's listings and orders, the order details and supplier links you added to them, and the listings you published from the website; your SellFalcon account itself stays until you ask us to delete it. We keep a record that we did this, holding your eBay username and eBay's id for the account, for 400 days, as proof to eBay that the deletion was carried out. If a buyer closes theirs, wherever a seller's data here names them their name, postage address, phone number and messages are removed within a few hours (their orders keep the money and the items, and name them only as a deleted eBay member), and the AliExpress purchase record that shipped to that name and postcode loses the address. Afterwards we keep no name for them, only a one-way code made from it, so that their details are removed again if eBay or your extension sends them back. Any label you put on a conversation with them stays, on the conversation, and loses their name with the rest. To find them in one step when such a notice comes, we keep beside each seller's data a list of the eBay usernames it has named, and nothing else: that list is read for this alone, lets a name go within two weeks once nothing of yours names it any more (no order, message, feedback, return or label), and is deleted with your account. A notice about someone who never bought from or sold through anyone here leaves nothing behind.

When the architecture changes, this policy is updated before that ships, with the date above and a plain-English note about what changed. Changed on 31 October 2026 (what the AI engine is told, and what is checked on what it writes): when the web listing editor asks the AI engine to write a title, a description or item specifics, the words you have set to Block under Settings, Blocked words are now sent with the product text, so that the engine is told not to write them. They are sent that one time, from our server, and are not kept by us beyond your own list. What the engine writes is then checked on our server before you see it: it is made eBay-ready as Publish makes it, held to eBay's length limits, and checked against your Block words. A reply the engine drafts in the Inbox is read once more against the order it was written about; a note under the draft names a date, order number or refund the order does not carry. Nothing else is collected, kept or shared differently.

Changed on 31 October 2026 (what a disconnected store leaves behind, and records this page had not named): this page said what leaves with a store you disconnect, but not what stays, and it had not named a few small records the tool has kept for a while. When you disconnect an eBay store on Settings, the supplier links, costs and notes you set against its items stay in your account, marked as a removed store's, so that a store connected again finds them and the hourly supplier check leaves them alone while no listing holds the item. They are yours, they are not shared with anyone, and they go when you clear them, when eBay tells us you closed your eBay account, or with your SellFalcon account; only when an account holds 5,000 of them are the oldest ones, for listings that are no longer live and untouched for 90 days, deleted to make room. A store's payment policy and returns policy defaults are part of its listing defaults, beside the postage policy, so they leave with the store and are kept aside for 180 days when you remove it, as the postage policy is; a draft also records which payment and returns policy you chose for it (eBay's own policy numbers), and that goes with the draft. A draft also remembers when its supplier cost was read, or that you typed the cost yourself, so the editor can say how old a cost is. The record of a supplier order also holds where AliExpress had got to with it (unpaid, paid, shipped, cancelled, done, or that it could not be read, and whether that was because AliExpress refused our sign-in), when it was made, and, for a sale of a store you have removed, that mark; it goes with the sale's other details, a month after the order has gone (later while that supplier order is still under way), and with your account. And the notice that your password was changed is one of the emails we keep a short record of when our email service refuses it or gives no answer: the address, the subject and the service's reason for 30 days, and deleting your account deletes it. Changed on 31 October 2026 (which AliExpress account bought an order): when SellFalcon creates a supplier order for you, it now keeps on that sale which of your connected AliExpress accounts placed it (the connection's number and its login name), so the hourly check on that order asks the account that bought it, even after you change which store an account buys for. It is deleted with the sale's record and with your account, and it is not shared with anyone. Changed on 31 October 2026 (orders with a return or case still open, and cancellation requests): an eBay order is normally kept for about 45 days. An order that one of your open returns, cases or item-not-received requests names is now kept past that, and read from eBay again each hour, until that return, case or request is closed, so that a refund eBay issues late reaches the sale's profit; it is deleted with the next hourly read after it closes. And where a buyer has asked to cancel an order, we now also keep the time they asked and, if eBay gives one, eBay's date for you to answer by, for as long as the order is kept. Nothing else is collected. Changed on 31 October 2026 (cancellation requests read by the browser extension): the browser extension now keeps those same two dates on an order it reads from eBay, in your browser, and sends them to your account with the order when you are signed in to it, where the website shows them beside the order. It is the same two dates, kept for as long as the order is kept, and nothing else is collected. Changed on 31 October 2026 (the browser extension's AI writing is checked the same way): when the browser extension asks the AI engine, through your account, to write a title, a description or item specifics, it now says which of the three it is asking for, and our server sends the words you have set to Block with the product text, one time, and checks what the engine writes before the extension shows it, as it does for the web listing editor. When the extension asks for a reply to a buyer, the server reads the reply against the order facts the extension sent with the request and sends back a note on anything they do not hold. Nothing is kept beyond the answer. Changed on 18 October 2026 (when AliExpress's saved sign-in runs out): when AliExpress tells us how long the saved sign-in for your linked AliExpress account lasts, we now keep that one date in your settings, so Settings and Today can warn you before it ends, and we also show the day a connection stopped working. It is deleted when you remove the AliExpress account, and with your account. Changed on 18 October 2026 (after you disconnect Google): when you disconnect your Google account we still forget the saved connection and the account's address, but we keep one short fingerprint of that address in your settings (a one-way scramble that cannot be turned back into the address), so that if you connect a different Google account later we know the earlier monthly report spreadsheets are in the other account's Drive and start new ones instead of failing on them. It is deleted the next time you connect a Google account, and with your account. Changed on 18 October 2026 (a draft remembers one setting): a draft you send to your account from the extension now also records whether your extension's setting “Keep out-of-stock variations” was on when the draft was made, as a yes or no, so the website's editor starts a variation the supplier has sold out the same way the extension does. Nothing else about your settings is sent with it. It is kept with the draft and deleted with it, and with your account. Changed on 18 October 2026 (a conversation you read here is read on eBay too): when a conversation has been open in your Inbox for about three seconds, SellFalcon tells eBay, through the eBay account you connected, that the buyer's unread messages in it are read, as if you had opened them on eBay. It is one request to eBay for that conversation, made only when something in it is unread, and never for a conversation you only scrolled past, for a buyer who has closed their eBay account or for eBay's own notices. If eBay refuses or does not answer, nothing changes. Nothing new is collected or kept for this: our copy of those messages is marked read, and it goes when they do. Changed on 18 October 2026 (photos buyers send you): when a buyer attaches photos to a message on eBay, SellFalcon now reads the photos' addresses along with the message and shows the photos in your Inbox, under the buyer's words. We keep only the addresses, never the pictures: an address is kept only if it is a secure (https) address on eBay's own image hosts (ebayimg.com and ebaystatic.com), and any other address in a message is dropped and never shown. The picture itself stays on eBay, and your browser asks eBay for it when you open the conversation. The photo addresses are kept with the message's words, in the same place and on the same terms: for as long as the words are kept (2 months unless you pick 12 in Settings, counted from the message's own date), and they go when the words go, which includes when you disconnect that eBay account, when you delete your SellFalcon account, and when the buyer closes their eBay account. Your browser keeps the addresses with the conversation it keeps for up to 30 days, as it keeps the words. eBay's own notices are not kept, so none of their pictures are. For a photo on any other address we keep only a count of such photos with the message, never the address, so the Inbox can say that photos were not shown and send you to eBay for them; and our own error list may name the host of such an address (never the address, the message or the buyer), at most once a day for each host, so that we hear if eBay moves its image hosts. Changed on 18 October 2026 (Activity says who on the team did it): the line Activity keeps when someone changes a price or stock, ends or brings back a listing, rewrites a title, sets an ad rate, sends a reply to a buyer or places a supplier order from SellFalcon's own screens now also keeps which person did it, as their account number on that line. Your team is shown it as the person's email, "the owner" or "you", and only once there is a team; the lines the supplier watch makes carry none. It is kept as long as the line is (the log keeps your newest 500), deleted with the line and with your account, and when you remove a member, or the member's account is deleted, their mark is taken off every line and the line stays. Changed on 18 October 2026 (team invitations run out and can be sent again): an invitation to join your team that is not accepted within 14 days now ends on its own: the seat is free again and the sign-in made for that email address is deleted, with the email address, as when you revoke the invitation yourself. Before, it stayed until you revoked it. Pressing Send again on a pending invitation emails the invited address once more, at most once an hour and out of the same ten invitation emails a day your workspace can send; for that we note the time of the last invitation email for the person invited, which is deleted within a day and with the person if they are removed. Changed on 18 October 2026 (every reply you send from the Inbox): the words of a reply are kept for each reply you send, not only the last to a message. A second reply to the same buyer message (a follow-up with a tracking number, or a reply you chose to send again) is kept beside the first, on the same terms: for as long as the buyer's message is kept, and deleted with it, with the eBay account, with your account, and with the buyer's words if the buyer closes their eBay account. Changed on 17 October 2026 (the words of a reply you send from the Inbox): a reply you send to a buyer from SellFalcon's Inbox was kept as a record of when it went and how long it was, never its words, and its words were read back only from eBay's Sent folder, which does not hand back replies sent this way, so the conversation showed the buyer's message alone. Once eBay takes a reply now, its words are kept with the buyer's message it answers, for as long as that message is kept (60 days, or 12 months if you chose that), and deleted with it, with the eBay account, with your account, and with the buyer's words if the buyer closes their eBay account. Changed on 17 October 2026 (which eBay account each extension store is): the extension now sends, with its list of stores, the eBay user id each of its own stores sells as, which eBay writes on that store's orders, and your account keeps it beside the store's name. It is used for one thing: telling which of the eBay accounts connected on the website a store in the extension is, so a listing is only ever judged ended by its own store's list on eBay. It is replaced with each sync of the store list and deleted with your account. Changed on 16 October 2026 (open returns, cases and item-not-received requests): for an open return request we now also keep how many of the items bought are being sent back, as eBay records it, and for an open case the buyer's eBay username and the case's status, which this policy already listed but the tool was not reading from eBay's answer. They are kept and deleted with the rest of the return or case, as before. We also read the item-not-received requests buyers have opened on your account and not yet escalated (eBay keeps them apart from returns): the buyer's eBay username, the item, the status, when it was opened and eBay's respond-by date, kept while the request is open and deleted as returns and cases are. And for an order of several items, what eBay refunded on each item is kept with the order (eBay's order already carried it), so an item refunded in full is not marked dispatched. What a supplier gave back that you type on Reports' sheet (an AliExpress refund, or a dispute won) is kept with the order, as a postage label is, and your Google backup's order rows carry it in a last column. Changed on 16 October 2026 (when a sign-in was last used): we now keep, for each sign-in, the day it was last used, the date only, so that a seller who uses the website every day on a sign-in made weeks ago is not taken for one who has stopped. It is written at most once a day, and deleted with the sign-in (within the hour of a sign-out or its end) and with the account. Changed on 16 October 2026 (what an error report can hold): a script error's report could carry the page's whole web address as the place it happened, including anything after a ? or a #, which on the sign-in page can be a sign-in token, and the text some errors quote. Your browser now cuts any address in a report to the page or script it names and takes out anything shaped like an email address, a long number, a postcode or a token, and our server does the same when a report arrives; a report from another browser extension's own script is not sent. Our server's own failures are now kept in the same list for the same 14 days, naming the part of the server and what went wrong, never who was using it or what they sent. Changed on 16 October 2026 (how fast the hourly tidy-up deletes): the hourly tidy-up that deletes what has passed its time (the words of messages, purchase records, email failures, finished commands and the other records above) now deletes at most 2,000 records an hour, so that one tidy-up can never use up the day's database writes and stop the tool for everyone. In an ordinary hour that is far more than is due. After a long pause, or when you move your messages from twelve months to sixty days, the records past their time go over the following hours instead of all at once. Changed on 16 October 2026 (the returns and cases of a store that stopped syncing): we keep only open returns and cases, and delete a closed one the next time we check. A store whose eBay sign-in ended, or that we have not been able to read for two days, is not checked again, so its returns and cases stayed, buyers' eBay usernames with them, for as long as the store stayed connected. Each is now deleted 30 days after eBay's respond-by date for it; until then the tool says when it was last checked rather than counting it as waiting on you. Changed on 16 October 2026 (when your eBay sign-in runs out): when you connect an eBay store on the website, we now also keep the date eBay gives for the end of that saved sign-in (eBay ends one about 18 months after it is given), encrypted with the sign-in itself, so Today and Settings can tell you a month ahead to reconnect it. For a store connected before, the date is worked out from when you first connected it. It is about your own connection, nothing about a buyer, and goes with the connection. Changed on 16 October 2026 (the extension's sync and your computer's clock): each sync from the extension now also carries the time your computer's clock showed as it was sent. We use it only to read the publish times the sync carries on our own clock, so a listing you have just published is not taken for one that has ended when your computer's clock is wrong, and we keep a listing's publish time read that way beside the one your extension sent, for as long as we keep the listing. And when you sign the extension out, it keeps in that browser only which version of each draft your account last took from it (an id, a time and a short fingerprint of each part, never the draft itself), so that when the same account signs in again a draft changed both there and on the website is merged rather than written over; signing in as another account does not use it. And when you press Send to this account in the extension, every purchase record that browser holds now goes to the account you send the shop to, those it had already sent to the account the shop came from included; until now only records never sent anywhere went, though the note of 10 October says the shop's purchase records go with it. Changed on 16 October 2026 (a supplier link or cost for a listing your extension holds, and the times it writes): a supplier link or a cost you set on the website for a listing on an eBay store that only your extension is signed in to is no longer kept as a record of its own on your account: it goes to that extension as a queued job, is kept there with the listing, and comes back to the website in the extension's sync, as the rest of the listing does. For such a listing we keep only the AliExpress product number and what our supplier check last read for it, so that our servers can watch that product, telling you of a change and changing nothing on eBay, while your extension cannot watch it (a listing with options imported without their details, or a link still on its way to the extension); once your extension watches it, our servers stop.A link or cost set that way before today stays on your account as it was until you change it. The times your extension writes into its sync (its activity, when it last checked a supplier, when a draft was added, where a store's orders start) are now shown on our clock, moved by the difference the sync measures, and we keep the time your extension sent beside each, for as long as we keep that item. And each queued job now tells the extension when the website made it, so that a price or stock job made before a change you made in the extension is not run over that change. Changed on 13 October 2026 (how long a browser's last request for work is kept): the record of when each browser's extension last asked our server for queued work (the time, the extension's version and its random install id) was kept until your account was deleted. It is now kept for the 20 browsers that asked most recently, and a browser's record is deleted 90 days after it last asked, except the browser that holds your shop. Changed on 13 October 2026 (team invite emails are counted): a team invite you send from Your account is emailed to the person, and we now note which workspace sent it and when, so that one workspace can send ten invite emails a day and no more. The note holds nothing else, is read for that count alone and is deleted within a day; the invite itself is made either way. Changed on 13 October 2026 (a checkout never paid): the record a checkout keeps while it is open (Paddle's reference for it, which plan it is and when you opened it) was meant to go after half an hour if no payment came through, but it stayed until your next checkout replaced it, or your account was deleted. It is now deleted by the hourly tidy-up once its half hour has passed. Changed on 13 October 2026 (the postage a listing was priced on, and labels and currencies in your backup): a listing you publish from the website's editor now keeps, beside the supplier cost it always kept, the postage and extra cost its price was worked out on (whether the AliExpress postage rule was on, a postage figure you typed, and your extra cost), so Inventory works out its profit from the same cost the editor showed. These are figures you typed or chose, kept with the listing and deleted with it, the store or your account. Your Google backup's order rows now also carry the postage label cost kept with each order and the currency the buyer paid in; both were already kept with your orders, and nothing about anyone else is collected or kept. Changed on 12 October 2026 (a listing relisted on eBay keeps its supplier): for a listing that ended without selling and that you relisted on eBay itself, the hourly read of your ended listings now also keeps the new item number eBay gave it beside the old one, and copies the supplier link you set on the listing (and, for a listing published here, our record of it) to the new number, once, as a relist made here already did. It is your own listing data, deleted with the store or your account; nothing about anyone else is collected or kept. Changed on 12 October 2026 (a checkout you have open): when you open a plan's checkout, we now keep Paddle's reference for it, which plan it is and when you opened it, so that a second checkout cannot be opened on top of it and charge you twice. It goes when your payment comes through, after half an hour if it does not, and with your account. We also keep the day your free trial began, as Paddle reports it, beside the trial dates we already kept, so the trial bar on Your account counts from that day. Changed on 12 October 2026 (a label or refund typed on Reports, refunds in your backup, and where the extension's orders start): a postage label cost or a refund you type on the Reports monthly sheet used to be kept in that month's report data only, so only the sheet took it off the order's profit. It is now kept with the order's own extras (where its supplier cost and notes are), so Today, Orders and the Inbox take it off too; what months already held is moved there once, and an order no longer held keeps its figure in the month as before. It is deleted with the order's extras, as those are, and with your account. Your Google backup's order rows now also carry what was refunded on each order, and say each order's status in words. From extension 1.51.20, the list of your eBay stores that cloud sync carries (name and internal id) also says, for each store, when the extension's first read of its orders began, so Reports can say when a month before that is short of orders; nothing else about the store is sent. Changed on 12 October 2026 (a share link from the AliExpress app in Add a product): a share link from the AliExpress app (an address on a.aliexpress.com or s.click.aliexpress.com) pasted into Add a product is now followed by our server to the product it opens, so the product can be fetched. Our server asks only those two AliExpress addresses, sends nothing with the request but the link you pasted, reads the product number from the answer and keeps nothing of it. Changed on 11 October 2026 (Mark answered, for your whole team): a conversation you marked answered in the Inbox used to be remembered only by the browser you pressed it in, so your team and your other computers still showed it waiting. Each mark is now kept in your workspace on our server: which Inbox row it was (eBay's number for the message, or the return or feedback it is about) and when it was marked, nothing else. A mark goes 60 days after it was made, and with your account. The marks a browser kept from before are moved up to your workspace once, the first time that browser opens the dashboard, and that browser then stops keeping its own copy. Changed on 11 October 2026 (who on your team sent a reply): the record that a reply went from SellFalcon now also keeps which person on your team pressed Send, so a teammate who presses Send on the same message is told who replied and when, instead of "You have already replied". It is kept and deleted with that record (400 days at most, and with your account), and a team member's go when they are removed from the team. Changed on 11 October 2026 (a closed buyer's conversation in the Inbox): opening a conversation with a buyer who has closed their eBay account asked eBay for their messages again after we had removed their name and their words, and showed whatever eBay sent back, which your browser then kept for up to 30 days. Such a conversation is no longer read from eBay at all: the Inbox shows that the buyer closed their account, with no name and no words, and your browser drops any copy of their words it kept from before. Nothing new is collected. Changed on 11 October 2026 (joining a team): when you accept a team invitation, your account now keeps the date and the way you joined (a code and a password, a password reset, or Google or Microsoft), so the team list shows you as joined even when you sign in only with Google. A Google or Microsoft sign-in of an invitation you have not accepted yet now asks whether to join that workspace or, when sign-up is open, to create your own account, and while you answer we hold a one-way hash of a one-time ticket for ten minutes. Both are deleted with your account. Changed on 11 October 2026 (signing out here, and back in): signing out of this website told the extension in the same browser to sign out whichever account it was signed in to, so a second person signing out here on a shared computer signed the computer owner's extension out, and signing back in here left the extension signed out. Signing out here now signs the extension out only when it holds the account you are leaving, and signing back in to that account here signs it back in. To tell the two apart, the extension keeps a note, in that browser only, that it was this website that signed it out. Nothing new is collected or sent. Changed on 11 October 2026 (a removed store's defaults, for when it comes back): removing or switching off an eBay store on the website used to leave its listing defaults and default postage policy in your settings under the store's old connection, where nothing would read them again: connecting the same eBay account again made a new connection, and its defaults started empty. They now leave your settings with the store and are kept aside for 180 days, under a SHA-256 hash of eBay's own id for that account (never the id itself or the username), and come back if the same eBay account is connected to the same SellFalcon account again. They are deleted then, after 180 days, when eBay tells us the account has been closed, or with your SellFalcon account. A store that is closed on eBay keeps nothing aside. Changed on 11 October 2026 (a store's postage default reaches your extension): the signed-in extension was told each website store's name and whether it works; it is now also told the name of the postage policy you set as that store's default in Settings, so a listing it publishes through that store starts on that policy, as one made on the website does. It is your own setting, sent only to the owner's own signed-in extension; nothing new is collected or kept. Changed on 10 October 2026 (when each of your browsers last asked for work): the account now keeps, for each browser whose extension signs in to it, that browser's install id (a random id the extension makes for itself, nothing about the computer), when it last asked for work and which version of the extension it ran. Until now only the latest browser to ask was kept. It lets the website say when the browser that holds your shop was last seen, and it goes with everything else when your account is deleted. Changed on 10 October 2026 (one account's shop is not sent to another): the extension used to send the shop it holds (listings, eBay orders with their buyers, drafts, purchase records with the buyers' addresses, blocked words and eBay fees) to whichever SellFalcon account was signed in, so signing out of one account and into another in the same browser sent the first account's data to the second. It now keeps, in that browser only, the email address of the account its shop was last synced to, and while a different account is signed in it sends none of that shop and runs none of that account's queued work until you press Send to this account in the extension and confirm. Nothing new is collected, and nothing leaves your browser that did not before. Changed on 10 October 2026 (later the same day: deleting on request, access records, pauses, disconnecting and buyers' usernames): this page said support would delete parts of your account on request (your synced data, your messages, your purchase records, your reports), and there was no way to do that short of deleting the account; it now says what is true: an account is deleted whole, and a support conversation or a piece of feedback can be deleted on its own. The record that you asked for access and were approved or declined had no end unless your account went; it is now kept twelve months and deleted sooner when you ask, which there is now a way to do. A paused account was said to be kept "exactly" as you left it; the time limits on this page still run while you are away, and the paragraph now says so. And disconnecting an eBay account now also deletes the listings you published from the website through it, which stayed behind, belonging to no account any more. The list of eBay usernames we keep to act on a buyer closing their eBay account kept every name for as long as your account lasted; a name now leaves it within two weeks once nothing of yours names it. Changed on 10 October 2026 (what is kept, held to this page): one paragraph this page was missing, and eight places where what we kept did not match what this page says, each now matching it. The paragraph is Limits on guessing and flooding: a failed sign-in has always noted the email address typed and the network address it came from, and the code, access, contact, support and error-report forms the network address alone, and this page never said so; those notes were also deleted only when the next one was written, and now go within a day whatever happens. The eight: the details you or the tool attach to an order (its cost, a note, the supplier's order number and tracking) were said to be deleted with the order, and were kept long after it had aged out of the tool and nothing could show them; they now go a month after the order has, unless its supplier order is still under way, and this page says when. Purchase records older than twelve months were deleted only when your extension next sent some, so if it stopped sending they stayed, and now they go on time whatever the extension does. Orders from an eBay account whose sign-in eBay had ended, or that had stopped selling, never aged out of our copy, each buyer's name, address and phone number with them; they now age out after about 45 days, as this page says, with that account's message list and questions. The record of a closed eBay account was deleted after 400 days only when another closure arrived; it now goes on its day. A support conversation or a piece of feedback could be deleted on request only by deleting your whole account; each can now be deleted on its own, at once, and feedback goes with the conversation that answered it. Deleting an account now also removes the alert and limit rows we kept named after it, and any file of its file cabinet that our index of the cabinet had lost track of. Removing a team member now removes everything kept under their own account, where before it removed some of it. And disconnecting an eBay account now also removes an AliExpress account's pairing with it, so that AliExpress account serves the whole workspace again rather than an account that is gone. Two more from the same day, under When someone closes their eBay account: a buyer who closes theirs now also loses their name from any label you put on a conversation with them (the label stays); and that section now says that, to find such a buyer in one step, we keep a list of the eBay usernames each seller's data has named, which was always so and was not said. And the record that you replied to a buyer's message from inside the tool, kept so a reply is never sent twice, had no end; it is now deleted after 400 days, which the eBay section now says. Last, the Paddle row said that what we store from Paddle is "only" your customer and subscription references, the plan, the status and the dates; we have also kept each payment that went through, and from 5 October each refund or chargeback, with its amount, currency, date and Paddle's reference, and the row now says so. Nothing about that changed today except this page. The same is true of cookies: since September, connecting eBay, AliExpress or Google on the Settings page has set one short-lived security cookie on our API's own domain, like the Google or Microsoft sign-in's, and this page named only two exceptions to "no cookies"; it now names three. Changed on 10 October 2026 (team invites by email): when a seller invites someone to their team from Your account, we now email that address once, through Resend like the rest of our email, saying how to join. Until now nothing was sent and the seller passed the steps on themselves. Changed on 10 October 2026 (an email that did not go): when an email we send only once (the welcome email, the payment-failed notice, or one of the alerts the person who runs SellFalcon gets about your account) is refused by our email service or gets no answer, we now keep a short record of it for 30 days: the address, the subject, the service's reason and when, so it can be sent by hand. Deleting your account deletes these records too. Changed on 9 October 2026 (orders: the buyer's checkout note and eBay's hub reference): for an eBay account connected on this website, the hourly order sync now also keeps, per order, the note the buyer wrote to you at checkout when they wrote one, and, for a sale eBay carries on itself from its own hub (eBay International Shipping, the Global Shipping Programme or authentication), that fact and eBay's reference for the parcel. Both are on the order in eBay already. The note is shown to you and your team on Orders and before an order is placed at the supplier, and it is never sent to AliExpress; it is kept with the order, and goes with the buyer's other details if they close their eBay account. An order placed at AliExpress from here also keeps a short fingerprint of the address it was sent to, never the address itself, so that a change of address on eBay afterwards is noticed. Changed on 6 October 2026 (the extension's old Settings page): this page said that opening the extension's own Settings page asked our API whether open sign-up was switched on. That was the extension's old Settings page, which nothing in the extension opened any more; it has been removed, and the extension's Settings (in its workspace) asks no such question, so the sentence is gone from the SellFalcon's own API row. Changed on 6 October 2026 (closed eBay accounts): this page said nothing about what happens when someone closes their eBay account. eBay tells us, and until now a seller's closed account removed only the web connection and what was synced through it, while a buyer's closed account removed nothing; we also kept a record of every closure eBay reported, including those of people who never used SellFalcon. Now a closed seller account also takes that store's copy in the extension's data, a closed buyer account is removed wherever a seller's data names them, and only the closures that removed something here are recorded. See When someone closes their eBay account under Your rights and choices. Changed on 6 October 2026 (support and feedback): four corrections, none of them a change in what is collected. This page said feedback is never answered; an answer to feedback is written into a support conversation of its own, starting with a copy of what you sent, and now it says so. It said a voice note is kept until the conversation is resolved; it is kept until the conversation is deleted, 30 days after it is resolved (or after 90 untouched days for one started while signed out). The list of moments that send the person who runs SellFalcon one email naming your address left out one: the last day of a complimentary plan we gave you. And the account emails named the approval of a request to join but not the one short email sent when a request is declined. Changed on 5 October 2026 (when Paddle’s checkout loads): the payments row said Paddle’s checkout software loads when you open the plan card on the Settings page. The plan card has been on Your account since the website’s redesign, and Paddle’s software is not loaded by opening it at all: only pressing a plan’s button (Start free trial or Subscribe), or following a Paddle payment link, loads it. Nothing else changed. Changed on 4 October 2026 (support conversations): this page said a support conversation is deleted once it is resolved, but a conversation from a signed-in account was in fact deleted only with the account or when you asked. Now a resolved conversation, with its messages, its attachments and any private note we wrote on it, is deleted 30 days after it is resolved, or sooner if you ask; writing in it again before then reopens it and stops that clock. A conversation that was already resolved before today counts its 30 days from the last change made to it. Changed on 4 October 2026 (eBay's own notices): this page has said that eBay's own notices are not kept, only what people wrote. That was not wholly true: the tool never fetched them in the background, but opening one in the Inbox kept its text beside your buyers' messages. From today opening a notice keeps nothing (it is read from eBay each time you open it), and the copies kept before were deleted. Buyers' messages and your own replies are kept exactly as before. Changed on 26 September 2026 (your eBay fee settings): the eBay fee percentage and fixed fee per order you price by belong to your account now, so the prices our servers work out for you (the automatic reprice, price suggestions and the check before a supplier order) use your own figures rather than eBay’s published fees. The website’s Settings reads and saves them, and a signed-in extension sends its own saved figures to your account once if the account has none, then keeps its copy in step with the account. They are two numbers about your fees; nothing else travels with them. With an extension that is signed out, they stay on your computer only, as before. Changed on 26 September 2026 (two pointers, nothing about your data): the section on who we are sent you to the services table "above"; it is below, in section 3. And signing the extension in or out is on Your account → Your extension, where the September redesign moved it from Settings. What is collected, and why, is unchanged. Changed on 16 September 2026 (one blocked-word list): the blocked-keyword (VeRO) word list belongs to your account now. Until this date it lived in the extension and reached us only as part of the extension’s settings copy; now the website’s Settings reads and saves it directly, and a signed-in extension keeps a copy on your computer, sends any word you add or remove there to your account, and takes the account’s list when it changes. The words are the brand names and terms you choose to be warned about; nothing else travels with them. With an extension that is signed out, the list stays on your computer only, as before. Also from this date, an eBay store that is already connected to another SellFalcon account cannot be connected to a second one: you are told, and nothing about that store is stored under the second account. Changed on 11 September 2026 (ordering at the supplier): the AliExpress connection can now CREATE an order, which is the first time anything about your buyer is sent out of SellFalcon rather than only stored. When you press Order at the supplier on an eBay order (in the tool’s Orders tab or on eBay’s own orders list) the tool shows you what it would buy, and on a second press sends AliExpress the product, the variant, the quantity and the delivery details of that order: your buyer’s name, address and phone number. It is the same information you would type into the supplier’s checkout yourself. What comes back and is kept is the supplier’s order number, and later the tracking number, stored against that eBay order in your account’s private space. Three things are true of every one of these orders and cannot be switched off: it is created UNPAID for you to pay in your own AliExpress account (their API has no payment call), SellFalcon never holds or uses a card of any kind, and nothing is ordered without a press. Ordering is off unless you turn it on, and marking the eBay order dispatched when the supplier ships is a second switch, also off. The "Connecting AliExpress on the website" section above has the full description. Changed on 11 September 2026: two features that read a page in your browser and send us nothing. First, Paste the buyer’s address at checkout: pressing Copy address on an eBay order reads your buyer’s name, address and phone so the next press at a supplier’s checkout can type them in. One address is held at a time, with the last five run logs beside it, in this computer’s storage only and never in Chrome’s settings sync; both are deleted after 30 days or at once from Settings → Buyer addresses. It is the first thing the extension keeps that is about your BUYER rather than about you, which is why it says so here, keeps only one, and forgets it quickly. Second, Save Temu’s own tax invoices: on a Temu orders page, saving an invoice asks Temu for its own tax-invoice pages with the session you are already signed in with, assembles them into a PDF and puts it in your Downloads. Nothing is stored and nothing is sent to us: not the order numbers, not the invoice, not the fact that you saved one. Reading a Temu page needs permission for temu.com, and reading an eBay order on the market you sell in needs permission for those eBay sites, so Chrome asks you for both when the extension updates; that is a permission to READ those pages, and neither feature sends anything from them anywhere. Changed on 10 September 2026: purchase records. Switching on Invoices in the extension lets it read your own AliExpress order history from the pages you are signed in to; the extension keeps four months of it on your machine, and, if you are signed in, each record is also copied to your account, which keeps twelve, so the year survives a reinstall or a new computer. What is copied includes the delivery address on the order, which for a dropshipped order is your buyer's address. The new "Your AliExpress purchase records" section above says exactly what is stored, for how long, where you see it, and what deletes it. Changed on 8 September 2026: the optional profile photo on Your account, described under "Accounts on this website"; eBay's own feedback percentage for each connected account is read with the hourly sync (one figure, no new personal data); and the replies you send to buyers on eBay are read from that account's Sent folder and kept with the buyer messages, so a conversation shows both sides, described under "eBay". Changed on 6 September 2026: private notes on support conversations, the one-email alerts to the person who runs SellFalcon, and the record of access decisions, all described under "Support chat on this website". Changed on 24 August 2026 (messages are kept on our servers now): this reverses the promise above, openly rather than quietly, on the owner's decision and for one stated reason: so your inbox opens instantly, from any computer, without asking eBay again for words it already gave us. What is kept: the cleaned text of each buyer message the tool has read (the tool reads the newest two months by itself, so your inbox is ready before you click) plus the sender, subject and date it already held. What is NOT kept: eBay's own notices, and anything older than your setting. How long: 2 months unless you choose 12 in Settings; every message older than that is deleted automatically, judged by the message's own date. What else deletes it: disconnecting the eBay account it came from, deleting your SellFalcon account, or asking support@sellfalcon.com. Choosing 12 months only reaches messages eBay still holds; history eBay has already cleared cannot be recovered. Nothing about this is shared with anyone, ever. Changed on 23 August 2026 (listing templates): the web listing editor can now save a listing template (your own description wording, item specifics, condition, brand, fee and cost settings, margin and price ending) so you do not retype them on every listing. A template is stored with your account until you delete it, and is deleted with your account. It holds nothing about any buyer, and by design it cannot hold a listing title, category, photo, item cost or variant: those belong to a single product rather than to how you list. Nothing is sent to eBay or anyone else by saving or using one. Changed on 23 August 2026 (messages stay readable offline): the text of your buyer messages is still never stored on our servers: that promise is unchanged. What changed is how long the copy in your own browser lasts: it used to be wiped the moment you closed the tab, so the tool asked eBay for the same messages again every time you came back. It now stays in your browser for up to 30 days, which is what lets the tool leave eBay alone. It never leaves your computer, it is tied to the account that read it, and signing out deletes it, so on a shared computer the next person cannot read your messages. Clearing your browser data removes it too. (Superseded on 24 August 2026: read messages are now also kept on our servers, see that entry.) Changed on 20 August 2026 (the invoice generator grew up, and a place for your logo and files): the Reports page's invoice now carries everything the documents you already send carry, due date, purchase order, currency, unit cost and quantity per line, discount, tax rate, shipping and a bank-details payment block: all typed by you and saved in the same per-month report space described above. The Settings page's Business details tab gained a logo (stored with your account, printed top-right on your invoices) and a company file cabinet: up to 15 files of 20MB each, stored in Cloudflare R2, owner-only, never read or processed by us, each deletable in one press and all of it deleted with your account. The new "Your logo and company files" section above has the full description. Later the same day: the invoice can also carry a one-off logo you pick just for it (for an invoice made for someone other than your own company); it is shrunk to print size and stored with that month's report data, deleted with the month or your account like everything else there. Changed on 20 August 2026 (alert emails, off unless you switch them on): the daily supplier check can now email you when it finds something waiting for your decision: a supplier price change with a suggested new price, an out-of-stock or restock, or a supplier page that has gone. One email per check at most, sent through the same email service named above, listing only your own listings' names and the supplier figures the check read. It is OFF unless you turn it on in Settings under Notifications, exactly as this tool promised when the switch did not exist yet, and turning it off stops it at once. Nothing new is stored: the email describes alerts the tool already records. Changed on 20 August 2026 (billing notices): two billing emails now exist, and only these two. Before a free trial ends you get one reminder naming the end date and, when the payment provider confirms it, the price, so the first charge is never a surprise; and when a subscription payment fails you get one note saying you keep access while the provider retries and where to fix the payment method. What we store to make that work is one small row per notice sent (which account, which notice, when), deleted with your account. Changed on 20 August 2026 (error reports): the website's pages now report their own script errors to us, as the new "Error reports from this website" section above describes: the error text, script, line, page and site version, nothing about you, deduplicated, capped, and deleted after about 14 quiet days. Changed on 19 August 2026 (a backup you own): you can now connect your own Google account on the Settings page, and SellFalcon keeps a copy of your inventory and orders in a "SellFalcon backup" spreadsheet in your own Google Drive, written when you press Back up now and roughly daily while you use the tool. The connection token is stored encrypted like the eBay and AliExpress ones, the permission is the narrow one that reaches only files SellFalcon itself created, disconnecting deletes our stored connection while the spreadsheet stays yours, and the whole thing is optional: nothing changes if you skip it. The same day added "Save to Google Sheets" on the Reports page: that month's sheet, written into a per-month spreadsheet in the same Drive, updated in place on a re-save. The new "Backing up to your Google account" section above has the full description of both. Changed on 19 August 2026 (the ad rate you choose): the ad-rates entry of 14 August said SellFalcon never changes a bid or spends your advertising budget, and until today that was the whole truth. From today there is exactly one exception, and it only happens on your own press: if you type an ad rate while publishing a listing from the web editor, that one listing is added to your running Promoted Listings campaign at that rate (or its bid is updated to the rate you typed, if it is already advertised) through your connected eBay account. One listing per publish, never on its own, never a campaign created for you, and everything else about ad rates remains read-only. The same day: you can connect several AliExpress accounts and pair each with one of your eBay accounts, as the AliExpress section above now describes; what is stored per connection is unchanged, plus the pairing itself (two connection ids). Changed on 19 August 2026 (the extension learns your connections' names): the signed-in extension is now told the display name and working/not-working status of each eBay connection on your account, never a token, so its Settings page and account menu can name the account listing runs through instead of claiming no store is connected. Owner sign-ins only, like the short-lived eBay token above; nothing new is stored anywhere by this. Changed on 19 August 2026 (naming your AliExpress accounts): you can now give each connected AliExpress account a name of your own choosing, stored with your account and deleted with the connection: the AliExpress section above says so. Two behaviour fixes the same day, with nothing new stored: signing into an AliExpress account that is already connected now refreshes that connection instead of failing (the several-accounts feature announced earlier on 19 August had kept an old one-account check in the final step of the connect flow, so a second account was still refused: that check is gone), and how many AliExpress accounts each account can connect is now a per-account setting we can adjust, shown on the Settings card. Changed on 18 August 2026 (a photo flow named, and a section corrected): two fixes to this page itself. First, attaching a photo to a message reply (added 17 August) sends the image from your browser through our server to eBay Picture Services, which hosts it; the reply then carries eBay's link to the photo and we keep no copy: the services table now says so, and this sentence dates when the flow began. Second, the "Connecting eBay on the website" section still said synced orders carry only buyer usernames; that stopped being the whole truth on 17 August when the order details described above (name, address, phone, postage service, delivery estimate, paid breakdown) began syncing, and the section now names them. What is collected did not change on 18 August; what changed is that this page now describes all of it in the sections people actually read, not only in this footnote. Changed on 18 August 2026 (the extension is set up by signing in): two new flows for a signed-in extension, both optional in the sense that your own keys always take priority. First, AI without a key: when the extension has no AI key of its own, its AI requests travel through our server to the AI engine under a key we hold, counted against your plan's hourly allowance: the AI engine row above describes exactly what is in such a request, and we keep no copy. Second, eBay without a developer app: the extension can ask our server for a short-lived eBay access token minted from the eBay connection you made on this website, so it can list on that account with nothing to configure; the long-lived connection token never leaves our server, the short-lived one expires within minutes, and only the account owner's sign-in can request one. Nothing new is stored about you by either flow. Changed on 17 August 2026 (support conversations): two small changes to the support chat. A conversation you start signed OUT now follows you INTO your account when you sign in on the same browser: the random key in your browser is exchanged once for account ownership of that conversation, so the answer reaches you on the Support page instead of being stranded. And signing out now also clears that random key from the browser, so on a shared computer the next person cannot open your conversations. What is stored about a conversation is unchanged. Changed on 17 August 2026 (order details): for an eBay account connected on this website, the hourly order sync now also stores, per order, what eBay already shows you in Seller Hub: the buyer’s name, the postage address and phone number they gave eBay, the postage service they chose, eBay’s delivery estimate, the paid breakdown (item price, postage, total), and the note you yourself wrote on the order on eBay. This is so the tool’s own order page can show a whole order (and its packing slip can carry the address) without a trip to eBay. These details live in your account’s private space, come only from eBay, age out with the order (the sync keeps roughly the last 45 days), and are deleted with your account. Changed on 17 August 2026 (message labels): you can now put a label of your own choosing on a message conversation (like eBay’s folders); the label and which conversation it belongs to are stored in your account’s private space until you remove them, and deleted with your account. The text of messages was still browser-only when this entry was written; from 24 August 2026 read messages are kept on our servers too; see that entry below for what is kept, for how long, and what deletes it. Nothing about any of it is shared with anyone. Changed on 16 August 2026 (the licence ping): the extension’s standing licence/plan check is retired: a signed-out extension no longer contacts our API on any schedule, and a signed-in one learns its plan from its own account session, as the services table now says. One small request was added at the same time: opening the extension’s Settings page asks our API whether open sign-up is switched on, so its sign-in box can describe the door correctly; the question carries no account data. Also from 16 August: complimentary access granted by hand has an end date, and that date (with the plan and where it comes from) is shown to you in Settings, in the extension, and stored with your account so every surface can agree. Changed on 16 August 2026 (the waitlist): the public waitlist form is retired and no new waitlist emails are collected; the handful already held are kept only until each person is invited, creates an account, or asks for deletion, exactly as before. Changed on 16 August 2026 (the short version, corrected): the summary at the top of this page still described the tool as it worked in its first week, "unless you sign in and use cloud sync, your selling data never touches our servers", with your API keys on your own computer and the AI running on a key you configure. That stopped being true when the work moved onto our servers, and three other answers on this page already said so, which means the summary was the one paragraph contradicting the rest of its own policy. It now describes what actually happens: an encrypted eBay connection on our servers, your ledger and orders in your account because the daily watch and the order sync run there with your computer off, no AI key for you to supply on this website, and card details that go into the payment provider's own form. Nothing about what is collected changed today; what changed is that the summary now matches the sections under it. Changed on 15 August 2026 (who runs this): this policy said SellFalcon was "an independent service based in the United Kingdom". That was wrong. SellFalcon is run by Khizar Hayat, a sole trader established in Pakistan, trading as SellFalcon, and he is the data controller. Nothing about what is collected, where it is stored or who it is shared with has changed: the services and their locations are unchanged and still listed above; what changed is that the person responsible is now named correctly. Changed on 15 August 2026 (sign-up): accounts can now be created two ways: by invitation, as before, or (when open sign-up is switched on) by you, by proving your email address with a one-time code. What we store for an account is identical either way and is described above; the code itself is stored only as a one-way hash and expires within fifteen minutes. Open sign-up is off unless we switch it on. Changed on 15 August 2026 (the payment overlay): the billing entry of 14 August said payment would be taken “on our payment provider’s own checkout page”. The flow that actually shipped is better described and is now described correctly: pressing a plan (or following a Paddle payment link with ?_ptxn= in it) opens Paddle’s checkout as an OVERLAY on our own page, drawn by Paddle’s software loaded from cdn.paddle.com, and that software is fetched as soon as the plan card is shown, so the overlay opens quickly, which means Paddle’s servers see your IP address and browser details when you view the plan card, not only when you pay. Your card details still go into Paddle’s form directly and never touch SellFalcon; what we store is unchanged and listed in the new Paddle row of the services table above. Changed on 14 August 2026: returns and cases: for an eBay account connected on this website, SellFalcon now also reads the return requests and cases that are currently OPEN on that account, and stores them in your account's private space so the dashboard can warn you before eBay's respond-by date passes. What is stored per request is small and comes from eBay: the buyer's eBay username, the item, the reason and status eBay records, when it was opened and the deadline. Only open ones are kept: when a return closes, it is deleted the next time we check. SellFalcon never answers a return, accepts one, sends a label or issues a refund on your behalf: every row links to eBay for you to decide, because that is your money. Changed on 14 August 2026 (later): listing traffic: for an eBay account connected on this website, SellFalcon now also reads eBay's traffic report for your own listings (how many times each listing was shown, the click-through rate eBay works out, and how many sold over the last 30 days) and stores the busiest 300 per account so the dashboard can show which listings are being scrolled past. These are aggregate counts about your listings; they contain nothing about any individual shopper. If you press “Suggest better titles” on one of them, that listing’s current title is sent to the AI engine (with a key we hold) exactly as the listing editor already does, and if you then press “Use this” the new title is sent to eBay through your connected account. Both are one press each, on one listing at a time, and neither happens on its own. Changed on 14 August 2026 (evening): ended listings: SellFalcon now also reads which of your listings ended without selling and have not been relisted, and stores up to 60 of them per account so the dashboard can show you what is still worth bringing back. If you press “Relist” on one, that single listing is relisted on eBay through your connected account: one listing per press, never in a batch and never on its own. Changed on 14 August 2026 (later that evening): ad rates: SellFalcon now also reads your running Promoted Listings campaigns and the rate each advertised listing is bidding, so the dashboard can tell you which ads cost more than the listing earns. This is read-only; SellFalcon never changes a bid, starts or stops a campaign, or spends your advertising budget. Changed on 14 August 2026 (night): questions: SellFalcon now also reads the questions buyers have asked about your listings and not yet been answered, so the dashboard can tell you one is waiting. What is stored is the subject line, the asker's eBay username, the listing and the date, not the full message body. SellFalcon never sends a reply: you answer on eBay, where the extension can draft the wording for you to change and send yourself, exactly as it already does. Changed on 14 August 2026 (late): the dashboard now has a Check eBay now button, which asks eBay for the same things the hourly sync asks for (your returns, listing traffic, ended listings, ad rates, questions and feedback) instead of waiting for the next hour. It only reads: nothing behind that button changes a listing, sends a message, answers a return or spends anything. Changed on 14 August 2026 (billing): if paid plans are switched on and you subscribe, the payment is taken by our payment provider on their own checkout page; SellFalcon never sees, handles or stores your card details. What we store is the provider's customer and subscription reference, the plan you chose, the status they report (trialing, active, cancelled and so on) and the trial/renewal dates, so the tool knows what you are entitled to. Cancelling is done in the provider's own portal; this tool cannot end a subscription for you. Updated 16 August 2026: paid plans went live on that date, so this paragraph applies from then on (it previously ended by saying paid plans were not switched on yet). Changed on 14 August 2026 (messages): the web tool now has a Messages screen. For an eBay account connected on this website, SellFalcon stores the LIST of your buyer messages from the last 30 days (subject, sender's eBay username, the listing, the date, and whether each has been read or answered) so the screen can tell you who is waiting. The TEXT of a message was not stored on our servers when this entry was written: it was read from eBay each time and kept only in your browser. That changed on 24 August 2026; see that entry below for exactly what is kept now, for how long, and what deletes it. If you press Write me a reply, that message's text and the order facts the tool already holds are sent once to the AI engine, exactly as the extension's older Draft reply button does. Nothing is sent to a buyer unless you press Send yourself; there is no automatic reply in this tool, and there will not be one. When you do send, we record which message you replied to, when, and how long the reply was (never the words), so a double press cannot message a buyer twice. Any saved replies you write are stored in your account until you delete them. Changed on 13 August 2026: one shared sign-in (see the section of that name above): the extension can now sign itself in from the session this website already holds in your browser, instead of asking you for your password a second time, and it is signed out when you sign out here. The extension also marks this site's pages so the tool knows it is installed in this browser, and our server now records when an extension last asked for its queued work, with its version and install id, so the tool can tell you whether anything is actually listening. Nothing new about your selling data is stored. Changed on 12 August 2026: support became a chat that lives on this website (see "Support chat on this website"): conversations are stored until resolved so replies can appear in the chat, and a signed-out conversation is tied to a random key in your browser. Also from 12 August: the signed-in feedback page stores what you choose to send us (message, category and optional attachments) so we can improve the tool. Changed on 12 August 2026 (later): support conversations and feedback can now carry attachments, including short voice notes; they are stored with the conversation or the feedback and deleted with it. Changed on 10 August 2026: the Orders tab stores the per-order details you type (supplier cost, supplier order number, a private note, tracking) in your account's private space, and dispatching from the web sends the fulfilment, with your tracking number, to eBay through your connected account or your extension. Changed on 10 August 2026 (later): the tool can now read the private notes you write on your own eBay orders (through your connected eBay account) and store what it finds (the supplier cost, supplier order number and tracking number) in your account's private space, so your profit figures fill in on their own; a tracking number read this way is only ever shown to you, and is never sent to eBay unless you press dispatch yourself. Also from 10 August: you can optionally connect your AliExpress account on the Settings page, which stores an encrypted connection token so the tool can read supplier product prices and stock without your browser being open (see "Connecting AliExpress on the website"). Changed on 10 August 2026 (evening): once you link a listing to its AliExpress product, SellFalcon checks that product's price and stock about once a day on our own servers, with no browser open, and stores what it finds so it can tell you when your supplier's price or stock changes. It only reports unless you switch automation on. Changed on 10 August 2026 (later still): you can now turn on automatic changes in Settings. With them on, SellFalcon updates your eBay price when your supplier's price moves (working out a price that keeps your profit, never copying the supplier's price) and sets your eBay stock to 0 when the supplier sells out, restoring it when they restock. Both are OFF unless you switch them on, both run on our servers, and every change is listed for you under Notifications. Changed on 9 August 2026: added the Users & Team section above: inviting a team member stores their email, role and sign-in, and gives them access to your workspace data; removing them deletes their account. Also from 9 August: the synced preference list now includes your blocked-keyword (VeRO) word list, so the web Settings page can edit it, and the extension settings card moved from the dashboard to the new Settings page. Changed on 9 August 2026 (later): cloud sync now also carries the names you gave your eBay stores (name and internal id only, never tokens), so the web tool and your team see real store names instead of internal ids. Changed on 9 August 2026 (evening): added the optional "Connecting eBay on the website" section above: accounts that connect eBay directly on the site have an encrypted connection token stored so the tool can sync orders and manage listings without the extension; it is deleted on disconnect or account deletion. This changes nothing for extension-only users. Changed on 9 August 2026 (night): the web listing editor: cloud sync now carries your full staged drafts (description, image addresses, prices, variants, item specifics and the supplier link, previously only a short summary), so you can edit them at sellfalcon.com/editor and publish straight to an eBay account connected on the website. Publishing uses the same encrypted eBay connection described above; a published or discarded draft is deleted from the server copy. Changed on 8 August 2026: added the optional "Sign in with Google or Microsoft" section above: the provider tells us only your verified email, which we match against invited accounts; nothing else changes and nothing new is stored. Also from 8 August: the support page's contact form stores your message and reply email until it is handled (see "The support form on this website"). Changed on 7 August 2026: added the monthly reports and invoices section above: what you type on the reports page (expenses, per-order extras, profit-share settings, and your and your client's business details for invoices) is saved to your account. Also from 7 August: the AI engine row covers the optional buyer-message reply drafts, and cloud sync now includes the short monitoring/orders preference list so the dashboard's Extension settings card can show and change those preferences. Changed on 3 August 2026: added the optional cloud sync: signed-in users can keep a copy of their listings ledger and orders in their account for the web dashboard. Nothing changed for signed-out users.

Questions, complaints or requests: support@sellfalcon.com. A human answers.