Comment DM Automation Privacy Policy
Version of 16 November 2026
A Polish version is available: Polska wersja. This is a translation of the Polish original. In case of any discrepancy, the Polish version prevails. This does not limit any rights you have under mandatory law.
This policy explains how we process personal data in connection with the Comment DM Automation service - a tool that automatically responds to comments containing a keyword under posts on Instagram and on Facebook Pages: it sends the author of the comment one private message and, optionally, publishes one reply under the comment. The account owner can also choose that the first message contains only a button, and we send the announced content only after the button is clicked.
If you came here from a link in a message you received after commenting on a post, the most important information is in section 3.
Contents: 1. Controller · 2. Whose data we process · 3. People who comment · 4. Data we process · 5. Purposes and legal bases · 6. Source of the data · 7. Recipients · 8. Transfers outside the EEA · 9. Retention periods · 10. Your rights · 11. Disconnecting an account and deleting data · 12. Data from Meta platforms · 13. Cookies · 14. Security · 15. Automated decisions · 16. Changes to this policy
1. Controller
The Comment DM Automation service is provided, and the data controller is, Tomasz Starzyński and Piotr Starzyński, jointly running a business as a civil-law partnership (spółka cywilna) under the name KEO S.C., ul. Bursztynowa 41/32, 20-576 Lublin, Poland, partnership tax ID (NIP): 7123104545, REGON: 060330239 (hereinafter: "KEO", "we", "us").
The partners are joint controllers. They have agreed to handle all personal data matters jointly at one address: contact@commentdmautomation.com. You may exercise your rights against each of them.
Contact for personal data matters: e-mail contact@commentdmautomation.com, phone +48 514 110 411, by post: KEO S.C., ul. Bursztynowa 41/32, 20-576 Lublin, Poland.
We have not designated a data protection officer - we are not required to (Article 37 GDPR).
2. Whose data we process
- Panel users - people who have an account in the Comment DM Automation panel (employees and associates of KEO and of companies using the service - "Clients").
- People who comment - people who commented on a post on an Instagram account or a Facebook Page connected to Comment DM Automation.
- Visitors to the website commentdmautomation.com and people who e-mail us.
3. People who comment
What happened. You commented on a post on Instagram or Facebook and used a keyword that the account owner specified in the post (e.g. "LINK"). In response, Comment DM Automation sent you one automatic private message with the announced content and - if the account owner set this up - one reply under your comment. The account owner may also choose that the first message contains a short text with a button, and we send the announced content in one message only when you click the button (no later than 24 hours after the click). If you do not click, you will receive nothing more. We do not send any other messages.
Who is the controller of your data.
- If the comment was under a post of an account or Page of KEO or one of its brands (e.g. LecimyJutro.pl) - the controller is KEO (details in section 1).
- If the comment was under a post of another company (a Client that uses Comment DM Automation) - the controller is that company: it decides which comments to respond to and with what message. KEO then processes the data solely on its behalf and on its instructions, under a data processing agreement (Article 28 GDPR). You can recognise the company by the account that sent you the message; its details and privacy policy may be given in the message footer. You can contact that company or us - we will pass your request on to the company and help fulfil it.
What data and where from. The identifier of your profile assigned by Meta for our app, your username or first and last name from your profile, the content and time of your comment, and information about the reply sent (and, if the message had a button, whether and when it was clicked and the identifier of your profile in messaging). We receive this data from Meta Platforms Ireland Limited through the official Instagram and Facebook interface - not from you directly. Details in sections 4 and 6.
Why and on what legal basis. To respond to your request expressed with the keyword. Where KEO is the controller, the legal basis is our legitimate interest (Article 6(1)(f) GDPR): to respond to a person who publicly asked for the announced information. The message contains only that information - no other commercial content. Where the Client is the controller, the Client specifies the legal basis.
How long. We anonymise the content of your comment and your name after the period set by the account owner (90 days by default, 365 days at most). We delete your profile identifier and the content of the message sent after the same period, but not earlier than 38 days after the comment (that is how long we need to avoid sending you a second message). Details in section 9.
Who else sees the data. The account owner (in the panel, only in its own workspace), our technical providers (section 7) and Meta, through which we send the message.
Right to object. You may object to the processing of your data at any time (Article 21 GDPR). Write to contact@commentdmautomation.com or to the company whose post you commented on. After you object, we add you to the exclusion list (that company's automations will no longer respond to you, even if a message was already scheduled) and anonymise your data. Only your profile identifier and name remain on the list, so that the exclusion works.
Your other rights. Access to your data, rectification, erasure, restriction of processing and a complaint to the President of the Personal Data Protection Office (UODO) - section 10. Deletion instructions: Data deletion.
How we inform you. The account owner chooses the method: a permanent link to information about data in the account profile (the bio on Instagram, the Page information on Facebook) or a short footer in the private message ("Info about your data", or "Info o Twoich danych" in Polish, with a link to this part of the policy or to the account owner's own policy). The footer is optional and off by default.
Meta. Meta Platforms Ireland Limited is a separate controller of the data processed in Instagram and Facebook, under its own rules: https://privacycenter.instagram.com/policy and https://www.facebook.com/privacy/policy. As regards Page statistics (Page Insights), the owner of a Facebook Page is a joint controller with Meta on the terms described by Meta: https://www.facebook.com/legal/terms/page_controller_addendum.
4. Data we process
Panel users
- e-mail address, password (stored only as a cryptographic hash by the authentication provider),
- first and last name (if you provide them),
- second-factor login data (authenticator app - TOTP),
- the workspaces you belong to and your role,
- the configuration change log: who made which change and when (without the content of comments),
- technical session data: login dates, IP address and browser information recorded by the authentication provider.
People who comment
- the identifier of your profile assigned by Meta for our app (an "app-scoped" identifier - it is not a login, phone number or e-mail address),
- your Instagram username or the first and last name shown in your Facebook profile,
- the content of the comment, the time it was added, the comment and post identifiers,
- information whether the comment contained the keyword and whether we sent a private message or a public reply (the content of the message sent, time, result, any Meta error description),
- if the message had a button: the time of the click and the identifier of your profile in messaging assigned by Meta (needed to send you the content after the click) - without the content of any messages,
- if you object to the processing or the account owner decides not to respond to you - an entry on the exclusion list (profile identifier, name, date and source of the entry).
We do not collect the profile photo of people who comment, their list of friends or followers, or their contact details. We do not hold conversations and we do not display the company's message inbox. Messages that someone sends to the company's account (Messenger, Instagram Direct) are not stored by us - we discard them before storage. The only exception is information about a click on our button: from it we store only the sender's identifier, the time and our button identifier.
Website visitors
- technical data recorded automatically in server logs by the hosting provider (IP address, time, page address, browser information),
- data from correspondence, if you write to us.
5. Purposes and legal bases
| Purpose | Legal basis (GDPR) |
|---|---|
| Creating and maintaining a panel account, login, two-step verification | Article 6(1)(b) (contract) - where you are a party to the contract; in other cases Article 6(1)(f) - our legitimate interest in performing the contract with the Client you work for |
| Security of the service, change log, abuse detection | Article 6(1)(f) (security and accountability) |
| Automatic reply to a comment under a KEO post | Article 6(1)(f) - legitimate interest: responding to a person who asked for the information themselves by typing the keyword announced in the post; the message contains only the announced content |
| Automatic reply to a comment under a Client's post | we process on the Client's instructions (Article 28 GDPR); the legal basis is specified by the Client as the controller |
| History and statistics for the account owner | as above, depending on whose account it is |
| Exclusion list and handling your rights, including erasure requests forwarded by Meta | Article 6(1)(c) (legal obligation under Articles 12-22 GDPR) |
| Handling correspondence, establishment, exercise or defence of legal claims | Article 6(1)(f) |
| Billing, once the service becomes paid | Article 6(1)(b) and (c) (tax and accounting law) |
Providing data by a panel user is voluntary, but without an e-mail address and password the panel cannot be used. We do not collect the data of people who comment directly from them - see section 6.
6. Source of the data
We receive the data of people who comment from Meta Platforms Ireland Limited (Instagram, Facebook) through the official application programming interface (Graph API) and notifications (webhooks), only for the accounts and Pages that their owner has connected to Comment DM Automation and for which the owner has granted permissions. Data of panel users comes from them or from the person who invited them (e-mail address).
7. Recipients
The data may be received only by entities that help us provide the service, under data processing agreements:
| Entity | Role |
|---|---|
| Vercel Inc. (USA) | application hosting, server functions (Frankfurt region), job queue, logs |
| Supabase Inc. (USA) | database and authentication (Frankfurt region) |
| e-mail provider with its registered office and servers in the EU | sending invitation, password reset and technical notification e-mails (without data of people who comment) |
In addition:
- Meta Platforms Ireland Limited - the recipient of API calls: through Meta we send the private message and publish the reply under the comment. Meta processes this data as a separate controller.
- The Client - sees in the panel the comments under its posts and the history of replies sent (only in its own workspace).
- public authorities - only where required by law.
We do not sell data, and we do not share it for advertising purposes or to build profiles.
8. Transfers of data outside the European Economic Area
We run the database and application functions in the Frankfurt region (Germany). Vercel Inc. and Supabase Inc. have their registered offices in the USA and - according to their data processing agreements - may access the data from the USA or through sub-processors outside the EEA (e.g. as part of technical support and monitoring). The bases for such transfers:
- standard contractual clauses adopted by Commission Implementing Decision (EU) 2021/914, included in the Vercel and Supabase data processing agreements - the main basis,
- for Vercel Inc., additionally, European Commission Implementing Decision (EU) 2023/1795 of 10 July 2023 (EU-US Data Privacy Framework), in whose programme Vercel Inc. participates.
The e-mail provider has its registered office and servers in the EU - we do not transfer data to it outside the EEA. You can obtain a copy of the safeguards by writing to contact@commentdmautomation.com.
9. Retention periods
| Data | Period |
|---|---|
| Notifications received from Meta (containing the comment content and author data) | 14 days from receipt, then deleted automatically |
| Comment content and the author's username or first and last name | the period set by the account owner for its workspace: 90 days by default, from 7 to 365 days after the comment was added; then anonymised automatically |
| App-scoped author identifier, recipient identifier (including the messaging identifier when the button is clicked), content of the message sent, private message identifier and error descriptions of sending attempts | the same period, but not shorter than 38 days from the comment (the longest window of the "one message per person" limit - 30 days - plus 7 days in which Meta allows a reply to be sent, plus 1 day of margin); then purged automatically |
| Entry on the exclusion list | until the account owner deletes the entry - without the entry, the automation could respond to you again |
| Data of a social media account disconnected from Comment DM Automation (comments, sends, list of posts) | 30 days from disconnection, then deleted; only aggregate numbers without personal data remain |
| Access token to an Instagram account or Facebook Page | until the account is disconnected or the app is removed on Meta's side - then deleted immediately |
| Panel user account data | for as long as the account exists; we delete it no later than 30 days after a deletion request or the end of the contract with the Client |
| Configuration change log | until the end of the calendar year in which 3 years from the entry expire (limitation of claims, Article 118 of the Civil Code - Kodeks cywilny); after the user account or workspace is deleted, the entries no longer identify the person or the details of the change |
| Correspondence with Clients and complaints | 3 years from the closing of the matter, until the end of the calendar year |
| Correspondence about data subject requests (access, erasure, objection, etc.) | 3 years from the closing of the matter |
| Register of data deletion requests from Meta (confirmation code, hash of the identifier) | 3 years from closing the request; it contains no data in plain form |
| Billing data (once the service becomes paid) | 5 years from the end of the year in which the tax payment deadline expired (Article 70 § 1 and Article 86 § 1 of the Tax Ordinance - Ordynacja podatkowa) |
| Database backups | up to 5 weeks, in encrypted form |
| Server logs (hosting) | briefly, according to the hosting provider's settings |
The identifiers of our own public replies remain in the database - they are content of the account, not data of people who comment. Statistics (numbers of comments and messages sent) contain no personal data.
10. Your rights
You have the right to:
- access your data and obtain a copy of it (Article 15 GDPR),
- rectification of your data (Article 16),
- erasure of your data (Article 17),
- restriction of processing (Article 18),
- portability of data we process on the basis of a contract (Article 20) - applies to panel account data,
- object to processing based on legitimate interest (Article 21) - an objection by a person who comments results in an entry on the exclusion list (automations stop responding to them) and anonymisation of their data,
- lodge a complaint with the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych, UODO), ul. Stanisława Moniuszki 1A, 00-014 Warszawa, Poland (Article 77 GDPR).
How to exercise your rights: write to contact@commentdmautomation.com or by post to KEO's address. We will respond without undue delay, at the latest within one month (in exceptional cases this period may be extended by two months - Article 12(3) GDPR; we will inform you of this). We may ask for information needed to find the data (e.g. the profile name, a link to the comment). We search for the data of a person who comments in all workspaces. We act on an objection or an erasure request immediately, also where we process the data on behalf of a Client (the Client has instructed us to do so), and we inform the Client. We forward other requests concerning a Client's data to the Client and help fulfil them.
Detailed data deletion instructions: Data deletion.
11. Disconnecting an account and deleting data
- Disconnecting in the panel (Accounts → Disconnect): the access token is deleted immediately, the Meta notification subscription is unregistered, and after 30 days we delete the comments, sends and list of posts of that account.
- Removing the app on Meta's side: Meta notifies us automatically; we disconnect the linked accounts and delete the tokens, and we delete the accounts' data after 30 days as above.
- Data deletion request sent by Facebook: we disconnect the linked accounts and delete the tokens; Meta will show you a confirmation code, and you can check the status at
https://commentdmautomation.com/api/meta/data-deletion/status?code=CODE. If we do not find any linked account, the status is "received", and we handle the request manually within 30 days. - Deleting a panel account or a workspace: on request sent to contact@commentdmautomation.com, no later than within 30 days. Before a workspace is deleted, its owner can receive a data export.
12. How Comment DM Automation uses data from Meta platforms
This section addresses the requirements of the Meta Platform Terms (sections 3 and 4).
- What platform data we process: basic data of the connected Instagram account or Facebook Page (identifier, name, profile photo of the business account), the list of its posts (identifier, type, excerpt of the caption, thumbnail, link, date), comments under those posts (content, author, time) and the results of sending replies; the access token granted by the account owner.
- For what purpose: solely to, on behalf of the account owner, detect a comment with the keyword, send the author one private message (the Meta "Private Replies" feature - at most one message per comment, no later than 7 days after the comment), optionally publish one reply under the comment, and show the account owner the history and statistics. If the account owner chose a message with a button - after the button is clicked, to send one message with the announced content (within 24 hours of the click).
- What we do not do: we do not send messages other than those described above (any further conversation is handled by the company in its own inbox), we do not store messages sent to the company (from information about a button click we store only the sender's identifier, the time and the button identifier), we do not write to people who have not commented on a post, we do not sell or license data, we do not use it for advertising, profiling, creditworthiness assessment, employment, insurance or housing, we do not combine data of different Clients (each Client's data is in a separate workspace).
- Message limit: one private message per person within the time window set in the automation (24 hours by default, 30 days at most), even if someone comments several times. We do not respond at all to people on the exclusion list.
- Retention and deletion: as in sections 9 and 11. We store tokens encrypted and delete them immediately after the account is disconnected.
- How to request deletion of data originating from Meta: write to contact@commentdmautomation.com, send a deletion request in Facebook settings (section 11) or follow the instructions on the Data deletion page. You can submit a request whether or not you have a Comment DM Automation account.
13. Cookies
The public website commentdmautomation.com does not use cookies or analytics or advertising scripts.
The panel (the /panel and /auth paths) uses only cookies strictly necessary to provide the service you request. We do not need consent to store them (Article 399(3)(2) of the Electronic Communications Law - Prawo komunikacji elektronicznej):
| Name | Purpose | Duration | Attributes |
|---|---|---|---|
sb-ID-auth-token, where ID is the project identifier (may be split into parts .0, .1) | login session (Supabase Auth) | until logout or session expiry | HttpOnly, Secure, SameSite=Lax |
panel_przestrzen | remembering the selected workspace | 1 year | HttpOnly, Secure, SameSite=Lax, /panel path only |
meta_oauth_state | protecting the process of connecting an account with Meta against forgery (CSRF) | 10 minutes | HttpOnly, Secure, SameSite=Lax, /panel/accounts/meta path only |
When logging in in the Meta window (facebook.com), Meta's cookies and policy apply.
You can delete or block cookies in your browser settings; without the session cookie it is not possible to log in to the panel.
14. Security
Our measures include: encryption of access tokens (AES-256-GCM, with the key stored outside the database), encrypted connections (HTTPS with HSTS), mandatory two-step verification for people managing accounts, separation of Clients' data at database level (Row Level Security) with automated tests, verification of signatures of notifications from Meta, a change log, automatic deletion and anonymisation of data after the retention periods expire, encrypted backups, and an emergency switch that stops sending. We store data in the Frankfurt region (EU).
If you notice a security vulnerability, write to contact@commentdmautomation.com.
15. Automated decisions
Sending replies is automatic: if a comment contains the keyword chosen by the account owner, the system sends the message. This is not a decision producing legal effects concerning you or similarly significantly affecting you within the meaning of Article 22 GDPR, and we do not profile people who comment.
16. Changes to this policy
We update the policy when the way the service works, the list of providers or the law changes. The current version and date are always on this page. We will also inform panel users of significant changes by e-mail or in the panel.