Privacy policy
Last updated 19 October 2026.
This policy explains what personal information MediSearch collects when you use MediSearch, why, who else sees it, and what you can ask us to do about it. We handle personal information under Canada's Personal Information Protection and Electronic Documents Act (PIPEDA).
MediSearch is a tool for businesses. It measures how AI search engines describe a clinic or practice. It is not a place to put patient records, and you should not enter any patient's personal health information into it.
What we collect
| What | Why |
|---|---|
| Your name and email address | To create your account, sign you in, and contact you about the service |
| The website, business name, address and phone number you add | To write your question set and to recognise your business in an AI answer |
| The questions asked and the answers recorded | This is the measurement. It is what the product reports |
| Billing status and a Stripe customer reference | To run your subscription. We never see or store your card number |
| Usage and cost records for the work your account runs | To apply plan limits and to account for what was spent on your behalf |
| Data from services you choose to connect | Google Analytics, Search Console and others, only if you connect them, and only to show the numbers you connected them for |
Connecting Google
Connecting Google is optional and nothing in MediSearch requires it. When you connect it we ask for two permissions, both read only, in one consent:
| Permission | What we do with it |
|---|---|
View Search Console data for your verified sites
(webmasters.readonly) |
Read the search queries and clicks your own site already receives, so the questions we ask AI assistants are grounded in real demand rather than a model's guess. |
View your Google Analytics data
(analytics.readonly) |
Read visit counts, and in particular visits that arrived from an AI assistant, so you can see whether being named is sending anyone to your site. |
Both are read only. We cannot change, create or delete anything in your Search Console or Analytics, because we never ask for permission to. Google's consent screen lets you grant one and not the other, and we record which permissions actually came back, so the app reflects what you granted rather than what it asked for.
We store the access and refresh tokens Google gives us so the connection survives until you end it. They are held in our database, which runs in the United States, as described under "Where it is stored" below. They travel over an encrypted connection and are never shown to another customer.
What we read from Google is shown only inside the MediSearch account that connected it. No other customer sees it, and we do not combine it with anyone else's data.
Search Console results are read when the app needs them and are not stored. From Analytics we store visit counts, including the visits that came from AI assistants, so the app can show how they change over time.
You can disconnect Google inside MediSearch at any time. Disconnecting deletes the tokens we hold and the Analytics figures we stored, and tells Google to cancel our access. You can also revoke our access directly at myaccount.google.com/permissions, which stops us reading anything further straight away. To have what we already stored deleted as well, disconnect inside MediSearch or write to callum@medisearch.net and we will delete it within thirty days.
We do not use Google user data to train any model, we do not sell it, we do not use it for advertising, and we do not transfer it to anyone except the service providers listed under "Who else sees it" who run MediSearch on our behalf.
MediSearch's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Your mailbox
MediSearch never asks for access to your email. Connecting Google does not grant it, and nothing in MediSearch can read, send or delete mail in your account. We do not send you marketing email.
Who else sees it
We use other companies to run the service. They only get what they need to do their part:
- Anthropic and Google, to generate your questions, to ask them, and to grade the answers.
- DataForSEO, to ask questions of Google's AI Overviews from the markets you serve.
- WorkOS, for sign-in and account identity.
- Stripe, for payment.
- Google Ads, to count sign-ups that came from our ads, unless you decline advertising cookies.
- Railway, where the application and database run.
- Any integration you connect yourself, such as Google Analytics, Search Console, Slack, WordPress, HubSpot or Mailchimp.
We do not sell personal information, and we do not share it for advertising.
Where it is stored
The application and its database run in the United States. Information about you is therefore stored outside Canada and may be accessible to United States authorities under the laws of that country. By using the service you consent to that transfer.
How long we keep it
We keep your account and its measurements for as long as your account exists. Deleting a website removes that website and everything scanned for it. Closing your account removes your account data.
Two things survive a deletion on purpose: records of what was spent running your account, which we keep for our own accounting with the account reference removed, and anything we are required by law to retain.
We do not delete measurements on a timetable. If you want something gone sooner, delete the website or ask us and we will do it.
Your rights
You can ask us for a copy of the personal information we hold about you, ask us to correct it, or ask us to delete it. Write to the address below and we will answer within thirty days. If you are not satisfied with our answer you can complain to the Office of the Privacy Commissioner of Canada.
Cookies
The public website and the application load Google's advertising tag so we can tell whether our ads lead to sign-ups. It is on unless you turn it off: choose Decline in the cookie banner on our public website, or at any time from "Cookie choices" at the bottom of its pages, and it stops and removes the cookies it set. A browser sending Global Privacy Control is treated as having declined. Your choice is remembered in a cookie for six months. While it is on, Google sets its own advertising cookies, and if you arrived from one of our ads, that ad's reference is kept so the sign-up can be counted.
The application sets a session cookie so you stay signed in, and stores a small amount of preference data such as your chosen theme in your own browser. Nothing from your Google connection and nothing you enter in the application is used for advertising.
Security
Access to the application requires a sign-in. Each account's data is separated from every other account's, and we test that separation. We use encrypted connections throughout. No system is perfect, and if a breach affects you we will tell you and the Privacy Commissioner as the law requires.
Changes
If we change this policy we will update the date at the top, and we will tell you directly if the change is significant.
Contact
Questions, requests and complaints about privacy go to:
MediSearch
callum@medisearch.net