Privacy Policy

Reportagram Privacy Policy

Last Updated: October 19, 2026

Overview

Reportagram sends reports on your advertising (Meta Ads, Google Ads) and your sales (amoCRM, Bitrix24, HubSpot) to Telegram, Slack or email, with short AI commentary and answers to questions about those reports. This policy explains what data we collect from the platforms you connect, how we use it, who processes it and how to delete it.

Data We Collect

Account data: your email address, name and settings. Advertising data (read-only): ad account, campaign, ad set and ad names and IDs, and performance figures such as spend, impressions, clicks, leads and purchases, with links to your ad previews. CRM data (read-only): your pipelines and stages, managers' names, and for each lead the lead ID, its stage and pipeline, dates, deal amount, the responsible manager, its source, and the values of custom fields that hold tracking data (such as UTM tags and the Meta lead ID). We do not store a lead's name or its contacts' names, phone numbers or email addresses: when a feature you turn on needs them (such as instant lead alerts), we read them at that moment and don't keep them. Messenger data: chat and channel IDs and names, and the messages you address to the Reportagram bot.

How We Use Data

We use the data you connect only to build your reports, AI commentary and answers, and, when you turn it on, to send the conversion events you choose to your own Meta dataset. We do not use data from Meta APIs to develop, train, or improve any Artificial Intelligence (AI) models or machine learning systems.

We do not sell user data or marketing insights to third-party data brokers or advertisers.

AI commentary: when it is turned on, the computed figures for a report (such as spend, cost per lead, new and qualified leads, won deals and response time, and their change from a usual day) are sent to Anthropic, our AI provider, to write a short summary of what changed. Reportagram calculates every number; the AI only writes the wording. For this summary, campaign names and personal data are not sent. When you ask a question in the thread under a report, your question and that report's figures are sent to Anthropic to write the answer, including the campaign and ad names, ad links, and the names of the sales managers and lead sources the report shows. Anthropic processes this data on our behalf to provide the service and does not use it to train its models. Messages addressed to the bot are stored for 30 days, then their text is deleted; other messages in your channels are never stored.

Reportagram's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Data Minimization

We request read-only access to advertising insights and CRM data, and basic profile information (name and email) when required for sign-in. We ask for Meta's ads_management permission only when you turn on the Conversions API in Settings → Connections, and use it only to send conversion events to the Meta dataset you pick. We never create, edit or pause your ads, and never change campaigns, budgets or spend.

Access Revocation

You can disconnect any source at any time in Reportagram's settings. You can also revoke Reportagram's access to your Meta data in the "Apps and Websites" settings of your Facebook profile, remove the Reportagram app from your amoCRM, Bitrix24 or HubSpot account, and remove the bot from your Telegram chats or Slack workspace.

Messenger Disclosure

Reports, AI commentary and answers are delivered only to the channels you connect: Telegram, Slack or email. Other channels, such as WhatsApp, may be added later and are used only when you enable them. Data from Slack is used only to deliver reports and answer questions in your workspace, and is never used to train AI models.

Meta Lead Ads and Conversions

Sales by ad (when you turn it on): for lead IDs already in your own CRM, we read only the ad, the form and the time of each Meta lead (ad_id, form_id, created_time) through Meta's lead access permission. For this we don't read the answers people gave in your lead forms. We store the pair of lead ID and ad ID with that CRM lead, to count leads, qualified leads and sales per ad for your reports. We do not share it with anyone.

Sending results to Meta (Conversions API, when you turn it on): you pick one of your own Meta datasets, and we send it the stages your Meta form leads reach in your CRM, such as contacted, qualified or won. Each event carries only the Meta lead ID, the CRM stage and the time it happened: no names, emails or phone numbers. Meta uses these events to show which ads bring customers and to optimise delivery for you. Nothing is sent until you turn it on. Press "Stop sending" in Settings → Connections, or remove the Meta connection, and sending ends.

Instant lead alerts (when you turn them on): when someone submits one of your lead forms, we read their answers (such as name and phone number) through Meta's lead access permission, to post the new lead to the chat you choose within seconds. We don't keep the answers after the message is sent.

Third-Party Stack

We use the following providers to run Reportagram. Each processes data only to deliver the service: Supabase (database and authentication), Vercel (hosting), Stripe and Lemon Squeezy (payments), Resend (email delivery), Upstash (report scheduling), Anthropic (AI commentary and answers), PostHog (product analytics) and Sentry (error monitoring). Data you connect from Meta, Google, amoCRM, Bitrix24 and HubSpot is read from those platforms with your permission, and is never sold or shared with data brokers or advertisers.

Data Retention and Deletion

We keep data only as long as you use Reportagram. The text of messages to the bot is deleted after 30 days. Your report history, CRM lead records and lead-to-ad pairs are kept while your account is active and are deleted with it. You can delete your account and all its data in the dashboard, or by emailing support@reportagram.com.

Security

We apply standard security practices to protect stored tokens and report configurations. Access is restricted to authorized systems.

Contact

Questions about this policy? Contact support@reportagram.com.