Your privacy, in plain language.

Account authentication identifiers, one creator workspace, one Instagram connection, and the inbound DMs and comments delivered after that connection.

When you connect Instagram, Mingly also reads your last 30 days of comments and DMs, a small number of times soon after you connect, to show you which questions are still waiting. This happens whether or not your replies are turned on. This read does not send anything and does not add those people to your contacts. From it we keep only counts and up to five short question excerpts, each with the date it was asked. Before an excerpt is stored we check it for names and contact details, and if we find any, or cannot be sure, we do not store it. Excerpts hold no name or account, so we cannot pick out and delete one person's excerpt before it expires. We delete excerpts within 30 days, and we delete all of it when you disconnect the account. If Instagram does not allow the read, we tell you what we could not see.

The inbound record can include sender handles, message or comment content, timestamps, connection references, and provider event identifiers needed to keep records separated and deduplicated.

If you join a waitlist, Mingly stores your email address and which waitlist you chose in Resend, our email provider, so we can tell you when it opens.

Mingly does not ask for a Google or Instagram password. Those credentials remain with their authentication providers.

Mingly does not send Instagram replies or publish content from a source import or private reply preview.

If a workspace administrator enables and starts a website import, Mingly sends only the supplied public website URL and bounded public page content to Firecrawl. Imports stay on the same domain and exclude authenticated pages, downloads, legal pages, shopping flows, and private network addresses.

Normalized page text is held only for analysis and purged within 24 hours. Mingly retains the source URL, page title, content hash, and the short evidence excerpts attached to suggestions. Instagram DMs, cookies, passwords, and published Setup Revisions are never sent to Firecrawl.

Evidence extraction and private reply previews run through a third-party AI model provider. A private preview receives the active published Setup Revision and the creator-entered test message, then returns a review-only result. It cannot create or deliver a reply.

The question excerpts from your 30-day read go to that provider only if you ask Mingly to draft sample replies from your Overview, after you have published your setup. The drafts are for you to read. They are not sent to anyone, and we delete them with the excerpts.

When you press “Suggest from my Instagram” during setup, Mingly reads your recent captions, and your comments and DMs from the last 60 days, once, through your connected account. We use what it reads to suggest who your audience is, questions your followers often ask, and examples of your own writing. Before anything goes to the AI provider, we remove names, handles, contact details and similar personal details from your followers' text, and we leave out any text we cannot be sure about. Your own captions and replies are sent to the provider too. Mingly does not store what it reads for this, and nothing is added to your setup until you choose it. Our removal of personal details is not perfect: a third party's name that a follower writes in their own words can still reach the AI provider, as it can with AI replies.

The specific model provider and its processing region will be named in the approved notice before launch.

Mingly keeps operational metadata such as model and prompt versions, hashes, token use, latency, and failure codes. Raw prompts and model responses are not stored in AI run telemetry or sent to Sentry.

In Settings, on the Instagram tab, anyone in the workspace can disconnect Instagram. On the Profile tab, a workspace owner can send a request to delete the workspace or a request to erase all follower data. A request is recorded and shown with its status. It does not remove anything by itself, removal does not start automatically, and requests have no set date. After sending a request, email support@hellomingly.com so we can act on it.

In Leads, you can clear one contact's lead details straight away and stop them being captured again. Their conversations stay.

Mingly does not have a data export or a message retention setting today.

This page must be updated with approved retention periods, provider disclosures, legal bases, contact details, and request procedures before launch.