Doctor Advertise

Privacy Policy

Effective: November 6, 2026 · Last updated: November 6, 2026

Who we are

This policy covers the Doctor Advertise platform at doctoradvertise.com (the "platform"), a customer-relationship, content and operations system used by a group of related companies (the "group", "we", "us"). It applies to the platform as a whole, not to one company. Legal name and mailing address of the operating company: [to be completed before publication].

What personal data we collect

What we hold depends on how you deal with us:

  • Contacts and sponsors: name, email address, phone number, job title, organisation, notes our staff write about our dealings with you, and the history of messages, proposals and agreements with you.
  • Podcast and event guests: name, contact details, biography, availability, interview questionnaire answers, and the recording release or consent you give.
  • Staff, freelancers and other collaborators: name, email, role, the companies and projects you work on, tasks, time and assignment records, HR and evaluation records kept by your employer, and the details needed for your login (email and a password stored only in hashed form).
  • Forms, surveys and polls: the answers you submit, and any file you upload through a form.
  • Agreements and electronic signatures: the agreement text, your typed or drawn signature, the date and time you accepted, and the decision you made. We do not store your IP address or browser details for e-signature acceptance.
  • Event registrations: name, email, ticket or attendance details, answers to registration questions, and check-in status.
  • Payments and donations: the amount, date, payer name and email, and the provider's reference. Card numbers are entered on the payment provider's own page and never reach our servers.
  • Mailbox data you connect: if you connect a mailbox, we hold the connection settings (the password is stored encrypted) and the messages we fetch or send through it, so they can be shown next to the right contact.
  • Calendar data through Google sign-in (OAuth): if you connect a Google calendar, we ask for one permission only, "calendar.app.created". It lets the platform create one new calendar called "Doctor Advertise" and manage events on that calendar only. It does not let us see or change your other calendars or events.
  • Social account tokens: if a company connects a social account (Facebook, Instagram, LinkedIn, TikTok, X or YouTube) to schedule posts, we store the access tokens the network issues, encrypted, plus the account name and the posts we publish or schedule.
  • Technical and security records: the pages used, sign-in times, and an audit record of staff actions that includes the IP address the action came from.

Why we use it

  • To run the platform and the services you asked for: accounts, projects, bookings, events, podcasts, payments, agreements.
  • To manage business relationships: replying to you, preparing proposals, recording consent, and following up.
  • To send email and text messages that you asked for or agreed to (see Consent and unsubscribe).
  • To keep the platform secure, prevent abuse and keep a record of who did what.
  • To meet legal, tax and accounting duties.

We do not sell personal information.

Who else handles data (service providers)

We use these providers only for the purposes shown. Several are used only if a company has switched the feature on.

  • Google: the Website Translator widget on staff screens (loaded only after a staff member presses the translate button and agrees; the text of the page then goes to Google); Google Calendar through the single scope above. We do not currently load Google Analytics; if we ever do, we will update this policy first.
  • Stripe and PayPal: to take online payments and donations. They are independent controllers of the payment details you give them.
  • Meta (Facebook, Instagram), LinkedIn, TikTok, X and YouTube: to publish and schedule social posts for a company that connected its account.
  • Mailchimp: to send email campaigns to people who agreed to receive them, where a company uses it.
  • Twilio: to send text or WhatsApp messages, only when a company has switched it on and the recipient agreed.
  • Hosting: the platform runs on shared hosting managed through cPanel. The hosting provider stores the data and its backups on our behalf.

Companies in the group use shared records only in line with the sharing settings their administrators choose; one company cannot see another company's private data.

Google API Services User Data Policy

Our use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We use Google user data only to provide the calendar feature you switched on (creating and updating events on the calendar the platform created). We do not use it for advertising, do not sell it, do not transfer it to others except as needed to provide that feature, comply with law or as part of a merger with notice to you, and our staff do not read it except with your consent for support, for security, or where the law requires. You can disconnect at any time, which deletes the stored tokens, and you can also remove access in your Google Account.

How long we keep data

We keep personal data while it is needed for the purpose above, then delete or anonymise it. Some fixed periods: technical request logs are kept about 30 days; raw files from data imports about 90 days; staff evaluation records are flagged for review after about 36 months. Official receipts and records we must keep for tax or legal reasons are kept as the law requires and are not deleted on request. Audit records are kept so we can show who did what; when we remove you we remove or mask personal details in them where we can. Copies in backups are overwritten when the backups expire.

Consent and unsubscribe

We email people for marketing only with their consent. Consent is recorded with the wording shown, the date and where it was given, and we may ask you to confirm by clicking a link (double opt-in). Every marketing email names the sender and includes an unsubscribe link that works without logging in; we stop sending as soon as it is processed and in any case within 10 business days. Addresses that unsubscribe or bounce are put on a suppression list and are not emailed again. Messages you need to receive about something you asked for (an invitation, a password reset, a receipt, a booking) are not marketing and carry no unsubscribe link, but we keep them to what is needed. You can withdraw consent at any time by using the link or by contacting us.

Your rights

  • Canada (PIPEDA and CASL): you may ask to see the personal information we hold about you, ask us to correct it, withdraw consent (subject to legal limits), and complain about how we handled it. You can also complain to the Office of the Privacy Commissioner of Canada. Our commercial messages follow Canada's Anti-Spam Legislation (CASL).
  • United States: you may ask us to access, correct or delete your personal information, and to stop emailing you under the CAN-SPAM Act. Some states give further rights, such as the right to know and to delete; we honour those requests for residents of those states.
  • Europe, UK and similar laws (GDPR-style note): if those rules apply to you, you may ask for access, correction, deletion, restriction, a portable copy, and to object to processing, and you may complain to your local data protection authority.

How to contact us and ask for deletion

Contact: the form on our data deletion page. To ask us to delete your data, use the data deletion page. We will confirm your identity first, because deleting the wrong person's data would harm them, and we aim to answer within 30 days.

Changes to this policy

When we change this policy we publish the new version here with a new "last updated" date.