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.
- For platform user account data (name, email, access credentials), FlakeDesk acts as the controller.
- For data entered or received by customer organizations (contacts, companies, messages, attachments), FlakeDesk acts as the processor, handling data according to the instructions of the customer organization, which is the controller.
2. Data we collect
Account and platform usage data:
- Name, email, profile picture, and login method (Google, Microsoft, or email/password);
- Language, preferences, and access records (IP address, date/time, session identifiers);
- Audit logs of actions performed on the platform.
CRM data (processed on behalf of the customer organization):
- Registered contacts and companies: name, email, phone, role, company, notes, tags, and custom fields;
- Interaction history, follow-ups, pipelines, and attached documents.
WhatsApp message data (official Meta WhatsApp Business Platform integration):
- Phone number, profile name, message content, and media sent/received in conversations between you and the customer organization;
- Delivery metadata (sent, delivered, read).
- History imported from the WhatsApp Business app: when a customer organization connects the WhatsApp Business app to FlakeDesk, it authorizes Meta to send us up to 6 months of one-to-one conversation history and the number's contact list. We treat this content like the organization's other messages: the same retention, deletion and access rules apply, and it can be removed at the request of the controlling organization or of the data subject.
- Voice message transcription: voice messages you send to the customer organization over WhatsApp are automatically transcribed into text by the platform's artificial intelligence provider (Google Cloud Vertex AI, described below), so the team can read what was said without listening and the virtual support assistant can understand the request. The transcript is stored with the conversation and follows the same retention, deletion and access rules as the messages. The customer organization can turn the feature off, and it is also off when the organization disables artificial intelligence in the settings.
Chat widget data on customer websites:
- Name, email address, WhatsApp number, and message voluntarily provided by you in the chat form on the customer organization's website.
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:
- The connection: the account identifier and name, the connection date, its validity (when the social network provides it) and its status (active, needs reconnecting or disconnected) and, for a personal LinkedIn profile, who connected it. The access token the social network gives us is stored encrypted, never shown on screen and never written to technical logs;
- On LinkedIn, only the member identifier that LinkedIn reports at authorization and the token. The name the profile shows in FlakeDesk is the person's own name in their FlakeDesk registration, which they can edit. We do not store the e-mail address, the photo or the name that LinkedIn reports, and we do not read likes, comments or any other LinkedIn activity;
- The posts: text, images (JPEG, PNG or GIF) with the alternative text of each one or a video (MP4 or MOV, only for Instagram and the Facebook Page) with the measurements read from the file (duration, width, height and format), chosen networks and the text specific to each network, scheduled date, time and time zone, campaign name, the option to tag the links in the text, the post status, who created it, who approved it and when, the reason for a refusal and, after the attempt to publish, the result on each network (address and identifier of the published post, error code and number of attempts);
- Notices: in-app notifications and e-mails to the people involved (whoever created the post, whoever approves posts and whoever administers the account), about a post that did not go out, an approval request or decision, and a connection that needs renewing. They carry the account name, the reason and, in approval requests, the name of the person who asked, not the text of the post.
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
- To provide, operate, maintain, and improve the platform;
- To authenticate users and protect accounts;
- To enable customer service via WhatsApp and other channels on behalf of customer organizations, including creating contact records (leads) from received messages;
- To publish, on the social networks the customer organization connected (Facebook, Instagram and LinkedIn), the posts its team writes and schedules in Marketing, at the time it chose, and to tell the team the result. We only publish what a person in the organization wrote and scheduled, and we do not use this data for any other purpose. LinkedIn member data is not used for advertising, is not sold and is not used to enrich contact records;
- To send operational platform notifications;
- To offer artificial intelligence features (team assistant, insights, summaries, WhatsApp voice message transcription and support chatbot), processing only the data necessary for the requested functionality. The organization administrator can disable the assistant and voice message transcription at any time in the settings;
- To answer people who ask for information through the forms in our ads, such as the one for the partner program for agencies;
- To comply with legal and regulatory obligations and exercise rights in legal proceedings.
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:
- Meta Platforms (WhatsApp Business Platform): for sending and receiving WhatsApp messages; processing by Meta is governed by Meta's own policies;
- Meta Platforms (Facebook and Instagram), in Marketing: to publish the posts on the connected Pages and professional accounts, we send the text and the images or the video of the post. Meta downloads each image, and the video meant for Instagram, from a temporary address generated by FlakeDesk, which stops working after 2 hours; the video meant for the Facebook Page is sent directly from FlakeDesk to Meta. To give the network time to prepare the video, it is sent up to 20 minutes before the scheduled time and stays unpublished until that time; if the post is canceled before then, we ask Meta to delete the not yet published video on the Facebook Page, and the Instagram one expires on its own at Meta within 24 hours. Processing by Meta is governed by Meta's own policies;
- LinkedIn Corporation, in Marketing: to publish on the connected personal profile, we send the text and the images of the post, directly from FlakeDesk to LinkedIn; processing by LinkedIn is governed by LinkedIn's own policy;
- LinkedIn Corporation, in our ads: we receive from LinkedIn the data of the ad forms described in section 2; LinkedIn also keeps a copy of the answers, and its processing follows LinkedIn's own policy;
- E-mail delivery provider (Resend): delivers the platform's e-mails, such as account verification, invitations and notices, including the Marketing notices about a post that did not go out or an account that needs reconnecting. It receives the recipient's address and name and the text of the message, which in those notices carries the account name and the reason, never the text of the post;
- Meta Platforms (Pixel and Conversions API, only after you choose Accept all in the cookie banner): Facebook and Instagram, to measure the results of our ads and, under Meta's own policies, build audiences for ads, limited to the data described in section 2;
- Infrastructure providers: Google Cloud Platform (hosting, database, and file storage), with data encrypted in transit and at rest;
- Artificial intelligence provider: Google Cloud (Vertex AI), under FlakeDesk's account, for the AI features included in the plans. The data sent (excerpts of contacts, companies, interactions and messages needed for the question, and the audio of voice messages to be transcribed) is not used to train models. Voice message transcription always uses this provider, even when the organization connects its own AI provider. If the organization chooses to connect its own AI provider (OpenAI, Anthropic or a compatible endpoint), processing by that provider is governed by the agreement between the organization and the provider;
- Login and calendar providers (when you connect them): Google and Microsoft, limited to the purposes you authorize;
- Public website analytics providers (only after you accept in the cookie banner): Google (Google Analytics) and Microsoft (Clarity), limited to the audience and browsing of the public pages, with forms masked;
- AI providers (when enabled by the customer organization): only the content necessary for the functionality, according to the organization's configuration;
- Public authorities, when required by law or court order.
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.
- No calendar data reaches any AI model. We do not use, transfer or sell this data to create, train or improve foundational or generalized AI or machine learning models, our own or third-party. The FlakeDesk assistant's tools read only contacts, companies, interactions and the organization's own knowledge base;
- Your events are not stored. They are read live from your account for display on the calendar screen and are never persisted in our databases;
- The authorization is revocable. The token is stored encrypted and bound to your user; you can disconnect at any time from your Profile, which also removes the connection.
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
- Encryption in transit (TLS) and at rest;
- Integration credentials (such as WhatsApp tokens) stored encrypted;
- Logical data isolation per organization (multi-tenant);
- Role-based access control, audit logging, and the principle of least privilege;
- Private file storage with authenticated and authorized access;
- Access tokens of the social networks connected to Marketing stored encrypted, never shown on screen and never written to technical logs; post images and videos kept in private storage, delivered only to people authorized in the organization or to the social network, through a signed temporary address or by direct upload from FlakeDesk to the network;
- Antivirus scanning of every uploaded document, performed on our own infrastructure (the file is not shared with third parties); files with threats are refused and never stored;
- Optional two-step verification at sign-in, with an authenticator app code and recovery codes; the app secret is stored encrypted and recovery codes only in a non-reversible form.
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):
- When you disconnect an account under Marketing → Connected accounts, we delete the access token right away, cancel what was scheduled for it and stop using it. The account name stays in the post history, so the organization knows where each post went out. The account record, with its identifier, is kept while the account stays disconnected; if another organization later connects that same account, the old record is deleted and only the name remains in the post history. Disconnecting in FlakeDesk does not remove FlakeDesk from the list of authorized apps on your social network account: to do that, use the settings of the network itself;
- Posts (drafts, scheduled, canceled and failed) stay until the organization deletes them. When a post is deleted, its text is erased and its images are removed from our storage right after, and this cannot be undone; if removing a file fails, we log the failure and the file may remain in private storage, shown on no screen, until the organization's data is deleted as described at the start of this section. A post that was already published on a network cannot be deleted in FlakeDesk: its text, images and result stay in the organization's history, subject to the retention described at the start of this section, and FlakeDesk never deletes or edits the post on the social network (to do that, use the network itself);
- Images that were uploaded and never used in a post are erased automatically after 24 hours;
- Videos are kept for 30 days after the post's last activity (the last edit, scheduling, publication, failure or cancellation of the post or of any of its networks), and this period only runs once no network of the post is still waiting to go out. After that, the video file is erased from our storage; the post stays in the organization's history with its text, the file measurements and a note that the video was removed, and the published video stays on the social network. If the post is deleted earlier, the video is removed like the images. Videos that were uploaded and never used in a post are erased automatically after 24 hours;
- Storage backup: erased images and videos (through the periods above or the deletion of the post) can still be recovered by us for up to 7 days, to fix a deletion made by mistake, and are then permanently eliminated;
- Deleting a user's account deletes the personal LinkedIn profile that user connected, with the identifier and the token, and cancels the posts that were still going out through it; the user's name, which was the label of that profile in the post history, is replaced by an anonymous marker. The posts and images stay with the organization, unlinked from the deleted account (section 10).
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.
- If you are a platform user, contact us directly through the channels below.
- If you are a contact/customer of an organization that uses FlakeDesk (e.g., you talked to a company via WhatsApp or its website chat), please direct your request preferably to that organization, which is the controller of your data; we will support the handling of your request.
10. How to delete your data
You can request deletion of your account and personal data at any time, through two paths:
- Without needing the app: through the page Delete my data. Enter your account email and we send a confirmation link.
- Inside FlakeDesk: under Profile → Account → Delete account.
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
- Contacts, companies, interactions and customer conversations belong to the organization using FlakeDesk. It is the controller of that data, and you operated it as its representative. Those records stay with the organization, unlinked from your account (without identifying you as the owner). To request their deletion, the request must go to the organization itself.
- Marketing posts and their images also belong to the organization: they stay with it, unlinked from your account (you no longer appear as author or approver). The names of the organization's Facebook Pages and Instagram accounts stay in the post history, because they are the organization's business accounts; the label of your personal LinkedIn profile, which is your name, does not stay: it is replaced by an anonymous marker. To request their deletion, the request must go to the organization itself.
- Audit records and tax/accounting obligations are retained for the legal periods (LGPD art. 16) and then erased. The personal identifier is removed at deletion time.
- Signup source and Meta identifiers are stored on the organization, not on your account: campaign parameters are labels that do not identify a person and stay with the organization for as long as it exists, and Meta's browser identifiers (
_fbpand_fbc) identify only a browser. Those identifiers follow the period in section 2 (deleted after the attempt to send the first purchase to Meta, whatever the result, and within 90 days of being stored) and deleting your account does not delete them earlier.
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