Skip to content
DMCrew

Privacy policy

Last updated 11 November 2026

DMCrew (“we”, “us”) lets creators automate replies to messages and comments on Telegram, Instagram, Facebook Messenger and TikTok. This policy says what data we process, why, for how long, and what you can do about it.

1. Who is responsible

The service is operated by Denys Zinych, sole proprietor (jednoosobowa działalność gospodarcza) registered in Poland, NIP 5842758579, ul. Jana Heweliusza 11/811, 80-890 Gdańsk, Poland. For anything about your data write to privacy@dmcrew.io; for everything else, support@dmcrew.io. We have not appointed a data protection officer; the law does not require one for a service of this size.

Two roles. For the data of people who use DMCrew (you, your team) we are the controller. For the data of people who message your connected accounts (your audience) you are the controller and we are your processor: we handle it only on your instructions, which are the automations you set up and the replies you send. Section 9 is the summary of that processing agreement.

2. Data we process

  • Account: e-mail, name and profile picture from the sign-in provider, the workspaces you create and your role in them.
  • Connected channels: identifiers and access tokens for the Telegram bots, Instagram accounts, Facebook Pages and TikTok accounts you connect. Tokens are stored encrypted and used only to receive and send messages for you.
  • Messages and contacts: messages, comments and button taps people send to your connected accounts, with the basic profile the platform provides (name, username, avatar, follower status). We use this to run your automations and show you your inbox.
  • Automations and usage: the flows you build, run history and aggregate statistics (people reached, conversions).
  • Billing: your plan, invoices and a Stripe customer id. Card details are entered on Stripe’s pages and never stored by us.
  • Technical: IP address, browser and page in server logs and error reports, used to keep the service running and secure.
  • Support: what you write to us, so we can answer.

3. Why, and on what legal basis

  • To provide the service you signed up for, including receiving platform events, sending your replies and billing (performance of a contract, GDPR Art. 6(1)(b)).
  • To keep it secure and working: logs, error reports, abuse prevention (legitimate interest, Art. 6(1)(f)).
  • To tell you about product changes by e-mail. Every such e-mail has an unsubscribe link; e-mails about your account, invoices and security go out regardless (legitimate interest, and consent where the law asks for it).
  • To meet legal duties, for example keeping invoices for tax law (Art. 6(1)(c)).
  • Optional cookies only with your consent (Art. 6(1)(a)); see section 8.

We do not sell data, do not show advertising, and do not use message content to train AI models.

3a. AI features

DMCrew has no AI features yet. Before any ship, this policy will name the provider and what is sent to it, and you will be able to leave them off.

4. Platform data

Data received from Telegram, Meta (Instagram and Messenger) and TikTok is used only to provide DMCrew’s features to the account owner who connected the account, in line with the Telegram Bot terms, the Meta Platform Terms and TikTok’s developer terms. Disconnecting an account in Settings stops all processing for it; you can also revoke DMCrew’s access from the platform’s own settings. DMCrew is not affiliated with, endorsed by or sponsored by any of these platforms.

5. Who helps us, and where data lives

ProviderWhat forWhere
Vercelhosting and content deliveryUSA / EU
Prisma PostgresdatabaseEU (Frankfurt, eu-central-1)
WorkOSsign-in and sessionUSA
Stripepayments and invoices; card numbers never reach usUSA / EU
Sentryerror reports and a technical log of actions in the app (which action, your account id, whether it worked), never message contentUSA / EU
Resendtransactional e-mailUSA
Flowserywebsite visit analytics, only if you accept analytics cookiesEU (Poland); any transfer under Standard Contractual Clauses

Each provider processes data under its own terms and security programme. Where data leaves the EU/EEA it is covered by the EU–US Data Privacy Framework or the European Commission’s standard contractual clauses. We tell you here before adding a provider that handles your data.

6. How long we keep it

  • Account, workspace, contacts and messages: while your workspace exists.
  • After you delete an account, a workspace or your DMCrew account: gone from the live database at once, from backups within 30 days.
  • Server logs and error reports: up to 90 days.
  • Invoices: as long as tax law requires (in Poland, five years from the end of the tax year).

7. Deleting your data

You can do it yourself, at any time, without asking us:

  • One connected account: Accounts → the account’s … menu → Remove. This removes its contacts, conversations, automations and tokens.
  • A workspace: Settings → Delete workspace. Everything in it is removed. An organization’s only workspace goes with the organization: Billing → Delete organization.
  • Your whole DMCrew account: Account → Delete account. Workspaces you own alone are deleted with it.
  • By e-mail: write to privacy@dmcrew.io from your sign-in address and we delete within 30 days.

Deletion requests that reach us from a platform (for example Meta’s data-deletion callback when someone removes DMCrew from their Instagram account) are carried out the same way, without you having to do anything.

8. Cookies and browser storage

NameTypePurposeLastsCategory
wos-sessioncookiekeeps you signed insessionstrictly necessary
dmcrew-consentcookieremembers your cookie choice12 monthsstrictly necessary
sidebar_statecookieremembers whether the sidebar is collapsed1 yearfunctional
themelocal storageremembers light or dark modeuntil clearedfunctional
_fs_vidcookierecognises a returning visitor (Flowsery), only if you accept analytics2 yearsanalytics
_fs_sidcookiegroups page views into one visit (Flowsery), only if you accept analytics30 minutesanalytics
flowsery_ignorelocal storageremembers that you declined analytics, so Flowsery stays offuntil clearedstrictly necessary

None of these track you across sites. Flowsery, the only analytics tool we use, counts visits and where they came from, loads only after you accept analytics cookies and sets the two _fs_ cookies above; declining or withdrawing removes them. We name any other such tool here first. You can change your choice from the Cookie preferences link in the footer or by clearing site data.

9. For business customers: the processing agreement

When we process your audience’s data for you, these terms apply (GDPR Art. 28): we process it only to run the service as you configured it; the people with access are bound to confidentiality; we use the sub-processors in section 5 and tell you before changing them; we help you answer data subject requests and keep the security measures in section 10; we delete or return the data when you delete it or close your account; and you can verify this by asking us. A signed copy of the agreement is available on request.

10. Security

Encrypted transport (HTTPS), encrypted channel credentials at rest, per-account webhook secrets, sign-in through WorkOS with verified e-mail, and access limited to the workspace that owns the data.

11. Your rights

Under the GDPR you can ask for access, correction, deletion, restriction, a copy of your data (contacts export as CSV from the app) and object to processing based on legitimate interest. Write to privacy@dmcrew.io; we answer within a month. You can also complain to a supervisory authority; in Poland that is the President of the Personal Data Protection Office (UODO, uodo.gov.pl).

If you messaged a DMCrew customer and want your data corrected or removed, ask them: they decide what happens to it, and we help them do it. If you cannot reach them, write to us and we will pass the request on.

12. Children

DMCrew is for people aged 18 or over. We do not knowingly process data of anyone younger who signed up for the service.

13. Changes

We post changes here and update the date above. Material changes are announced by e-mail or in the app before they apply.