Privacy Policy
Last updated: November 14, 2026
1. Who we are and our roles
Blocks2Work, a brand operated by Blocks2Work - B2B Inc, is a platform that brings together a business's WhatsApp, a customer-service bot, scheduling, a booking page, a CRM and campaigns for small and medium-sized businesses.
- Your account data (your name, email, company, platform usage): Blocks2Work is the controller.
- Data about your business's customers (contacts, conversations and appointments you keep in the platform): your company is the controller and Blocks2Work is the processor, handling that data only to provide the service, under our Data Processing Agreement.
2. Data we process
- Account: name, email, password (stored irreversibly hashed), company, phone and team members.
- WhatsApp: messages sent and received through the connected number, including photos, voice notes, videos and documents, and the account number/identifier.
- CRM: contacts and companies you enter or import (for example name, phone, email, ID document, birthday, tags, notes, deals, agreed payments and attachments).
- Scheduling and booking page: appointments and the data end customers provide when booking or filling in a form on your page (name, WhatsApp, email).
- Connected calendars (Google or Microsoft), if you choose to connect them — see section 8.
- AI account, if you connect one: the API key, stored encrypted.
- Billing: subscription status and invoices. Card details stay with the payment processor, not with us.
- Record of acceptance of our Terms and Policies: date and time, IP address, browser and the version of each document — kept as proof of electronic acceptance for as long as the account exists and for the applicable legal period.
- Technical data: access and error logs (IP, browser, date and time), used for security and to fix problems.
3. How we use data and legal bases
- To provide the service — receiving and sending messages, running the bot, booking, syncing calendars, sending the emails and campaigns you set up. Legal basis: performance of our contract with you.
- Billing, support and account notices (for example: WhatsApp disconnected, payment declined). Legal basis: performance of the contract and compliance with legal obligations.
- Security, fraud prevention (including in the Refer and earn program) and legal compliance. Legal basis: our legitimate interests and legal obligations.
- Improving the platform with aggregated usage metrics. Legal basis: our legitimate interests.
- Connecting your Google or Microsoft calendar or your AI account: only when you choose to, based on your consent, which you can withdraw at any time by disconnecting.
We do not sell personal data, we do not "share" it for cross-context behavioral advertising, and we do not use your customers' data for advertising.
4. Who we share data with
Only with providers needed to operate the service, each limited to its role:
- Infrastructure: application hosting, database and file storage (United States); WhatsApp QR code connection server (Germany); email delivery (United States).
- Meta Platforms, when the number uses the official WhatsApp Business API.
- Paddle.com Market Ltd., payment processor and Merchant of Record for customers outside Brazil, which processes billing data. See paddle.com/legal/privacy.
- Asaas Gestão Financeira Instituição de Pagamento S.A. (Brazil), which processes payments in Brazilian reais for customers in Brazil.
- Artificial intelligence providers — see section 7.
- Google and Microsoft, only if you connect your calendar — see section 8.
The named list of providers is available to customers on request at [email protected]. We may also disclose data when required by law or a court order.
5. International transfers
Our servers are located in the United States (application, database, files and email) and in Germany (WhatsApp QR code connection), and Blocks2Work is operated from Brazil. When personal data from the European Economic Area, the United Kingdom or Switzerland is transferred to countries without an adequacy decision, we rely on the Standard Contractual Clauses approved by the European Commission (and the UK addendum where applicable) or other valid transfer mechanisms, together with the security measures in section 11.
6. WhatsApp integration
There are two ways to connect a number:
- QR code (the number you already use): works like WhatsApp Web. Messages pass through our connection server to reach the platform. Use remains subject to WhatsApp's terms, and WhatsApp may restrict numbers with unusual sending patterns.
- Official WhatsApp Business API (Meta): by connecting, you authorize Blocks2Work to send and receive messages on your behalf, under the WhatsApp Business Policies.
7. Artificial intelligence
- AI answers using your own AI account (Claude, ChatGPT or Gemini): when a customer asks the bot a question, we send that question and the business information you wrote for the AI to the provider you chose. This happens under your account and the provider's terms. The key is stored encrypted and you can remove it at any time.
- AI-assisted creation features (building the bot, the page or an email draft) and the support chat use an AI provider contracted by Blocks2Work, with the information you type into those features.
- Our AI providers may not use this data to train their models. Data received from Google or Microsoft (calendars) is never sent to AI providers.
8. Google Calendar and Microsoft Outlook integration
If you choose to connect Google Calendar or your Microsoft calendar (Outlook / Microsoft 365), Blocks2Work requests access only to your calendar events (and, for Microsoft, the account name and email, to identify which calendar was connected). For Google, the only scope requested is https://www.googleapis.com/auth/calendar.events. We do not access email, contacts, files or any other data in your Google or Microsoft account.
- Reading events (date, start and end time and whether the time is busy) — to show your appointments in the Blocks2Work calendar and prevent customers from booking a time when you are busy.
- Creating, updating and deleting events — only for appointments booked through Blocks2Work (by you, your team or your customers), so they appear in your calendar automatically.
Storage: access credentials are encrypted (AES-256-GCM, with the key kept outside the database). We keep a temporary copy of busy times only to calculate your availability, and it is replaced at every sync.
Sharing: none. Calendar data is not sold, not used for advertising, not used to train artificial intelligence or machine-learning models and not read by our staff, except with your explicit consent for support, for security reasons or to comply with the law.
Revoking access: disconnect the calendar at any time in Agenda → Integrations or directly in your Google or Microsoft account. On disconnection we delete the credentials immediately and the cached busy times within 30 days.
Blocks2Work's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
9. Data retention
Data is kept while the account is active. After cancellation, the account stays read-only for 30 days so you can download your data, and then it is deleted. For non-payment, data is deleted on day 60, with notices on days 45 and 55. Photos, voice notes, videos and documents received through WhatsApp are deleted after 30 days. You can download your data at every stage ("Download my data" in Settings). Billing records and acceptance records are kept for the period required by law.
11. Security
We apply technical and organizational measures to protect all data, with reinforced care for sensitive data — access credentials, calendar data received from Google and Microsoft APIs, messages and attachments:
- Encryption in transit: all communication with the platform and with Google, Microsoft and Meta APIs uses HTTPS/TLS 1.2 or higher.
- Encryption at rest: the database and file storage are encrypted (AES-256). Messages, internal notes, notification previews and attachments also get application-level encryption with a key unique to each business (AES-256-GCM). Google and Microsoft tokens and AI keys are also encrypted at the application level, with the key stored outside the database.
- Access control: each business can access only its own data (isolation enforced on every query). Files and attachments are stored privately and open only for authenticated users of the owning business. Internal access to infrastructure is restricted to authorized people with individual accounts, following the principle of least privilege.
- Logging and monitoring: we log critical actions (logins, connecting and disconnecting integrations, creating, editing and deleting contacts) and continuously monitor the infrastructure to detect unauthorized access and failures.
- Backups: daily, encrypted and access-restricted.
- Incidents: if a security incident may cause a relevant risk to individuals, we notify the affected customers and the competent data protection authorities within the legal deadlines (including the 72-hour deadline under the GDPR, where applicable).
12. Your rights
Depending on where you live, you have the right to access, correct, download (portability) or delete your data, to restrict or object to certain processing, to know who it is shared with and to withdraw consent at any time. The full data download, including the acceptance records, and account deletion are available in Settings. If you are in the European Economic Area or the United Kingdom, you may also lodge a complaint with your local data protection authority (in Spain, the Agencia Española de Protección de Datos — aepd.es). We will not discriminate against you for exercising your rights.
If you are a customer of a business that uses Blocks2Work, contact that business first — it is the controller of your data, and we will help it handle your request. For any other request: [email protected].
13. Changes and contact
Relevant changes to this policy are announced and must be accepted in the platform, with a new acceptance record. Data protection contact (DPO) and questions: [email protected].
EU representative (Article 27 GDPR): Rodrigo Vinhas, resident in Portugal. Contact: [email protected].
Terms of Service · Billing and Refund Policy · DPA · Support