Home

Privacy Policy

Last updated: September 2026

1. Overview

Uptake Pro LLC, operating as UptakePro ("we," "our," "the Service"), is committed to protecting your privacy. This Privacy Policy explains what data we collect, how we use it, who we share it with, and your rights regarding your information.

2. Data We Collect

2a. Account Information

When you create an account, we collect:

  • Email address — for authentication and account recovery
  • Display name — optional, shown in the interface
  • Specialty and institution — optional, for profile personalization
  • Authentication provider — if you sign in with Google, we request access to your Google account's email address and basic profile information (name and profile picture). These are the only data scopes we request. We do not access your Google contacts, calendar, Drive, or any other Google services. We do not receive or store your Google password.

2b. Usage Data

  • Clinical questions — questions you submit are sent to third-party APIs (Anthropic, PubMed, ClinicalTrials.gov, and our embedding and reranking provider) for processing. We also store your questions on our servers: the first 200 characters of every question are retained in our usage log so we can monitor answer quality and improve retrieval. Separately, if a question comes back with weak or no supporting evidence, the first 500 characters are saved to a review queue so we can investigate and close that gap. Questions are retained indefinitely unless you delete your account or ask us to remove them.
  • Cached searches — to stay within the rate limits of the medical databases we query, search terms derived from your question are cached in Upstash Redis. Short search terms are stored as readable text in the cache key; longer ones are stored as a hash. Cache entries expire automatically.
  • Conversation history — if you are signed out, conversations are stored only in your browser (localStorage) and are never saved to our servers. If you are signed in, your conversations and their full message text are saved to your account on our servers so they sync across devices. You can delete any conversation from the history sidebar, which removes it from our database.
  • Saved content — favorites, collections, case logs, and care plans you create are stored on our servers under your account until you delete them.
  • Analytics events — product analytics (e.g., feature usage, error occurrences) are collected via PostHog. The events we send to PostHog record the length of a question, not its text.

2c. Payment Information

If you make a voluntary donation, payment processing is handled entirely by Stripe, Inc.We do not receive, process, or store your credit card number, bank account details, or other payment credentials. We receive only a Stripe customer ID and donation status to manage your account.

2d. Technical Data

  • IP address — used for rate limiting and abuse prevention; not stored long-term
  • Browser type and device — collected by analytics for compatibility and performance monitoring
  • Error reports — application errors are reported to Sentry for debugging. These reports can include the text of the clinical question that was being processed when the error happened (up to 500 characters), along with request metadata. If you use the "Report an issue" button, the report sent to Sentry also includes your question, a preview of the response you received, and any details you typed.

3. How We Use Your Data

  • Provide the Service — authenticate your account, process your questions, return evidence-based responses
  • Improve the Service — analyze anonymized usage patterns to improve features and performance
  • Prevent abuse — enforce rate limits, detect automated or malicious access
  • Communicate — send transactional emails (account verification, password reset) via our authentication provider
  • Process donations — manage voluntary donation subscriptions through Stripe

Organization Accounts

If your employer or institution provides your account through an organization plan, the administrators of that organization can see your activity in the Service: how many questions you have asked, when you were last active, which features you use, and the text of the questions you submit. Administrators cannot see your password, and they cannot see activity from any separate personal account you may hold.

If you do not want your employer to see a question, do not submit it through an account they provided.

Advertising

The Service displays advertisements from healthcare-focused ad networks. To serve relevant professional content, we share a one-way cryptographic hash (SHA-256) of your email address with our advertising partner, Doceree. This hash cannot be reversed to recover your email. Doceree uses it to determine whether you are a verified healthcare professional (HCP) by matching against their existing NPI registry database. This process enables the display of professional-grade healthcare advertisements relevant to clinical practice.

We do not share your raw email address, clinical questions, conversation history, or any other personal data with advertisers. You may opt out of HCP identity matching at any time (see Section 8); you will still see advertisements, but they will be based on page content context only.

4. Third-Party Services

To provide the Service, your data is processed by the following third parties, each governed by their own privacy policies:

Supabase

Authentication, user profiles, and account management. Privacy Policy

Google (OAuth Sign-In)

If you choose to sign in with Google, we use Google OAuth 2.0 to authenticate your identity. We request only your email address and basic profile information (name). We do not access any other Google services or data. You can revoke access at any time via your Google Account permissions. Google Privacy Policy

Anthropic (Claude)

AI model for synthesizing evidence-based responses. Questions are sent to Anthropic's API for processing. Privacy Policy

NCBI / NLM (PubMed, PMC, DailyMed)

Medical literature search and drug labeling data. Search queries are sent to NCBI APIs. NLM Privacy Policy

Stripe

Payment processing for voluntary donations. We never receive your payment credentials. Privacy Policy

Doceree

Healthcare advertising network. Receives a one-way SHA-256 hash of your email address for HCP identity verification. Does not receive your raw email, clinical questions, or any other personal data. HIPAA-certified. Privacy Policy

PostHog

Product analytics for usage patterns and error tracking. When you are signed in, PostHog receives your user ID and email address so activity can be tied to your account. Question events record the length of a question, not its text. Privacy Policy

Sentry

Error monitoring and performance tracking for application stability. Error reports can include the text of the question being processed when the error occurred, and issue reports you submit include your question and the response you received. Privacy Policy

Upstash (Redis)

Caching layer for rate limiting and API response caching. Stores rate limit counters and cached search results. Short search terms derived from your question are stored as readable text in the cache key; longer ones are hashed. Entries expire automatically. Privacy Policy

Modal Labs

Hosts the medical embedding and reranking models used to match your question against the literature. Receives your question text for this purpose. Privacy Policy

ClinicalTrials.gov (NIH)

Clinical trial registry search. Search queries derived from your question are sent to their API. NLM Privacy Policy

Europe PMC (EMBL-EBI)

Supplementary full-text literature search. Search queries derived from your question are sent to their API. Privacy Notice

Vercel

Hosting and deployment infrastructure. Processes all requests to the Service. Privacy Policy

Inngest

Schedules and runs our background maintenance jobs (literature refresh, guideline updates). Does not receive your questions or account data. Privacy Policy

5. Protected Health Information (PHI)

This Service is not HIPAA-compliant and is not designed to store, process, or transmit Protected Health Information.

  • Do not enter patient names, medical record numbers, dates of birth, or any individually identifiable health information
  • We do not knowingly collect or retain PHI
  • If PHI is inadvertently submitted, we cannot guarantee its confidentiality as it may be processed by third-party services listed above
  • We do not automatically scan for or redact PHI. Free-text fields — questions, case logs, and care plans — are stored as you type them, so please de-identify before entering clinical detail.

We do not sign Business Associate Agreements. If your organization requires a BAA for a tool that handles patient information, this Service is not an appropriate place to enter that information.

6. Data Retention

  • Account data — retained while your account is active; removed when you delete your account from Settings
  • Conversation history — if you are signed out, stored only in your browser and cleared when you clear browser data. If you are signed in, stored on our servers until you delete the conversation or your account.
  • Saved content — favorites, collections, case logs, and care plans are retained until you delete them or delete your account
  • Usage log — the question excerpts described in Section 2b are retained indefinitely. Deleting your account removes them.
  • API response cache — cached for up to 24 hours in Redis for performance; automatically expires
  • Rate limit counters — reset on a rolling 24-hour window
  • Analytics data — retained by PostHog per their retention policies
  • Error reports — retained by Sentry for up to 90 days

We do not currently run automatic deletion on a fixed schedule for stored questions, conversations, or saved content. They persist until you remove them or delete your account.

7. Cookies & Local Storage

  • Authentication cookies — set by Supabase to maintain your login session
  • Disclaimer acceptance — stored in localStorage to remember your acknowledgment
  • Conversation history — stored in localStorage/IndexedDB for chat persistence
  • Analytics cookies — set by PostHog for anonymized usage tracking
  • Ad identity opt-out — stored in localStorage if you choose to opt out of HCP ad identity matching
  • Advertising SDK — the Doceree SDK may set cookies or local storage entries for ad delivery and frequency capping. These are governed by Doceree's Privacy Policy

We do not use cross-site behavioral tracking cookies. HCP identity matching is performed using a one-way hash of your email (see Section 3), not through cookie-based tracking. Ad content is delivered within a sandboxed iframe.

8. Your Rights

Depending on your jurisdiction, you may have the right to:

  • Access the personal data we hold about you
  • Correct inaccurate personal data (via your account settings)
  • Delete your account and associated data — you can do this yourself at any time from Settings. This removes your login, profile, conversations and their messages, favorites, collections, case logs, care plans, quiz and Question-of-the-Day history, newsletter subscription, and any feedback reports you filed. Your stored question text is erased from our usage log; the remaining row is stripped of anything identifying you and kept only as an anonymous counter for capacity and cost analysis. Deletion is immediate and cannot be undone.
    Two cases are refused so that deletion does not cause a side effect you did not ask for: if you have a paid subscription, cancel it in Billing first (deleting the account does not stop Stripe billing); and if you are the only owner of an organization, transfer ownership first, or that organization would be left with no one able to administer it.
  • Export your personal data in a portable format — contact us and we will provide it
  • Opt out of analytics tracking
  • Opt out of ad identity matching — you can disable HCP identity verification for advertising by navigating to your account settings and enabling the ad opt-out option. When opted out, advertisements will be based on page content context only; your hashed email will not be shared with advertising partners. You will still see advertisements.
  • Revoke third-party access — if you signed in with Google, you can revoke our access to your Google data at any time by visiting your Google Account permissions page and removing UptakePro

To exercise these rights, contact us through the information provided within the Service. We will respond to requests within 30 days.

9. Data Security

We implement reasonable technical and organizational measures to protect your data, including:

  • HTTPS encryption for all data in transit
  • Secure authentication via Supabase with bcrypt password hashing
  • Server-side rate limiting to prevent abuse
  • Security headers (CSP, X-Frame-Options, X-Content-Type-Options)
  • Input sanitization to prevent cross-site scripting (XSS)
  • Row-level database policies so one account cannot read another account's conversations, case logs, favorites, or profile

Clinical questions and, for signed-in users, conversation content are stored on our servers. See Sections 2b and 6 for what is kept and for how long.

No method of electronic transmission or storage is 100% secure. While we strive to protect your data, we cannot guarantee absolute security.

10. Children's Privacy

The Service is not intended for use by individuals under 18 years of age. We do not knowingly collect personal information from children. If we learn that we have collected data from a child under 18, we will take steps to delete that information.

11. Changes to This Policy

We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated "Last updated" date. Continued use of the Service after changes constitutes acceptance of the revised policy.

Related policies: Terms of Service · Disclaimer & Terms of Use