Privacy Policy

Who we are

Etronics Limited, registered in England and Wales under company number 15321490 at 20 Willow Close, Penarth, CF64 3NG, provides Seller Spring and is the controller of the personal data described here.

Payments for Seller Spring are taken through Stripe. Stripe receives only the account and billing details needed to take payments.

For data received from Temu, Etronics Limited, the registered Temu partner, is responsible and processes it only in the United Kingdom, as set out in Data from Temu below. Keepa, Rainforest and Firecrawl, named in Who we share it with, receive only Amazon product codes or Amazon page addresses from your own file, never data from Temu.

Contact Etronics Limited about anything in this policy at contact@seller-spring.co.uk.

What we collect

When you contact us through this website: your name, your email address, where you sell now, roughly how many products you have, whether you asked for product updates, and what brought you to the website (see Cookies and analytics below).

When you create an account in the Seller Spring app: your name, email address and password (stored only as a one-way hash), and the setup details you enter: business name, store label, business location, business type, whether you already sell on Temu, the marketplaces you sell on, your website, a contact name, roughly how many listings you have, and whether you want product updates.

When you set up your workspace we ask for your phone number. You can also add your company number, VAT number, marketplaces and rough listing count. We use your phone number to contact you about your account and trial, not for marketing calls without asking you first. These details are stored encrypted. Only the Seller Spring owner can open them. We delete them within 30 days after you close your account.

When you use the app: a record that an upload was checked (a count and a time, not the file). The quick check reads your eBay, Amazon or other export file inside your own browser and does not send it to our servers. If you ask us for a Temu-ready file, that export is uploaded to our UK server so we can prepare it. We delete the original 14 days after we release, send back or fail the file, and we keep the files we make for one year. If you ask us to prepare your product images, your browser sends us the web addresses of those images only; we download the images from the marketplace, prepare them for Temu and store the prepared copies. If you add pictures to Image Studio directly, they are stored on our UK server for 30 days, like the other originals you send us.

When you use the help chat: the messages you type are stored on our UK server for 90 days after the last message. Do not type personal, financial or tax details into it.

When you use the Compliance check: the product details you type (product, model number, manufacturer, store legal entity), any Temu rejection message you paste, and the files and photos you add. Files are stored encrypted and deleted at most 24 hours after you start the check. The saved upload plan lists your file names. It is stored encrypted and kept for 12 months, with the details and messages you entered for the check. Documents can carry the names and addresses of people at a manufacturer, insurer or test lab. Add only the documents Temu asks for.

When you connect a store: if you connect your eBay or Amazon seller account, we read your active listings (titles, descriptions, item details, images, prices, stock levels, SKUs and barcodes) through that marketplace's own authorised connection. If you connect your Temu store, we read your Temu listings so we do not create duplicates, and create or update listings, prices and stock as you approve. We keep the access tokens each marketplace gives us, encrypted. We do not request your buyers' personal details from any marketplace. Store data is used only to provide the service to you. When you disconnect a store we stop accessing it at once and delete its tokens; the rest is deleted with your account.

WooCommerce gives a read-only key technical access to products, coupons, customers and orders. Seller Spring uses that key only to fetch products and read currency, weight and dimension settings; we do not fetch buyer details, orders or coupons. We do not request buyer details from Temu, eBay or Amazon.

When you subscribe: your plan, subscription status and the identifier Stripe gives your customer record. Card details go to Stripe and are never seen or stored by us.

Technical data: a sign-in session cookie while you use the app, and standard server logs (IP address, time, page requested) kept for security.

Errors and bug reports. When the app hits an error, it reports it to us automatically. A report holds the type of error, the page name, the status code, the app version, and the time. It holds no file, product data, text you typed, web address or account details. If you press Report a bug, we keep what you write, the page, your browser type, language and screen size, and the last few error types and request numbers, linked to your workspace. Please do not put passwords, customer details, listings or uploads in a bug report. Emails, links and long numbers are removed before we store it.

Data from Temu

Connections to Temu are authorised to the Seller Spring app operated by Etronics Limited, the registered Temu partner. If you connect your Temu store, we access product and listing data so we can create and update your listings. We do not use Temu buyers' names, addresses, phone numbers or order details.

• Where it is kept: only on our dedicated server in the United Kingdom (Contabo, Portsmouth data centre). It is not sent to any other provider listed in this policy and is not transferred outside the UK.
• What it is used for: only to provide the service you asked for. We do not sell, share or use it for marketing, profiling or any other purpose.
• How long we keep it: it is deleted within 30 days of you disconnecting your store, closing your account or the service ending, unless the law requires us to keep it longer.
• How it is protected: personal data is encrypted at rest with AES-256 and in transit with TLS 1.2 or higher, and access is limited to the staff who need it.
• Incidents: if we detect a security incident affecting Temu data, we notify Temu within 24 hours of detection.
• Your rights: we help you and Temu respond to requests to access, correct or delete personal data.

Connected accounting software

Where an accounting connection is available, you can authorise Seller Spring through Xero, QuickBooks Online, FreeAgent or Sage Accounting's own sign-in and approval screen. If you authorise a connection, we use it to identify the organisation you select and read the accounts, tax codes or rates, and relevant Temu or Whaleco contacts needed to map your settlement figures. We keep the connection's organisation, status and permissions, and any account, tax and contact mappings you confirm.

We encrypt the access and refresh tokens we store on our UK server. Your original settlement file, its filename, transaction rows, order IDs and customer details in that settlement file stay in your browser. We do not send settlement or connected accounting data to an AI provider, analytics service or telemetry service.

Accounting posting is currently disabled. Connecting an accounting service or saving mappings does not authorise Seller Spring to create or change documents in that service. QuickBooks Online is being tested in sandbox and is not yet available for production companies.

The accounting service you select and our UK hosting provider process the connection data needed to provide this feature. The provider and operator roles described in this policy remain the same. We use connected accounting data only to provide the service to your business, not to build products for other customers or train AI models.

To ask us to disconnect an accounting service, delete connection data, or help with your data rights, email contact@seller-spring.co.uk. When we complete a disconnect, we remove our stored access and refresh tokens. For Xero and QuickBooks, we first confirm provider revocation; if it cannot be confirmed, the disconnect remains pending. For FreeAgent and Sage, you must also remove Seller Spring's access in that provider. Removing a connection does not delete records already held by your accounting service. Disconnecting does not by itself delete saved mappings. Contact us to request their deletion.

Why we use it, and our lawful basis

• To provide the app and your account: performance of our contract with you.
• To take payment and keep billing records: performance of contract and our legal obligations.
• To reply to messages you send us: our legitimate interest in answering enquiries.
• To send product updates: your consent, which you can withdraw at any time.
• To keep the service secure and prevent abuse: our legitimate interest in running a safe service.
• To find and fix faults, using automatic error reports and the bug reports you send: our legitimate interest in keeping the service working. Automatic error reports hold no account or personal details. A bug report is sent only when you press the button. You can object at any time at contact@seller-spring.co.uk.
• To run the Compliance check you ask for, including the AI review when it is on: performance of our contract with you.
• To see how people find and use this website (Google Analytics and the ss_attr cookie): your consent, given with Accept. You can change your choice at any time, see Cookies and analytics below.
• To test, measure and improve our service and listing tools, including the rules and AI prompts we use: our legitimate interest in making Seller Spring work better. We do this only with data from testers (people who joined through a tester invitation or tester code) and from our own team's accounts. We do not record or learn from anyone else, including customers who pay for a plan. For testers, we use the exports you send for a Temu-ready file, the listings, files and prepared images we make from them, and the corrections you make and results you get (for example changes to a suggestion, and whether a file was released or sent back). We do not use data that comes from Temu through a store connection or from a connected accounting service, anything made from that data, or anything that stays in your browser. An export of your own Temu listings that you upload to us yourself is different: from a tester we use it as our terms describe, and from anyone else we use it only to check their file. Testing a change can mean sending the same kind of product text or photo address to OpenAI as the live feature sends (see Who we share it with). We remove names, contact details and store identifiers wherever we can. We do not sell this data, use it in other sellers' listings or use it to train AI models run by other companies. It is kept only as set out in How long we keep it; after that we may keep summary results that are fully anonymous, meaning no one (including you or your business) can be identified from them, even when combined with other information.
• We may make general rules from patterns across our testers and our own team. These rules hold counts, never anyone's text, images, prices or product codes. We never learn product facts, claims or prices. Testers can ask us to stop at any time, as described below.
• Your right to object. If you are a tester, you can object at any time to our use of your personal data to improve Seller Spring by emailing contact@seller-spring.co.uk. We will then stop using your personal data for this. If you are not a tester, we do not use your personal data for this.
• To record how you found us when you sign up (the source carried in the sign-up link, saved with your account): our legitimate interest in knowing which channels bring us customers. You can object at any time.

Who we share it with

Data from Temu is handled only by:

• Etronics Limited: operating Seller Spring and processing Temu data in the UK.
• Contabo GmbH: the server in the United Kingdom that runs the Seller Spring app and database.
• Temu: only the listing data you choose to publish to your own Temu store.

Other data (this website, your account, email and billing) is also shared with the providers below. None of them receives data from Temu. Amazon product codes from your own file also go to ScrapingDog, Keepa, Rainforest and Firecrawl, for photo and price look-ups, as set out in their entries.

• Contabo GmbH: the servers that run the Seller Spring app and database, located in the United Kingdom.
• Cloudflare, Inc.: hosting of this website, and cookieless website analytics that do not identify you.
• Google LLC: our business email (Google Workspace), the fonts used on this website, and website analytics (Google Analytics 4, only if you choose Accept).
• Nylas, Inc.: sending email from our mailbox, such as account confirmation and password reset emails.
• Stripe: payment processing and subscription management.
• Telegram: if you choose Talk to a person in the help chat, the conversation so far is sent to our team through Telegram so they can reply. We also send our team a short alert through Telegram when a new kind of error appears. It holds the error type, the page name and a reference number we made, and no seller data.
• OpenAI: the AI provider for seller-facing features, used through its API. For a Temu-ready file, choosing the Temu category sends the product title, brand and your own category, and estimating size and weight sends the title, brand, category and up to four bullet lines. Other features run only when we have switched them on: writing a missing description or bullets sends facts taken from the title; reading colour, size and pack size from the title sends the title and brand; improving your own description and bullets sends them with the title (you can untick “Improve descriptions for Temu” on the Upload page for any file, and its own words are kept); writing new bullet points and a description sends the title, brand, Temu category, your description and bullet points and a short list of your product details (such as size, colour and material) to OpenAI twice, once to write and once to check each line against your text, and again if you ask for a new suggestion; if you tick “Optimise my titles and descriptions for Temu search” on the Upload page, the title, category and your own description, bullet points and attributes from your export may be sent to OpenAI so a better title can be suggested (nothing we wrote ourselves is sent, and a title is changed only where our checks pass); and reading the main product photo sends the title and the photo's web address, from which OpenAI fetches and reads the photo. In Titled, the title, category and your own product text (the description, bullet points and attributes from your Edit-products file) are sent when you ask for AI titles or suggestions, and for automatic improvement if you switch it on. For paid plans, Titled may also send OpenAI the weekly Temu search terms that match your product's category, to suggest title improvements. In Image Studio, if you switch on AI suggestions, the product title and variation text are sent so it can read the pack size. We do not send your name, contact details or store identifiers, but anything you put in your product text is sent, so please keep personal information out of it. Help-chat messages are sent with email addresses, links and long numbers removed. We do not send your account details, store connection keys, settlement data or your uploaded files as files. The Compliance check is the exception. When its AI review is on for your workspace, we send OpenAI the text of your PDFs (about the first 9,000 characters of each), up to 16 images (your photos, the first pages of scanned PDFs, and page 1 of a declaration of conformity, insurance certificate or declaration of identity), your file names, and the product, model number, manufacturer and store legal entity you typed for the check. We do not send the Temu rejection message you paste in. We send the rest so the AI can read your documents and match them to Temu's slots. The statement above about training and abuse-monitoring logs applies to this too. OpenAI says that data sent through its API is not used to train or improve its models unless the customer opts in, and we do not opt in. Its abuse-monitoring logs may contain what we send and are normally kept for up to 30 days, longer where the law or safety requires. Making a small photo larger (upscaling) runs on our own UK server and does not use an AI provider.
• ScrapingDog: an external photo lookup service. If an Amazon export has no photos and you have not connected Amazon, we send each product's ASIN to it, or to Keepa, Rainforest or Firecrawl below, to find the product's public Amazon photos. If one look-up service is unavailable we try another. Nothing else about you or your file goes with it.
• Keepa: an Amazon data service. It receives the Amazon product code (ASIN) from your own Amazon file, only to look up product photos and prices. If a product has no ASIN, its barcode (EAN or UPC) from your file is sent for the price look-up instead. No Temu data, product titles or your prices are sent.
• Rainforest: an Amazon data service. It receives the Amazon product code (ASIN) from your own Amazon file, only to look up product photos when your file has none. No Temu data, product titles or your prices are sent.
• Firecrawl: an external web page service. It receives the public Amazon page address for an Amazon product code from your own file, only to look up product photos when your file has none, and it opens that public Amazon page for us. No Temu data, product titles or your prices are sent.

We do not sell personal data. We share it with the organisations listed above and when the law requires us to.

International transfers

Seller Spring's service systems are in the United Kingdom. Temu data stays on Etronics Limited's UK systems. Some other providers are based outside the UK; where they process personal data abroad, we rely on UK adequacy regulations or the UK International Data Transfer Addendum, as appropriate. The text and images we send to OpenAI for the Compliance check, the Amazon product codes we send to ScrapingDog, and the product codes, barcodes and page addresses we send to Keepa, Rainforest and Firecrawl, may be processed outside the UK.

How long we keep it

• Account and setup details: while your account is open, then deleted within 30 days of closure.
• Prepared product images: the links to them stop working 30 days after we prepare them, and we remove the stored copies at the next clean-up after that. If you close your account, we delete your prepared images straight away.
• Exports you send for a Temu-ready file (the originals): deleted 14 days after we release, send back or fail the file.
• Temu-ready files we make: one year.
• Compliance check files and photos: deleted at most 24 hours after you start the check, or at once if you press "Delete my files now".
• Compliance check upload plans (they list your file names, stored encrypted), with the details and messages you entered for the check: 12 months.
• Automatic error records and bug reports: 90 days. A bug report is also deleted if the user is disabled.
• Help chat messages: 90 days after the last message, or sooner if you close your account.
• Billing records: six years for tax and accounting requirements.
• Contact form messages: up to two years after our last exchange.
• Server logs: up to 90 days.
• The ss_attr cookie: 90 days from your last visit, and only if you choose Accept.
• How you found us when you signed up: while your account is open, then deleted with it.
• Data used to improve the service (testers and our own team only): corrections, staff review notes, values our tools were unsure about and other results held in a Temu-ready file's record, including image results in its report, are deleted when that record is deleted. Image results held in store-sync records, and Titled suggestions and your decisions on them, are kept while your account is open and deleted with your account data after you close it. These results can outlast the prepared image or report they relate to. We may keep summary results that are fully anonymous, meaning no one (including you or your business) can be identified from them, even when combined with other information, including after your account closes.
• Your answers on the fix screen are kept while your account is open and deleted with your account data after you close it. An export of your Temu listings that you upload for checking is deleted 14 days after we finish with it.
• Google Analytics: visit-level data for 2 months, and its cookies for up to two years from your last visit.

Cookies and analytics

Your choice on this website. When you first visit seller-spring.co.uk we ask whether you accept analytics cookies. Accept and Reject are side by side and work the same way. Until you choose Accept, Google Analytics does not load and nothing about where you came from is stored in your browser. You can change your choice at any time with Cookie settings at the foot of every page, or the button below.

Visitor numbers. Cloudflare Web Analytics counts visits to this website. It sets no cookies and does not identify you. It sees the page you opened, the site you came from, and your browser and country in general terms. We use it only to count visits, which the PECR statistical-purposes exception allows without asking first. You can object at any time, free, here on the site: open Cookie settings and choose Turn off anonymous statistics. We then stop loading it from the next page you open, and remember your choice in the ss_consent cookie.

The Seller Spring app shows no cookie banner because it uses only the essential and preference storage above, none of it for tracking. The app does not store where you came from on your device.

How you found us, when you sign up. If you reach the sign-up page from a link that carries a source (for example a campaign tag, the referring site, the page you landed on and the date of your first visit), that source travels in the sign-up link and is saved with your account when you set up your workspace. It is not stored on your device. Our lawful basis is our legitimate interest in knowing which channels bring us customers. We keep it while your account is open and delete it with your account. You can object at any time by emailing contact@seller-spring.co.uk, and we will delete it.

Session recording for testers. If you take part in our test programme, you can choose to turn session recording on with the Turn on recording button in the app. This is separate from the tester agreement and stays off until you turn it on. While it is on, we record clicks, the pages you visit, client errors, failed requests and page loading times. All typed text and page text are masked, and forms, files, payment details, product tables and images are blocked in your browser before anything is sent. Recordings are kept on our own UK server, seen only by authorised admins, and deleted after 90 days. You can turn recording off at any time with the Turn off recording button. It also stops when your tester access ends. We do not record the sessions of anyone who is not a tester. The sessions of customers who pay for a plan are never recorded. Automatic error and bug reports (see Errors and bug reports above) are not session recording and apply to everyone.

Cookie settings

Your rights

You can ask us for a copy of your data, to correct it, to delete it, to restrict or object to how we use it, or to move it to another provider. You can withdraw consent to product updates at any time. Email contact@seller-spring.co.uk and we will reply within one month.

If you are unhappy with how we handle your data, you can complain to the Information Commissioner's Office at ico.org.uk.

Security

All traffic to this website and the app is encrypted with TLS 1.2 or higher. Personal data is encrypted at rest with AES-256, and passwords are stored only as one-way hashes. Each seller can see only their own business's data, and our staff access is limited to what their role needs. If a personal data breach puts you at risk, we will tell you and the Information Commissioner's Office as the law requires.

Changes

We will post any changes to this policy on this page and update the date at the top. If a change is significant, we will email account holders.