Privacy Policy

This is the complete list. It is read from the site’s own database when this page is rendered, so it cannot drift away from what the software actually does.

• Account record (table `users`)stored on our server
• Signed-in sessions (table `sessions`)stored on our server
• Email verification and password reset tokens (table `auth_tokens`)stored on our server
• Linked social sign-ins (table `social_accounts`)stored on our server
• Sign-in attempts (rate limiting) (table `login_attempts`)stored on our server
• Pending email change requests (table `pending_email_changes`)stored on our server
• Subscription records (table `subscriptions`)stored on our server
• Purchased and granted access (table `access_grants`)stored on our server
• Your language and currency preference — `mc_locale`up to 365 days
• An anonymous identifier for a visitor with no account — `mc_user`session
• A one-time value that protects social sign-in from forgery — `mc_oauth_state`minutes
• A one-time flag so a first-time sign-in notice is shown once — `mc_welcome`short
• Medical records, scans or uploaded documentsnot collected — this product does not accept them
• Third-party analytics or advertising trackersnone in the product today — we run no third-party analytics and no advertising pixels

Nothing above is a medical record, an uploaded document, a diagnosis, a symptom, a treatment you are considering, or a note written by you about your health. This product does not have anywhere to put them.

1. Email address — to sign you in, to send a password reset or an email-verification link, and to reach you if a purchase needs attention. It is not used for advertising and is not sold.
2. Password hash — stored only as a salted scrypt hash. The password itself is never written anywhere.
3. Display name — optional. Used to show who you are signed in as.
4. Session records — a token hash and the browser’s user-agent string, so you can be signed out and so a stolen session can be traced to its origin. No IP address is stored with a session.
5. Sign-in attempts — the email address and a timestamp, used only to slow down automated guessing. These records age out quickly.
6. Social sign-in details — if you sign in with Google, Facebook or Apple, we keep the provider, your identifier at that provider, the name and picture your provider returns, and the last time you signed in. We do not receive your contacts, your email history, or anything else from that account.
7. Payment details — handled entirely by the payment provider. Card numbers never reach this site; what is kept is a reference so a refund or a renewal can be matched to your account.
8. Language preference — a cookie, so the site renders in the language you chose instead of guessing from your browser.

Health information is treated as sensitive under the privacy regimes of most countries, and this site has no reason to hold any. You are not asked for a condition, a diagnosis, a test result, a medical record, a passport number, or any free-text description of a health problem — not at sign-up, not in the search filters, and not in the correction form.

If a field ever needs free text, treat what you type as potentially visible to us and avoid putting health details in it. Please do not include them.

This site sets four cookies, all of them functional. There is no advertising cookie, no cross-site tracking cookie, and no third-party analytics script anywhere in the product.

See the table in section 1 for each cookie’s purpose and lifetime. Two of them exist only to make sign-in safe and are deleted within minutes.

1. The payment provider, to take payment and issue a receipt.
2. The social sign-in provider you chose, at the moment you sign in and each time you sign in again.
3. Our hosting provider, which stores the database and serves the pages. It processes this data on our instructions.
4. Nobody else. Your data is not sold, not rented, not shared with hospitals, and not shared with advertisers, because there are no advertisers.

We will disclose data to a public authority where we are legally required to, and will narrow the request to what is actually asked for.

The site is operated to serve readers outside China, and its servers are outside China. If you are in the European Economic Area, the United Kingdom or Switzerland, data may therefore leave your region under the safeguards those regimes require.

1. Ask what personal data is held about you, and get a copy.
2. Ask for inaccurate data to be corrected.
3. Ask for your account and its data to be deleted.
4. Ask us to stop processing your data.
5. Ask to move your data somewhere else.

Send any of these to privacy@chinamedbase.com. We will not ask you to create an account or prove your identity beyond confirming access to the email address on file.

If you are in the EEA or the UK and are unhappy with the answer, you may complain to your local data protection authority.

This site is written for adults arranging their own or a relative’s medical care. It is not directed at children, and accounts are not created knowingly for anyone under the age at which you may enter a contract where you live.

1. Passwords are stored as salted scrypt hashes, never as readable text.
2. Session and reset tokens are stored only as hashes.
3. Traffic is served over HTTPS.
4. Access to the database is restricted to the people who maintain the site.

No system is perfectly secure. If a breach affects your data we will tell you and the relevant authority as the law requires.

This site is operated by ChinaMedBase, of China (no street address is published — write to the privacy address instead).

These terms are governed by the laws of the People's Republic of China and the courts of the People's Republic of China.

See also the Terms of Use, the refund and access rules, and the medical information disclaimer.