Privacy Policy

Last updated: November 18, 2026

This Privacy Policy describes how FlakeDesk ("we"), a customer operations and CRM platform operated by FLAKEDESK INOVA SIMPLES (I.S.) (CNPJ 69.481.905/0001-27), collects, uses, stores, shares, and protects personal data, in compliance with the Brazilian General Data Protection Law (LGPD, Law No. 13,709/2018) and other applicable legislation.

By using FlakeDesk (the application at flakedesk.com and subdomains) or interacting with channels operated by our customers through the platform, you agree to the practices described in this policy.

1. Who we are and our roles

FlakeDesk is a multi-tenant CRM software (SaaS) used by customer organizations to manage contacts, companies, sales pipelines, and customer service, including via WhatsApp.

2. Data we collect

Account and platform usage data:

CRM data (processed on behalf of the customer organization):

WhatsApp message data (official Meta WhatsApp Business Platform integration):

Chat widget data on customer websites:

Support chat on the FlakeDesk website: flakedesk.com may show a chat button in the corner of its pages. The chat does not send anything you write or store anything in your browser until you start a conversation. Once you start one, we process the name, email address or phone number you provide and the messages exchanged, to respond to you. In this chat FlakeDesk is the controller: the conversation goes into our own CRM as a contact and may first be answered by an AI-powered virtual assistant, which hands the conversation over to our team when needed. Your browser keeps the conversation code and the name and email address you provided in local storage, as described in the Cookie Policy. The chat also lets you continue the conversation on WhatsApp; in that case the WhatsApp message rules described above apply. Requests about this data, including deletion, follow section 9.

Forms in our LinkedIn ads: when you fill in the form of a FlakeDesk ad on LinkedIn, such as the one for the partner program for agencies, LinkedIn gives us the data the form shows and that you confirm when you submit it: first name, last name, email, phone, job title, company and your answers to the form questions. For this form FlakeDesk is the controller: we use this data only to answer your request and talk to you about the subject of the ad, and it enters our own CRM as a contact. The legal basis is your request for information (preliminary procedures related to a contract, art. 7, V, of the LGPD). We do not use this data for any other purpose, we do not sell it and we do not add you to email lists unless you ask. We do not install LinkedIn's ad measurement code (Insight Tag) on the website. Requests about this data, including deletion, follow section 9.

Connected social network data (Marketing module): when an administrator of the customer organization connects a Facebook Page or an Instagram professional account, or when a person connects their own LinkedIn profile, to schedule posts in FlakeDesk, we process:

Through this connection FlakeDesk only publishes, checks that the account is still connected and looks up the status and address of the post it published itself: we do not read messages, comments or metrics. This data is processed on behalf of the customer organization (section 1), which is responsible for the content it schedules and for being authorized to publish on each connected account. FlakeDesk does not write or review the text and images of the posts; when publishing, it only adds the campaign tags to the links, when that option is on, and the formatting escapes the network requires for the text to come out as written.

Technical data: strictly necessary cookies for authentication and session.

Product usage measurement: inside the application we use Google Analytics to understand which screens are used and where the product fails, on the basis of our legitimate interest in improving the service you subscribed to (LGPD, art. 7, IX). We record the screen path with record identifiers already stripped (for example, /contacts/:id instead of the contact number), plus technical browser data. We also record which actions were taken, from a closed list declared in code (for example, "contact created", "reply sent in the inbox"), along with labels that identify no one, such as the channel used or the signup source, and the organization's subscription plan, so we can compare adoption across plans. We do not send your organization's or your user's identifier. We do not send the content of your data, customer names, messages or files. Two actions are sent to Google Analytics by our servers, not by the browser, because they are only confirmed there: the first purchase of a plan (amount, currency, subscribed plan and a verification code derived from the subscription) and the first connection of an organization's official WhatsApp number (only the name of the action). They use the same anonymous Google Analytics browser identifier, are only sent if measurement is on for that device, and carry no user or organization identifier. You can turn this measurement off at any time under Profile → Account → Usage measurement; the choice applies to the device where it was made.

Product usage measurement in the mobile app (Android and iOS): when you use the FlakeDesk app with your account, we measure how it is used through Google Analytics for Firebase, based on legitimate interest (art. 7, IX, of the LGPD). We record which screens you open, without record identifiers, and which actions you take, from a closed list declared in code: signing in, replying to a conversation, creating a lead, moving a funnel stage and asking the assistant. We also record your organization's plan, an anonymous identifier of the app installation, which identifies neither you nor your organization, and technical device data such as the model and operating system version, plus an approximate location (country and region) that Google infers from the masked IP address. Measurement only starts after you sign in, does not use the device advertising identifier and is not used for advertising. We do not send your name, email, phone number, messages or your customers' data. You can turn measurement off at any time in Profile → Usage measurement, in the app; the choice applies to the device where it was made.

Public website audience analysis (only if you allow it): on flakedesk.com we use Google Analytics to learn which pages are visited and Microsoft Clarity to produce heatmaps (where visitors click and how far they scroll) and recordings of how the pages are browsed, in order to improve the site. None of it is loaded before you accept usage analysis in the cookie banner, on the basis of your consent (LGPD, art. 7, I), which you can withdraw at any time through Manage cookies in the site footer. What you type into the site forms (contact, data deletion) is masked in the recordings and never reaches Microsoft; the IP address is truncated by these providers. None of these tools is used inside the authenticated application.

Measuring our ads (public website only, and only if you allow it): when you reach flakedesk.com through a Google ad, the page address carries a click identifier (gclid, gbraid or wbraid). If, and only if, you choose Accept all in the cookie banner, we keep that identifier for up to 90 days in your browser (cookie flakedesk_ads_click) and carry it through to the creation of your account. When an organization subscribes to a paid plan, we tell Google Ads, from our servers, that the click led to a purchase, sending only the amount, currency and time of the purchase and a verification code derived from the subscription (no name, email, organization or plain subscription identifier). The purpose is to measure how our ads perform, based on your consent (LGPD, art. 7, I), which you can withdraw at any time through Manage cookies in the site footer: withdrawing deletes the identifier stored on the site. Once the purchase has been sent, or if the subscription is not completed, we delete the identifier from our records. If you have already created an account, the identifier also stops being used when you turn off measurement under Profile → Account → Usage measurement. Through Google, we do not run remarketing and we do not allow ad personalization: Google's ad_personalization category stays disabled at all times. Inside the authenticated application we do not use advertising cookies, except for the Meta exception described further below.

The campaign that brought you here (public website only, and only if you allow usage analytics): when you reach flakedesk.com through a campaign link, the address may carry four parameters that say where the visit came from: utm_source, utm_medium, utm_campaign and utm_content. If, and only if, you accept usage analytics in the cookie banner (including by choosing Usage analytics only), we keep the parameters of the first page you visit after consenting that carries them, for up to 90 days in your browser (cookie flakedesk_utm, set by flakedesk.com itself and not shared with third parties) and carry them through to the creation of your account. They are campaign labels, limited to letters, numbers and a few symbols, with no personal data. When the account is created, we record these parameters once as the signup source of the organization (not of a person), visible to the FlakeDesk team in our internal panel, so we know which campaigns bring customers, and they are kept for as long as the organization exists. In the application, the source received (these parameters and, if any, the Meta identifiers described below) stays in the browser's local storage (localStorage) for up to 90 days, until it is delivered once to our server, at the first access to the application after signup, and is then deleted from the browser. The basis is your consent (LGPD, art. 7, I), which you can withdraw at any time through Manage cookies in the site footer: withdrawing usage analytics deletes the cookie from your browser. If you have already created the account, turning off measurement under Profile → Account → Usage measurement also makes the app stop storing and delivering this source to our server (the choice applies to the device where it was made; what has already been recorded on the organization remains).

Measuring our ads on Meta, Facebook and Instagram (public website only, and only if you allow it): if, and only if, you choose Accept all in the cookie banner, the site starts loading the Meta Pixel. Choosing Usage analytics only or declining does not load it and sets no Meta cookie. On the site, the Pixel sends Meta only the view of each page: the automatic configuration of events from the elements of the page is turned off. It sets two Meta cookies in your browser: _fbp, which identifies the browser, and _fbc, which identifies the click on a Meta ad (derived from the fbclid parameter in the address). When you go on to sign up, we carry these two identifiers through to the creation of your account at app.flakedesk.com. Inside the application, the Pixel is loaded once, at the first access to the application after signup, only to record the completed signup, and only if the identifiers were recorded on the organization and the Meta integration is active (this is the only exception to the rule that the application uses no advertising cookies). On that access the application loads Meta's script (fbevents.js) and keeps in the browser's local storage (localStorage, key flakedesk.metaPixelFired, with no expiry) only the event code, so the signup is not sent twice; that marker stays until you clear the browser data. Because the Pixel is a request made by your browser to Meta, not a submission from our servers, on that access Meta receives, as with any page that loads its script, the IP address, the user agent, the address of the application page being shown (at the first access, / or /admin/organization?checkout=<plan>&cycle=<cycle>), the referring page (referrer) and the _fbp cookie, among other technical browser data. The script reads that cookie, which sits on the .flakedesk.com domain and is shared with the site, and, if it does not exist, creates one. If you turned off usage measurement under Profile → Account → Usage measurement, the Pixel is not loaded in the application.

When the account is created and the Meta integration is active, we store on the organization (not on you as a person) these two identifiers and the browser's technical identifier (user agent), and we tell Meta, from our servers (Conversions API), about three events: the completed signup (the same one the Pixel records, sent with the same code so that Meta counts it only once), the first official WhatsApp number connected and the first purchase of a plan. Each submission made by our servers carries only: the name of the event, the moment it happened, an event code, the application address without parameters (https://app.flakedesk.com/), the source type (website), Meta's browser identifiers (_fbp and _fbc), the browser's technical identifier (user agent, the full text, which includes the operating system and version), an external identifier (which represents the organization to Meta) and, for the purchase, the amount and currency. The event code and the external identifier are codes derived from the organization's internal number (and, for the purchase, from the subscription's) by a SHA-256 cryptographic hash, without name, e-mail or phone number. We never send e-mail, phone number, name or IP address in these submissions made by our servers, and the Pixel and the Conversions API do not receive contacts, messages or your customers' data. (The Pixel, on the site and in the application, is a request your browser makes directly to Meta, not a submission from our servers: as on any page that loads Meta's script, Meta receives technical data such as the IP address in that communication. The promise above applies to the submissions made by our servers.)

Meta uses this data to measure the results of ads and may use it to build audiences for ads, under Meta's own policies. The basis is your consent (LGPD, art. 7, I), which you can withdraw at any time through Manage cookies in the site footer: when you stop choosing Accept all (by switching to Usage analytics only or Decline), _fbp and _fbc are deleted and the page is reloaded, which removes the Pixel from it. Note: withdrawing does not undo what has already been recorded on the organization. Those identifiers can still be used in the server submissions (signup, WhatsApp and purchase) until they are deleted, which happens after the attempt to send the first purchase to Meta, whatever the result, including if the submission fails, and, in any case, within 90 days of being stored, by a daily routine. Deleting a user's account does not delete them earlier, because they sit on the organization and identify only a browser (see section 10). If you have already created the account, turning off measurement under Profile → Account → Usage measurement makes the app stop delivering these identifiers to our server; what has already been recorded on the organization follows the period above.

3. How we use the data

Legal bases (LGPD, art. 7): performance of a contract, legitimate interest (security, fraud prevention, and service improvement), compliance with legal obligations, and consent, where applicable.

4. Data sharing

We do not sell personal data. We share data only with:

5. Google Workspace data (Limited Use)

When you connect your calendar, FlakeDesk requests a single scope — https://www.googleapis.com/auth/calendar.events — required to create, update and display the events tied to your follow-ups. We do not request access to other calendars, we do not list your calendars and we do not query your availability.

The use of raw or derived user data received from Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements.

6. International transfer

Data may be processed on servers located outside Brazil (currently the United States, via Google Cloud). Data sent to Meta (Pixel and Conversions API) is processed by Meta on its own servers, which may be outside Brazil, including in the United States, under Meta's policies. We adopt appropriate contractual and technical safeguards, pursuant to articles 33 et seq. of the LGPD.

7. Security

8. Retention and deletion

We keep personal data only for as long as necessary for the purposes of this policy, the customer organization's instructions, and legal obligations. Upon termination of the contract with the customer organization, data is deleted or anonymized within the agreed timeframes, except for retention required by law.

Documents uploaded by the organization (proposals, contracts, receipts, and other files) are kept in FlakeDesk's storage (Google Cloud, us-east1 region), accessible only to authorized people within the same organization. A deleted document stays in the trash for 30 days before permanent deletion. Deleting a user's account does not delete the organization's documents: they are the organization's data, not the individual user's.

Signup source and Meta identifiers: the Meta browser identifiers stored on the organization are deleted after the attempt to send the first purchase to Meta, whatever the result, and, in any case, within 90 days of being stored (section 2). The campaign parameters of the signup source are kept for as long as the organization exists.

Social network connections and posts (Marketing):

Requests about this data follow section 9 and can be sent to info@flakedesk.com.

Contacts received through the forms in our ads: they stay in our CRM while the conversation is ongoing and are deleted within 12 months after the last contact, unless they become a partnership or a contract. The spreadsheet downloaded from LinkedIn is deleted after the data enters the CRM. You can ask for deletion earlier, at any time (section 9).

9. Your rights (LGPD, art. 18)

You may request: confirmation of processing, access, correction, anonymization, blocking or deletion, portability, information about sharing, and withdrawal of consent.

10. How to delete your data

You can request deletion of your account and personal data at any time, through two paths:

What is deleted

Your account, profile (including your profile picture and the files you attached to feedback), access credentials, sessions, calendar connections (Google/Outlook), the personal LinkedIn profile you connected to Marketing (with its identifier and token), your conversations with the AI assistant, the assistant's memory, notifications, feedback and personal preferences. Where your e-mail address appeared in records that remain (invitations, access requests, the history of e-mails sent to you), it is removed or replaced by an anonymous marker.

Where your name appeared in Marketing, as the label of your personal LinkedIn profile in the post history or in the text of the approval-request notices you generated for colleagues, it is replaced by an anonymous marker or the text of the notice is removed.

What remains, and why

Timelines

Deletion happens 15 days after confirmation. During that period you can cancel through the emailed link or in the app. Once completed, we email you a record of it. Backup copies are overwritten in the normal retention cycles, within 30 days.

One exception

If you are the only admin of an organization that has other members, deletion stays pending until another person is promoted to admin. Otherwise, your colleagues would lose access to the company account's administration. We email you when this happens. Your deletion right stands: this is only sequencing.

11. Children and adolescents

FlakeDesk is intended for professional use and is not directed at persons under 18 years of age.

12. Changes to this policy

We may update this policy periodically. The current version will always be publicly available, with the update date at the top. Relevant changes will be communicated through the platform's channels.

13. Contact

FlakeDesk · FLAKEDESK INOVA SIMPLES (I.S.)
CNPJ 69.481.905/0001-27
Alameda Rio Negro, 503, Suite 2020, Alphaville, Barueri/SP, Brazil, ZIP 06454-000
Data Protection Officer (DPO) email: info@flakedesk.com
Website: https://flakedesk.com