1. Scope and acceptance
This Policy applies to the wisedatamail.com website, to the WiseData Mail platform — dashboard, mobile app and API —, to the emails sent by our customers through it and to communications related to these services.
By using any of these services as a customer, you declare that you are aware of the practices described here. This Policy forms part of the Terms of Use.
If you are here because you received an email from a company that uses WiseData Mail, read sections 3, 5, 6 and 7: they explain who decides about your data and how to ask to be removed from the list.
2. Target audience and minimum age
The Platform is intended for professional use by companies and self-employed professionals. It is not intended for anyone under 18 and we do not knowingly collect data from children or adolescents as customers.
If we identify a registration that does not comply with this rule, the account may be closed and the data deleted. The choice of message recipients belongs to the customer, who is responsible for the legal basis of that processing.
3. Roles under the LGPD
We are the controller of the data of those who subscribe to or show interest in the Platform: account registration data and team users' data, tax and billing data, access logs, support interactions and browsing on the website.
We are a processor of the data of the contacts that the customer registers, imports or sends through the API, and of the sending results associated with them — deliveries, bounces, complaints, opens, clicks and unsubscribes. In this case the customer is the controller: it decides whom to write to, on what legal basis and for what purpose, and we process those data exclusively according to its instructions and as necessary to provide the service, as set out in clause 16 of the Terms of Use.
There is one exception, described in section 7: the Platform's suppression list, which we maintain for our own purpose and in which we act as controller.
The distinction matters in practice: requests from recipients about the data of a message must first be addressed to the company that sent it, as set out in section 20.
4. What data we collect from customers
Registration data: name, email address, password in encrypted form, preferred language and, when provided, phone number; and the same data for users invited to the team.
Tax and billing data: company name or full name, CNPJ, CPF or foreign document, billing address and contact, and the record of acceptance of the legal documents. Full credit card data are not stored by us — processing is carried out by the payment processor.
Sending configuration data: domains, sender addresses, DNS records and tracking host registered by the customer.
Technical and security data: IP address, browser and device type, date and time of access, session and login history, API key usage and logs of security-relevant events.
Mobile app data: notification delivery identifier and device model, to send notices to users who have enabled notifications.
Error reports: when a technical failure occurs, we automatically collect error and performance diagnostics, configured not to send the user's personal data, solely to fix the problem.
Browsing data on the website and the Platform: pages and screens visited, source of the visit and campaign parameters, collected as described in section 9.
Communication data: messages exchanged with support, including those exchanged with the artificial intelligence assistant, and the content of contact forms.
5. Data of contacts and message recipients
On the customer's behalf, we process the data of the contacts it loads into the Platform: email address and, if the customer provides them, name, phone number and custom fields; the lists and segments the contact belongs to; the legal basis declared by the customer when importing; and the history of sends, deliveries, bounces, complaints, opens, clicks and unsubscribes, with the reason given by those who unsubscribed.
We also process the content of the messages the customer sends. The body and attachments of transactional messages are kept only until the delivery attempt is completed; campaign images remain hosted for as long as the account exists, so that they display to whoever opens the message.
At the time of sending, the recipient's address and the content of the message are transmitted to the sending provider and, from there, to the recipient's mailbox provider, which processes this information according to its own policies.
We do not use contact data for our own purposes, do not cross-reference them with other customers' data — except for the suppression list in section 7 —, do not use them to train artificial intelligence models and do not sell them.
If you received an email from a company that uses WiseData Mail and no longer want to receive them, use the unsubscribe link in the message itself: it works in one click, without logging in. To access, correct or delete your data, address the request to the company that sent the message — it is the controller.
6. Open and click tracking
So that the customer can measure the results of its messages, the Platform may include a small tracking image in them and rewrite the links. When the image loads, we record an open; when a link is clicked, the recipient passes through a redirect address and is taken to the original destination, and we record the click.
Each open and each click records date, time, IP address, browser or email app and, for clicks, the link accessed. Some opens are generated automatically by mailbox providers and security systems; we try to identify them, and for that reason open figures are estimates.
The redirect addresses pass through the network of an infrastructure provider identified in section 11. On the plans that include it, the customer may use its own subdomain for these addresses.
This processing is carried out on behalf of the customer, which must disclose it to recipients in its own privacy policy. As a recipient, you can reduce this tracking by blocking the automatic loading of images in your email app; links continue to work normally.
7. Platform suppression list
When an address generates a permanent bounce — because it does not exist or does not accept messages — or when the recipient marks a message as spam, it is added to the Platform's suppression list and stops receiving messages from any customer, not only from the one that sent it.
In that list we keep only the email address, the reason, the number of occurrences and the dates, with no link to the originating account. Here we act as controller, on the basis of the legitimate interest in protecting the sending reputation shared by all customers and in preventing the recipient from continuing to receive messages they refused or that cannot be delivered.
The list is kept even after the originating customer's account is deleted, because its purpose does not depend on that account. If your address was added by mistake — for example, because the mailbox started existing again —, you can request a review through the public privacy form.
In addition, each account has its own suppression list, with the unsubscribes and bounces from its sends, which is customer data and is deleted with the account.
8. Purposes and legal bases
Performance of a contract: creating and maintaining the account, executing sends, generating reports, processing payments, issuing tax documents and providing support.
Compliance with a legal or regulatory obligation: retention of access logs under article 15 of the Brazilian Internet Civil Framework (Marco Civil da Internet) and tax and accounting obligations.
Legitimate interest: Platform security, prevention of fraud and sending abuse, maintenance of the suppression list in section 7, error monitoring, performance measurement and product improvement, always with an assessment of the impact on the data subject's rights.
Consent: sending marketing communications and use of non-essential cookies. Consent may be withdrawn at any time, with no effect on the contracted service.
Compliance with the controller's instructions: all processing of the contacts, messages and sending results that the customer loads, in which we act as processor. The legal basis for that processing is defined and evidenced by the customer.
Institutional promotion: use of the customer's business name, trademark and spontaneous testimonials to publicly identify the relationship, as authorised in the Terms of Use. A company name is not personal data, but a testimonial signed by a person is — in that case the basis is consent, which may be withdrawn at any time.
We do not use the data customers enter into the Platform to train artificial intelligence models, nor do we sell it, under any circumstances.
10. Data sharing
We share data only with the providers necessary to deliver the service, always under contract and with a duty of confidentiality, listed in section 11.
When you use a linked account, the agency authorised by the holder of that account gains access to its data, as set out in the Terms of Use. When the customer configures webhooks, the sending events, including the recipient's email address, are sent to the address it indicated.
We may share data to comply with a legal obligation, a court order or a request from a competent authority, and for the regular exercise of rights.
We do not sell personal data and do not hand it over to third parties for advertising.
11. Subprocessors
The providers below process personal data on our behalf, each limited to the purpose indicated. When they process customers' contact data, they act as sub-processors, as set out in clause 16 of the Terms of Use. The list is kept up to date on this page; any new subprocessor is added here before it starts operating.
Emails are sent from cloud infrastructure in Brazil. The location shown is that of the infrastructure where the data is processed; providers with an edge network serve each request from the point closest to the person accessing it.
Internal administrative tools that do not receive customer or recipient data are not included in this list.
| Subprocessor | Purpose | Location |
|---|---|---|
| Amazon Web Services | Sending and storage infrastructure | Brazil |
| Cloudflare | Security, network and storage | United States and global network |
| Hosting provider | Application hosting | Brazil |
| Stripe | Payments | United States |
| OpenAI | Artificial intelligence features | United States |
| Postmark (ActiveCampaign) | Message quality analysis | United States |
| Sentry | Error monitoring | United States |
| Expo (650 Industries) | App notifications | United States |
| Website measurement, with consent | United States |
12. Sharing with WiseData group companies
WiseData Business LTDA maintains other products under the WiseData brand. Registration and contact data of customers and users are shared with the group's help desk, for unified support, notices and the support assistant, and may be used for fraud prevention, management of the commercial relationship and the offer of the group's own products.
To prevent fraud and abuse, the Platform checks a central group blocklist, with email addresses, domains, IP addresses and phone numbers associated with proven abuse, and looks up the CNPJ entered in the tax registration in a group service based on public sources.
Licensee Content — contacts, messages and sending results — is not shared between group products. When another WiseData product sends emails through the Platform, it does so as a customer, through the API, like any other.
Offering other group products through marketing communications depends on consent and can be cancelled at any time.
In the event of corporate reorganisation, merger, spin-off, incorporation or sale of assets, data may be transferred to the successor, under the same conditions as this Policy, with prior notice to data subjects.
13. International transfer
Email sending and database backups are processed in Brazil. Some of the other subprocessors in section 11 maintain infrastructure outside Brazil, which constitutes an international data transfer.
These transfers comply with article 33 of the LGPD and are supported by contractual clauses that ensure a level of protection compatible with Brazilian law, as provided in the International Data Transfer Regulation approved by ANPD Board Resolution No. 19/2024.
Where an equivalent alternative with infrastructure in Brazil exists, it is preferred.
14. Artificial intelligence and data
On the plans that include the feature, the Platform uses artificial intelligence to generate and review campaign copy. The model provider is identified in section 11. The group's help desk also uses an artificial intelligence assistant for support.
What you send to these features is transmitted to the provider solely to generate the response. We do not use Licensee Content to train models.
Avoid sending contacts' personal data, sensitive data or trade secrets to the artificial intelligence features: they are not needed to write a campaign, and the response is generated by an automated system.
We record the use of the features — quantity, cost and the generated text linked to the campaign — to control the plan quota and identify abuse. Generated responses are suggestions and do not replace human review.
15. Automated decisions
Article 20 of the LGPD guarantees data subjects the right to request a review of decisions taken solely on the basis of automated processing that affect their interests, including those intended to define their personal, professional, consumer and credit profile.
The Platform automatically takes some operational decisions: pausing a campaign or suspending an account's sending when complaint or bounce rates exceed the thresholds in clause 9 of the Terms of Use; adding an address to the suppression list in section 7; preventively blocking a registration showing signs of fraud or reuse of the trial period; and blocking sending when the plan quota is reached.
The criteria for these decisions are described in the Terms of Use and in this Policy. All of them can be reviewed by a member of our team, upon request through the support channels or the public privacy form.
The reports, segments and suggestions presented to the customer are inputs to human decisions — it is the customer who decides whom to write to. Should a feature start producing a solely automated decision with significant effect other than those described here, we will disclose the criteria and make a review request available, subject to commercial and industrial secrecy.
16. Information security
We adopt technical and administrative measures to protect data, including encrypted traffic, passwords stored with a key derivation algorithm, two-step verification available, encrypted authentication secrets, role-based access control, isolation between accounts of different customers, API keys with permission scopes, webhook signatures, private storage for attachments, encrypted backups with a credential that can neither read nor delete them, and logging of security events.
Sending is only enabled for domains authenticated by the customer, which makes it harder to use the Platform to forge senders.
Access by the Licensor's staff to customer data is restricted to what is necessary for support and maintenance, logged and subject to a confidentiality undertaking.
No system is completely immune to incidents, and no security measure eliminates the risk entirely.
17. Security incidents
If a security incident occurs that may result in significant risk or harm to data subjects, we will notify those affected and the Brazilian National Data Protection Authority under article 48 of the LGPD and the ANPD's regulations, describing the data involved, the risks and the measures taken.
When we act as processor, we will notify the controlling customer as soon as we become aware, with the information available, so that it can fulfil its own notification duties.
18. Retention periods
We keep data for as long as the contractual relationship lasts and, after it ends, only for the periods below. Once the periods expire, the data are deleted or anonymised.
The customer may, at any time, delete contacts and the data associated with them. The periods below apply to what it does not delete earlier.
| Data | Period | Basis |
|---|---|---|
| Account and Licensee Content — contacts, lists, campaigns, templates, images, history of sends, opens and clicks | During the relationship. After account deletion, immediate removal from the Platform and up to 30 days in backups | Performance of the contract and controller's instructions |
| Body and attachments of transactional messages | Until the delivery attempt is completed | Necessity |
| Messages sent with the sandbox key | 30 days | Necessity |
| Contact import file and error report | 7 days; the import record, without the file, 12 months | Necessity and evidence of the declared origin |
| Webhook delivery log, with the content sent | 30 days | Necessity and diagnostics |
| Log of emails sent by the Platform itself to users (verification, password, invitations, notices) | 60 days | Legitimate interest — delivery diagnostics |
| Login history shown to the user | 90 days | Account security |
| Application access logs | 6 months | Article 15 of the Brazilian Internet Civil Framework |
| Agency activity in a linked account | 12 months | Transparency between the parties and security |
| Database backups | 30 days, on rotation | Service continuity |
| Tax documents and billing records | 5 years | Tax legislation |
| Account deletion record (date, reason, IP, author and identification of the holder) | 5 years | Regular exercise of rights and evidence of compliance |
| Platform suppression list (email, reason and dates) | For as long as necessary to protect sending reputation, including after the originating account is deleted | Legitimate interest |
| Encrypted anti-fraud indicators (document, email, device) | For as long as necessary to prevent reuse of the trial period and abuse | Legitimate interest |
| Contact data for marketing | Until consent is withdrawn | Consent |
| Support and service history | 5 years after the account is closed | Regular exercise of rights |
19. Deletion of the account and data
Account deletion is requested within the Platform itself, by the Account Owner, after the subscription has been cancelled, and is immediate and irreversible. The full procedure is on the account deletion page.
Removal covers everything created during use — contacts, campaigns, messages, events, images, domains, API keys and webhooks —, not just the main registration. Users' identification data are anonymised. Only the data whose retention is required by law or necessary for the regular exercise of rights, the Platform's suppression list and the anti-fraud indicators remain, as set out in section 18.
Resources created on the account's behalf with providers — the domain identities at the sending provider and the customer's own tracking host — are removed shortly afterwards, in the background.
Before deleting, the customer can obtain a copy of its content through the Platform's features or by request to support.
Moving to a less comprehensive plan does not imply deletion: the data remain stored.
Accounts without an active subscription and without any access for an extended period may be deactivated and have their data deleted. Keeping data that no one uses indefinitely runs counter to the necessity principle in article 6, III, of the LGPD. Before deletion we notify by email, in advance and with the opportunity to reactivate or obtain a copy.
20. Data subject rights
Under article 18 of the LGPD, you may request: confirmation that processing exists; access to the data; correction of incomplete, inaccurate or outdated data; anonymisation, blocking or deletion of unnecessary or excessive data or data processed in breach of the law; portability to another provider; deletion of data processed on the basis of consent; information about whom we share the data with; information about the possibility of not giving consent and its consequences; and withdrawal of consent.
You also have the right to object to processing based on legitimate interest and to request a review of automated decisions, as set out in section 15.
If you receive emails from one of our customers, your data are controlled by that customer. To leave the list, use the unsubscribe link in the message. For other requests, contact the company that sent the message. If the request reaches us, we will forward it to the responsible controller and provide the necessary assistance; requests about the Platform's suppression list, which is ours, are handled directly.
21. How to exercise your rights and response times
Open a request through our public privacy form, stating the right you wish to exercise and the details that allow us to locate your record. The form requires no registration or login — it serves people who are not customers, people who received an email from one of our customers and people who have already closed their account —, and returns a ticket number so you can track its progress.
Those with an active account may, if they prefer, open the request through the help desk, under the Privacy and LGPD category. It is the same flow and the same deadline.
Confirmation that processing exists and access in simplified form are provided immediately. A clear and complete statement, with the origin of the data, the criteria and the purpose of the processing, is provided within 15 (fifteen) days, under article 19 of the LGPD.
We may request additional information to confirm the requester's identity before fulfilling the request — a measure that protects the data subject, and the deadline runs from that confirmation.
Manifestly excessive or repetitive requests may be justifiably refused, with an explanation of the reason.
22. Data protection officer and communication channel
WiseData Business LTDA qualifies as a small-scale processing agent under ANPD Board Resolution No. 2 of 27 January 2022.
Under article 11, paragraph 1, of that Resolution, a small-scale processing agent is not required to appoint a data protection officer, provided it makes a communication channel with data subjects available. Article 7 of the same Resolution allows service to be provided electronically, provided the rights under the LGPD and facilitated access to information are ensured.
Our official channel is the public privacy request form, open to anyone, with no registration and no login. We chose a form instead of an email address precisely for facilitated access: each request receives a ticket number, is trackable and is routed internally without depending on someone monitoring an inbox.
Requests received through this channel are handled by an internally designated person, who responds within the deadlines in section 21.
Should the Licensor no longer qualify as a small-scale agent, we will formally appoint a data protection officer and their identification will be included in this section.
24. Communications and anti-fraud
We send transactional communications necessary for the relationship, such as sign-up confirmation, billing and quota notices, reputation alerts and security notices. These communications do not depend on consent and cannot be disabled while the account is active.
Marketing communications depend on consent and can be cancelled at any time through the unsubscribe link in each message.
We may analyse usage and sending patterns to identify abuse, fraud, sending to a base of prohibited origin or improper automated use, on the basis of the legitimate interest in protecting the Platform, other customers and recipients.
To verify the truthfulness of registrations and prevent parallel accounts created to circumvent limits, repeat the trial period or start over after a suspension, we cross-check signals such as document, email address, phone number, sending domain, payment method, IP address and device characteristics, stored in encrypted form whenever possible. We may request documentary proof before releasing or reactivating access. This processing is limited to this purpose and does not feed any commercial profile or advertising.
Any block resulting from this verification can always be reviewed by a person, as set out in section 15.
25. Changes to this policy and governing law
We may update this Policy periodically. The most recent version will always be available on this page, with its version number and date. For material changes, we will notify you by email or by a notice within the Platform.
This Policy is governed by Brazilian law. The courts of the Judicial District of Goiânia, State of Goiás, Brazil, are elected to settle any disputes, without prejudice to the courts of the domicile of an individual consumer data subject.