Legal
Privacy Policy
This policy explains what personal data DoctorX handles, why, who we share it with, and what you can ask us to do about it. It covers two very different situations: data about you as our customer, and data about your buyers that your sales channels (the marketplaces you connect) send us on your behalf. The difference matters, so it is the first thing we set out.
Last updated November 19, 2026
Who is responsible for your data
The service is operated, and personal data about our customers is controlled, by:
Nguyen Quoc Duy
Tay Xuan, Tay Son, Gia Lai, Vietnam
Contact: admin@doctorx.vn opens in a new tab
Write to that address for anything in this policy, including a request to see, correct, export or delete your data. It reaches a person, not a ticket queue.
What this policy covers
It applies to:
- the DoctorX web application and its public website;
- the DoctorX app for Shopify, a separate application with its own section below;
- the DoctorX public API and its webhook deliveries;
- the DrX CrawlBot browser extension;
- the emails and browser notifications we send you.
It does not cover what a marketplace, Shopify, a payment provider or a print supplier does with data inside their own systems. Those companies publish their own policies, and their handling of your buyers and your payouts is between you and them.
Two roles, and why the difference matters
For data about you and your team - your name, your email, your workspace, what you paid - we are the controller. We decide what to collect and why, and this policy is our account of it.
For data about your buyers - the name, address, phone number, email and order contents your sales channels send us when you connect a shop or a store - you are the controller and we act as your processor. We hold that data because you instructed us to import your orders, we use it only to run the features you use, and we do not use it for any purpose of our own.
Data we collect about you
| Data | Where it comes from | Why we hold it |
|---|---|---|
| Name, email address, profile picture | You, through our identity provider, or an invitation you accepted | To create your login, identify you in your workspace, and contact you |
| Workspace and team membership: your role, which shops you may access, when you were last active | You or your workspace administrator | To enforce permissions and shop-level access |
| Shop connections: the seller account name, region and the access token the marketplace issued | The marketplace, when you complete its authorization flow | To act on your shops as you instruct |
| Your catalog and operations data: products, templates, prices, costs, images and print files | You, your imports, or a listing you pulled from a connected shop or store | To provide the service |
| Billing records: plan, term dates, amount, payment reference, transaction id | You and our payment partners | To sell you a subscription and keep accounting records |
| Support correspondence | You, when you write to us | To answer you |
| Technical logs: API request paths, status codes, timing and the calling IP address | Automatically, when you or your integration calls the API | Security, abuse prevention, rate limiting and debugging |
| Crash reports: an error message and stack trace, the page it happened on, and a short trail of the actions before it | Automatically, from your browser when the app fails | To find and fix defects |
| Browser push subscription: the endpoint URL and keys your browser issues | Your browser, only if you turn notifications on | To deliver the alerts you asked for |
| Preferences: your language, your sidebar state, and which table columns you hide | Your browser | To keep the interface as you left it |
We do not ask for and do not want special-category data (health, biometrics, political or religious views, and so on). Please do not put it into product descriptions, file names or support messages.
We never receive your card number or your bank credentials. Payments happen at the payment provider, and what comes back to us is a reference and an outcome.
Data your sales channels send us
When you connect a shop or a store, DoctorX imports what that channel exposes about your business. Some of it is personal data about your buyers, and we hold it as your processor.
| Data | Why it is imported |
|---|---|
| Buyer name, email address and phone number, where the channel provides them | To show you who an order is for and, where you use print-on-demand, to send it to a supplier for fulfilment |
| Shipping address | To fulfil the order, produce a label where the channel provides one, and, where you use print-on-demand, export it for a print shop |
| Order contents, quantities, amounts, taxes and status | Order management, fulfilment and profit reporting |
| Buyer messages and the conversation around them, on marketplaces that offer buyer chat | So you can read and answer buyer chat inside DoctorX |
| Returns and refunds | To show you the state of an order and to reconcile it |
| Settlement statements, fees and payouts, where the marketplace reports them | To reconcile marketplace fees and report real profit |
A buyer’s data reaches a print supplier only when you send that order for fulfilment, and only the fields the supplier needs to make and ship it.
The DoctorX app for Shopify is separate, and the next section sets out what it reads and writes.
The DoctorX app for Shopify
The DoctorX app for Shopify is a separate application that runs inside your Shopify admin. It has no DoctorX account and no workspace, and it shares no data with the DoctorX web application. It runs on its own server and database.
| Data | Why it is read |
|---|---|
| Orders: items, quantities, prices, discounts, taxes, shipping, status, fulfilments and returns, including orders older than 60 days | To show and fulfil orders of any age |
| On an order: the buyer’s email and phone, the shipping address with the recipient’s name, and the order note | To show who an order is for and where it goes |
| Products, variants, images, prices, inventory and store locations | To list products and publish to the right location |
| Your store’s sales reports | To show sales and gross profit, using Shopify’s own figures |
| Only once you allow it: your Shopify Payments balance, payouts and balance transactions | To show your payouts and the orders behind them |
| Only once you allow it: your discounts, delivery profiles, markets with their price lists, and store languages | To list and edit discounts, and to let a template choose a delivery profile, market prices and translations |
The app does not ask for access to your store’s customer records. A buyer’s details reach it only as part of an order.
What it stores: your store’s address and encrypted access tokens; the templates you create, with their last 20 saved versions and the delivery profile, market prices and translations you give them; which product came from which template; the status of a publish; the results of a bulk action you run; your notification email and settings; the customer data requests Shopify forwards; and a log of which staff member opened which order. It stores no order, product or buyer details. An order export is built from Shopify’s data when you ask for it and is not kept.
How long: the access log is kept for 12 months. A data request’s customer and order ids are removed 90 days after its response date. A bulk action’s results are kept for 30 days, and a finished publish’s status for 90 days. The id of a Shopify Flow run is kept for 48 hours, so a run Flow sends twice acts once. A staff member’s session is removed once it expires. Encrypted backups are kept for 30 days.
What it writes, only when you act: products you publish or update, with their variants, images, prices and stock, and, when the template states them, their delivery profile, market prices and translations; costs you enter, to Shopify’s Cost per item; fulfilments and tracking you enter, after which Shopify notifies the buyer; and, once you allow each, an order’s tags, note and details, an order marked as paid (a payment received outside Shopify), order items you edit, decisions on return requests, and discounts you create or change. A product a Shopify Flow workflow of yours asks for is published the same way. It never cancels or refunds an order: a balance from an edit is collected by Shopify’s own invoice when you choose to send it, and a refund is made in Shopify. Updating a product from a template keeps what you changed in Shopify, apart from what the review screen lists.
Security: data is encrypted in transit all the way to the app’s server (TLS). The app’s database and backups are on an encrypted volume (LUKS2, AES-256), access tokens are also encrypted individually (AES-256-GCM), backups are encrypted (AES-256), and row level security in the database keeps each store’s rows apart.
Shopify’s privacy requests are acted on as they arrive:
- When a buyer asks your store for their data, Shopify notifies us. The request appears in the app under Settings, and we email your notification address, for you to respond within 30 days.
- When a buyer asks your store to erase their data, Shopify notifies us and we remove every reference the app holds to that buyer and their orders.
- When you uninstall the app, its access ends at once. Shopify asks us 48 hours later to erase the store’s data, and we delete everything held for that store, unless you have installed the app again by then.
- Every request from Shopify is checked against the app’s signature before anything acts on it.
Sub-processors for this app: Cloudflare (network), Backblaze (encrypted backups) and Resend (the notification email, which contains no buyer details).
The DrX CrawlBot browser extension
DrX CrawlBot is the Chrome extension a DoctorX seller uses to turn a product page they are authorized to sell into a draft listing in their own DoctorX workspace. It reads a page when you click Load in the extension, and it sends what it read only when you click Send to DoctorX, Translate or Remove background.
Before it does anything, the extension shows you what it reads and sends and asks you to agree. Until you have agreed, no part of the extension runs on any website.
| Data | When | Where it goes |
|---|---|---|
| Your CrawlBot token, the key you paste from DoctorX | When you connect | Stored only in this browser (Chrome extension storage, not synced) and sent only to DoctorX, with each request the extension makes. |
| The product page you are on: title, photos, description, variants, prices, stock, and the weight and size it states | Only when you click Load | Stays in the extension until you send it. Sent to your DoctorX workspace when you click Send to DoctorX, with the template you chose for it, where it becomes a draft listing. |
| The names of your DoctorX templates | When the screen for sending a product opens | Read from your DoctorX workspace so you can choose one, and shown only in the extension. |
| On TikTok, Taobao, Tmall and AliExpress: the product data those pages load while they open | While such a page is open, once you have agreed | Kept only in the memory of that browser tab and gone when the tab closes. It leaves the tab only as part of a product you load and send. |
| Text you choose to translate: the product title and its variant options | Only when you click Translate | Sent to DoctorX, which has it translated by an AI service provider (Replicate) and returns the result to you. |
| The address of a photo whose background you choose to remove | Only when you click Remove background | Sent to DoctorX, which has the background removed by an AI service provider (Dr.X AI Design) and stores the result in your workspace. |
| Background images you choose from your computer | Only when you upload them in the extension | Uploaded to your DoctorX workspace. |
| Your in-progress edit, the "Selected variant only" setting, the template you last chose for each channel, and your agreement with its date | While you use the extension | Kept only in this browser. The in-progress edit is cleared when you send it, cancel it, or close the browser. |
To recognise and read the product, the extension uses the address of the page you are on and, on Amazon, the page’s currency setting. On some marketplaces it re-reads the same product page, opens the page of each of the product’s variants (on Amazon, for the weight each one states), or asks the same marketplace for the prices of the product’s variants, the way the page itself does; those requests go from your browser to that marketplace. None of this is sent to DoctorX: DoctorX never receives the address of the page you import, which the extension keeps only in your in-progress edit in this browser.
What the extension does not do:
- it does not read pages you do not load (apart from the product data it keeps inside TikTok, Taobao, Tmall and AliExpress tabs, described above), and it keeps no record of the sites you visit;
- it does not collect your name, email address, contacts, location or payment details;
- it does not show ads, track you or use analytics;
- it does not sell your data, or use it for anything other than creating your draft listings.
Chrome lists the extension’s access when you install it. It can read and change data on TikTok, Taobao, Tmall and AliExpress, because on those sites it has to be present while a product page loads; on api.doctorx.vn, which is DoctorX itself; and on the AliExpress and eBay hosts that serve product descriptions, which it fetches for a product you load. On any other site it can read only the tab you are on, and only after you click Load.
You stay in control. Disconnect in the extension deletes the token, your agreement, your settings and any in-progress edit from the browser, and stops the extension from running on any site; removing the extension from Chrome does the same. You can revoke the token itself at any time in DoctorX under Settings, CrawlBot. Drafts you have already sent are part of your DoctorX workspace, are covered by the rest of this policy, and can be deleted there.
If we change what the extension reads, sends or keeps, it will show you the new notice and ask you to agree again before it continues, and this section will be updated at the same time.
Why we use it, and on what basis
We use personal data to:
- provide the service you signed up for, and act on your shops as you instruct;
- authenticate you, enforce roles and keep one workspace’s data away from another’s;
- take payment, apply plan limits and keep accounting records;
- send you the operational alerts and account emails you have enabled;
- send you one welcome email when you first join DoctorX, and one email when you have not opened DoctorX for 7 days, saying what is waiting in the shops you look after; each kind can be turned off from the link in the email or on your Profile page;
- answer your support requests;
- keep the service secure: detect abuse, rate-limit callers, investigate incidents;
- find and fix defects, and understand which features fail;
- meet legal obligations, including tax record keeping.
Where data-protection law asks for a legal basis, ours are: performing our contract with you (running the service, taking payment); our legitimate interests (security, abuse prevention, debugging, and improving the product) balanced against your interests; your consent, where we ask for it, such as browser notifications, which you can withdraw at any time; and legal obligation, for records we must keep.
We do not sell personal data. We do not share it with advertising networks or data brokers, and we do not use it to build profiles for advertising.
Service providers we share it with
DoctorX runs on a small set of providers, each doing one job. They may only process data on our instruction and for that job.
| Provider | What it does for us | Personal data involved |
|---|---|---|
| Clerk | Login, sessions and team invitations | Your name, email and authentication data |
| Sales channels: TikTok Shop, eBay, Etsy, Amazon | The shops and stores you connected; DoctorX reads from and writes to them on your instruction | Your seller account or store, your listings, your orders and your buyers’ data |
| Dr.X Bridge | Brokers the marketplace authorization handshake for TikTok Shop and eBay | The authorization grant for the shop you are connecting |
| DodgePrint integrator | The gateway DoctorX uses to reach Etsy and Amazon | Listings, orders and buyer address data for those channels |
| Backblaze B2 | Stores your images, print files and documents | File contents and file names you upload |
| Cloudflare | Serves the site and the media CDN, and filters abusive traffic | Request metadata, including IP address |
| Resend | Sends notification and account emails, the welcome email and the away-for-a-week email | Your email address and the message content |
| Web push (your browser vendor’s push service) | Delivers browser notifications | Your push endpoint, and the notification text |
| Replicate, Dr.X AI Design | Runs the AI features: text generation, image editing, background removal, and reading a question typed to Dr.X Assistant | The text or image you submitted to that feature; for Dr.X Assistant, the question, the earlier questions of that conversation and the names of the shops you can see, never a figure, an order or a buyer's details |
| Dr.X Pay (PingPong, PayPal), SePay; Shopify, for a plan bought in the Shopify App Store | Takes subscription payments | Your payment identifiers and the amount; they hold the card or bank details, we do not |
| Print-on-demand suppliers: DodgePrint, Lenful, FlashShip, Jade | Produces and ships the orders you send for fulfilment | Buyer name, shipping address, phone or email, and the order contents |
| Dr.X Tracking | Tracks shipments and reports status back | Tracking numbers and carrier status |
| Hosting and infrastructure provider | Runs our servers and databases | All data at rest, as the operator of the machines |
We also disclose data where the law requires it, to respond to a valid legal request, or to protect our rights, our customers or the public. If the business is ever reorganised or sold, data may transfer with it, and this policy travels with the data.
Where data is stored, and international transfer
Our application servers and databases are hosted in Vietnam. Uploaded files are stored with a cloud object-storage provider in the United States and served worldwide through a content delivery network. Our email, AI, payment, tracking and sales-channel providers operate in several countries.
That means personal data can be transferred to, and processed in, countries other than your own, including outside the European Economic Area and the United Kingdom. Where such a transfer needs a safeguard, we rely on the transfer terms in our agreements with those providers.
How we protect it, stated plainly
What is in place today:
- The application and the API are served over HTTPS.
- The disks holding your data are encrypted. The database, the cache and the key store sit inside an encrypted volume (AES-256-XTS), and the key that opens it is not kept on the machine: a person types a passphrase after every restart. That is slower to operate than an automatic key, and it is the reason the protection is real rather than nominal, because a key kept on the same disk as the data it protects would not survive that disk being taken.
- Files you upload are encrypted where they are stored (AES-256), and the storage itself is private. A file can only be fetched through a link our server signs, and that link expires. A link that leaks stops working, and a link with one character altered is refused.
- Every workspace’s data is separated by a workspace identifier that every query is scoped by, so one customer’s catalog, orders and files are not returned to another.
- Access inside a workspace is deny-by-default: an endpoint a member has no explicit permission for is refused, and members with a limited role are further restricted to the shops granted to them — enforced below the application’s own queries rather than in each one.
- Credentials we hold for third-party services and marketplace integrations are stored encrypted with AES-256-GCM. The key that protects them is held in a dedicated key-management service rather than in application configuration, every use of it is logged, and it can be rotated without re-encrypting your data. Every stored credential has been migrated onto that key - there are no records left on the older mechanism.
- Reading a buyer’s name, contact details or address is a separate permission from being able to see the order. A member without it is shown those fields partially masked, and the masking is applied by the server before the data is sent, so it cannot be undone by the browser or by calling the API directly. Searching by a buyer’s name or phone number is likewise unavailable to them, because a search result is itself a disclosure.
- Every read or export that returns buyer personal data is recorded: who did it, when, from which address, and which FIELDS were returned. The record never contains the values themselves. It is kept for at least twelve months and reviewed on a fixed fortnightly cycle, and each review is itself recorded.
- Backups are taken daily, encrypted with AES-256 before they leave the server, and stored with a provider in the European Union - a different company and a different continent from the systems that run the service, so one failure cannot take both. Restoring from them is rehearsed, not assumed: the most recent rehearsal restored the whole database and the encrypted off-site copy, and both matched the original row for row.
- Inbound webhooks are signature-verified, and the API is rate-limited per caller.
- An upload is classified by its actual file contents rather than the type your browser declared, and a file that is not what it claims to be is rejected and deleted.
This changed on 22 August 2026, and if you read this policy before then you were told the opposite, so it is worth being explicit. File addresses used to be unguessable but not secret: anyone holding the exact URL could open a file without signing in. They are now private. Every address our service hands out carries a signature and an expiry, and the storage refuses anything else. Two consequences are worth planning around. A file link you saved, mailed to yourself or pasted into a document will stop working, so re-open the file from DoctorX rather than keeping the link. And a link we put into a file you export for a print supplier is deliberately long-lived, because a print shop downloads artwork when the job reaches the press rather than when you send it, so treat an exported file as something to share only with that supplier.
No system is perfectly secure. If a breach affects your personal data and the law requires notification, we will notify you and the relevant authority within the time the law allows, and tell you what happened and what to do.
How long we keep it
- A BUYER’S PERSONAL DATA - their name, email address, phone number, shipping address, the personalisation text printed on a product, and their messages - is kept for at most 30 days after the order ships, and is then removed automatically. Where we have no record of a ship date, or the order never shipped because it was cancelled or refunded, the clock runs from the order date instead, which removes the data sooner rather than later.
- The order itself is NOT deleted. What is left behind is the commercial record: what was bought, for how much, on which channel, on which date, and what it cost us. That is what invoices, tax returns and profit reports are built from, and it identifies nobody.
- Workspace data you own - your catalog, templates, files, settings and reports - is kept while your account is open, because it is the record you run your business from.
- If a workspace stays locked for 7 days after its plan lapsed and its grace period ended, its business data is permanently deleted, the buyer personal data inside it included: products and listings, orders and returns, chat, promotions, finance records and the files stored for them. The account, its members, the subscription record, settings, integrations and connected shops are kept. The terms set out what is deleted and when.
- Account and billing records are kept while you are a customer and afterwards for as long as tax and accounting law requires.
- The log of who read buyer personal data is kept for at least twelve months, because an audit trail shorter than the period it covers is not an audit trail. It records field NAMES, never values.
- Technical logs are kept on their own shorter clocks: API request logs for 90 days, webhook delivery logs for 30 days.
- A browser push subscription is deleted when you turn notifications off or the endpoint stops working.
- Uploaded files are removed when you delete them, when your workspace is deleted, or when a locked workspace’s business data is deleted as described above.
When you ask us to delete your workspace, or a locked workspace’s business data is deleted, we remove it from our production systems. Copies inside routine encrypted backups age out on the backup schedule rather than being erased individually - backups are retained for 7 days on the server and 30 days off-site, and a deleted file stays recoverable in storage for 7 days before it is gone - and a small number of records are kept where the law requires it, for example an invoice.
Asking us to delete a buyer’s data
A buyer whose order passed through DoctorX can ask to have their personal data removed, and so can the seller on their behalf. One mechanism handles every channel the DoctorX web application supports - TikTok Shop, eBay, Etsy and Amazon - so the outcome does not depend on which channel the order came from.
What happens when a request is made:
- The request is recorded before any data is touched, so there is a durable record that it was received.
- We locate every place that buyer appears: the order, its line items and any personalisation printed on them, the shipping address, any note written about the order, the return reason, the fulfilment records sent to a print supplier, and the chat thread including messages our own staff wrote.
- Their personal data is removed from all of those. Free-text notes and messages are not simply erased: the personal details inside them are replaced and the operational content is kept, so the seller does not lose the instruction that told them how to make the product.
- The commercial record of the order survives, for the reason given in the previous section.
- A request is normally completed within minutes and always within 30 days. If it cannot be completed it is retried, and a request that keeps failing is escalated to a person rather than retried silently for ever.
eBay sends us these requests automatically when someone closes their eBay account, and we act on them without anyone at DoctorX being involved. Etsy and Amazon reach us through the integration partner that connects those channels and do not send such a notification, so for those a request is raised by the seller or by us. To make a request yourself, contact us using the details at the end of this policy.
Your choices and your rights
Depending on where you live, you can ask us to:
- tell you what personal data we hold about you, and give you a copy;
- correct data that is wrong or incomplete;
- delete your data, and close your workspace;
- export your data in a portable form;
- restrict or object to a use we base on legitimate interests;
- withdraw a consent you gave, such as browser notifications.
Much of this you can do yourself and immediately: edit your profile, change your notification settings, export any list to a file, delete a shop connection, revoke our access at the marketplace, or uninstall the app from your Shopify store. For anything else, write to us. We will confirm your identity first, and we answer within one month.
If a request concerns one of your buyers rather than you, we will refer it to you, because you are the controller of that data. We will then act on your instruction.
If you are not satisfied with how we handled a request, you may complain to your local data-protection authority. We would rather you told us first so we can put it right.
Your obligations for buyer data
Because you are the controller of your buyers’ data, some duties are yours and cannot be delegated to us.
- Use buyer data only for fulfilling and supporting the order it came from, and only as the policies of the channel it came from allow.
- Do not export buyer lists in order to market to them outside the channel they bought through, unless you have a lawful basis to do so.
- Keep the exports you download secure: an order export is a spreadsheet of names, addresses and phone numbers.
- Give your own team the narrowest role that lets them do their job, and remove members who leave.
- Answer buyer privacy requests, and ask us for help when carrying one out needs a change inside DoctorX.
Children
DoctorX is a business tool and is not intended for children. We do not knowingly collect data from anyone under 16. If you believe a child has given us personal data, write to us and we will delete it.
AI features and automated decisions
Some features send content you chose to an AI provider to generate a title or description, edit an image, or remove a background. Only what that feature needs is sent, the result comes back to you as a draft, and you decide whether to use it.
Dr.X Assistant answers questions about your own workspace. A question picked from its list is answered by DoctorX alone and sends nothing to an AI provider. A question you type is sent, with up to three earlier questions of the same conversation (each cut to 200 characters) and the names of the shops you can see, to the AI provider on your workspace's own key, only to decide which of the assistant's read-only answers fits it. Your figures, orders and buyer details are never sent: the answer is read and written by DoctorX. The conversation stays in your browser tab; DoctorX keeps a technical record of each question for 90 days (which answer was given and how long it took), and keeps the text of a typed question only when the assistant could not answer it, with anything that looks like personal data removed.
DoctorX makes no automated decision that has a legal effect on a person. Automated processes in the product act on listings, orders and money figures, and a person is always the one who decides.
Changes to this policy
We update this policy when what we do changes, including when we add a service provider. The date at the top always shows when the current version took effect, and we will give notice in the product or by email before a material change takes effect.
Contact
For any privacy question or request:
Nguyen Quoc Duy
Tay Xuan, Tay Son, Gia Lai, Vietnam
Contact: admin@doctorx.vn opens in a new tab
The agreement governing your use of the service is set out in our Terms of Service.
