Privacy Policy
This policy explains what data the WhatsApper CRM application handles when a company ("Customer") installs it on its Bitrix24 account, where that data goes, how long it is kept, and how to exercise your rights. It applies to the Customer's administrators and operators and to the people who write to the Customer on WhatsApp ("contacts").
1. Roles
For the conversations between the Customer and its contacts, the Customer is the controller and Moccelin Júnior Sociedade Individual de Advocacia ("we") processes the data on the Customer's behalf, only to deliver messages between WhatsApp and the Customer's Bitrix24. For installation and account data (section 3.4), we act as controller.
2. Summary
- Messages and files pass through our server only to be delivered. The destination is the Customer's own Bitrix24.
- Files are not kept. Each file is offered to the Customer's Bitrix24 through a temporary link valid for at most 15 minutes.
- The WhatsApp connection engine keeps message records, metadata and thumbnails while the number is connected (section 3.2).
- From the Bitrix24 CRM, the app only reads phone numbers, only when a user clicks the "Check WhatsApp" button on the card, and with that user's permissions. It does not write to the CRM (section 3.6).
- Our server is located in Brazil.
- We do not sell data, do not use it for advertising and do not use conversation content to train any model.
3. What data, why, and for how long
3.1 Messages and files in transit
What: text, photos, videos, voice messages, audio, documents, fixed locations and contact cards exchanged between contacts and the Customer's operators; the contact's WhatsApp number and display name.
Why: to deliver each message to the other side (WhatsApp to Bitrix24, or Bitrix24 to WhatsApp).
How long: message text stays in our delivery queue only until it is delivered or definitively fails, and is then erased. Files are not stored: while a file is being transferred it exists only in temporary memory of the server, and the temporary link that the Customer's Bitrix24 uses to download it expires after at most 15 minutes and is revoked as soon as delivery ends. After delivery, the copy that remains is the one in the Customer's Bitrix24, under the Customer's control and Bitrix24's own policy.
Messages typed on the company's phone: what the Customer's team writes directly in the WhatsApp of the connected number (on the phone or in WhatsApp Web) is copied to that contact's conversation in Bitrix24 as a system message, so the history stays complete. This only happens in a conversation that already exists in Bitrix24. The text passes through our server and is erased after delivery, like the text of all other messages.
Reactions and missed calls: when a contact reacts to a message or makes a call that is not answered, the conversation in Bitrix24 receives a short notice (the reaction emoji, with an excerpt of the message reacted to when it still exists; or the type and time of the missed call). Calls are not recorded or answered by the application.
WhatsApp groups: only for numbers where the Customer's administrator turns on "Receive WhatsApp groups" (off by default; while it is off, group messages are discarded without their content being read). Each group becomes one conversation in the Customer's Bitrix24, with the group name, read from WhatsApp and kept on our server only in memory. The display name of the participant who wrote goes in the message text to Bitrix24 and stays in the delivery records until it is deleted with the other contact data (section 3.3). Participants' phone numbers are never stored, logged or sent to Bitrix24, and mentions of participants appear as "@participant". The group identifier (which, in older groups, contains the number of the person who created the group) is treated as the conversation identifier of section 3.3. The application does not send group phone numbers to the CRM.
View-once photos and videos, live location and polls are not downloaded or forwarded.
3.2 Data kept by the WhatsApp connection engine
To keep a number connected (as a "linked device", like WhatsApp Web), the connection engine that runs on our server keeps, in the database of that pairing, records of messages, metadata (such as chats, contacts and times) and thumbnails of images of the connected number. This happens while the number stays connected. This database is not accessible through any interface, is not copied elsewhere and is not written to logs.
How long: while the number is paired. When the connection is ended in the application ("End connection" or "Disconnect"), the WhatsApp session is logged out. Uninstalling the application stops the connection but does not unlink the number by itself: use "End connection" before uninstalling, or remove the device on the phone (WhatsApp > Linked devices). The Customer can ask us to delete this database at any time through atendimento@grmjr.com.
3.3 Delivery records
What: message identifiers, the conversation identifier (which contains the contact's WhatsApp number), the contact's display name, times and delivery status, and the Open Channel used. No message content.
Why: to avoid duplicate deliveries, to link replies to the right conversation and number, and to show the Customer's administrators which messages failed.
How long: contact data (phone number and name) is removed 30 days after the message is delivered or fails; the delivery record without contact data stays while the app is installed.
3.4 Installation and account data
- Bitrix24 access tokens (OAuth), which let the application deliver messages to the Customer's Bitrix24: kept until the application is uninstalled, then deleted.
- Bitrix24 account identification: the portal address, and the account and application identifiers stored only as an irreversible hash (SHA-256).
- Connection settings: connection name, the last digits of the connected number, an irreversible hash of the WhatsApp account identifier, the linked Open Channel, connection quota and status (active, suspended, or paused because the subscription is due).
- Administrator identification: the Bitrix24 user ID of the administrator who performs an action in the application, in short-lived signed session data.
- Installing administrator: the Bitrix24 user ID of the administrator who installed (or reinstalled) the application, so that we, as the vendor, can send them service notices through the "WhatsApper CRM" chat bot (or, if the bot is unavailable, through Bitrix24's own notifications).
- "WhatsApper CRM" chat bot: the application creates in the Customer's Bitrix24 a chat bot named "WhatsApper CRM", used only to deliver to the installing administrator our service notices (including subscription due-date reminders) and the automatic notice that a connected number has disconnected. We keep only the bot's identifier. Messages that users write to the bot are not stored: the bot only answers, at most once every 10 minutes per chat, with a short fixed note pointing to support.
- Blocked numbers list: the numbers the Customer's administrator blocks in the application, so that their messages are discarded before anything is stored. Each number is kept only as an irreversible hash (SHA-256) and its last 4 digits (to show on screen), while it stays on the list.
- Vendor notification history: date and time, text, optional link and result of each notice we sent to the Customer's administrator.
- Subscription and payment orders: the subscription status (trial start, paid due date, complimentary) and each payment order placed in the application screen: type, number of WhatsApp numbers, amounts in US dollars and in reais, the PTAX rate used and its date, the order identifier in the Pix, when the payment was reported, and the result of our check with the bank (confirmed or declined, with the reason shown to the Customer). We never receive or store bank details: the Pix is paid in the Customer's own banking app.
How long: tokens, the installing administrator's ID and the bot identifier until uninstallation, then deleted (Bitrix24 removes the bot when the application is uninstalled). The vendor notification history and the payment orders are kept with the installation record (payment orders also for as long as tax and accounting rules require). The installation record (portal address, hashes, quota and status) is kept after uninstallation so that a reinstallation keeps the same settings, and is deleted on request.
3.5 Technical logs
What: times, types of events, error codes and internal identifiers. Logs do not contain message content, files, full phone numbers, QR codes or tokens.
Why: to operate the service, investigate failures and protect it against abuse.
How long: at least 3 days, and no longer than their rotation by size (about 30 MB per service); they never contain message content.
3.6 CRM, automation and campaigns
With the permissions for the CRM (read-only), SMS sending, automation and card buttons, the app registers in the Customer's Bitrix24: one "SMS" provider for each connected number (with its nickname and the last 4 digits of the number), two automation rules ("WhatsApp: send message" and "WhatsApp: check number") and a "Check WhatsApp" button on the card of leads, contacts, companies and deals. The app never deletes anything in Bitrix24; when a number is disconnected, its provider shows "(disconnected)" and the number leaves the automation rule's list.
Reading the CRM: only the phone numbers of the open record (on a deal, those of the contact and company linked to it), only when a user clicks "Check WhatsApp", and with that user's permissions. The app never reads the CRM with its own permissions, never sees what the user could not see and does not write to the CRM. The phone numbers read are not stored; the screen shows only the last 4 digits.
WhatsApp check: to know whether a number has WhatsApp (on the card button, in the "WhatsApp: check number" rule and before each message started from the CRM), the app asks WhatsApp through the connected number. The result (has it or not) is stored only with an irreversible hash (SHA-256) of the number, never the number, for at most 30 days.
Messages started from the CRM: when a user sends from the card, an automation rule runs or a campaign uses the connected number, Bitrix24 sends us the destination number, the text and, for the rule, the link to a file. These data stay in our queue only until sending ends (at most 72 hours) and are then deleted. The request record, without number, text or link (with a hash of the number, the Bitrix24 ID of the user who asked and the status), is deleted 30 days later. The sending status goes back to Bitrix24.
File by link (automation rule): the file is downloaded from the given link only at the time of sending and goes straight to WhatsApp, without being stored. Only https links to public internet addresses are accepted, up to 10 MB, for images, PDF and common documents.
User credentials: together with SMS sending and automation requests, and with the click on the card button, Bitrix24 sends credentials of the user who acted. The app discards them at once, without storing or logging them; only the one from the card click is used, once, to read the phone numbers of that record.
Sending pace: the pace settings of each number (the start of the warm-up, the pauses and the reduction chosen by the Customer) are kept while the connection exists.
4. Where the data is processed and who receives it
- Our server, located in Brazil and operated by Moccelin Júnior Sociedade Individual de Advocacia.
- The Customer's Bitrix24 account, which is the destination of the messages and is governed by the agreement between the Customer and Bitrix24.
- WhatsApp, which carries the messages between the contact's phone and the connected number, under WhatsApp's own terms.
- The Central Bank of Brazil, only to read the public US dollar exchange rate (PTAX) when a payment is quoted; no Customer data is sent.
We do not share the data with anyone else, except when required by law or court order. If the Customer or its contacts are outside Brazil, the data is transferred to Brazil to provide the service.
5. Security
All connections to our server use encrypted HTTPS. Access tokens and keys are stored on the server with access restricted to the service account of the application. Bitrix24 account identifiers are stored only as hashes. The administration screen inside Bitrix24 accepts actions only from the Customer's own installation, and the vendor panel used to manage connection quotas and check payments never shows conversations, phone numbers, QR codes or tokens.
6. Your rights
Under the Brazilian General Data Protection Law (LGPD, art. 18) and, where it applies, the EU General Data Protection Regulation (GDPR, arts. 15 to 22), you may ask for confirmation that we process your data, access, correction, deletion, anonymization, portability, information about sharing, and you may object to processing or withdraw consent where consent is the legal basis. You may also complain to the Brazilian data protection authority (ANPD) or to the supervisory authority of your country.
Contacts of a Customer (people who wrote to a company on WhatsApp) should first address the company they talked to, which controls those conversations. We will help the Customer answer such requests.
Requests: atendimento@grmjr.com. Data protection officer (encarregado): Moccelin Júnior Sociedade Individual de Advocacia, at atendimento@grmjr.com. We answer within 15 days.
7. Children
The application is a business tool and is not directed to children.
8. Changes
We will publish any change to this policy at this address, with a new date at the top. Material changes will be announced in the application or by email before they take effect.
Contact: Moccelin Júnior Sociedade Individual de Advocacia, CNPJ 32.488.558/0001-54, Rua Santos Dumont, 64, sala 1103, Centro, Florianópolis/SC, Brazil. Email: atendimento@grmjr.com.