Privacy Policy

DM Hero Privacy Policy

DM HERO sp. z o.o., ul. Twarda 18, 00-105 Warszawa

Last updated: 21 November 2026

1. Who we are

The controller of the personal data described in this policy is DM HERO spółka z ograniczoną odpowiedzialnością, with its registered office in Warsaw, ul. Twarda 18, 00-105 Warszawa, Poland, entered in the Register of Entrepreneurs of the National Court Register under KRS number 0001241535, tax ID (NIP) 5253090444, REGON 544773198 (DM Hero, we, us).

DM Hero is a tool for running sales conversations in Instagram direct messages. It includes the web application, the Chrome browser extension, the developer API and the dmhero.ai website (together: the Service).

For any matter concerning personal data, you can write to contact@dmhero.ai or to the postal address given above.

2. Who this policy covers and the role we act in

This policy covers several groups of people. Depending on whose data we process, we act either as a controller or as a processor acting on our customer's instructions.

  • We process the data of our customers and the people using their accounts, relating to the account, payments, support and security, as a controller (section 3).
  • We process the data of the people our customers contact (leads, people they talk to on Instagram, people commenting on the customer's posts and people invited to meetings) on behalf of the customer, who is their controller (section 4).
  • We process data from public Instagram profiles within the lead discovery feature as a controller (section 5).
  • We describe the data of visitors to the dmhero.ai website in section 10.
  • The data of people who join our affiliate program is described in section 17 of the Affiliate Program Terms.

Meta Platforms Ireland Limited, the operator of Instagram, is not our processor. It acts as a separate controller of its users' data, on the terms described in its own privacy policy.

If you are talking on Instagram with a business that uses DM Hero and you want to exercise your rights, contact that business first, because it decides how your data is used on its account. If you write to us, we will pass your request on to that business and help it handle the request. Section 6.5 explains how AI tools may be used in such conversations.

This policy does not cover the services of other companies that you may reach from DM Hero, such as Instagram, Google or Stripe. Those companies are responsible for the data you give them, on the terms described in their own privacy policies.

3. Our customers' data

3.1 What data we process

  • Account and sign-in. You sign in with your Google account. Google gives us your email address, your name or display name and your profile photo. You do not set a separate password with us.
  • Connected Instagram account. You connect your account through the official Instagram business login. We then receive basic information about the account and an access token, which we store in encrypted form. With the consent you give on the Instagram screen, we get access to the account's profile, its direct messages and the comments under its posts, to the extent needed for the features you use. We do not publish posts or stories on your behalf. We never see your Instagram password.
  • Payments. Payments are handled by Stripe. You enter your card details directly in the Stripe form and they do not reach us. We store the data needed for billing, such as your plan, payment status and purchase history.
  • Acceptance of the Terms. When you accept the Terms and this policy, we record the version of the documents, the time of acceptance, your IP address and browser data. This record is evidence of the terms on which we concluded the agreement.
  • Setup answers. When you set up your account, we may ask how you heard about DM Hero and what you sell. Answering is optional.
  • How you found us. When you create an account, we record how you found us: the dmhero.ai page your visit started on, the type of site or app that sent you to us (for example a search engine, an AI assistant, a social network or one of our partners; never its full address), the campaign tags from your link, if it had any, and the referral code, if you used one. We do this to know which pages, channels and campaigns bring us customers (legitimate interest, Art. 6(1)(f) GDPR). We do not use cookies for this and keep it with your account until the account is deleted.
  • Use of the Service. Information about how you use the Service, for example the number of messages sent, AI units and tokens used, and the state of your limits. We do not use third-party analytics or advertising tools in the application.
  • Correspondence. When you write to us, we process your email address and the content of your message to reply and deal with the matter.
  • Support chat. If you choose a support chat while setting up your account, we store the messaging app you pick (WhatsApp, Slack or Telegram) and your contact: a phone number or an email address. We use it to add you to a chat with our team, help you finish setting up and answer your questions. We also process the content of the messages in that chat. Giving the contact is voluntary.
  • Technical and security data. IP address, browser data, server logs, error reports and the account change log, which help us keep the Service running and protect it from abuse.

3.2 Chrome extension

The extension runs in your browser, in your own Instagram session, and recognises the account you are signed in to. It sends the messages you schedule in campaigns and reports back to DM Hero on how the sending is going. If you turn on that feature, it can also add new followers of your account to your leads. It does not read your browsing history or your Instagram password. You can uninstall it at any time.

3.3 Data from Google services

Signing in with Google is described in section 3.1. This section covers Google Calendar, which you can connect in Settings, under Integrations, so that the AI Setter can propose meeting times to the people you talk to and book them in your calendar. Connecting it is optional. Before you continue to Google, the application shows what we do with your calendar.

What we access. We ask Google only for the following permissions and use them only as described:

  • the email address and ID of your Google account (the openid and email permissions): to show in Settings which account is connected, and to recognise the same account if you connect it in more than one workspace;
  • the list of your calendars (calendar.calendarlist.readonly): ID, name, time zone, whether it is your primary calendar, and your access level. It lets you choose which calendars are checked and which one meetings are booked into, and lets us set your time zone. This permission is optional; without it, we book into your primary calendar;
  • your free/busy times (calendar.freebusy) in the calendars you choose, including calendars others share with you: only the start and end times of busy periods, never titles, descriptions, locations or guests. From them we compute the free ranges in which a meeting can be proposed;
  • the events DM Hero creates in calendars you own (calendar.events.owned). On your behalf we create the event, later read that same event (status, time, the invited person's response) to see whether a meeting was moved, cancelled or declined, and delete it if the booking is withdrawn before the message confirming it reached the other person, for example when that message could not be delivered. The event contains its time and time zone, a title you set or a default one, which may contain the other person's Instagram username or first name, a description you set, that person's email address as a guest or, for a phone call, their phone number, which we set as the event's location and add to its description together with their Instagram username and a link to your conversation with them in DM Hero, reference numbers linking the event to the booking and, unless you choose phone calls, a Google Meet link. Anyone with access to event details in that calendar can see the event's details.

We do not read, store or change any other event in your calendar.

Storage and protection. The access tokens Google issues to us are stored encrypted in our database in the European Union. No API returns them, and they are never written to logs. In the same encrypted form they are also included in encrypted database backups. We also store the connected account's email address and Google account ID, the permissions granted, the list of your calendars and the time zone taken from it, so that Settings can show them and meetings are proposed in your working hours. Connecting and disconnecting the account, with its email address, is recorded in the account change log (section 3.1).

The times we offered and the data of booked meetings are stored with the conversation they belong to: the time, the invited person's email address or phone number, the Google event ID, the Google Meet link, the text of the confirmation message, and whether the meeting was moved, cancelled or declined. The invited person's address or number is also saved on their lead record. We process the invited person's data on your behalf, as a processor (section 4 and section 16 of the Terms).

Your busy times are kept only in the server's working memory, used for at most two minutes, and never stored in our database. All Google user data we store is encrypted in transit and at rest, and access to it is limited to staff who need it and are bound by confidentiality (section 11).

Sharing. We share Google user data only as needed for this feature to work, or on your instructions:

  • AI provider. To write the message that proposes a time, our AI sub-processor (Anthropic, see the list of sub-processors) receives the computed free time ranges, the time zone, the times the AI Setter has already offered and, after a booking, the meeting's date and time. It never receives the content of your calendar, calendar names, your Google account email address or tokens. Anthropic processes this data in the United States under standard contractual clauses, may not use it for its own purposes or to train models, and deletes it within the period set out in its terms (section 6.3). If you use your own Anthropic API key (section 6.2), the same data reaches Anthropic through your own account, under your own agreement with Anthropic.
  • Google. Event details are sent to Google to create the event. For a video meeting, Google sends the invitation, and any cancellation, to the invited person.
  • The person you talk to. The times we propose and the meeting confirmation reach the person you are talking to.
  • Tools you connect yourself. If you connect them, the meeting's time and status go to your CRM (HubSpot, Pipedrive, GoHighLevel) together with the lead's details, including their email address or phone number, and HubSpot, when meeting sync is on, also receives the Google Meet link; to your Slack workspace, without the email address or the link; and to your webhook endpoints, which also receive the invited person's email address. The connected Google account's email address, your calendar list, time zone and your free times are available through the DM Hero API and MCP server to whoever holds an API key of your workspace. Such a key is created by a member of the workspace, and creating it is your instruction to make this data available. Once data is passed on, you and that recipient are responsible for its further processing (section 4).
  • Providers that run DM Hero. The data is stored and processed by the hosting, database and encrypted backup providers named in the list of sub-processors, only on our behalf. Some backup providers are based in the United States, and the transfer relies on the EU-U.S. Data Privacy Framework or standard contractual clauses, as stated in the list (section 8).

Apart from this, we share Google user data with no one, except where the law requires it. The data may also be transferred as part of a merger, acquisition or sale of assets, and only after obtaining your explicit prior consent.

We do not sell this data. We do not transfer it to advertisers, data brokers or other resellers, and we do not use it for advertising or to determine creditworthiness. We do not use Google Workspace APIs, or user data obtained through them, to develop, improve or train generalized or non-personalized artificial intelligence or machine learning models, and we do not transfer that data for that purpose, whether for our own models or anyone else's.

No person at DM Hero reads this data unless you ask us to (for example in a support request), it is necessary for security (for example to investigate a bug or abuse), or the law requires it. If we want to use data from Google in a new way or for a different purpose, we will first ask you to consent to an updated policy.

Your controls and deletion. Any member of the workspace can disconnect Google Calendar at any time in Settings, under Integrations. If you do not see Google Calendar there, remove access at https://myaccount.google.com/permissions. On disconnect, we delete the tokens, release any tentatively held times and revoke our access at Google. One exception: if the same Google account is still connected in another DM Hero workspace, including one that belongs to another organisation, Google keeps a single shared grant for it. In that case we only delete the tokens in this workspace, and access at Google ends when the account is disconnected there too. If you connect a different Google account in a workspace in place of the previous one, remove DM Hero's access for the previous account on the same Google page.

Meetings already booked stay in your calendar, because they were arranged with the other person; you can delete them in Google Calendar. After you disconnect, your workspace keeps the list of your calendars and which Google account (email address and ID) was connected and with which permissions, until the workspace or your DM Hero account is deleted. Offered times and the data of booked meetings stay with the conversation until they are deleted with it, until the Instagram account's data is deleted (section 7.3), or until the workspace or DM Hero account is deleted.

When a workspace is deleted, we delete the data above, but you must remove DM Hero's access at Google yourself, on the Google page named above. When you delete your DM Hero account (section 7.4), we delete all of the data above and attempt to revoke our access at Google for every connected Google account, subject to the exception above. Change log entries about connecting and disconnecting the account are kept like other security-related data (section 9), and data may also remain in encrypted backups until they are deleted automatically.

You can also remove DM Hero's access yourself at any time, on the Google page named above. The AI Setter then stops proposing times from your calendar. We delete tokens Google no longer honours when you disconnect the calendar in Settings, or when we delete the workspace or the account. Your organisation's data export (section 7.5) includes a copy of the calendar data stored in DM Hero: the connection, bookings and offered times.

Limited Use. DM Hero'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, and to the Google Workspace API User Data and Developer Policy.

3.4 Data from Pipedrive

If you connect Pipedrive, you sign in to it and approve access on a Pipedrive screen. We then receive an access token, which we store encrypted, the ID and name of your Pipedrive user, the address and ID of your company in Pipedrive, and the scope of the permissions granted. We never see your Pipedrive password.

We use the access to Pipedrive only to run the integration you switch on. We create and update the persons, leads, deals, notes and tasks that match your leads in DM Hero, create the DM Hero fields, check whether a person is already in your Pipedrive (for example by email address or phone number), read the number of active users of your company so as to stay within its request limit, and receive notifications about deleted or merged records and completed tasks. From notifications we keep only identifiers and the type of event. When you use the DM Hero actions or panel in Pipedrive, or an automation, Pipedrive sends us the identifiers of the selected records, and we read from them only what is needed to carry out the instruction, for example the Instagram username.

We do not sell data from Pipedrive, do not use it for advertising or to train AI models, and do not share it with anyone except as needed for the integration to work. We process the data of people in your CRM on your behalf (section 4).

You can disconnect the integration in DM Hero settings or by uninstalling the DM Hero app in Pipedrive. We then stop synchronising data. We revoke the access to Pipedrive once no connection in DM Hero uses it any more. Data already sent to Pipedrive stays in your Pipedrive account, where you can delete it.

3.5 Data from Cal.com

If you connect your Cal.com account so that the AI Setter can send the people you talk to a booking link or book meetings in the conversation, you give us that account's API key. We store it encrypted and use it only for this feature.

From your Cal.com account we read its ID, username, email address and time zone, the list of event types with their settings, and the free slots of the event type you choose. We create one webhook on your account, through which Cal.com tells us when a booking is created, changed, confirmed, rejected or cancelled. We store attendee details only for bookings that come from conversations held in DM Hero. For other bookings we keep only a technical record of the event, with no attendee details. We do not read the content of other events.

When you disconnect Cal.com, we delete the API key and remove the webhook from your account. Bookings already made stay in Cal.com. You can also revoke the key at any time in your Cal.com settings. We process this data to perform our contract with you (Art. 6(1)(b) GDPR).

3.6 Where we get your data from

You give us most of the data yourself, when you set up your account and use the Service. We receive some of it from the services you connect to DM Hero: from Google (account data at sign-in and the connected calendar), from Meta (data of the connected Instagram account), from Pipedrive (data of the connected Pipedrive account, section 3.4), from Cal.com (data of the connected account, event types and bookings, section 3.5) and from Stripe (payment and subscription status).

3.7 Purposes and legal bases

  • Performance of the contract (Art. 6(1)(b) GDPR): creating and running your account, connecting Instagram and other services, providing the features of the Service, billing, handling your support requests, including in the support chat you ask for while setting up your account, and, before the contract is concluded, the demo call you book.
  • Legal obligation (Art. 6(1)(c) GDPR): keeping invoices and tax records, responding to requests from competent authorities, handling requests to exercise your rights.
  • Legitimate interest (Art. 6(1)(f) GDPR): security of the Service and abuse prevention, keeping evidence that the contract was concluded, establishing, pursuing and defending claims, statistics used to develop the Service, learning which pages, channels and campaigns bring us customers (section 3.1), informing you about changes to the Service, and settling our affiliate program when you buy with a referral code (section 3.8).
  • Consent (Art. 6(1)(a) GDPR): where it is required, for example for marketing messages sent by electronic means. You can withdraw your consent at any time.

Providing data is voluntary, but without account data and a connected Instagram account we cannot provide the Service.

We send messages about the contract, payments, changes to the Service and security to your account email address, because you need them to use the Service. We send marketing information, including about new features, only with your consent.

3.8 Buying with a referral code

If you enter a code from our affiliate program when you buy a subscription, we record whose code it is and, based on your payment data from Stripe, calculate a commission for the person who referred you (the referrer). Before we pay the commission, we check account and payment data, our message inbox, call bookings and email and, where needed, public business registers to see whether the referral counts: whether you were already our customer, whether you were in touch with us about DM Hero in the 30 days before you used the code, and whether the code belongs to you or to a person or company connected with you. We hold the commission on a payment that is subject to your open complaint or chargeback until it is closed.

From the moment you use the code, the number of referred clients in the referrer's dashboard goes up by one. From your first payment they also see, next to each commission, your number (for example “Client 1”), the plan you chose when you bought with the code, the month of the payment and the amount and status of the commission, including any reduction after a refund or chargeback. In payout statements we give them the dates of your payments and, at their request, the net amounts and which payment a deduction concerns and when the refund, correction or chargeback happened. If the referral does not count, we tell them which condition was not met and, for contact with us within the 30 days, its type, date and channel. If we hold a commission, we tell them why, for example that the payment is subject to a complaint or chargeback, without the details. We do not give them your name, company name, email address, Instagram profile or the content of your conversations with us.

The legal basis is our legitimate interest (Art. 6(1)(f) GDPR) in running and settling the affiliate program and preventing abuse of it.

4. Data we process on behalf of customers

When using the Service, a customer enters data about the people it contacts into the Service and receives data about them from it. The customer, as the controller, decides what data this is, for what purpose and how long it is kept. We process it only on the customer's instructions, to provide the Service, under the data processing agreement contained in the Terms. The customer is responsible for the legal basis for processing this data and for informing the people it concerns.

Depending on the features the customer uses, this may include:

  • Leads and CRM: Instagram username, name or display name, company name, information from the public profile (for example bio, website, number of followers), contact details, notes, tags, status and fields added by the customer.
  • Instagram messages: the content of messages in the connected account's conversations and the basic details of the other person made available by Instagram (username, display name, profile photo).
  • Comments: other people's comments under the connected account's posts, when the customer uses comment automations.
  • Voice messages: if the feature is turned on, we convert incoming voice messages to text and store the transcript, not the recording.
  • Files sent in conversations: materials the customer uploads to send to the people it talks to.
  • Output of AI features: suggested and sent replies, conversation summaries, notes and classifications (section 6).
  • Lead enrichment and research: on the customer's instructions, we complete a lead's record with information from their public Instagram profile and prepare a short summary of their publicly visible offer.
  • Meetings: name or display name or Instagram username, email address, phone number (when the meeting is held by phone), time zone, language and the time slot, when a meeting is booked in the customer's calendar or in its booking service, such as Cal.com, and the details of the event created in the customer's Google Calendar (a title that may contain the other person's Instagram username or first name, the Google Meet link, the response to the invitation). The other person gives the email address or phone number in the conversation. We check that the address's domain accepts mail, and an AI model may work out from that person's messages which address they meant. For a video meeting in Google Calendar, Google sends the invitation to the address given in the conversation. When the AI Setter sends a Cal.com link, we fill in the person's name and, if we know it, their email address, and Cal.com itself sends the person the meeting confirmation and reminders. The customer is responsible for having a basis to send the invitation.

On the customer's instructions, we pass this data to services the customer connects itself, for example its CRM (such as HubSpot or Pipedrive), messaging tool, calendar, its own webhooks or tools using the API. When the customer sets up an integration that way, data about people also reaches DM Hero from its CRM, for example when it adds a person to a campaign from Pipedrive, and we process it on the same terms. The customer and the providers of those services are responsible for how those services process the data, and data already passed on stays with them even after it is deleted in DM Hero.

The customer can correct, export or delete the data on its account at any time. We also help the customer handle the rights of the people the data concerns: if we receive such a request directly, we will pass it on to the customer and, where needed, help fulfil it.

We do not sell data processed on behalf of customers and do not use it to train AI models (section 6.3). Publicly available information about Instagram profiles that we obtain while providing the Service may feed the database described in section 5, and we use the fact that a campaign message was sent recently to limit repeated contact (section 5.3). To that extent, and for the security of the Service and for establishing, pursuing or defending claims, we act as a controller, on the basis of legitimate interest (Art. 6(1)(f) GDPR), and you can object to such processing (section 7.1).

5. Lead discovery: information for people whose public profiles we process

This section is mainly for people who do not use DM Hero. If you run a public Instagram profile, it may have entered our database when someone searched in DM Hero for businesses or creators they want to contact for business. For this processing, DM Hero is the controller. You can object to it at any time (section 5.6).

5.1 What data we process

We process only information that is publicly available on Instagram: profile information, such as username, display name, bio, category, website and basic statistics (for example the number of followers), the captions of recent posts, and public relationships between accounts, for example who follows whom and who liked a given account's posts.

We do not store photos or videos, content from private accounts, direct messages or comments. We do not deliberately collect contact details or special categories of data, such as information about health, beliefs or religion.

5.2 Where we get this data from

We do not receive this data from you or through Meta's interfaces. We obtain it from third-party providers of publicly available Instagram data, named on the list of sub-processors, when a profile appears in a search run by a DM Hero customer. Once a profile has been fetched, we store it in a shared database and reuse it instead of fetching it again. The database does not record who searched for what.

5.3 Purpose and legal basis

We process this data to help customers find business and creator accounts that match their offer. The legal basis is legitimate interest (Art. 6(1)(f) GDPR): ours, in providing a service for finding business contacts, and that of our customers, who are looking for people to offer their products or services to. We consider that your rights and freedoms do not override these interests, because we use only information you have made public yourself, we show customers a limited part of it, and you can object at any time.

We also take care that the same person does not receive messages from many businesses using DM Hero within a short time.

5.4 Who receives this data

The customer whose search reached your profile receives a limited set of data, including your username, basic statistics, the beginning of your bio, your category and how your profile was found. On that customer's instructions, an AI model may also assess whether the profile matches the description of its ideal customer, and only that customer sees the result.

From the moment it receives the results, the customer is the controller of its copy and is itself responsible for how it uses it, including for informing you about the processing under Art. 14 GDPR. The data is also processed by our technical service providers, AI model providers and data providers.

5.5 How long

We keep the data for as long as it is needed to provide the lead discovery feature. We delete it earlier if you object or ask for it to be deleted.

5.6 Objection and your rights

You can object to the processing or ask for your data to be deleted at any time. We treat an objection as a request for deletion: after verification, we delete your profile and the data linked to it from our database. You can also ask what data we hold about you and receive a copy of it free of charge.

Write to contact@dmhero.ai with the subject "Lead discovery" and give your Instagram username. We will ask you for a short confirmation that the account is yours, so that nobody else can act on your behalf.

Deletion on our side does not cover copies a customer has already moved to its CRM, including the CRM in DM Hero. In that case we will help you contact that customer. We describe your other rights, including the right to lodge a complaint with the President of the Personal Data Protection Office (UODO), in section 7.

5.7 Why we do not inform each person individually

We usually do not have your contact details and deliberately do not collect them. Informing each person individually would require obtaining them or sending an unsolicited message, which would intrude further on your privacy and involve a disproportionate effort. That is why, in line with Art. 14(5)(b) GDPR, we provide this information in this publicly available policy.

Lead discovery is for finding business and creator accounts, not minors, and if we learn that a profile belongs to a minor, we will delete it without delay.

6. Artificial intelligence

6.1 What we use AI for

The Service uses artificial intelligence models from third-party providers, named on the list of sub-processors: text features use Anthropic's Claude models, and voice messages are converted to text by ElevenLabs. DM Hero does not generate speech and does not clone voices. AI helps suggest replies in conversations or, if the customer sets it up that way, send them automatically (AI Setter), summarise conversations and recognise the type of a reply, personalise messages, summarise a lead's offer, assess how well a profile matches the ideal customer description, and configure the account.

6.2 What data reaches AI providers

A model receives only the data needed for the task at hand, for example the latest messages in a conversation and basic details of the other person, the customer's information about its offer and business, or publicly available information about a lead's profile or website. When the AI Setter proposes or books a time in a connected Google Calendar, the model receives only the computed free time ranges, the time zone, and the times it has itself proposed or booked, never the content of the calendar (section 3.3). We store the models' output on the account of the customer it serves. If a customer uses its own key for Anthropic models, requests from AI Setter, the test chat, insights, and reply suggestions and reply classification in the inbox go through its own Anthropic account, under its own agreement with that provider.

When AI helps configure the account (AI setup), the model receives the text of the website the customer points to, the username, display name, bio and post captions of the customer's Instagram account, the customer's description of its business, its answers and the text of the files it adds. We open the files in the customer's browser and send only their text, without file names and without the email addresses, phone numbers and links we recognise. We do not store the full text of the files in our database; we keep only short notes taken from them (single sentences that may repeat a sentence from a file) and the draft we build from them (section 9). AI setup always runs on our Anthropic account, even when the customer uses its own key.

6.3 No model training

We do not use data from the Service to train AI models, either our own or anyone else's. AI providers process the data as our processors, under contracts, may not use it for their own purposes (except with the customer's own key, section 6.2), and may keep it for the period set out in their terms. For each provider on the list of sub-processors, we state whether it uses data to train models. In particular, we do not use Google Workspace APIs, or user data obtained through them, to develop, improve or train generalized or non-personalized artificial intelligence or machine learning models, and we do not transfer that data for that purpose.

6.4 The customer's role

The customer decides whether and how to use the AI features. AI Setter is off by default, can work in suggestion mode or in automatic mode, and the customer can take over a conversation at any time. AI output may be inaccurate, so the customer should check it. The customer is responsible for how it uses these features, including its information and transparency obligations towards the people it talks to and, to the extent they apply, the obligations of a deployer under Regulation (EU) 2024/1689 (the AI Act), in line with the Terms.

6.5 If you are talking with a business that uses DM Hero

Replies in a conversation with a business that uses DM Hero may be prepared or sent with the help of AI tools that the business has configured itself. That business decides whether and how it uses AI and is the controller of your data, so direct any questions about this to that business. If you write to us, we will pass your matter on to that business.

6.6 Automated assessments

Some features assess or describe people automatically, for example the ideal customer match assessment or the classification of replies. They help the customer organise its work and do not lead to decisions that produce legal effects concerning anyone or similarly significantly affect them within the meaning of Art. 22 GDPR: the customer decides whom to write to and what to write.

7. Your rights and data deletion

7.1 Right to object

You have the right to object at any time to the processing of your data based on legitimate interest, on grounds relating to your particular situation, including profiling. This applies in particular to lead discovery (section 5). You can always object to processing for direct marketing, without giving a reason. You can send your objection to contact@dmhero.ai.

7.2 Other rights

Under the conditions set out in the GDPR, you have the rights listed below. You can exercise some of them yourself in your account settings, for example exporting or deleting your account data, and ask us for the rest by email. You have the right to:

  • access your data and receive a copy of it;
  • have inaccurate or incomplete data corrected;
  • have your data deleted;
  • restrict processing;
  • receive the data you have provided to us in a portable format (data portability);
  • withdraw your consent at any time, where processing is based on consent, without affecting the lawfulness of processing before its withdrawal;
  • lodge a complaint with the President of the Personal Data Protection Office (UODO, ul. Stawki 2, 00-193 Warszawa, uodo.gov.pl) or with the data protection authority in the country where you live or work.

7.3 Data deletion through Instagram

You can disconnect your Instagram account or remove the DM Hero app in your Instagram settings at any time. When you remove the app, Meta will send us a data deletion request, and we will delete the data that comes from that account, including conversations and messages, except data we keep for as long as it is needed for the reasons described in section 9, and we will confirm the deletion. Data you have added to your workspace, such as leads and campaigns, is deleted together with your DM Hero account (section 7.4).

7.4 Deleting your DM Hero account

You can delete your account in the account settings in the application or by writing to contact@dmhero.ai. We then delete the account and your organisation's data, and the subscription ends. We keep only what the law requires, and data needed to keep the Service secure and to protect against claims, for the reasons described in section 9. The Terms describe what this means for payments and tokens.

When you delete your account, we also attempt to revoke DM Hero's access to every connected Google Calendar, subject to the exception in section 3.3. You can check this at https://myaccount.google.com/permissions. We remove the webhook we created on your Cal.com account ourselves. Meetings already booked in connected calendars are not cancelled. Before deleting your account, also disconnect any integrations you have set up on the side of other services, for example in your Calendly account, and uninstall the DM Hero app in Pipedrive if you use it.

7.5 Data export

You can download an export of your organisation's data in your account settings. If you need a copy of data the export does not include, write to us.

7.6 If you are not our customer

  • If your public profile was included in lead discovery, see section 5.6.
  • If you are talking with a business that uses DM Hero, contact that business, and we will help (section 2).
  • For anything else, write to contact@dmhero.ai.

7.7 How we respond

We respond to requests without undue delay and within one month at the latest. For complex matters, we may extend this period by a further two months, and we will tell you so within the first month. If we have doubts about your identity, we will ask for additional information. Exercising your rights is free of charge.

8. Recipients of data and transfers outside the EEA

We use service providers, for example for hosting, databases, AI models and payments, who process data on our behalf under data processing agreements and may not use it for their own purposes. We give advance notice of planned changes to the providers that process customer data, in line with the Terms. We publish the current list in a separate document: List of sub-processors. For each provider we state what we use it for, where it processes data, on what basis data is transferred outside the EEA, and whether it uses data to train models.

They include providers of hosting and databases, website protection and backups, error monitoring, website analytics, AI models, speech-to-text, publicly available Instagram data, payments, and our own email, calendar and team messaging.

Data may also be received by:

  • Meta (Instagram), through which messages and comments pass, as a separate controller;
  • Stripe, for its own legal obligations, such as fraud prevention and tax obligations, as a separate controller;
  • WhatsApp or Telegram, if you choose one of them for the support chat, as a separate controller;
  • services the customer connects to its account itself, for example Google Calendar, Pipedrive or Cal.com (sections 3.3 to 3.5 and section 4);
  • DM Hero customers, to the extent described in section 5.4;
  • the person who referred you in our affiliate program, to the extent described in section 3.8;
  • our accounting service providers, as regards billing documents;
  • courts and public authorities, where the law requires it.

We keep the database and application servers in the European Union. Some providers are based or process data outside the European Economic Area, mainly in the United States. Such transfers take place on the basis of a European Commission decision finding an adequate level of protection (the EU-U.S. Data Privacy Framework) or standard contractual clauses adopted by the European Commission, as stated for each provider on the list. The referrer (section 3.8) may live or be established outside the European Economic Area. If the transfer of the information in section 3.8 to them is not covered by a European Commission adequacy decision, we transfer it under standard contractual clauses adopted by the European Commission, which form part of the Affiliate Program Terms. You can send us requests and complaints about how the referrer uses this information, and we will forward them to the referrer. You can obtain a copy of the safeguards by writing to us.

We do not sell data, do not share it with advertisers and do not show ads.

9. How long we keep data

We keep data for as long as it is needed for the purpose for which we collected it, and then we delete or anonymise it. We keep it longer only where the law requires it or where it is needed to establish, pursue or defend claims, until those claims become time-barred. In particular:

  • account data, settings and the record of acceptance of the Terms: for as long as you use the Service, until the account is deleted;
  • subscription data in DM Hero, such as plan, payment status and purchase history, and AI unit and token usage: until the account is deleted;
  • invoices and billing records: for the period required by tax and accounting law, as a rule 5 years from the end of the year in which the tax payment deadline passed;
  • data on a purchase with a referral code (Stripe customer, subscription and invoice identifiers, plan, payment dates and amounts, and the result of the referral check) and the commissions on it: for the period required by tax and accounting law, because they document commission payouts, or, where no commission was earned, until claims relating to the program are time-barred; they also stay after the account is deleted, and the referrer still sees the commissions in their dashboard;
  • data processed on behalf of a customer (leads, conversations, transcripts, comments, notes, lead research results, bookings, offered meeting times): until the customer deletes it, the Instagram account data is deleted, or the DM Hero account is deleted;
  • Google Calendar access tokens: until the calendar is disconnected or the workspace or account is deleted; busy times from Google Calendar: used for at most two minutes, kept only in the server's working memory, never stored in our database;
  • data of the connected Google account (email address, ID, permissions), the calendar list and time zone: until the workspace or the DM Hero account is deleted, also after the calendar is disconnected;
  • the access token and settings of the Pipedrive integration: until the integration is disconnected or the account is deleted; identifiers and event types from Pipedrive notifications: for as long as they are needed to run the integration and keep the Service secure;
  • the Cal.com API key: until Cal.com is disconnected or the account is deleted;
  • lead discovery search results and match assessments saved on the customer's account: until the account is deleted;
  • AI setup data (the domain, the list of pages read and the languages the website is available in, the customer's description and answers, the draft and the short notes it was built from, including those from files): until the account is deleted or the data is deleted through Instagram (section 7.3); of the files themselves we keep only information about them, such as their kind, the number of pages and characters and the recognised document type and language;
  • the text of files added in AI setup: only in server memory while it is being read, for at most 10 minutes; we do not keep the full text of websites, posts or files read in AI setup, and file names stay only in the customer's browser;
  • public profiles in the shared lead discovery database: as set out in section 5.5;
  • message content passed to webhooks, when the customer turns this on: we delete it from the delivery queue 7 days after delivery is complete;
  • server logs, error reports, performance measurements and records of events detected by the website's security measures: about 30 days;
  • analytics data from the dmhero.ai website (PostHog): 12 months;
  • event logs and security-related data: for as long as they are needed to keep the Service secure and to defend against claims;
  • inputs and outputs held by AI providers: for the period set out in their terms (section 6.3);
  • correspondence: until the matter is closed, and after that to the extent needed to defend against claims;
  • support chat: the contact until the account is deleted, and the messages like correspondence;
  • demo call bookings: until the call, and after that for as long as we are discussing working together with you;
  • backups: they are encrypted and deleted automatically when their rotation period ends.

After your subscription expires, we keep your data so that you can come back to your account. We may delete an account whose subscription expired at least 12 months earlier, after notifying you by email at least 30 days in advance, in line with the Terms.

10. The dmhero.ai website and cookies

The dmhero.ai website shows no ads. The only form on it that sends us data is the affiliate program sign-up; we process the data from it as described in section 17 of the Affiliate Program Terms. Every request passes through our hosting and website protection providers, who process your IP address and basic technical data to deliver and secure the website (Art. 6(1)(f) GDPR). On the same basis, we report website server errors to our error monitoring provider. You book a demo call through Calendly; we use the data you give there to hold the call. When you click a link to the DM Hero application, we add to it the dmhero.ai page your visit started on and the type of site that sent you to us (section 3.1). We do not store them in cookies or anywhere else in your browser.

Without your consent, we use only cookies and similar technologies that are strictly necessary for the website and the application to work: keeping you signed in, remembering your choices (for example your language, theme, plan and answer in the cookie banner), and protecting against bots and abuse. They are not used for analytics or advertising.

With your consent (Art. 6(1)(a) GDPR), the following also run on the dmhero.ai website:

  • PostHog, an analytics tool: it stores a random identifier in your browser and shows us where visitors come to the website from, which pages they view, where they click, where they rest the cursor and how far they scroll. In doing so, it processes your IP address, the approximate location derived from it, and data about your browser and device. It does not record sessions or what you type into fields;
  • Sentry: it reports website errors that occur in your browser and measures how fast the website runs;
  • campaign tags (for example utm_source, gclid, fbclid) from the link that brought you to the website: we keep them until you close the tab and add them to links to the DM Hero application and to Calendly, so we know which campaign brought a customer.

Data from PostHog and Sentry is stored in the European Union, and we give the retention periods in section 9. We do not use analytics tools in the application.

You can withdraw your consent at any time under “Cookie settings” in the website footer. We will then delete the data these features stored in your browser. We remember your answer for 6 months, then we ask again. You can also block and delete cookies in your browser settings, but some features may then not work properly.

11. Security

We use appropriate technical and organisational measures to protect data. All traffic to our services is encrypted, we store access tokens and keys in encrypted form, and our team's access to data is limited to what is needed for their work and requires a second sign-in factor, while reading conversation content requires a justification and is logged. Backups are encrypted. People with access to data are bound by confidentiality, and we choose providers taking into account the security measures they use.

If a personal data breach occurs that may put you at risk, we will report it to the supervisory authority and, where the law requires it, we will also inform you. If you notice a security problem, write to contact@dmhero.ai with the subject "Security".

12. Children

The Service is intended for businesses and adults. We do not knowingly collect data from people under 18. If we learn that we are processing a child's data without an appropriate legal basis, we will delete it. A parent or guardian can write to contact@dmhero.ai.

13. Changes to this policy

We may update this policy, for example when the features of the Service or the law change. We will notify active customers of material changes by email or by a notice in the application (for example, in a window after you sign in) at least 14 days before they take effect, and we will update the date at the top of this page. We announce changes to the list of sub-processors in that document and notify customers of them in line with the Terms. Previous versions of this policy are available on request.

14. Contact

  • Email: contact@dmhero.ai
  • Address: DM HERO sp. z o.o., ul. Twarda 18, 00-105 Warszawa, Poland
  • KRS 0001241535, NIP 5253090444, REGON 544773198