Skip to content
← MDML Technologies

MDML Technologies — Privacy Policy

Effective: 2026.11.17

This Privacy Policy explains what data MDML Technologies LLC ("MDML") collects, how we use it, and your choices.

1. What We Collect

  • Account information: email, business name, optional owner name, phone, address.
  • Payment information: handled by Stripe. MDML never sees full card numbers; Stripe stores them under PCI-DSS compliance.
  • Site data: business website URL, scraped content (markdown, services, hours, photos) we cache to render template previews.
  • Usage: bandwidth, function invocations, page views — for billing and performance.
  • Sign-in: Supabase Auth manages your password (hashed) and session.
  • Logs: standard server logs (IP, user agent, request path) for security and debugging.

2. How We Use It

  • Provide and operate the Service.
  • Generate template previews and customizations.
  • Bill you correctly.
  • Send transactional emails (welcome, payment failures, security alerts) via Resend.
  • Prevent abuse, fraud, and ToS violations.
  • Comply with legal obligations.

We do not sell your personal information.

3. Third Parties

We share data with these service providers only as needed to operate the Service:

  • Stripe — payments, payouts, billing.
  • Supabase — database, authentication, file storage.
  • Vercel — hosting and CDN.
  • Resend — transactional email delivery.
  • Firecrawl — public-website scraping when you import a site.
  • NVIDIA NIM — LLM-based extraction of public-site content.
  • OpenAI — AI drafts and MDML assistant answers, including those that use Google data you connected (section 9). OpenAI's API does not train on what we send.

Each is bound by their own privacy policy and contractual data-protection terms.

4. Your Rights

  • Access / Correct / Delete: email hello@mdmltechnologies.com to request a copy of your data, corrections, or deletion. We'll respond within 30 days.
  • California residents (CCPA): you may request what we collect, request deletion, and opt out of any "sale" (we don't sell, but the right exists).
  • EU/UK residents (GDPR): you have rights of access, rectification, erasure, restriction, and portability. Our legal basis for processing is performance of the contract (these Terms) and our legitimate interest in operating the Service.

5. Retention

Account and billing data is retained while your account is active and for 7 years after termination (for tax and dispute records). You can request earlier deletion under "Your Rights" above; we'll honor it unless we are legally required to retain.

6. Security

We use industry-standard safeguards: TLS in transit, encryption at rest, scoped service-role keys, signed Stripe webhooks, and least-privilege access. No system is 100% secure; we cannot guarantee absolute protection.

7. Contact

hello@mdmltechnologies.com — MDML Technologies LLC, Florida.

8. Billing and usage records

To bill the plans above we keep: what price sentence you were shown and when you pressed pay; your plan, trial and renewal dates; your monthly usage (AI credits, emails, texts, call minutes) and any cap you set; and cancellation and plan-change history. Card details are held by Stripe, not by us. We keep billing records for as long as tax and accounting law requires, then delete them. Usage counts are tied to your business account, not to your customers' identities, except where a message has to be addressed to them.

9. Google user data (Gmail, Google Business Profile and Google Ads)

MDML (shown as RoleCall on some Google screens while we finish renaming it) asks for access to your Google account only when you choose to connect it, and only for the feature you turn on. You can connect one without the others.

What we access

  • Gmail (permissions: read your email; manage drafts and send email). When an owner or manager connects their own business mailbox, MDML reads the sender, subject, date and short preview of messages from the last 30 days in Inbox and Spam each time Email is opened in MDML, to sort them into supplier bills, customer and job requests, messages from your team and everything else. Sorting is done by rules on our servers, not by AI. When you press Write a reply on one email, we read that email's full text to draft a reply. We also read your email address, to show which mailbox is connected.
  • Google Business Profile (permission: manage your business listings): the accounts and listings your Google login manages; listing details such as name, address, hours, phone, website and categories; verification status; your reviews; the posts and review replies you approve; and listing performance (searches, views, calls, website clicks and direction requests).
  • Google Ads (permission: manage your Google Ads accounts): the ad accounts your login can access; their campaigns, budgets, spend, clicks and conversions; keyword ideas for phrases you type; and the monthly budget you approve in MDML.
  • A sign-in token from Google, so MDML can keep working without asking you to sign in each time. We store it encrypted.
  • Aggregated data: we don't combine Google user data across businesses, build profiles from it, or use it for analytics or benchmarking. We keep simple counts, such as how many replies a business sent today, to enforce limits.

How we use it

Only for the features you asked for: showing and sorting your email, drafting the replies you ask for, and saving or sending the replies you confirm; keeping your listing up to date, creating and verifying a listing for a new business, and publishing the posts and review replies you approve; showing your listing and ad results, pausing the campaigns you choose to follow, and applying the monthly ad budget you approve. Ad spend amounts are also used to calculate our service fee, which is a share of spend you've agreed to. We do not use Google user data for advertising, to assess credit or for lending, and we do not sell it.

Who we share it with

Only with the service providers that run these features for you, under contract:

  • Supabase — database and sign-in.
  • Vercel — hosting.
  • OpenAI — AI drafts of the replies and ad wording you ask for, and MDML assistant answers that use your email, Google Ads or Business Profile data. OpenAI's API does not use what we send to train its models.

Google user data is never sent to any other AI provider, to advertisers or to data brokers. We share it otherwise only if the law requires it, to protect security, or as part of a merger or sale of MDML after asking your consent.

AI and Limited Use

We do not use Google user data, or anything derived from it, to develop, improve or train generalized artificial intelligence or machine learning models.

The use of raw or derived user data received from Google Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements.

MDML's 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.

How we protect it

  • All traffic is encrypted (TLS), and the database is encrypted at rest.
  • The sign-in token Google gives us is sealed with AES-256-GCM before it is stored.
  • Connecting, reading and replying to email require two-step sign-in. The one exception is a test login on sample data that Google's reviewers use to check MDML.
  • Only the person who connected a mailbox can read its email in MDML; the business owner sees only that it is connected and can disconnect it.
  • People at MDML don't read your Google data unless you ask us to (for support), it's needed for security or to investigate abuse, or the law requires it.

How long we keep it, and how to delete it

  • Email content: never stored. It is read when you open Email and is not kept.
  • Reply log: for each reply sent we keep who sent it, when, to whom and the subject (never the words), while the business account is open.
  • Listing and ad data: the figures MDML saves (such as past ad spend, the campaigns you follow and listing performance) stay with the business's account until you ask us to delete them.
  • Disconnecting: press Disconnect in MDML's Settings, or remove access for MDML or RoleCall at myaccount.google.com/permissions. Disconnecting deletes the stored sign-in token at once, and MDML stops reading anything new. For Gmail we also ask Google to cancel MDML's access, unless the same Google account is still connected to MDML for something else (a Google listing, Google Ads or another business), because Google keeps one permission for all of them. Removing MDML at myaccount.google.com/permissions ends every MDML connection for that Google account.
  • Deleting: email us at the address in section 7 and we delete the Google data we stored within 30 days, except records we must keep for billing and tax (section 8). Deleted data leaves our backups within 7 days after that.

10. MDML Connect browser extension

MDML Connect is our optional Chrome extension. It does your business's own tasks on websites from your MDML account, in your own browser, after you approve: filling forms, connecting your domain, filling supplier carts, filing your receipts, looking products up and reading your connected Instagram grid. You sign in with MDML; its sign-in keys stay on your computer. It works only on websites you allow, one at a time, sends us only what each task needs (never what's typed in a form), never reads passwords, Social Security, bank or card numbers, and places an order only if the owner turns on Autopilot and sets that store to "Place the order". It has its own policy: MDML Connect privacy policy.

11. Facebook and Instagram data

A business owner can connect the business's own Facebook Page and Instagram business account on the Posts page in the MDML app, through Meta's own sign-in. MDML reads the Pages you manage and the linked Instagram account so you can choose one, publishes only the posts you approved or scheduled, and reads the reach, views, likes, comments, saves, shares and clicks of those posts to show you how they did. The Page's sign-in key is stored encrypted. Your Facebook and Instagram data is not sold, is not used for advertising, and is never used for another business.

To stop access, remove MDML in your Facebook settings under Business Integrations. To delete what MDML keeps from Facebook and Instagram (the stored key, the account names and the post numbers), email support@mdmltechnologies.com from your account's email and we will delete it within 30 days. Step by step: mdmltechnologies.com/data-deletion.

12. Website visits and app usage

When you visit mdmltechnologies.com we keep our own record of the pages you open, how long each page is on your screen, how far you scroll, the buttons you press, the site or campaign that sent you, your browser and device type, and your approximate city and country (from your connection, not GPS). We store a random ID in a first-party cookie on our own domain for up to 13 months so we can tell a returning visit from a new one. We don't use it to identify you, we don't fingerprint your browser, and in these visit records we keep only a scrambled form of your IP address. If you later sign up or sign in, the visits made on that same browser become part of your account so we can see how you found us. We never buy or combine data from other sources to identify you. If your browser sends Global Privacy Control or Do Not Track, we record only which page was viewed, with no cookie or ID. Raw visit records are kept 13 months; daily totals 25 months.

When you use the MDML app while signed in, we record which screens you open and how long they're on screen to improve the product, never what you type or your customers' information. Deleting your account deletes this usage record.