Privacy Policy

Last Updated: October 11, 2026

Introduction

MDLMN ("we," "our," or "us") is committed to protecting your privacy. This Privacy Policy explains how MDLMN collects, uses, and safeguards your information across our services, including our Chrome Extension and our web platform for business customer messaging (including connected Instagram, Facebook Messenger, and WhatsApp accounts).

Information We Collect

Information You Provide

  • Account ID: You provide your MDLMN account ID through the extension's options page to connect to your account
  • Phone Number: Your preferred phone number for making calls (stored locally in your browser)
  • Dial Preferences: Your call handling preferences (stored locally in your browser)

Information Collected Automatically

  • Selected Phone Numbers: When you use the extension to dial, call, or text, the selected phone number is sent to our API
  • Selected Text: When you use the "Clip" feature, the selected text and current page URL are sent to our API

Business Messaging Platform (Connected Instagram, Facebook & WhatsApp Accounts)

MDLMN offers a web platform that lets a business connect its own Instagram professional account, Facebook Page, and/or WhatsApp Business account so that messages from that business's customers appear in one unified inbox. This section explains the data involved when a business connects a Meta (Instagram, Facebook, or WhatsApp) account.

What Connecting Grants

A business owner or authorized admin connects their account through Meta's official login (Instagram Login or Facebook Login for Business) and grants MDLMN permission to receive and respond to that account's messages. We store an encrypted access token so the connection persists; we never ask for or store the account's Instagram or Facebook password.

Connecting WhatsApp

A business connects its own WhatsApp Business account through Meta's official WhatsApp signup flow, choosing the business phone number it wants to use. WhatsApp messages for that number are sent and received through Twilio, our messaging provider, which connects to Meta's WhatsApp Business Platform on the business's behalf. We never ask for or store the business's Facebook password.

Information We Receive from Meta

  • Message content: the text of messages sent to or from the connected business account
  • Sender identifiers: the Meta-scoped ID (and, where provided, username) of the person messaging the business, used to organize a conversation. For WhatsApp, this is the customer's WhatsApp phone number and, where provided, their WhatsApp profile name
  • Message metadata: message IDs, timestamps, and the connected account ID the message was sent to
  • Connected account details: the business's own Instagram/Facebook account ID and Page ID, or its WhatsApp Business account ID and business phone number
  • WhatsApp message templates: the templates a business creates for messaging customers outside WhatsApp's 24-hour reply window, and their approval status from Meta

We request only the permissions needed to receive and reply to messages on the connected account. We do not access posts, followers, ad accounts, or other Meta data beyond the messaging scope described here.

How This Data Is Used

  • Deliver the unified inbox: display incoming messages and let the business read and reply to them within MDLMN
  • Maintain conversation history: associate messages with the correct customer and connected account
  • Operate the service: we do not use message content for advertising, and we do not sell it

Your Choices & Deletion

A connected business can disconnect its Instagram, Facebook, or WhatsApp account at any time, which stops MDLMN from receiving further messages for that account. To request deletion of message data MDLMN holds, see the "Your Rights," "California Privacy Rights," and "European Users (GDPR)" sections below, or contact us using the details in "Contact Us." MDLMN's use of information received from Meta APIs follows Meta's Platform Terms and Developer Policies.

Google Calendar (Connected Calendars)

A business can connect its Google Calendar to MDLMN so that booked jobs and open times stay in one place. Connecting is optional and is done by the business owner or an admin, in their own Google account.

What Connecting Grants

MDLMN asks Google for four permissions:

  • Calendars MDLMN creates: to create a Jobs calendar for the business and to fully manage only the calendars MDLMN creates, including seeing, adding, changing and deleting their events
  • List of calendars: to see the list of the business's calendars
  • Busy and free times: to see when the business is busy or free on the calendars it chooses
  • Account identity: the connected Google account's email address and a basic account identifier, used only to recognise which Google account is connected

MDLMN cannot see or change events on any other calendar. For calendars the business chooses only so that MDLMN avoids times it is busy, MDLMN receives busy and free times only, never the details of the events on those calendars.

What We Read and Write

We read the event details on the Jobs calendar to show the business its booked work, to keep bookings and reminders in step when a job is moved or cancelled in Google, and to offer customers real open times. On the other calendars the business chooses, we read busy and free times only, to avoid offering times when the business is busy. Bookings made through MDLMN, including requests waiting for the owner's approval (shown as tentative), are added to the Jobs calendar with the job and customer details the business needs to do the work.

Separately from Google Calendar, booking hours can come from the business's public Google listing (Google Places), which MDLMN looks up without using the business's Google account.

How We Use It

We use Jobs calendar events to run the business's schedule in MDLMN. If the business turns it on, we also use an AI service to read a job's details so we can link it to the right customer and send that customer the reminders the business has set up. We do not use Google Calendar data for advertising, do not sell it, and do not use it to train or improve general artificial intelligence or machine learning models. Where we use an AI service to read a job's details, we send only what is needed for that one job, only to provide that feature to the business, and the service may not keep or train on it.

Storage and Sharing

The access granted by Google is stored encrypted. We also store the connected Google account's email address and account identifier, and a copy of the Jobs calendar's event details so the business's schedule stays current. Calendar data is shared only with the service providers that run MDLMN for the business (hosting and database, and the AI service described above), only to provide these features, or when the law requires it. MDLMN staff do not read a business's calendar data unless the business asks us to for support, or for security or legal reasons.

Disconnecting and Deletion

A business can disconnect Google Calendar at any time from its Calendar settings in MDLMN, which removes our access at Google (unless the same Google account is still connected to another business in MDLMN) and deletes the stored access and our copy of the Jobs calendar's events. A business can also remove MDLMN's access at myaccount.google.com/permissions; that stops our access, but our stored copy is deleted only when the business disconnects in MDLMN or asks us to delete it. The Jobs calendar and its events stay in the business's Google account. When a customer of the business asks MDLMN to delete their personal data, we also delete the events MDLMN added to the Jobs calendar for that customer's bookings and requests. If MDLMN can no longer reach that calendar (for example, the business connected a different Google account, or the calendar was deleted or unshared), we tell the business, which is then responsible for removing those events. Deleting a business in MDLMN deletes its stored Google Calendar connection and calendar data.

Limited Use

MDLMN'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.

How We Use Your Information

We use the collected information to:

  • Authenticate your account with the MDLMN service
  • Initiate phone calls through your Twilio account
  • Send text messages through your Twilio account
  • Process clip requests by sending selected text to your phone
  • Deliver the messaging inbox for connected Instagram, Facebook Messenger, and WhatsApp accounts

Data Storage

  • Local Storage: Your account ID, preferred phone number, and dial preferences are stored locally in your browser using Chrome's storage API
  • No Cloud Storage: The extension itself does not store any of your data on our servers
  • Server Processing: Information sent to our API (phone numbers, text content) is processed in real-time and not permanently stored

Third-Party Services

Twilio

Our service uses Twilio to handle phone calls, text messages, and WhatsApp messages. When you use the extension, or when a business sends or receives WhatsApp messages through MDLMN, data is transmitted to Twilio's servers. Please review Twilio's Privacy Policy for more information.

Meta (Instagram, Facebook & WhatsApp)

When a business connects an Instagram, Facebook, or WhatsApp account, MDLMN exchanges data with Meta's messaging APIs (for WhatsApp, through Twilio) to receive and send messages on that account. Please review Meta's Privacy Policy for more information. MDLMN's use of information received from Meta APIs adheres to Meta's Platform Terms and Developer Policies.

MDLMN API

Selected phone numbers and text are sent to our API (api.mdlmn.co) to process your requests. This data is used solely to fulfill your request and is not stored permanently.

Analytics (Google Analytics & Microsoft Clarity)

We use analytics to understand how our websites and extension are used and to improve them:

  • Google Analytics runs on mdlmn.co, consentlink.co, and askrupert.co. It records page views and general usage such as device and browser type and approximate location.
  • Microsoft Clarity runs on mdlmn.co. It records how visitors interact with pages, such as clicks and scrolling, to help us fix usability problems.
  • The MDLMN Chrome extension sends usage events to Google Analytics, such as which feature was used and, for dialing, the website’s domain.

On consentlink.co and askrupert.co, Google Analytics does not receive the contact details you submit, and the extension’s usage events do not include the phone numbers or text you select. Please review Google’s Privacy Policy and the Microsoft Privacy Statement for more information.

Data Sharing

We do not:

  • Sell your personal information
  • Share your data with third parties for marketing purposes
  • Use your data for purposes other than providing the MDLMN service

We may share data:

  • With Twilio to process calls, texts, and WhatsApp messages
  • With Meta to send and receive messages on a connected Instagram, Facebook, or WhatsApp account
  • When required by law or to protect our legal rights
  • With your explicit consent

Data Security

We implement appropriate security measures to protect your information:

  • HTTPS encryption for all data transmission
  • Secure API authentication
  • Local browser storage (data never leaves your device unless you use the extension features)

Your Rights

You have the right to:

  • Access your data stored in the extension (through Chrome extension settings)
  • Delete your data by removing the extension or clearing its storage; for messaging data from a connected Instagram, Facebook, or WhatsApp account, disconnect the account or contact us to request deletion
  • Delete your MDLMN account and personal data: if you have an MDLMN account, you can request permanent deletion of it and your personal information by contacting your administrator or emailing support@mdlmn.co. We verify your identity before anything is deleted. The minimal consent/message records the law requires are retained as compliance evidence.
  • Control what information you provide to the extension and which accounts you connect
  • Opt-out by not using the extension or by disconnecting a connected messaging account

If you received text messages from a business using MDLMN and want to access or delete your data (as a message recipient), use that business's privacy request page at consentlink.co/{business}/privacy-request, linked from the privacy notice they shared with you.

Children's Privacy

Our extension is not intended for users under the age of 13. We do not knowingly collect information from children under 13.

Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of any changes by updating the "Last Updated" date at the top of this policy.

Contact Us

If you have questions about this Privacy Policy, please contact us:

California Privacy Rights

If you are a California resident, you have additional rights under the California Consumer Privacy Act (CCPA):

  • Right to know what personal information is collected
  • Right to delete personal information
  • Right to opt-out of the sale of personal information (Note: We do not sell personal information)

European Users (GDPR)

If you are in the European Economic Area (EEA), you have rights under the General Data Protection Regulation (GDPR):

  • Right to access your data
  • Right to rectification
  • Right to erasure
  • Right to restrict processing
  • Right to data portability
  • Right to object

Consent

By using the MDLMN Chrome Extension or platform, or by connecting a messaging account, you consent to this Privacy Policy and agree to its terms.