1. Controller and scope
MEUME DESIGN sp. z o.o.
Objazdowa 15, 43-100 Tychy, Poland
Polish tax ID (NIP): 6463008478 · Company register (KRS): 0001069341
For personal data enquiries, contact privacypolicy@meumedesign.com or write to the address above.
This policy covers MEUME CRM, listed in the Meta dashboard as MEUME CRM Test (App ID: 1454795581050149). It is MEUME DESIGN’s internal system for customer service, correspondence and orders. It covers people contacting us, customers, representatives of business customers and authorised system users.
This document concerns the CRM and its Meta integrations. Browsing and purchases through our shop are covered by the separate shop privacy policy. Staff receive separate information about the processing of employment records.
2. Data categories and sources
- Contact details: name or profile name, username, email address, telephone number and other information provided in correspondence.
- Instagram and Messenger: profile, business account, conversation, message, comment and post identifiers; profile name or picture available through the API; message and comment content, attachments or attachment URLs, timestamps and available conversation information. The scope depends on API functionality, granted permissions and interactions with our business accounts.
- Customer service and orders: company details, information needed for quotations, billing and delivery, product arrangements, contact history, case or order status, documents and staff notes relevant to customer service.
- Team accounts: user name, login, role and permissions, authentication information and records of system actions necessary for security and accountability.
- Technical data: IP address, request time, browser, session and error information, to the extent recorded by the infrastructure used.
Data comes directly from you, your company’s representative, authorised MEUME DESIGN staff and Meta services in connection with interactions with our profiles. Comments on public posts may come from publicly available sources. This integration does not give the CRM access to all private conversations in your account.
Do not send passwords, login codes or full payment card details. Health information is not needed to handle enquiries about our products.
3. Purposes and legal bases
| Purpose | GDPR legal basis |
|---|---|
| Quotations and orders | Article 6(1)(b): steps requested before entering into a contract and performance of a contract when you are a party to it. |
| Correspondence and business customers | Article 6(1)(f): our legitimate interests in responding to enquiries, maintaining continuity of service, contacting customer representatives and organising order fulfilment. |
| Legal obligations | Article 6(1)(c): applicable tax, accounting and customer protection obligations. |
| Security and team accounts | Article 6(1)(f): access control, data protection, preventing misuse and establishing the history of CRM actions. |
| Legal claims | Article 6(1)(f): establishing, exercising or defending legal claims. |
| Separate voluntary consent | Article 6(1)(a): only where we request consent for a specific additional purpose. Contacting our company does not itself constitute marketing consent. |
Providing data is voluntary, but without information necessary to respond or fulfil an order we may be unable to do so. Legally required information is necessary to fulfil the relevant obligation. Staff account information is required to grant access to the CRM.
4. Use of Meta data
The integration is used to receive, display and organise correspondence with our company, send replies, manage comments and associate a contact with a customer record or order. We use only data made available to the app by Meta within the permissions granted.
Access tokens connect business accounts to the app and are not intended for public disclosure. Connections are managed by people authorised by our company.
We do not sell data obtained through Meta APIs. We do not use conversation content to create databases for sale, advertising profiling or training general-purpose artificial intelligence models. The current app does not make decisions based solely on automated processing that produce legal or similarly significant effects on a person.
Meta also processes data within its services under its own Privacy Policy. Deleting data from the CRM does not automatically delete your Facebook or Instagram account or data independently retained by Meta.
5. Who can access data
Access is limited to authorised staff handling customers and orders according to their duties. Data may be entrusted to hosting, infrastructure, backup, email and IT support providers necessary to operate and maintain the system. Providers processing data on our behalf act under appropriate agreements.
Sending a reply to Instagram or Messenger requires sending its content and recipient identifier to Meta. Order information may be disclosed to delivery and billing service providers and advisers where needed for their services, and to authorities entitled to receive it by law.
During parallel operation of our service tools, correspondence may also be available in the company’s Bitrix24, Manychat and Meta Business Suite systems. Introducing MEUME CRM does not itself erase data from these tools. Requests concerning data processed by MEUME DESIGN may also cover those systems.
6. Transfers outside the EEA
Meta services and infrastructure or support providers may involve processing outside the European Economic Area. Choosing a European server does not, by itself, rule out such access.
Transfers require an appropriate basis under Chapter V of the GDPR: an applicable European Commission adequacy decision or appropriate safeguards, such as standard contractual clauses and supplementary measures where necessary. The EU–US Data Privacy Framework may be used only within the scope of a recipient’s valid certification. You may contact us for information about safeguards applying to a particular transfer and how to obtain a copy.
7. Retention
- Enquiries and correspondence: for the time needed to handle the matter and necessary follow-up. Afterwards, we retain only data needed to document arrangements, meet legal obligations or handle legal claims.
- Orders and billing documents: during contract performance and afterwards for applicable statutory document retention periods and as necessary for complaints and claims.
- Staff and contractor accounts: while access is authorised. Access is revoked when authorisation ends; necessary activity records may be retained for security, accountability or claims.
- Technical data: as needed to operate the service, investigate errors or incidents and maintain security.
- Data based solely on consent: until consent is withdrawn or the stated purpose ends.
Retention depends on the data category, case status, legal obligations and actual need for continued use. Unnecessary data is subject to erasure or anonymisation. Backups are used for system recovery; data marked for deletion should not return to active use after a backup is restored.
8. Your rights and data deletion
Subject to GDPR conditions, you may request access and a copy of your data, rectification, erasure, restriction of processing and portability where applicable. You may object to processing based on legitimate interests on grounds relating to your particular situation. Consent may be withdrawn at any time without affecting the lawfulness of processing before withdrawal.
Want your data removed from MEUME CRM?
Email privacypolicy@meumedesign.com
Include the profile name or contact details used in your conversation and the scope of your request. Read the full deletion instructions →
If we have reasonable doubts about your identity, we may request information necessary to verify that the request concerns your data. We do not require your Meta account password or authentication code.
We provide information on the action taken without undue delay, normally within one month of receiving the request. If a GDPR-compliant extension of up to two further months is necessary, we will inform you and explain the reasons within the first month. Where a legal obligation or the protection of legal claims prevents erasure of some data, we will explain what must be retained and why.
You may lodge a complaint with the President of the Polish Personal Data Protection Office (uodo.gov.pl) or the competent supervisory authority in your country of habitual residence, place of work or the alleged infringement.
9. Security and cookies
We use organisational and technical safeguards appropriate to the risk, including restricting permissions, protecting authentication data and encrypting connections in the online version served over HTTPS. We do not publish information that would enable administrative access.
This policy page contains no data collection form, advertising pixels or our own analytics scripts. Infrastructure providers may process technical information needed to serve the page and prevent abuse. The signed-in CRM uses necessary session mechanisms to maintain login and protect access.
10. Policy changes
We update this policy when data processing or the app’s scope changes. New integrations and processing purposes require appropriate information to be updated before they are used. The current version is available on this page.
Version date: 17 November 2026.