---
title: "Privacy Policy | Mentio"
description: "How Mentio collects, uses and protects your data: account details, the public posts it indexes, who we share it with, retention, and your rights."
canonical: https://mentio.dev/privacy/
markdown: https://mentio.dev/privacy/index.md
last-updated: 2026-11-19T09:45:21.580Z
---

# Privacy Policy | Mentio

> How Mentio collects, uses and protects your data: account details, the public posts it indexes, who we share it with, retention, and your rights.

Source: https://mentio.dev/privacy/

Legal

# Privacy Policy

Last updated: October 4, 2026

Mentio ("we", "us") is a social listening service for developer platforms, available at[mentio.dev](https://mentio.dev). This policy explains what data we collect, why we collect it, and the choices you have. Questions or requests: write to[support@mentio.dev](mailto:support@mentio.dev).

## Data you give us

-   **Account data.** Your name, email address, and a password (stored only as a salted hash) when you sign up, or your Google account identity if you sign in with Google.
-   **Workspace data.** The keywords you track, your company profile and context, feed and notification settings, and anything else you configure in the product.
-   **Integration credentials.** If you connect Slack, we store the workspace name, ids, and the bot token Slack issues so we can post notifications to the channel you pick. Disconnecting removes the token and we ask Slack to revoke it. API keys you mint are stored only as hashes and are shown to you once.

## Data we collect automatically

-   **Usage and billing counters.** Keyword-days and matched mention counts, which determine the daily deductions from your prepaid balance, and the ledger of top-ups and deductions behind it.
-   **Service logs.** Standard operational logs (timestamps, request metadata, errors) kept for reliability and abuse prevention.
-   **How you found us.** When you create an account we record where your first visit came from: the referring page, the page you landed on, and, if you arrived from one of our ads, the campaign, the keyword and the ad platform's click identifier. It travels in the page address, not in a cookie, and is stored once with your account. We use it to measure which ads lead to customers, and we may report a signup or a purchase back to the ad platform with that click identifier. No ad pixel runs on our pages.

On mentio.dev and our docs we set no cookies: page views are counted without one. In the dashboard (app.mentio.dev) we use a session cookie to keep you signed in, and PostHog, our product analytics provider, stores an identifier in a cookie and in your browser's local storage so we can see how the product is used. PostHog also records dashboard sessions so we can fix what confuses people, with everything you type masked. No advertising or cross-site tracking cookies, and no ad pixels.

## Public content we process

The product works by monitoring publicly available posts on platforms such as Bluesky, Hacker News, Reddit, X, LinkedIn, GitHub, Stack Overflow, DEV, YouTube, TikTok, Instagram, Facebook and news sources, and public reviews on the App Store, Google Play, Trustpilot and Google Maps. This section is for the people who wrote those posts.

**What we store about post authors.** When a public post mentions a keyword one of our customers tracks, we store:

-   the public text of the post and its link;
-   the author's public name, handle, avatar, and follower, following and post counts as the platform shows them;
-   for some platforms, public profile facts: bio, company, location, website, linked accounts, and an email address only where the author published it on their public profile;
-   the engagement counts (likes, reposts, replies) the platform reported when we read the post;
-   a classification our AI derives from the post: how relevant it is to the customer, its sentiment, and topic tags such as a question or a bug report.

**Why, and on what legal basis.** We process this data on the basis of legitimate interests (GDPR Art. 6(1)(f)): ours and our customers' interest in monitoring public conversations about their products, brands and markets. We keep the impact on authors low: we only read data that is already public, never private messages; we do not track anyone across the web and place no cookies or pixels on them; we look up a profile only for posts that matched a customer's keyword; and we never sell this data.

**Who decides what.** Customers can add their own notes, tags, outreach stages and contact activity about a person in their workspace. For that data the customer is the controller and Mentio processes it on their behalf.

**How long we keep it.** A stored post that no customer keyword matches any more is deleted after 30 days, and records of alerts delivered about a post after 90 days. A matched post stays while the customer's workspace keeps it, until the author asks us to remove it or the workspace is deleted. If a post is deleted at its source it may still be in our index until then.

**Objecting and removal.** You can object to this processing and ask us to erase your data at any time through our [removal page](/privacy/remove) or by writing to[support@mentio.dev](mailto:support@mentio.dev). We complete every request within 30 days. Erasure removes your posts from every customer workspace, empties your profile, and stops us from storing your future posts. We keep only your profile link as a suppression record, so we can keep honouring your request.

**AI assistants.** Our MCP server, which lets AI assistants read a customer's workspace, never returns a person's email address.

## YouTube API Services

Mentio uses YouTube API Services to find public videos whose title or description mentions a keyword you track. We read public data only, with an API key: no YouTube account is connected to Mentio, and we never upload, edit, rate or comment on videos. For a matched video we store the public title, description, channel name, link and publish date, refresh or delete that data within 30 days of retrieving it, and share it only with the delivery channels you configure (your dashboard, Slack, email, Telegram or webhooks). We do not sell YouTube data or use it for advertising. By using YouTube results in Mentio you also agree to the[YouTube Terms of Service](https://www.youtube.com/t/terms), and Google's handling of data is described in the[Google Privacy Policy](https://policies.google.com/privacy). To have a video removed from our index, email [support@mentio.dev](mailto:support@mentio.dev).

## How we use data

To provide and improve the service, deliver the notifications you configure, bill usage, secure the platform, and communicate with you about your account. We do not sell personal data and we do not run ads. AI classification runs on TypeSafe and Cloudflare Workers AI; we do not use your data or monitored content to train our own models.

## Who we share data with

-   **Cloudflare**: hosting, storage, and AI inference for the entire service.
-   **TypeSafe**: AI classification of the public posts that matched a keyword (relevance, sentiment and topic tags).
-   **Apify**: reads public posts and reviews from some platforms on our behalf.
-   **Resend**: sends our emails.
-   **Polar**: our merchant of record. Payments, invoices, and card details are handled by Polar; we never see or store your payment card data.
-   **PostHog**: product analytics and session recordings in the dashboard.
-   **Axiom**: stores our service logs.
-   **Slack**: only if you connect it, to post notifications you configure.
-   **Telegram**: only if you connect it, to post notifications you configure.
-   **Google** and **GitHub**: only if you choose to sign in with them.

## Retention and deletion

Account and workspace data is kept while your account is active and deleted when you ask us to close it. Billing records are kept as long as law requires. Monitored public posts live in a shared index; deleting your account removes your organization's associations with them. Data obtained from YouTube API Services is refreshed or deleted within 30 days of retrieval.

## Your rights

If you are in the EU/EEA (GDPR) or a similar jurisdiction, you can request access, correction, deletion, portability, or restriction of your personal data, and object to processing, by emailing [support@mentio.dev](mailto:support@mentio.dev). If you wrote a post we stored, you can also use our [removal page](/privacy/remove). You can also lodge a complaint with your local supervisory authority.

## Security

All traffic is encrypted in transit. Passwords and API keys are stored hashed, integration tokens are scoped to the minimum permissions the feature needs, and access to production data is restricted.

## Changes

We will update this policy as the service evolves and change the date above. Material changes will be announced in the product or by email.
