Mailinite (“we”, “us”), operated by Kashif Khan, runs mailinite.com and the Mailinite Outbound Readiness plugin, which is available in ChatGPT and other AI assistants that support the Model Context Protocol (MCP). This policy explains what data we collect, why, and what we do with it. Questions go to kashif@mailinite.com.
The short version
- The plugin doesn't need an account, a login, or any personal information.
- We don't store what you send to the plugin. Each request is processed and then discarded.
- We don't sell data, show ads, or use tracking cookies or analytics on mailinite.com.
The Outbound Readiness plugin
What the plugin receives
When your AI assistant calls one of the plugin's tools, it sends us only the inputs that tool needs:
- audit_sending_domain: a domain name (for example, example.com).
- plan_sending_infrastructure: numbers such as your planned monthly email volume and, optionally, prices you choose to enter.
- check_outbound_readiness: optionally a domain name and volume, plus yes/no/unsure answers about your sending practices (for example, whether your list is verified) and, optionally, a bounce rate.
The plugin doesn't ask for, and isn't designed to receive, names, email addresses, contact lists, email content, passwords, API keys or payment details. Please don't paste them into tool requests. Your AI assistant decides what to send to the plugin based on your conversation. Your conversation itself is handled by your assistant's provider (for example, OpenAI) under their privacy policy, not ours.
How we use it
We use the inputs only to produce the result you asked for: running the DNS checks, doing the capacity math, and returning the report to your assistant. To check a domain, the plugin makes public lookups that include the domain name:
- DNS queries for MX, SPF, DKIM, DMARC and A/AAAA records, through our hosting provider's DNS resolvers;
- DNS queries to domain blocklists: Spamhaus DBL, SURBL and URIBL;
- a registration-date lookup through the public RDAP service at rdap.org.
These services receive the domain name being checked and the network address of our server. They don't receive anything about you.
What we keep
We don't save plugin inputs or results in a database, and we don't build profiles or link requests to a person. Our host, Vercel, keeps standard request logs (such as time, URL path, status code and the requesting IP address) for operating and securing the service, for a limited period under Vercel's privacy policy. We don't use those logs for marketing.
mailinite.com
The website is a static site. It doesn't use analytics, advertising pixels or tracking cookies. Pages load fonts from Google Fonts, which means your browser connects to Google's servers. See Google's privacy policy. The pricing calculator runs entirely in your browser and doesn't send what you type anywhere.
If you email us (for example, to request a teardown), we receive your email address, your message and anything you attach. We use it to reply and to provide the service you asked for, and we keep the correspondence as long as needed for that and for our records. We don't add you to a mailing list without asking.
Sharing
We don't sell or rent personal data. We share data only with the service providers described above (hosting, DNS and blocklist lookups, email), or when the law requires it.
Your choices and rights
Depending on where you live (for example, under the GDPR in the EU/UK or the CCPA in California), you may have the right to access, correct, delete or export personal data we hold about you, and to object to how we use it. Email kashif@mailinite.com and we'll respond within 30 days. You can also complain to your local data protection authority.
Security
All traffic to mailinite.com and the plugin is encrypted with HTTPS. Because we don't store plugin inputs, there's very little to protect in the first place.
Children
Our services are for businesses and aren't directed at children under 16. We don't knowingly collect their data.
Changes
If we change this policy, we'll update it on this page and change the effective date. If a change materially affects how plugin data is handled, we'll say so on this page before it takes effect.