Updated November 7, 2026
MedSales Radar is run by MedSales Radar LLC, and “we” on this page means MedSales Radar LLC. You can browse listings and use the free search without an account. We collect the information needed to run the site and the optional tools you choose. This page explains what that includes.
Your browser sends network and request information when it loads the site. Netlify hosts the website; Render hosts our API and database. These services may keep operational and security logs, including IP addresses and requested URLs. Browsing without an account does not make those requests anonymous.
Search terms and locations go to our API to find matching jobs. If you allow browser location access, the coordinates are sent to our API for the nearby search. City lookups use our own copy of GeoNames data, rather than an outside geocoding service. Fonts are hosted on this site.
Employer logos load from logo.dev. That service receives the employer domain requested and ordinary browser request information, such as your IP address and browser type. We do not send your account details to the logo service.
We store your email address, a password hash, account creation and email-verification details, session-security information, and the version and time of your latest recorded terms acceptance. Your email is used for sign-in, verification, requested password resets, enabled alerts, a 30-60-90 day plan you ask us to email to you, and account or billing communications. When an account is created, we send ourselves an email naming its address, through Resend, so we know who has joined.
Signing in with Google is optional; an email address and a password work just as well. If you choose it, Google sends us a signed message with your email address, whether Google has confirmed it, your name, a link to your profile picture and Google’s number for your account. We keep only the email address, as your account’s confirmed address, and do not store the message, your name, the picture link or that number. An account made this way has no password until you choose one with “Forgot password?”. Google’s sign-in script is loaded from Google only when you open the sign-in or create-account window, never when a page loads, and Google handles the sign-in, including any of its own cookies, under its own privacy policy.
We also store the jobs you save, the applications and dates you record, the 30-60-90 day plan you write while signed in, alert preferences, territory watches, and when you last opened the jobs map, so the map can show what is new since then on any device. If you choose to tell us your background when we ask (once, after signing up or the next time you visit signed in) or on the account page — athlete, clinician, military, B2B sales, scientist, student, current rep or other — we store it to point you to the guide written for it and to list roles that welcome it first in your alert email. It is optional, you can change or clear it at any time, and it is never shown to employers or other visitors. Anything you put in the planner while signed in is part of your account data; signed out, the planner keeps your plan in this browser only and never sends it to us. Please do not include sensitive information you do not need for that purpose. If you confirm your email address and press “Email me my plan”, we email the plan saved to your account to that address and no other.
Applications happen on the employer’s website. We do not receive the application or an employer’s hiring decision; the tracker records what you tell us. We do not provide employers with your account activity.
Alerts are off unless you enable them. We store the search criteria you choose, the schedule, whether the alert is enabled, delivery progress, and unsubscribe information. Territory watches can include named employers and additional search criteria. A territory saved on the jobs map also stores its center point and radius, or the outline you drew, and any keyword you searched with.
Resend delivers our account and alert emails, so it processes the recipient address and message content, including the jobs in an alert and the text of a 30-60-90 day plan you ask us to email to you. Delivery, bounce and complaint information helps us avoid repeatedly sending to an address that cannot receive mail. If an employer takes down a job you saved, we email you once with similar open roles; you can turn this off on your account page. Job-alert emails, and that one, include an unsubscribe link that works without signing in. Turning an alert off keeps its settings unless you delete it or your account.
We count how many alert emails we send each day, by type of email, and how many people unsubscribe, as daily totals. Links in our alert emails pass through our site so we can count, per email type per day, how many are followed; they carry nothing that identifies you. To count a device once a day, the IP address is held in memory only, never written to the totals. The unsubscribe link does not pass through it, and our emails carry no tracking pixel: their one image, the logo, and the typeface they are set in are the same files for everyone and are not counted.
Resume tailoring was withdrawn on September 8, 2026. The site no longer offers resume uploads, storage or AI tailoring. Previously, a resume could be sent to Anthropic to create a tailored version.
The removal includes a cleanup of saved resume text and uploaded Word files in the active account database. This does not establish immediate erasure from historical provider logs or backups. If you used the former feature and have a question about your data, contact us.
Stripe handles checkout, card details and billing. We send your email address and account reference to associate a payment with your account. We store the Stripe customer identifier, plan and source, paid-through date, cancellation status and billing-event timing to manage access. Card numbers are entered on Stripe’s page and are not stored in our application database.
Stripe also processes billing details and payment history under its own privacy policy, including for fraud prevention and legal obligations. Canceling renewal keeps paid access until the end of the paid period and leaves your account data in place. Stripe may retain payment records after you cancel or delete your MedSales Radar account.
Business adds employer hiring alerts, private data links and a weekly data email. An employer hiring alert stores its name, the employers, regions, states, specialties, levels and product lines you choose, whether it is on, and when it last emailed you. Resend delivers those weekly emails, and each carries an unsubscribe link, like our alerts.
Your private data links let a spreadsheet fetch the Business files without signing in. We do not store the links themselves; each is worked out from your account and a version number. Anyone who has one of your links can download those files while your plan is active, so treat it like a password. We store whether your links are on, that version number, when a link was last used (recorded at most once an hour), whether the weekly data email is on, and when it was last sent. Switching the links off, or making new ones, stops the old ones at once.
We sometimes give a person Pro or Business free for a set number of months. To do that we store the email address we were given, the plan, its length, the name shown on the account page, and when it was given, started, ended or withdrawn. It starts once an account with that address has confirmed it and agreed to our terms, and ends on its own on the date the account page shows. Nothing is charged, no card is asked for, and the site sends no email because of it. Deleting the account deletes the record; if the address never opens an account, ask us and we will delete it.
Our contact and partnership forms use Netlify Forms. The information you submit, including your message, any contact details you supply and, on the partnership form, your organization and website, is processed by Netlify and may also be held in our email inbox so we can respond. For the partnership form, we count how many are sent, as a daily total that holds nothing you wrote; so that one address cannot inflate it, the IP address is held in memory only, for the day. Messages are separate from your account and are not automatically erased by the account-delete button. Do not send passwords, card details or sensitive medical information through either form.
We use Cloudflare Web Analytics for aggregate visits and website performance. Cloudflare describes this service as using no analytics cookies, local-storage identifiers or fingerprinting to track individuals. It receives browsing and performance information, such as page addresses, referring sites, country, and browser or device characteristics. We do not send your account email or account identifier to the analytics service.
Our API separately counts clicks on Apply, company pages, employer career links and the other roles a job page suggests. It stores daily totals by listing or employer. To avoid counting repeated clicks from the same address, it temporarily holds IP addresses with the relevant click in memory; that set resets when the daily counter rolls over or the process restarts. IP addresses are not written to the aggregate traffic table. Hosting logs and security controls are separate from those totals.
In the same way, it counts how many people see and use our sign-up and upgrade prompts, including how many view the pricing and Business pages: which prompt, the kind of page the visit began on (for example a job page, the home page or a particular guide), and whether the screen is a phone or a computer. It stores only daily totals, with no account, email or IP address attached.
It also counts, by plan, how many accounts confirm their email address, open checkout, make a first payment, set a subscription to end, have a payment fail or see a paid plan end, and the day’s total paid and refunded, and which prompt led to the checkout and the payment. These are daily totals as well, with no account, email or IP address attached. To count each account’s checkout once a day, and to match a payment to the prompt its checkout came from, it holds account numbers, and that prompt, in memory only, for no more than two days, until the payment arrives or the process restarts; they are not written to the totals.
It also counts downloads of the three free Business samples (the guide, and the 25-row sample as CSV and as Excel) once per browser per file per day, as daily totals for each file with no account, email or IP address attached; to tell one browser from another and to cap counts from one address, it holds the address and a one-way code made from it and the browser type in memory only, never on disk, until the daily counter rolls over or the process restarts.
For Business subscribers, it counts downloads of Business files, and fetches through the private data links, per file per day, with no account attached; to count each account or link once a day, it holds the account or link number in memory only until the daily counter rolls over or the process restarts.
It also counts which search filters are used, as daily totals, never what you typed; and clicks in the lists of other internships beside an internship posting, per list per day. As with Apply clicks, it holds the IP address in memory only, to count a device once a day.
It also counts, as daily totals, the kind of site a visit came from (for example a search engine, an AI assistant, a social network, one of our alert emails or a school’s site), worked out in your browser from the page that sent you, and how many accounts and alerts those visits led to; the sending page’s address is never sent to us. It counts the values picked on the board from its own lists, such as an industry, a call point, a state or a pay floor, and the employers picked in the employer filter; a typed keyword is never sent, and a typed place only as its state. It also counts, as daily totals, which two of those listed values were set at the same time (for example an industry and a state), once per device a day. Links in our alert emails carry the same short marker for every reader, so a visit from one can be counted as such.
If you have an account, we keep the day it last opened the site signed in (a date, never a time, page or address), and count accounts that come back each day by how long ago they joined. The stage you mark on an application in your tracker (for example Interviewing or Offer) is kept with that application, and we count moves into each stage as daily totals with no account attached. Both are in your account download and are deleted with your account.
The MedSales Radar application does not set cookies for advertising or analytics. It uses local storage for your sign-in token, dismissed prompts, the jobs you save before creating an account (these move to your account when you create one, and are then cleared from the browser), and a 30-60-90 day plan written while signed out (it moves to your account the first time you open the planner signed in, if the account holds no plan, and is then cleared from the browser; signed in, the planner keeps no copy in the browser). It uses session storage for temporary actions such as returning to a job after sign-in, and, for sign-up counts, the kind of page your visit began on and the prompt you clicked, cleared when the tab closes. The sign-in token is sent to our API to authorize account requests. Clearing browser storage signs you out but does not delete your account.
Employer websites, Stripe checkout and other linked services have their own cookies, storage and privacy practices. Their pages are governed by their policies.
Our guide to independent and 1099 rep work includes a disclosed RepHunter affiliate link. We may earn a commission from a qualifying referral. Following it sends you to another website and can identify the referral through the link. We do not send your MedSales Radar account details to RepHunter.
We do not sell or rent account data, run an advertising network, or sell employers placement or ranking on the board. The services named above receive information to host the site, serve images, measure performance, handle messages or process payments. They may also process information for security and legal purposes under their own policies. We may disclose information when legally required.
The account page offers a download of your account information, including your terms-acceptance and email-verification record, saved jobs, recorded applications, planner, alert and watch settings, the background you chose, data-link settings, and any complimentary access given to you. Password hashes and internal security information are not included, and neither are the data links themselves. You can change supported settings in the site and contact us to request access, correction or deletion of other information. We handle requests according to applicable law and may need to verify that the request is yours.
To delete your account, open the tracker and choose Delete account. A successful deletion removes the account, saved jobs, application records, planner, alerts, territory watches, employer hiring alerts and data-link settings from the active database, with any record of complimentary access given to you. If you have a Stripe subscription, deletion first attempts to end it immediately. If that cannot be confirmed, the account is kept and an error explains how to proceed.
Deleting an account is different from canceling renewal: it ends account access and does not automatically issue a refund. Contact us under the refunds policy to request one. Download anything you want to keep before deleting.
Account data is kept while your account remains open, however long it goes unused: no account is deleted after a set time. An account whose email address is never confirmed is sent nothing but its confirmation emails, and stays until it is deleted from the account page or on a request to us. Account deletion does not instantly erase separate support messages, payment records, operational logs or provider backups, or the coded email records described under Security. Their retention depends on the service and applicable security, accounting and legal requirements; we do not promise a fixed deletion period for those separate records. Contact contact@medsalesradar.com about information outside the account download or deletion controls.
Public employer postings are used to build the job board and its search labels. Each listing links to the employer, whose application and privacy practices are separate. Closed or aged listings are removed from the board during cleanup. We keep closed postings, including their text, as a permanent market-history archive of public employer postings, used to measure hiring over time; it is not deleted on a schedule. It contains job information, not your saved jobs or application history. An employer can ask for its listings and those records to be removed, and we delete them.
Passwords are stored as salted scrypt hashes, and sign-in uses expiring signed tokens. The public website and API use HTTPS. Access controls and security measures reduce risk, but no service can promise perfect security.
So that our sign-up and password-reset forms cannot be used to flood somebody’s inbox, we limit how many confirmation and reset emails one inbox can receive; spellings that reach the same inbox, such as an address with a +tag, count as one. To count them, we keep a one-way code made from the address, not the address itself, with the time of each such email. Those records are deleted once they are two days old, the next time the site sends one of these emails or restarts. If an address bounces, or one of our emails to it is reported as spam, we send that inbox no more confirmation or reset emails and keep its code for that purpose, even after the account is deleted, so that deleting and re-creating an account cannot start them again. Contact us to have that block lifted. The planner’s “Email me my plan” is limited the same way: each plan we email is recorded with that one-way code and its time, the records are deleted on the same schedule, and no plan is emailed to a blocked inbox.
We update this page when our practices change. The last-updated date identifies this version. For questions about this policy or your information, email contact@medsalesradar.com or use the contact page.
Last updated October 25, 2026.