Legal

Privacy Policy

Last updated 25 October 2026

Seller Oracle is operated by WhiteKnight Software Design - FZCO, registered in the IFZA free zone, Dubai Silicon Oasis, Dubai, United Arab Emirates (licence 87386). We are the data controller for the personal data described in this policy ("we", "us", "our"). If you have any questions, email support@selleroracle.com or write to us at IFZA, Dubai Silicon Oasis, Dubai, UAE.

UK representative: WhiteKnight Software Ltd (company number 14607486), Flat 7, 95 Chalfont Drive, Nottingham, NG8 3NS, United Kingdom. Because we are based outside the UK, you and the Information Commission (ICO), the UK's data protection regulator, can also contact our representative about how we handle personal data under UK GDPR (Article 27).

What we collect

  • Account details. Your name, email address, and business name when you create an account.
  • If you had a KeepaVault account, the sign-in details it held. When KeepaVault accounts move to Seller Oracle, we receive your email address, your first and last name if KeepaVault had them, and your KeepaVault password in the scrambled form KeepaVault stored, so you can sign in with the same password. We use the scrambled password only to check your password when you sign in, and delete it as soon as you have a Seller Oracle password, or 90 days after we email you about the move if you don't have one by then.
  • If you had an OA Hero account, the sign-in details it held. When OA Hero accounts move to Seller Oracle, we receive your email address, your name if OA Hero had it, and your OA Hero password in the scrambled form OA Hero stored, if your account had one, so you can sign in with the same password. If you never set one, you choose a Seller Oracle password with Forgot password. We use the scrambled password only to check your password when you sign in, and delete it as soon as you have a Seller Oracle password, or 90 days after we email you about the move if you don't have one by then.
  • If you had an AmazSeller account, the account and deal records it held. When AmazSeller closes on 29 October 2026 and its accounts move to Seller Oracle, we receive your email address, your name, your business name and your team, and every deal your business recorded. We keep the deals out of sight. The account owner can choose to import the purchases into their orders, and we delete the deals on 29 October 2027 either way.
  • Email data. When you connect your Google or Microsoft account or forward emails to your Seller Oracle address, we read your retailer and business emails (order confirmations, dispatch notices, delivery updates, verification codes, and expense receipts) to extract order and expense data.
  • Extracted data. The order, purchase, and expense records we build from those emails, including retailers, amounts, quantities, statuses, and attachments such as receipts and invoices.
  • Authentication tokens. If you connect Google, Microsoft, or Amazon, we store OAuth access and refresh tokens, encrypted at rest, so we can act on your behalf (reading emails, creating listings or checking what you can sell). We never see or store your account password.
  • Marketplace data. If you connect your Amazon seller account, we send listing data (ASIN, SKU, price, fulfilment method) to Amazon on your behalf to create offers on existing products. If you switch on automatic listing, we also send it for each new purchase without a click, and change a listing's price to your next markup when Amazon says it looks too high. When you open a listing pop-up, or automatic listing lists an item, we send Amazon the item's ASIN to read its current price. We also send Amazon the ASIN of each item you buy that isn't listed yet, automatically and again from time to time while it stays unlisted, to check whether you can sell it, and we keep Amazon's answer to show on the item. We do not access or store buyer personal information.
  • Product brands. If you connect your Amazon seller account, we also read the brand of each item we check from Amazon's catalogue, and show a warning on the item when that brand is on a list of brands sellers have reported problems with, such as IP complaints. We keep the brand with Amazon's answer for that item and delete it with the answer. Nothing about you or your account is sent anywhere to make that comparison.
  • Product details. If you connect your Amazon seller account, we also read each checked item's title, size, pack quantity and category from Amazon's catalogue, whether Amazon lists it as a parent of variations or for adults, its dangerous goods class, and whether Amazon lists it as dated for expiry, in the same request as its brand. We use the title, size and pack quantity to check that the ASIN is the product you bought, and the dangerous goods class to fill in the Prep centre's dangerous goods answer for you to check. We keep all of them with Amazon's answer for that item, deleted with it.
  • Your stock and sales on Amazon. If you connect your Amazon seller account and your plan includes Foresight, we read once a day, for each product you have in stock at Amazon or on the way there: its ASIN and title, your SKUs for it, your price, your stock at Amazon, on the way and that Amazon can't sell, the date you listed it, and how many units you sold and in how many orders. We use them only for Foresight, including in an AI assistant you connect, and we never read anything about your buyers. On the free plan, or while your Amazon connection is off, we read none of it.
  • Card exports. When you upload a card export (a list of transactions you download from your card provider, such as Capital on Tap), we read it to find the euro and dollar purchases in it. For each of those we keep its dates, merchant and amounts, to match it to your orders and expenses and set what your card actually charged. Nothing is created from them. We don't keep the file itself, and we never keep the card number, card ending or cardholder name it contains. You can delete an upload, which removes its purchases.
  • Amazon pages you open, if you use our browser extension. When you or anyone in your workspace connects the Seller Oracle extension for Chrome, it records each Amazon product page opened in that Chrome profile while it is connected. For each page it records the product's ASIN, the Amazon site, the product's title (from the tab's title, or read from the page when it switches to another version of the product, such as a different size or colour) and when it was opened. It records nothing else from Amazon and nothing from any other website. These pages are shared across your workspace, and we don't record which person opened each one.
  • Payment information. When you subscribe, your payment is processed by Stripe. We do not store your card number or bank details. Stripe acts as an independent controller for its own fraud-prevention and compliance purposes, and as our processor for billing. See Stripe's privacy policy for details.
  • Usage and diagnostics. Basic technical logs needed to run the service and diagnose errors. We scrub personal data, email content, and tokens from these logs.
  • Referral and payout information. Your referral code, the commissions you earn, your payout requests, and the PayPal email if you save one.
  • Qogita referrals. The name, and the business name if you give it, of a friend you tell us you referred to Qogita.
  • Giveaway entries. If you enter a Seller Oracle giveaway, your entry: when you joined and confirmed you can enter, your points, the challenges you completed and, if we disqualify it, when and why. If you win, we'll give your surname and county to anyone who asks, as the giveaway's rules say.
  • Feedback and support messages. When you contact us through the in-app feedback or support form, we collect your message, an optional subject, and the page you were on, together with your account email, so we can respond and improve the service.

Lawful basis for processing

Under UK GDPR, we must have a lawful basis for each type of processing we carry out. Here is how we rely on those bases:

  • Contract. Processing your account details, email data, extracted records, card exports you upload, and authentication tokens is necessary to provide the service you signed up for. Without this processing, Seller Oracle cannot function.
  • Contract. If you or your team connect our browser extension, processing the Amazon product pages it records is necessary to provide the ASIN suggestions you asked for.
  • Contract. If you sign in to KeepaVault, OA Hero or QogitaScout with your Seller Oracle account, sending it your name, email address, workspace name, Seller Oracle user ID and the status of your Seller Oracle trial is necessary to sign you in, as you asked.
  • Contract. Processing your payment through Stripe is necessary to perform the subscription agreement between us.
  • Legitimate interests. If you had a KeepaVault account with a confirmed email address, and that address had no Seller Oracle account, we move your sign-in details to Seller Oracle so you can keep signing in to KeepaVault, which now uses Seller Oracle accounts, with the same email address and password. If the address already had a Seller Oracle account, we copy nothing, and KeepaVault uses that account. If you can sign in to Seller Oracle, we email you once about the change, unless the address already had a Seller Oracle account and you've told us not to send you news emails. We have assessed that this does not override your rights. You can object by emailing support@selleroracle.com or replying to that email: we then leave you out of the move, or delete the Seller Oracle account it made for you.
  • Legitimate interests. If you bought OA Hero, and your email address had no Seller Oracle account, we move your sign-in details to Seller Oracle so you can keep signing in to OA Hero, which now uses Seller Oracle accounts, with the same email address and password. If the address already had a Seller Oracle account, we copy nothing, and OA Hero uses that account. If you can sign in to Seller Oracle, we email you once about the change, unless the address already had a Seller Oracle account and you've told us not to send you news emails. We have assessed that this does not override your rights. You can object by emailing support@selleroracle.com or replying to that email: we then leave you out of the move, or delete the Seller Oracle account it made for you.
  • Legitimate interests. If you could sign in to AmazSeller and didn't ask to be left out, we can move your business to Seller Oracle so you can keep your records. If its owner's email address had no Seller Oracle account, we make the business a Seller Oracle account, with its owner as the account owner. Its team members join it too, when we have their names and their email addresses had no Seller Oracle account. You choose a password when you confirm your email address. If the owner's email address already owned a Seller Oracle account, or they've confirmed an account is theirs, the business's records wait in that account instead, and we make no new one. AmazSeller deals are imported into the account's orders only when the account owner asks. If we make you an account, or add you to one, we email you once so you can confirm your email address. If your business's records wait in an account you already had and include purchases to import, we email you once to say they're ready, unless you've told us not to send you news emails. We have assessed that this does not override your rights. You can object by emailing support@selleroracle.com: if you're a team member, we then remove you from the account, and if you're the owner, we delete the business's AmazSeller records and the Seller Oracle account the move made, if it made one.
  • Legitimate interests. We process usage and diagnostic logs to keep the service running, detect and fix errors, and improve reliability. We have assessed that this does not override your rights, given that we scrub personal data and email content from these logs.
  • Legitimate interests. When you send feedback or a support request, we process your message and contact details to respond to you and to improve the service. We have assessed that this does not override your rights.
  • Legitimate interests. To keep the AI that powers the service accurate and cost-effective, we keep a record of the information we send to our AI providers and the results they return, so we can evaluate and compare AI models over time and choose the best one to process your emails and the receipts and invoices you upload. We have assessed that this does not override your rights: these records are encrypted, isolated to your account, used only to evaluate and improve how Seller Oracle uses AI, kept only while your account is active, and erased when you delete your account. You can object to this processing at any time.
  • Legitimate interests. We use cookie-free website analytics to count visits to our public website, the signed-out account pages and the plan page, and see how people find us. The analytics provider receives your IP address, browser details, the page you visited and the page you came from, and does not use them to identify you or track you across sites. We have assessed that this does not override your rights. You can turn it off at any time in Website analytics below.
  • Legitimate interests. When you tell us about a friend you referred to Qogita, we keep their name, and their business name if you give it, to check them against Qogita's monthly report, pay you the reward you asked for and tell you the result. We have assessed that this does not override your friend's rights: we use the name for nothing else and erase it with your account.
  • Contract. If you enter a giveaway, processing your entry is necessary to run the giveaway you entered under its rules, including checking the sign-in records we keep for your account to stop fraud in it.
  • Legal obligation. We retain certain billing and transaction records as required by applicable tax and accounting law.
  • Legitimate interests. If you sign up on or after 10 October 2026, we send you Seller Oracle news emails about new features and any changes to our plans and offers, unless you tick "Don't email me about new Seller Oracle features and offers." when you sign up. These rely on our legitimate interest in telling our customers about our own service, and on the rules that let a business email its own customers about its own similar products and services. We only use this list for Seller Oracle's own emails.
  • Consent. If your account was created before then, or you joined a team someone invited you to, we send you news emails only if you said yes in the app. Whichever applies to you, every news email has a one-click unsubscribe link, and you can turn news emails off at any time in Settings, under Profile.

How we use AI to process your emails

Seller Oracle uses artificial intelligence to classify your emails and extract structured data such as order details, quantities, prices, and expense records. This is a core part of the service and is necessary to deliver the features you signed up for.

When an email arrives, its content is sent to one or more third-party AI providers for classification and data extraction. The AI determines whether an email is a retailer order, dispatch notice, delivery update, expense receipt, or something else, and extracts the relevant fields. The AI does not make decisions that produce legal or similarly significant effects on you. It extracts data for your review, and you remain responsible for verifying the accuracy of extracted records.

When you upload a photo or scan of a paper receipt or invoice, that file is sent to the same category of third-party AI providers to read the order details from it, in the same way as an order that arrives by email. A receipt you import is created as a draft for you to confirm. An invoice you upload in bulk is matched to the order it belongs to and attached there; it is only sent to the AI when its order number can't be found in its file name or text.

When you upload a card export, Seller Oracle matches most purchases to your orders and expenses itself. A purchase it can't match exactly is sent to the same category of third-party AI providers, with the dates, retailers, amounts and item names of the orders and expenses it might belong to, so the AI can say which one it is. The money always comes from the card line, never from the AI, and no card number or cardholder name is sent. These requests are not kept as the AI records described below.

When an item you bought has an ASIN and your Amazon seller account is connected, Seller Oracle checks that the ASIN is the product you bought, so you can fix it before you list the item, or cancel the order. It sends the same category of third-party AI providers the item's name and shop, with Amazon's title, size and pack quantity for that ASIN, and keeps the answer on the item. Nothing else about the order is sent. These requests are not kept as the AI records described below.

If you use the Seller Oracle browser extension, Seller Oracle suggests the ASIN of an item you bought from another shop. It sends the same category of third-party AI providers the shop's name, the item's name and the titles of up to 10 Amazon products your workspace opened around the time you bought it, so the AI can say which of them is the same product. The ASINs themselves are never sent, and nothing is filled in on the item until you choose a suggestion. These requests are not kept as the AI records described below.

If you connect your Keepa key and track your Amazon UK buys on the EU stores, Seller Oracle checks whether each product plugs into the mains, so it isn't tracked on a store where its plug doesn't fit. It sends the same category of third-party AI providers each product's name and ASIN, and keeps only the answer. These requests are not kept as the AI records described below.

For price history, Seller Oracle checks which of the products a UK price comparison website found for an item you bought are the same product, so the history is that product's. It sends the same category of third-party AI providers the item's name, how many you bought and the shop's name, with the names, categories and lowest prices of up to 5 of the products found. Nothing else about the order is sent. These requests are not kept as the AI records described below.

To keep this accurate and cost-effective, we also keep a record of the information we send to the AI and the results it returns, so we can test and compare AI models over time and choose the best option to process your emails and the receipts and invoices you upload. These records are encrypted, kept only while your account is active, and deleted when you delete your account. We do not use them for advertising and we do not sell them.

To find and fix mistakes in how Seller Oracle reads emails, we may also send one of these records, for an email Seller Oracle read wrongly, sent to Needs review, or got wrong while testing a change to how it reads emails, to the same category of third-party AI providers, under the same terms, so the AI can describe what went wrong: the shop, the kind of email and the rule that reads it right, written to leave out personal details. This step shows people at Seller Oracle only the description, never the email itself, and for an email from a connected Gmail account only general rules drawn from the emails of several sellers. We use what we learn only to improve how Seller Oracle reads emails.

You have the right to query how a specific email was classified or how data was extracted. Contact support@selleroracle.com if you believe something has been processed incorrectly.

How we use Google user data

Seller Oracle requests access to your Gmail to read and label the retailer and business emails relevant to your purchase and expense tracking. We use this access only to provide and improve the features you see in the product: extracting your orders and expenses, surfacing verification codes, organising your backend, checking whether Amazon lets you sell the items you buy and listing them on Amazon once you connect your Amazon seller account, answering your questions in an AI assistant you choose to connect, checking that each item's ASIN is the product you bought, looking up the price history of the items you buy, showing a picture beside each item you buy, completing product names your order emails cut short, watching Amazon's price for the items you buy through a Keepa key you connect, sending your item costs to an app you choose to connect, sending alerts to a Discord, Slack or Telegram chat you choose, or by email to people in your team, and unsubscribing you from senders you choose.

Seller Oracle's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not use your Google data for advertising, we do not sell it, and we do not transfer it to others except as needed to provide or improve the service, comply with the law, or as part of a merger or acquisition. Human access to Google data is restricted to what is necessary for security, such as investigating a possible bug in how Seller Oracle read one of your emails, to comply with the law, or where you have given consent. People at Seller Oracle may also see aggregated, anonymised information drawn from it, such as general rules about the kinds of email shops send, to improve how Seller Oracle reads emails.

How we use Microsoft user data

If you connect a Microsoft account, Seller Oracle accesses your Outlook mailbox through the Microsoft Graph API solely to read and label the retailer and business emails relevant to your purchase and expense tracking, and to provide and improve the same user-facing features described above: extracting your orders and expenses, surfacing verification codes, organising your backend, checking whether Amazon lets you sell the items you buy and listing them on Amazon once you connect your Amazon seller account, answering your questions in an AI assistant you choose to connect, checking that each item's ASIN is the product you bought, looking up the price history of the items you buy, showing a picture beside each item you buy, completing product names your order emails cut short, watching Amazon's price for the items you buy through a Keepa key you connect, sending your item costs to an app you choose to connect, sending alerts to a Discord, Slack or Telegram chat you choose, or by email to people in your team, and unsubscribing you from senders you choose. We do not use your Microsoft data for advertising, we do not sell it, and we do not transfer it to others except as needed to provide or improve the service, comply with the law, or as part of a merger or acquisition.

Service providers (sub-processors)

We use a small number of trusted third-party providers to run Seller Oracle. Each receives only the data needed to perform its function, and only to provide or improve the service for you:

  • Email access — we connect to your mailbox through your email provider's API (Google Gmail or Microsoft Outlook) to read your retailer and business emails.
  • Marketplace integration: if you connect your Amazon seller account, we send listing data to Amazon through their Selling Partner API to create offers on your behalf, the ASIN of an item whose listing pop-up you open or that automatic listing lists, to read Amazon's current price for it, and the ASIN of each item you buy that isn't listed yet, to check whether you can sell it.
  • Price tracking: if you connect your own key for a price-tracking service, that service receives the ASIN of each item you buy from an Amazon store, the price to watch for on each store (the price you paid, one worked out from it, or one you set) and a reference of ours for each one, so it can tell us when Amazon's price comes back. It never receives your name, your email address, your order numbers or anything else about your account. When you remove the key, we stop sending it anything and ask it to delete our lists.
  • Market data: for Foresight, a market data service receives the ASIN of each product you have in stock at Amazon or on the way there, and the Amazon store, and tells us that product's sellers with their prices and stock, the Buy Box, Amazon's own price and stock, how many sell, and their history. To show the right picture beside your items, look up their price history by barcode or name and complete product names your order emails cut short, it also receives the ASINs of the items you buy and of the products suggested for them, with the Amazon store: Amazon UK for each, and for an item you bought on Amazon Germany, France, Italy or Spain, that store as well. It tells us each product's picture, barcodes and title. It never receives your name, your email address, your prices, your stock, your SKUs or anything else about your account.
  • Price comparison: for price history, a UK price comparison website receives the product name or barcode of items you buy, which can be the product's title or a barcode from the market data service's record of the product, and tells us their price history and which shops have them today. It never receives your name, your email address, what you paid, where you bought it or anything else about your account.
  • Product pictures — to show a picture beside an item wherever Seller Oracle lists your items, your browser loads it straight from Amazon, using the picture named in the market data service's record of the product when there is one, or else the item's ASIN, or the ASIN of a product suggested for it. Amazon receives that picture's name or ASIN, your IP address and the standard details your browser sends with any request, such as its type and language, but nothing else about the order. You can turn pictures off in your Appearance settings.
  • AI processing — third-party AI providers classify your emails and extract your order and expense data, including from photos or scans of receipts and invoices you upload, match card export purchases that Seller Oracle can't match by itself to your orders and expenses, suggest the ASIN of items you bought from other shops from the Amazon pages your workspace opened, check that each item's ASIN is the product you bought, match an item you bought to the same product on a price comparison website, describe what went wrong when Seller Oracle reads an email wrongly, and guess whether a product plugs into the mains, for tracking your UK buys on the EU Amazon stores.
  • Notifications — a third-party communications provider receives the feedback, support requests and problem reports you send, account activity such as sign-ups, connected accounts, subscription changes and payments, and calls you book with us along with your answers to the booking questions, together with your name, account email, business name, subscription status and the mailbox or Amazon seller account you connected, so our team can respond and support you.
  • Chat alerts: if the account owner connects a Telegram chat under Alerts, a messaging provider receives the alert messages our bot sends there, to deliver them to that chat.
  • Payment processing — Stripe processes your subscription payments and handles card data on our behalf.
  • Referral payouts: if you choose PayPal for a referral payout, PayPal receives your PayPal email and the amount so we can pay you.
  • Hosting and storage — cloud infrastructure providers host the application, database, and your stored attachments.
  • Email delivery — an email provider sends transactional and account emails, our news emails, and the daily alert summaries the account owner sets up, on our behalf.
  • Error monitoring — a monitoring provider helps us detect and fix errors, with personal data and tokens scrubbed.
  • Website analytics — a cookie-free analytics provider counts visits to our public website, the signed-out account pages and the plan page so we can see how people find us. It sets no cookies and does not track you across sites. It does not run on the pages that show your orders and email data.

We do not sell your data, and we do not share it with anyone except as needed to provide or improve the service, comply with the law, or in connection with a merger or acquisition (for data from our browser extension, only with your consent first). A current list of the specific providers we use is available on request.

Sharing with a prep centre you nominate

If you connect your Seller Oracle account to a prep centre and give your consent, we share the one-time delivery codes for your incoming parcels with that prep centre's staff, along with your name, your business name, the retailer, the product description and tracking number for each parcel, and the time each code arrived, so they can accept deliveries on your behalf. We do this only while you keep the connection active. Every code their staff view is logged, and you can stop the sharing at any time from your settings.

Connecting an AI assistant you choose

If you connect an AI assistant, such as Claude or ChatGPT, to your Seller Oracle account, we send that assistant's provider the data it asks for so it can answer your questions. That can include your orders with their items, refunds and whether each refund email showed its currency, what each purchase was for, who set its category and why any needs review, which orders you moved from AmazSeller, whether Amazon lets you sell each unlisted item, how each item's Amazon listing went, with the reason when it failed, whether each order counts as sent to your prep centre, the state of its PrepBusiness inbound shipments and which of its items each holds, any warning that an item's ASIN may not be the product you bought, with its reason, which can quote Amazon's title, the price history Seller Oracle found for items you bought, with the lowest prices and the shops that had them, your spend, retailers and expenses, your to-do list, including how many emails wait for your review, your invoice file names and links to download them, your products in Foresight, with your price, stock and sales at Amazon and the market figures Foresight shows for them, the checks Seller Oracle runs for you in the background, overall and for each order's items, with when each last ran, when it runs next, what it found and any problem, your price-back alerts: the products on your Keepa list, the price watched for on each Amazon store and the latest price Keepa reported when it came back, your Seller Oracle plan, its billing status and its billing dates, on the free plan or Starter this month's order allowance, orders used and left and how many order emails are waiting, your next payment's amount, and any failed payment: its amount, date, reason and next retry, and, on a trial or the free plan, what Seller Oracle has tracked for you since you started or over the last 30 days: how many orders, from how many shops, how many were followed to delivery, the invoices filed and the refunds matched with their total, how many orders you buy a month, the plan that fits and, on the free plan, how many order emails are waiting. We also send when each order's delivery code was received and, when you ask about a specific order, that order's delivery code. It can also include your Seller Oracle giveaway entry: whether you've entered, your points and the challenges still open to you. The assistant can read this data but cannot change anything. It never receives your emails or the invoice files themselves, only links that open them in Seller Oracle when you are signed in. Only the account owner can connect an assistant, by signing in to Seller Oracle and approving it. Each time an assistant reads your data, we keep a record of it. The record shows which assistant it was, what it looked up, any search words it used and whether it was shown a delivery code. You can see your connections in your settings and disconnect any of them at any time. How the provider handles the data after that is covered by your own agreement with them.

Connecting an app you choose

If you connect an app, such as a profit tool, to your Seller Oracle account, we send it the ASIN, SKU and cost of each item you've bought, with VAT. It never receives your orders, emails, invoices or delivery codes, or where or when you bought anything, apart from anything your SKU format puts in the SKU. Only the account owner can connect an app, by signing in to Seller Oracle and approving it, and can disconnect it at any time in your settings. Each time an app reads your costs, we keep a record of which app it was, when, and how many rows it read. How the app handles the data after that is covered by your own agreement with it.

Sending alerts to a chat you choose, or by email

If the account owner adds a Discord or Slack channel, or connects a Telegram chat, under Alerts in your settings, we send it short messages about your orders when Seller Oracle picks up changes from your emails or its own checks. A message can include shop names, item names and quantities, prices and order totals, refund amounts, order numbers and dates, why an order was cancelled, needs a check or had a refund held, the result of an Amazon listing, and links to the orders, which open only when you are signed in to Seller Oracle. A message can also say that a prep centre export failed, with the reason in our own words, that one of your mailboxes stopped importing emails, naming its provider (Gmail or Outlook) but never its address, that email reading is paused, that Amazon removed Seller Oracle's access, or that your plan's monthly order limit is holding order emails, with how many. If the account owner switches on Delivery code arrived for a channel or chat, a message also shows the courier's delivery code for an order, the courier and the order number, so anyone who can read that channel or chat can use it, and we keep a record of each code sent: which order, which channel or chat, and when. If you connect Keepa and switch on Amazon price back for a channel or chat, a message also tells you when Amazon's own price for a product you bought is back at or under your price: the product's name, Amazon's price on each store it came back on, what you paid and the Amazon store you bought it on, or the price you set, and for a store tracked from an Amazon UK buy the price in euros Keepa watches for and any discount you chose, a link to the product on Amazon, and a link to its page in Seller Oracle, which opens only when you are signed in. Anyone who can read that channel or chat can read the messages. Orders you hide, or hide on stream, are never sent, and we never send your emails, invoice files or our AI's notes. Discord and Slack messages go through the webhook link you create there, so they reach the channel you chose. Telegram messages go through Seller Oracle's own Telegram bot, so Telegram receives them from us and delivers them to the chat that was linked. To link a chat we keep its Telegram id and name, and a private chat's name is the Telegram name of the person in it. No alerts are sent until the account owner confirms the chat, and our record of who linked it (their Telegram name and username) is kept only until then. Only the account owner can add a channel or connect a chat, and when they save one, or confirm a Telegram chat, we record who agreed, when, and which wording they saw. Removing a channel or chat stops the messages at once. How Discord, Slack or Telegram handles the messages after that is covered by your own agreement with them.

The account owner can also have a daily summary sent to a chat, or by email to people in your team they tick who can see the Action Centre; we never send it to an address typed in. A summary covers what happened since the last one: how many new orders arrived and their totals, how many were dispatched, delivered, listed on Amazon or had an invoice added, the cancellations, refunds, held refunds, checks and Amazon listing failures, the orders that became late and how late they are, and how many orders wait in each Action Centre list. A summary sent to a chat also lists the products whose Amazon price came back, with the details a message gives, when Amazon price back is in it; a summary email never does. A summary also lists those prep centre export failures and account problems while they last, and never shows a delivery code. The cancellations, refunds, held refunds, checks, Amazon listing failures, prep centre export failures and late orders it lists carry the details a message does, such as shop names, item names, amounts, order numbers and reasons, and orders you hide, or hide on stream, are never in it. Summary emails go through our email provider, each one has a link that takes that person off it without signing in, and removing someone from your team takes them off at once. Only the account owner can set up a summary email, and when they save one we record who agreed, when, and which wording they saw.

Unsubscribing you from senders you choose

When you ask Seller Oracle to unsubscribe you from a sender, it sends that sender the one-click unsubscribe request their email offers, and keeps the unsubscribe link from their emails until then. Nothing else about you is sent.

The Seller Oracle browser extension

The Seller Oracle extension for Chrome is optional. Anyone in your workspace can connect it, and it records the Amazon product pages described above only while it is connected. Seller Oracle uses them only to suggest the ASIN of items you buy from other shops, on the Needs ASIN tab, where you choose whether to use a suggestion. You can disconnect it at any time in the extension, or in Settings under Chrome extension, where the account owner can also disconnect anyone's. Settings shows who connected each extension, when, and when it last sent a page.

Seller Oracle's use and transfer of information received from the Seller Oracle extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. We use this information only to suggest ASINs. We do not use it for advertising, we do not sell it, and we do not transfer it to others except to the providers that help us run that feature, such as the AI provider described above, to comply with the law, or, with your explicit consent first, as part of a merger, acquisition or sale of assets. Human access to it is restricted to what is necessary for security, to comply with the law, or where you have given consent, for example by asking our support team to look into a problem on your account. Otherwise we only look at aggregated, anonymised figures, such as how often a suggestion is used, to run and improve this feature.

Signing in to KeepaVault, OA Hero and QogitaScout

KeepaVault and OA Hero, Chrome extensions from the same company as Seller Oracle, and QogitaScout, a website from the same company, use Seller Oracle accounts to sign people in. When you sign in to any of them and click Allow, it receives your name, your email address, your workspace name, your Seller Oracle user ID and the status of your Seller Oracle trial, and checks them again about once a day while you stay signed in. None of them receives your orders, emails or anything else in your account, and none can change anything. You can disconnect any of them at any time in Settings under Chrome extension.

Referral codes

If you sign up with someone's referral link or code, we store that code on your account so we can pay them their commission. They see that someone signed up with their code, the date and its subscription status (on trial, free plan, paying, past due or cancelled). For each payment you make, they also see the date and the commission they earned on it, and whether the payment was refunded or disputed. They never see your name, email, business or orders. Referral links don't use cookies. The code travels in the link to the signup form.

If you refer sellers and want to be paid by PayPal, we keep the PayPal email you give us, encrypted, and use it only to send your payouts. We delete it when your account is deleted, after the 14-day grace period. Payout records (amounts, dates and payment references) are kept as financial records.

If you tell us about a friend you referred to Qogita, we keep their name, and their business name if you give it, and we use their name only to match them in Qogita's monthly report and to tell you the result.

International data transfers

Our company is based in the United Arab Emirates, and some of our sub-processors operate in the United States and other countries outside the United Kingdom. This means your personal data may be transferred to, stored, and processed in countries that may not have the same level of data protection as the UK.

Where we transfer personal data outside the UK, we rely on appropriate safeguards recognised under UK GDPR, including standard contractual clauses and the data protection frameworks of our sub-processors. Stripe, for example, incorporates a Data Processing Agreement and Data Transfers Addendum into its standard terms. If you would like more detail about the safeguards in place for a specific transfer, contact support@selleroracle.com.

How we protect your data

Authentication tokens and other sensitive credentials are encrypted at rest. Access to production data is restricted and your data is isolated from other accounts. We never display tokens or passwords, and we never include email content, personal data, or credentials in our logs.

Support access to your account

By default, Seller Oracle support can open your account to diagnose issues you report or that our own checks find. We record each time support opens your account.

You can ask us to restrict support access. While it's restricted, support can't open your account or see your orders in our admin tools without approval. To get in, support emails a request to one person on your team, and nothing opens unless that person approves. An approval lasts 24 hours. That person, the account owner or an admin can end it sooner in Settings, under Security.

Only support can change this setting. We restrict it when you ask us to, and support can open it again without asking you first. We email the account owner every time support access is restricted or opened.

A restriction doesn't hide the account details support needs to run the service, such as your plan, your connected mailboxes, how many orders and expenses you have, the type and status of recent emails, and the history of corrections made to your orders, expenses and email types. Our admin tools don't show the subject or content of your emails, with one exception: when our own checks find that two AI readings of an email would record different details, such as an item's price or a tracking number, support can see those details while it can open your account.

Data retention

We keep different types of data for different periods:

  • Account and extracted data (orders, expenses, email logs, retailers, credentials, users) — retained while your account is active. If you delete your account, all data except our news email list (see Email list below) is permanently erased after a 14-day grace period during which you can change your mind.
  • AI evaluation records (the information sent to our AI and the results returned, used to evaluate and improve how Seller Oracle uses AI) — encrypted, retained while your account is active, and permanently erased when you delete your account.
  • Card exports: the file is read when you upload it and not kept. The euro and dollar purchases taken from it are kept while your account is active, so a file uploaded twice isn't applied twice and a purchase not matched yet can be tried again later. Deleting an upload removes its purchases straight away. The settled amounts it set stay in the history of the orders and expenses they were on. Purchases you haven't deleted are erased with your account at purge.
  • OAuth tokens — disabled immediately when you disconnect your email or delete your account. Permanently deleted with your account at purge.
  • Amazon's answers about what you can sell: kept at most 90 days after Amazon last gave them. They are deleted within 30 days after you disconnect Amazon or Amazon tells us you removed Seller Oracle's access, and erased with your account at purge.
  • Wrong item checks: the answer is kept with the item and cleared 18 months after it was given. It is also cleared within 30 days after you disconnect Amazon or Amazon tells us you removed Seller Oracle's access, and erased with your account at purge.
  • Amazon's words on your listings: when Seller Oracle lists an item for you, it keeps what Amazon said about that listing (its reference, its reason if it refused, its link to ask for approval, and the price it showed when a listing was priced automatically) with the listing's record. Its reason, its link and that price are deleted 90 days after the listing finished, and the copy of its reason shown on the item once the item has gone 90 days without a change. Its reference stays with the listing's record. All of them are deleted within 30 days after you disconnect Amazon or Amazon tells us you removed Seller Oracle's access, and erased with your account at purge.
  • Foresight: each product's line and its daily numbers are kept while you have stock of it at Amazon or on the way there, and deleted 90 days after you no longer do; each day's numbers go 18 months after that day at the latest. While your plan doesn't include Foresight, nothing is read and they are kept unused, and deleted 18 months after they were last read unless Foresight is back on your plan first. They are deleted 7 to 22 days after you disconnect Amazon or Amazon tells us you removed Seller Oracle's access, unless you reconnect first. They are deleted at once if support unlinks your Amazon seller account, and erased with your account at purge. The market data holds nothing from your account, and is deleted 60 days after no seller using Foresight has the product.
  • Feedback and support messages — erased from our application database with your account at purge. Because we notify our team when you submit, a copy is also delivered at that time to our support inbox and to a third-party communications provider, as are notices of account activity; those notification copies are retained by those channels and are not retroactively deleted.
  • Billing records — retained for up to 7 years after your last transaction, as required by applicable tax and accounting law.
  • Referral records: commissions, payout requests and their payment references are financial records. Like billing records, they are kept for up to 7 years after the last payout, including after your account is deleted. Your PayPal email and any notes we added are erased with your account at purge.
  • Qogita referrals: the names you give us are kept while your account is active and erased with your account at purge. A £50 reward we added stays in your referral records, without the name.
  • Forwarded emails: we delete our copy of each email you forward to your Seller Oracle address 90 days after we last process it, and never keep one more than 365 days after it arrived. If an email is waiting to be read, for example because your plan's monthly order limit is holding it, we keep its copy until it is read, up to 365 days after it arrived. Copies linked to your account's emails are erased with your account at purge. Any other copy, such as a second copy of an email you forwarded twice, is deleted after 90 days.
  • Usage and diagnostic logs — scrubbed of personal data and retained for up to 90 days for debugging and service reliability.
  • Sign-in records: We keep a record of sign-ins and failed sign-ins to your account, with the IP address and browser used, for 12 months, to protect your account.
  • Giveaway entries: your entry, its points and the challenges you completed are kept until 12 months after the giveaway ends, then deleted. They are erased with your account at purge. If a draw picks your entry, we keep our record of that draw until the same time, then delete it. At purge it loses its link to your account, but keeps the reason we recorded if we disqualified the entry.
  • Website analytics — we keep no record of your visits ourselves. The analytics provider keeps full visit records for 7 days, then keeps a sample of about one in ten, and shows us up to six months of history.
  • AI assistant connections: the record of each time an assistant reads your data is kept for 90 days. A connection is deleted 90 days after it ends, whether you disconnect it or it ends for another reason, such as a password change. Its sign-in tokens are deleted 37 days after they are issued. All of it is erased with your account at purge.
  • App connections: the record of each time an app reads your costs is kept for 90 days. A connection is deleted 90 days after it ends, and its old sign-in tokens 37 days after they're replaced or the connection ends. All of it is erased with your account at purge.
  • Browser extension: each Amazon product your workspace opened is deleted 30 days after anyone in the workspace last opened it. An ASIN suggestion made from it goes when that product does, and at the latest 30 days after it was made. Once you save an ASIN for the item, we keep only whether each suggestion was the one used, without its ASIN or title, for 90 days. A connection is deleted 90 days after it ends. All of it is erased with your account at purge.
  • KeepaVault, OA Hero and QogitaScout sign-ins: a connection is deleted 90 days after it ends, as for the browser extension. All of it is erased with your account at purge.
  • AmazSeller records: until 29 October 2027, imported or not. All of it is erased with your account at purge.
  • Alerts: a Discord or Slack channel the account owner adds is kept, with its link encrypted, until they remove it. A Telegram chat they connect is kept, with its Telegram id and name (for a private chat, the person's Telegram name), until they remove it; our record of who linked it (their Telegram name and username) is kept only until it is confirmed, and one that is never confirmed is removed within 4 hours after its start link is made. An email the account owner sets up is kept until they remove it. It keeps which team members get it, and the day each last got one, until the owner unticks them, they use the email's link to stop it, or they leave your team. Each alert waiting to be sent holds only which order, which Keepa price alert, or which account alert (for a mailbox, which one), and which alert. It is deleted 3 days after it is sent or given up on, and one that can't be sent within 24 hours, or 8 days for a daily summary, is given up on. The record of each delivery code sent to a channel or chat is kept for 90 days. A note that an account alert has already been sent, so it goes once, is kept for 13 months. All of it is erased with your account at purge.
  • Unsubscribe links: the unsubscribe link from a sender's junk emails is kept, encrypted, until you unsubscribe from that sender or 90 days pass without a junk email from them. All of it is erased with your account at purge.
  • Unsubscribe results: what happened to each unsubscribe request you asked for (which of your mailboxes it was for, when it was sent, and whether the sender took it) is kept for 365 days, so you can see it in the Unsubscribed list. The unsubscribe link isn't kept with them. All of it is erased with your account at purge.
  • Email list: our news email list holds your email address and first name, whether you're on the list, when and how you joined or left it, and which news emails we sent you. It's kept until you unsubscribe, including after your account is deleted. After you unsubscribe, we keep your address, your first name and the record of when and how you joined and left, so we never email you again. We also keep the record of which news emails we sent you. If you ask us to erase it, we erase it completely.

Your rights

Under UK GDPR you have the following rights over your personal data. You can exercise any of them by emailing support@selleroracle.com:

  • Access. Request a copy of the personal data we hold about you.
  • Rectification. Ask us to correct inaccurate data.
  • Erasure. Ask us to delete your data. You can also delete your account directly from your settings.
  • Restriction. Ask us to restrict processing in certain circumstances.
  • Data portability. Request your data in a structured, machine-readable format where processing is based on consent or contract.
  • Object. Object to processing based on legitimate interests.
  • Withdraw consent. Where processing is based on consent, withdraw it at any time without affecting the lawfulness of processing before withdrawal.

We aim to respond to all requests within one month.

For Google accounts, you can also revoke Seller Oracle's access directly from your Google account permissions. For Microsoft accounts, you can revoke access from your Microsoft account app permissions (personal accounts) or, for work or school accounts, from Microsoft "My Apps".

Complaints

If you are unhappy with how we handle your personal data, you have the right to lodge a complaint with the Information Commission (ICO), the UK's data protection regulator. You can contact the ICO at ico.org.uk/make-a-complaint or by calling 0303 123 1113. We would appreciate the chance to address your concerns first, so please contact us at support@selleroracle.com before escalating.

Cookies

Seller Oracle uses a small number of cookies that are strictly necessary to run the service:

  • Session cookie. Keeps you signed in while you use the app. This is deleted when you close your browser or when your session expires.
  • CSRF token. Protects your account against cross-site request forgery attacks. This is a security measure required by the application framework.
  • Analytics choice. Set only if you turn website analytics off below, to remember that choice on this browser for 400 days.

We do not use any advertising or tracking cookies, and our website analytics is cookie-free. Because our cookies are strictly necessary for the service to function, no consent is required under UK PECR (Privacy and Electronic Communications Regulations). If this changes in future, we will update this policy and implement a consent mechanism before setting any non-essential cookies.

UK PECR also lets websites use analytics like ours without asking first, as long as they explain it and let you object. You can do that in Website analytics below.

Website analytics

We count visits to our public website, the signed-out account pages (signing up, signing in, password resets, email confirmation and account unlocks) and the plan page, so we can see how people find us and improve the website. A cookie-free analytics provider does the counting. It receives your IP address, details about your browser, the page you are on, the page you came from and how long the page took to load. It leaves out anything after a "?" in those addresses. It doesn't identify you or follow you to other sites, and it never runs on the pages that show your orders and email data.

You can turn it off for this browser at any time, free of charge. We remember your choice in the analytics choice cookie above for 400 days, or until you clear your cookies. It covers only this browser, so turn it off in each browser you use.

Website analytics is on for this browser.

Children

Seller Oracle is a business tool for Amazon sellers. It is not directed at anyone under the age of 18, and we do not knowingly collect personal data from children. If you believe a child has provided us with personal data, please contact us and we will delete it.

Changes to this policy

We may update this policy as the product evolves. When we make material changes, we will update the date at the top of this page and, where appropriate, notify you by email.

Contact

For any privacy questions or requests, email support@selleroracle.com or write to: WhiteKnight Software Design - FZCO, IFZA, Dubai Silicon Oasis, Dubai, United Arab Emirates.