Privacy Policy

Version: 2026-11-16
Effective: November 16, 2026
Controlling language: this Policy is written in Portuguese. This English text is a courtesy translation. If the two versions differ, the Portuguese version prevails.

This Privacy Policy explains how Dunkama processes personal data on dunkama.com, on platform.dunkama.com, and in related services (the “Service”). It is written for the Brazilian General Data Protection Law (Law No. 13,709/2018, the “LGPD”) and for situations in which other privacy laws also apply.

1. Controller and contact

Dunkama is the controller of the account (of the account holder and of each employee), invitation, organization, billing, support, security, legal-acceptance, account-closure, opt-out, and WhatsApp-reply data, and visit data described in this Policy. The controller’s channel, including for data-subject requests and for the encarregado if ANPD rules require one to be named, is:

  • Email: contact@dunkama.com
  • Form: https://dunkama.com/contact
  • Support in the platform: Account menu → Support (for account holders)
  • Data protection officer (encarregado): not appointed. Dunkama is a small-scale processing agent (ANPD Resolution CD/ANPD No. 2/2022, art. 11), and the channels above serve data subjects.

Dunkama is registered under Brazilian company number (CNPJ) 40.720.982/0001-00. Its legal name and registered office are in its corporate records and are provided through that channel on request. They complete the controller identification required by the LGPD.

For personal data about other people that a customer enters in the Service, such as a customer name on a contract or the mobile number of a customer who receives WhatsApp payment reminders, the customer is generally the controller and Dunkama is the processor. Section 5 explains that split.

2. Who this Policy covers

This Policy applies to:

  • platform account holders;
  • employees whom the account holder invites to the organization, each with their own account, and invited people who have not yet accepted the invitation;
  • former account holders and former employees, as to what we keep after deletion or removal (section 9);
  • people who contact Dunkama through the contact form, the platform support, or WhatsApp;
  • visitors to the website and the platform, to the extent we process an IP address to suggest a country and, on the website, with your consent, the Meta Pixel data (section 3);
  • third parties whose data a customer enters in the Service, in the processor role described in section 5, including the subscriber’s customers who receive WhatsApp payment reminders; as to the opt-out and the replies they send, Dunkama is the controller.

It is not directed to children or teenagers. There is no signup aimed at anyone under 18.

3. Personal data we process

We process what the current operation of the Service actually uses.

CategoryExamplesSource
AccountOf the account holder and of each employee: name, email address, phone number in international format (optional for the employee), password hash, preferred language, email-verification status and, for the account holder, the trial-reminder preference with the date and where the choice was madeRegistration, accepted invitation, and the account
InvitationEmail address of the invited person, who invited them, and the dates it was sent and when it expires. The link code is stored only as a hashOrganization account holder
TeamRole of each person in the organization (account holder or employee) and the date they joinedAccepted invitation
OrganizationName, legal name or full name, country (Brazil or the United States), type (individual or company), CPF, CNPJ, SSN or EIN, currency, time zone, and, when provided, the company’s contact email address and phone numberOrganization setup and the Company Profile
Use of the ServiceContracts, customers (name and, when provided, email address, phone number, and address), costs, revenue, targets, cash on hand, and receipts and payments entered manuallyWhat you enter
BillingStripe customer and subscription identifiers, price, status, period end, renewal preference; amount and invoice link when Stripe reports a payment or a failureStripe and the account
Legal acceptanceDocument type and version, language, hash of the text, date and time, IP address, user agent, request identifier, and source of acceptanceRegistration and later acceptance
Session and securitySession token and CSRF token stored as hashes, expiry, and last accessUse of the platform
Usage limitsRequest counters identified by IP address (the IPv4 address, or the /64 network for IPv6), by the internal account number, or by a hash; wrong-password counters identified by a hash only; on the website, the IP address of whoever sends the contact formUse of the platform and the website
Access recordIP address, date, and time of each entry into the account: signing in with the password, confirming the email address (at registration or on an email change), and resetting the passwordEntry into the account
Suggested countryIP address of the visit and the country code returnedWebsite, country suggestion in the platform, and, from the server, the status page
Contact and supportName, email address, and message; through the platform support, also the topic, the attachments, and the account context: account and organization identifiers; the organization’s name, country, and currency; language; and access state; through WhatsApp, the phone number, the profile name, and whatever the person sendsWebsite form, platform support, and WhatsApp
Account closureName and email address of the account holder; dates of the request, the cancellation, and the deletion; a copy of the acceptance records of everyone on the account; when a paid invoice exists, legal name or name, tax document (except the SSN), country, and Stripe customer identifierDeletion request
WhatsApp payment remindersName and mobile number of the subscriber’s customer, contract name, installment amount and due date, the subscriber’s company name (with the CNPJ, for a company), and the subscriber’s Pix key, which make up the message; the number and message identifier at Meta, the delivery state, and the error code; the date and author of the statement that the customer authorized the messagesSubscriber, Meta, and the sending operation
Opt-out and WhatsApp repliesMobile number, source (button or keyword), and date of the request to stop receiving reminders; of the messages received, only the mobile number, the date, and the type (leave request, come-back request, or other), never the textThe subscriber’s customer, through WhatsApp
CommunicationsContent of transactional account, invitation, employee-removal, trial, billing, WhatsApp reminder (monthly allowance use and Pix key change), data-copy, and account-deletion emailsOperation of the Service

We do not ask for LGPD sensitive data, such as health, biometrics, religion, or political opinion. Do not put that data in free-text fields unless it is necessary. An SSN, when the organization is an individual in the United States, is a tax identification document. It is not sensitive data as the LGPD defines that term, but access to it is limited to providing the Service. We do not put it in email content or send it to checkout as the document number, and we do not keep it after the account is deleted.

We do not receive the full card number or the security code. Stripe collects those on the payment page.

The company’s contact email address and phone number are shown to employees and in the quote PDF that the organization gives to its own customers; the phone number is also shown in the automatic reply to WhatsApp reminders. If the company does not provide its own contact, the platform uses, instead, the account holder’s sign-in email address and phone number. The account holder controls this by filling in the company contact. The quote PDF is generated in your browser, and Dunkama does not keep the file.

A message sent through the platform support goes by email to Dunkama’s support inbox, hosted by Google (Google Workspace). The reply-to address is your sign-in email, and the message carries the account context described in the table. The platform does not store the message or the attachments. You may add up to 3 image, audio, or video attachments, 25 MB in total. They go as attachments of the email, delivered by Resend, which keeps sent emails for 30 days.

The support page also offers a WhatsApp conversation. That channel is optional and happens outside the platform, under WhatsApp’s (Meta) terms and privacy policy. The first message comes filled in with the chosen topic and the account email; the text typed in the form is not included. Do not send passwords or card details through any support channel.

On the dunkama.com website, and only after you accept in the cookie notice, we use the Meta Pixel to measure the results of Dunkama’s ads. With your acceptance, the browser sends Meta the page address, the event (a page visit or a click to create an account), the IP address, the browser identifier, and the Pixel cookies. We do not send Meta your email, phone number, name, or anything you type on the website. Without acceptance, the Pixel is not loaded. Dunkama receives only aggregated ad reports from Meta; Meta keeps this data for the period set in its data policy. The platform (platform.dunkama.com) does not use the Pixel. We use no session recording and no other analytics tool.

4. Purposes and legal bases

PurposeDataLegal basis (LGPD, article 7)
Create the account, verify email, authenticate, reset the password, and confirm an email changeAccount data and one-time tokensItem V — performance of a contract and preliminary procedures
Create the organization and operate contracts, costs, cash, and calculationsAccount, organization, and data you enterItem V
Invite people to the organization and keep each employee’s accountEmail address of the invited person, account, and employee roleItem V — performance of the contract with the account holder, who chooses whom to invite
Send WhatsApp payment reminders on the subscriber’s behalfData in the “WhatsApp payment reminders” rowAs processor, under the subscriber’s instructions; the subscriber is responsible for the legal basis toward their customers (section 5)
Honor the request to stop receiving reminders, prevent abuse, and comply with WhatsApp rulesOpt-outs and the type of the replies receivedItem IX — legitimate interest; item II when there is a legal duty
Charge the subscription and record the plan stateEmail address, Stripe identifiers, plan country, status, and periodItem V; item II when retention is a legal or tax duty
Prove which version of the Terms and of this Policy was acceptedAcceptance record, including IP address and user agentItem V; item VI for the regular exercise of rights; item II when the law requires retention
Send account, invitation, employee-removal, 7-day trial, billing, WhatsApp reminder, data-copy, and account-deletion emailsName, email address, and message contentItem V. These are not marketing
Reply to people who write through the contact form, the platform support, or WhatsAppName, email address, message, and attachments; through the platform support, the account context; through WhatsApp, the phone number and profile nameItem V if the subject is contracting or use of the account; item IX to answer the request the person made
Deliver the data copy and handle other data-subject requestsAccount, organization, Customer Data, and acceptance recordsItem II, to comply with article 18 of the LGPD; item V
Delete the account on request and prove that the request was handledClosure record, copy of the acceptance records, and, when a paid invoice exists, tax dataItem II, for legal and tax duties; item VI, for the regular exercise of rights
Suggest a default country and plan before confirmationIP address and country codeItem IX — legitimate interest, limited as described below
Measure the results of Dunkama’s ads on the websiteEvents of a visit and of a click to create an account, IP address, browser identifier, and Pixel cookiesItem I — consent, given in the cookie notice and revocable at any time
Prevent abuse, limit attempts, and protect the sessionLimit counters (IP address, account number, or hash), session and attempt hashes, contact-form IP address, technical recordsItem IX; item II when there is a legal duty
Detect errors and slowness and keep the Service availableTechnical error records, with the internal identifiers of the account and the organization, and aggregated technical metricsItem V — performance of the contract; item IX — legitimate interest in keeping the Service stable and secure
Keep the application access recordsIP address, date, and time of each entry with the password, email confirmation, or password resetItem II — article 15 of the Brazilian Internet Civil Framework (Marco Civil da Internet, Law No. 12,965/2014)
Comply with an authority’s order and with tax dutiesThe minimum requiredItems II and VI

The legitimate interest in suggesting a country is limited to choosing, between the Brazil plan and the international plan, a visual default before you confirm the organization country. We use the country code, not a commercial profile. You may choose the other supported country. The charge follows the country saved on the organization, not the language and not the IP address alone. We do not use this signal for advertising.

There is no automated decision that produces a legal effect or similarly significant effect on a data subject under article 20 of the LGPD. Margin, price, cash projection, and bid simulation are calculations on figures the customer entered. They do not classify a person for credit, employment, or access to a right.

Registration, the phone number, and acceptance of the documents are not marketing consent. We do not keep a newsletter list and we do not send marketing. WhatsApp payment reminders are sent on the subscriber’s behalf, for the subscriber’s own charges, and are not Dunkama marketing. If that changes, we will update this Policy and ask for any consent the law requires, separately from the contract.

The trial reminders, sent on days 2, 5, and 6, can be turned off through the link in the email itself or in Profile. Turning them off does not affect the welcome email, the trial-ended notice, or sign-in, security, and billing messages, which are service messages for the account.

5. Third-party data entered by the customer

Contracts may contain personal data about customers, counterparties, or other people. In those cases:

  • the customer sets the purpose and the legal basis toward those data subjects;
  • Dunkama processes that data as a processor, to host and display the Service to the organization, to protect the platform, and to comply with a valid order;
  • Dunkama does not use that data for its own marketing and does not sell it;
  • requests from those data subjects may be directed to the customer controller. Dunkama assists the customer when the instruction and the law allow it.

The subscriber may send payment reminders to their customers through WhatsApp. For this, Dunkama processes, as the subscriber’s processor, the customer’s name and mobile number, the contract name, the amount and due date of each installment, and the subscriber’s Pix key. The subscriber is the controller: the subscriber is responsible for the legal basis and for having each customer’s authorization to receive the messages, and Dunkama records the date and author of that statement. A customer who receives a reminder can stop receiving them at any time, through the button in the message or by replying SAIR (Portuguese for “leave”), and can start receiving them again by replying VOLTAR (Portuguese for “come back”). The customer’s other requests belong to the subscriber, and Dunkama assists the subscriber.

This version does not include a separate processor contract for electronic signature inside the product. The processing instructions are in these documents. A business customer may request its own processor terms through the contact channel or the platform support.

6. Processors and international transfers

We use providers that process data on our behalf to operate the Service. This is sharing with processors, not a sale of personal data.

ProviderRoleData it receivesWhere it may process data
RenderApplication hosting and PostgreSQL databaseAccount, organization, Service-use, session, acceptance, and subscription metadata, and account-closure recordsUnited States
StripeCheckout, subscription, payment method, and invoicesEmail address, organization and account identifiers, plan country and plan name; card and invoice data collected by Stripe itselfUnited States and other countries where Stripe operates the payment
Resend (Plus Five Five, Inc.)Delivery of transactional email and of contact and support messagesRecipient, sender, subject, content, and attachments. On the contact form and the platform support, also the reply-to addressUnited States. Resend may use its own subprocessors to deliver and protect the email service. Sending through the email API does not use Resend’s artificial-intelligence editor
Sentry (Functional Software, Inc.)Technical error records of the Service, to find and fix failuresThe error message and technical trace; the page or route where it happened, without the address parameters; browser and operating system; Service version; and the internal identifiers of the account and the organization. Before sending, filters remove email addresses, CPF, CNPJ, phone numbers, passwords, tokens, and Pix key fields. We do not send request contents, cookies, or the IP addressUnited States
Grafana Labs (Raintank, Inc.)Performance and availability metrics of the Service, with alertsAggregated technical metrics, such as request count and response time by route type, error counts, queues, and database usage, and the results of availability checks of the public pages. It does not receive names, email addresses, account or organization identifiers, Service content, or the IP address of people using the ServiceUnited States
Google (Google Workspace)Dunkama’s email inbox, which receives contact and support messagesContact and support messages, with the account context and attachments, and emails exchanged with DunkamaUnited States and other countries where Google has infrastructure
Meta Platforms (WhatsApp Business Platform, Cloud API)Sending WhatsApp payment reminders on the subscriber’s behalfMobile number of the subscriber’s customer, message content, delivery state, and the customer’s repliesBrazil: Dunkama’s number uses local storage, and the content stays outside the country for at most 60 minutes, according to Meta’s documentation, which does not publish the retention period; Meta also operates in other countries
Meta Platforms (Meta Pixel)Ad measurement on the website, only with your acceptanceWebsite events, IP address, browser identifier, and Pixel cookies. Meta also processes this data for its own purposes, under Meta’s data policyUnited States and other countries where Meta operates

The default country comes from the network header that Render’s infrastructure adds to the request. When that header is missing, the country is looked up in an IP location database kept on Dunkama’s servers, and the IP address is not sent to any other provider for this. We do not keep a geolocation history. We store the country you confirm on the organization.

WhatsApp, operated by Meta, is also an optional support channel. Whoever chooses it talks with the Dunkama team outside the platform, under WhatsApp’s terms and privacy policy. Dunkama receives there whatever the person sends.

The DNS that resolves dunkama.com does not receive account content. A DNS lookup may expose a resolver IP address to the DNS provider, as is ordinary on the internet.

Render, Stripe, Resend, Sentry, and Grafana Labs process data in the United States; Google and Meta, as shown in the table. International transfers rely on the contracts with these providers and, where required, on standard clauses and the other mechanisms recognized by the ANPD, including Resolution CD/ANPD No. 19/2024. The Service cannot operate, in this architecture, without the transfers described above.

7. Cookies and browser storage

The dunkama.com website shows a cookie notice. The Meta Pixel advertising cookies, and the data it keeps in the browser, are stored only after you accept. Declining is as easy as accepting, and you can change your choice at any time in “Cookie preferences”, in the website footer. When you withdraw acceptance, the Pixel is no longer loaded and we delete its cookies and the data it kept in your browser; what was already sent to Meta follows Meta’s data policy. The other technologies below are required for the Service you request or only store a preference you set yourself.

TechnologyWherePurposeDuration
Cookie dunkama_sessionPlatformKeeps the session. HttpOnly7 days, or until sign-out
Cookie dunkama_csrfPlatformProtects actions against forged requests. Read by the application7 days, or until sign-out
Cookie dunkama_devicePlatformRecognizes a browser where you already signed in with your password, so other people's wrong attempts do not lock you out. Holds only a random code; we store only its hash, linked to your account. HttpOnly, sent only to the sign-in routes180 days from the last password sign-in; deleted on password reset or sign-in email change
Cookie dunkama_localeWebsite and platformRemembers the chosen language1 year
Cookie NEXT_LOCALEWebsite and platformCopy of the chosen language, used by the language libraryUp to 1 year
Cookie dunkama_consentWebsiteStores your choice in the cookie notice6 months
Cookie _fbpWebsite, only with your acceptanceIdentifies the browser for Meta’s ad measurement90 days
Cookie _fbcWebsite, only with your acceptance and when you arrive from an adRecords the ad click for Meta’s measurement90 days
localStorage dunkama-themeWebsite and platformLight or dark themeUntil you clear the browser
localStorage dunkama.tours.v2.*PlatformEach user’s tutorial progress in this browser. The key contains the user’s internal number. Progress saved earlier in the dunkama.tours.v1.* format moves to the first user who signs in and is then deletedUntil you clear the browser
localStorage dunkama_trial_welcome_*PlatformRecords that the trial welcome notice was dismissedUntil you clear the browser
localStorage dunkama.projects.*, dunkama.clients.*, dunkama.categories.*, dunkama.materials.* and dunkama.services.*PlatformSort order and page size of the contract, client, category, material and service listsUntil you clear the browser
localStorage lastExternalReferrer and lastExternalReferrerTimeWebsite, only with your acceptanceStored by the Pixel: where the visit came from (for example, Instagram) and whenUntil you withdraw acceptance or clear the browser
localStorage multiFbcWebsite, only with your acceptance and when you arrive from an adStored by the Pixel: a copy of the ad click, like the _fbc cookieUntil you withdraw acceptance or clear the browser
Email-resend sessionStoragePlatformPrevents another resend click for 30 seconds. The key may contain the email addressUntil the tab is closed
sessionStorage dunkama:check-emailPlatformRemembers, in this tab, the email address to which we sent the verification link, without putting it in the page addressUntil the tab is closed
sessionStorage dunkama:invitePlatformKeeps, in this tab, the invitation code and the invited email address while you sign in to your account to accept it, without putting them in the page address. Deleted when you accept, when the invitation stops being valid, or when you sign outUntil the tab is closed

The session is not stored in localStorage.

8. Sharing

We may disclose personal data:

  • to the processors in section 6, limited to what each one needs;
  • to lawyers, accountants, and advisers under a duty of confidentiality, when needed for our defense or to comply with law;
  • to a public authority, when there is a legal or regulatory duty or a valid order;
  • to a successor of the operation, in a reorganization, merger, or sale of the Service, with the protection the law requires;
  • to you, or to someone you designate, when you ask.

We do not sell personal data. We also do not say that we “never share data”: providing the Service requires the processors above and, when the law so requires, disclosure to authorities.

9. Retention

DataHow long
Account, organization, and Customer DataWhile the account exists. After a deletion request, we delete this data 7 days after the request; until then, you can cancel it
PasswordThe hash only, while the account exists
InvitationUntil it is accepted or cancelled; an expired invitation, which no longer opens the account, stays in the account holder’s list, marked as expired, and is deleted no sooner than 30 days after expiry. Requesting account deletion deletes open invitations
Removed employee’s accountDeleted at the moment of removal, with the employee’s sessions and acceptance records. What the employee entered in the organization stays with the organization
WhatsApp reminders and opt-outsWhile the subscriber’s account exists; they are deleted with it
Replies received through WhatsAppOnly the type, the mobile number, and the date, for 90 days; then they are deleted
SessionUp to 7 days, or sooner if you sign out or reset the password
Email-verification token24 hours
Password-reset token1 hour
Legal-acceptance recordWhile the account exists and for up to 5 years after closure, together with the account holder’s name and email address, to prove the contract and to exercise rights
Closure recordUp to 5 years after deletion, to prove that the request was handled
Error records (Sentry) and technical metrics (Grafana)30 days at Sentry and 14 days at Grafana; then the providers delete them
Billing and tax recordsFor the period required by Brazilian tax and commercial law, generally 5 years after the fiscal year they relate to. When a paid invoice exists, we keep after deletion, for up to 5 years, the legal name or name, the tax document (except the SSN), the country, and the Stripe customer identifier. Stripe keeps the customer and the invoices as the tax record, under its own rules
Contact and support messagesFor as long as needed to reply and to document the support exchange, in Dunkama’s inbox (Google Workspace) and, when the conversation took place on WhatsApp, in that conversation. The platform does not store these messages or the attachments. Resend keeps sent emails, with their attachments, for 30 days
Request-limit and wrong-password countersCounters keyed by IP address stay only in the server’s memory, for a few minutes. The others, keyed by the account number or by a hash, stay in the database for up to 48 hours; then they are deleted
Website contact-form limit IP addressIn memory on the website server, never written to a database. The counter lasts 10 minutes and is discarded afterwards, when the server restarts or clears expired counters
Access record (sign-in with the password, email confirmation, and password reset)6 months, including after the account is deleted; then it is deleted
BackupsUp to 3 days after deletion from the primary database, through the hosting provider’s recovery. That copy is not used to operate the account

The account holder can delete the account in Profile → Delete account, confirming with the password. Deletion covers the account, the organization, and the employees’ accounts. For 7 days, the account is read-only and the request can be cancelled. At the request, we end the account holder’s other open sessions, delete open invitations, notify the employees by email, and turn off subscription auto-renew, where there is one. After the 7 days, any subscription still open is ended in Stripe, and we delete the account, the organization, and the Customer Data. The request can also be made through the channel in section 1 or the platform support.

After deletion, we keep only what the table above lists: the closure record, the copy of the acceptance records of everyone on the account (document type and version, language, hash of the text, date and time, IP address, user agent, request identifier, and source), and, when a paid invoice exists, the tax data. The SSN is never kept after deletion. Backups may hold the deleted data for up to 3 days. The application’s technical records (logs) and the error records sent to Sentry identify the account and the organization only by internal numbers.

Each time someone enters the account (signing in with the password, confirming the email address at registration or on an email change, and resetting the password), we record the IP address, the date, and the time, and we keep that record for 6 months, including after the account is deleted, as article 15 of the Brazilian Internet Civil Framework (Marco Civil da Internet) requires; then it is deleted.

After deletion, the same email address can be used for a new registration. That new account starts from scratch, with a new trial.

An employee cannot delete their own account through the platform: the employee asks the account holder, who can remove them, or uses the channel in section 1. Removal ends access immediately and deletes the employee’s account, and the employee receives an email notice. The employee’s access record stays for the 6 months of the Marco Civil.

We may refuse or limit deletion when retention is required for a legal duty, for defense in a proceeding, or for the security of the Service. We explain the reason where the law allows it. While a payment is past due, a request made in Profile may be refused; in that case, contact support, which handles the request.

10. Security

We use measures appropriate to the risk, including:

  • transmission over HTTPS;
  • passwords stored with an Argon2id hash, not in clear text;
  • an HttpOnly session cookie and CSRF protection on actions that change data;
  • request limits and a temporary lock after wrong passwords, recognizing a browser already used so other people cannot lock the account holder out;
  • logical separation by account and organization;
  • a limit on simultaneous sessions per person;
  • only the account holder invites and removes people, turns on WhatsApp reminders and changes the Pix key, downloads the data copy, and deletes the account;
  • monitoring of errors, performance, and availability, with filters that remove personal data before it reaches the monitoring providers;
  • email verification before use;
  • an acceptance record with a hash of the current text;
  • password confirmation to delete the account;
  • an email notice after each download of the data copy.

No environment is absolutely secure. If we become aware of an incident with relevant risk or harm to data subjects, we will notify the affected data subjects and the ANPD in the cases and within the periods set by the LGPD and by ANPD regulation.

11. Data-subject rights

Under article 18 of the LGPD, you may request:

  1. confirmation that processing exists;
  2. access to the data;
  3. correction of incomplete, inaccurate, or outdated data;
  4. anonymization, blocking, or deletion of unnecessary or excessive data, or of data processed unlawfully;
  5. portability, subject to commercial and industrial secrecy and to ANPD regulation;
  6. deletion of data processed on the basis of consent, where consent is the basis;
  7. information about the public and private entities with which we shared data;
  8. information about the possibility of refusing consent and about the consequences, where processing is based on consent;
  9. withdrawal of consent, where consent is the basis.

In Profile → Your data, the organization owner can download, at any time, a copy of the account, organization, and Customer Data, with the acceptances, the subscription data, the records you deleted, the data of each person on the team (name, email address, phone number, role, dates, and each person’s acceptances, with IP address and browser), open invitations, and the WhatsApp reminder data, including opt-outs. The file is a ZIP with JSON and CSV and can be downloaded up to 3 times in 24 hours. This also works while the account is read-only, and we email a notice after each completed download. The file does not include password and token hashes, limit counters, access records, or what only Stripe keeps. Anyone who is not the organization owner, or has no organization yet, asks for the copy through the channel in section 1 or the platform support.

Account deletion is described in section 9. Other requests are handled through the channel in section 1 or the platform support. We may confirm identity before fulfilling a request. The response period follows article 19 of the LGPD: a simplified form immediately, where that fits, or a clear statement within 15 days of the request.

You may also petition the Brazilian National Data Protection Authority (ANPD). That path does not replace contacting us, and contacting us does not affect it.

When the data was entered by a customer acting as controller, we may direct the data subject to that customer. A customer of the subscriber who receives WhatsApp reminders can stop receiving them at any time through the button in the message or by replying SAIR; their other requests go to the subscriber, and Dunkama assists the subscriber.

12. Children and teenagers

The Service is directed to people aged 18 or older, for professional or business use. We do not knowingly collect data about children or teenagers. If we identify an account belonging to a minor, we may close it and delete the data, except for retention required by law.

13. Changes to this Policy

We may update this Policy. The current version has a single date identifier, the same on the website and in the platform. When a new version is required for use, the account becomes read-only until acceptance at platform.dunkama.com/legal/review. The earlier record is kept. Switching language for the same version does not require a new acceptance.

14. Contact

Dunkama
CNPJ 40.720.982/0001-00
Email: contact@dunkama.com
Form: https://dunkama.com/contact
Support: in the platform, Account menu → Support
Data-subject requests: use the same email, with the subject “Privacy”, or the platform support, with the topic “Privacy and data”, and enough information for us to find the account.

Terms of Use

We use necessary cookies to run this site. If you accept, we also use the Meta Pixel to measure our ads. Privacy Policy