QuickDash
PrivacyTermsData deletionPT

Quickdash Privacy Policy

Last updated: November 22, 2026

This Privacy Policy explains how Quickdash (quickdash.app) collects, uses, stores, shares, and protects personal data, including data obtained through the APIs of the advertising platforms that an agency connects to the service. It follows Brazilian Law No. 13,709/2018 (General Data Protection Law — LGPD) and the data policies of each platform, detailed in Section 16.

1. Who we are

Quickdash is operated by FELIPE VILELA BILITARDO, a Brazilian sole proprietorship (MEI) registered under CNPJ No. 41.161.862/0001-83, with the trade name FVB CIENCIA DE DADOS, which offers the service under the Quickdash brand (“Quickdash”, “we”, “us”).

  • Address: Jacareí, SP, Brazil
  • Contact and Data Protection Officer email: contato@quickdash.app
  • Data Protection Officer (encarregado under the LGPD): Felipe Vilela Bilitardo, reachable at the email above

2. What Quickdash does and how it handles advertising data

Quickdash is a white-label dashboard software-as-a-service (SaaS) for media agencies. Each customer agency has its own environment (tenant), accessed on a subdomain (for example, acme.quickdash.app) and carrying the agency’s brand. In that environment, agency users connect their clients’ ad accounts, with authorization granted on the platform itself, and follow the metrics in dashboards.

The integrations covered by this Policy are:

  • Meta Ads (Facebook and Instagram), through the Meta Marketing API;
  • Google Ads, through the Google Ads API;
  • TikTok Ads, through the TikTok API for Business (Marketing API);
  • LinkedIn Ads, through the LinkedIn Advertising API (Marketing Developer Platform).

Each integration is used only when the agency connects and authorizes it. The permissions requested on each platform are listed in Section 16. Google Analytics 4 is a future integration: it is not yet available and will be enabled only after this Policy is updated to describe it.

At this stage, access to the platforms is read-only: Quickdash does not create, change, pause, or delete campaigns, ads, budgets, or settings in the connected accounts. If this changes, this Policy will be updated beforehand.

How advertising data is handled:

  • On-demand queries. Quickdash queries the platforms’ APIs when a dashboard needs to be built. It does not copy campaign performance data into a data warehouse or analytical database.
  • Temporary cache. To display dashboards quickly and stay within the APIs’ usage limits, Quickdash may keep already aggregated metrics in memory for about 30 minutes. This cache expires on its own and is not written to a database. Users can request a manual refresh, subject to a minimum interval between refreshes.
  • What is stored. The Quickdash database stores: the access tokens of the authorizations (encrypted); metadata about the connected accounts (for example, identifier, name, currency, time zone, account status, the business portfolio or equivalent structure it belongs to, and its link to the agency’s client); the data of the agency’s account and its users; and operational records of the service itself, described in Section 4.

3. LGPD roles: controller and operator

  • The agency that is Quickdash’s customer is the controller of the data in the ad accounts it connects and of its own clients’ (advertisers’) data, including any personal data those accounts may contain. The agency determines the purposes of processing and must have a legal basis vis-à-vis data subjects and the advertisers it represents.
  • Quickdash is the operator (processor) of that data: it processes the data on the agency’s behalf and according to its instructions, in order to provide the contracted service (connecting the accounts, querying the metrics, and displaying them in dashboards).
  • Quickdash is the controller only of the data it processes to create and manage the agency’s and its users’ accounts (registration, authentication, billing, and service-usage records).

If you are an advertiser or a data subject whose information appears in a dashboard, please direct requests for information or deletion first to the agency that operates that dashboard. Quickdash will assist the agency, as operator, as described in Sections 10 and 11.

4. Data we process

We process only what is needed to provide, protect, and improve the service, within the limits of this Policy.

4.1 Account and authentication data (Quickdash as controller)

  • name and email address of agency users, and their authentication credentials and identifiers;
  • tenant data (agency name, subdomain, and brand settings such as logo, colors, and typography), user roles, permissions, and invitations;
  • records of the agency’s clients in Quickdash (for example, name and display settings);
  • billing and contract data, where applicable;
  • support communications sent to contato@quickdash.app.

Authentication is provided by Google Firebase Authentication (Identity Platform), in multi-tenant mode.

4.2 Advertising platform connection data (Quickdash as operator)

When an agency user connects a platform, we store:

  • the access tokens (and, where the platform issues them, refresh tokens) granted in the authorization, in encrypted form;
  • the identification of which Quickdash user made the authorization and when, so we can show who authorized each connection and allow it to be managed or revoked;
  • account metadata for the accounts accessible through the authorization and the accounts linked by the agency: identifiers, names, currency, time zone, status, the business portfolio, manager account, or Business Center they belong to, and their link to the agency’s client;
  • temporary authorization (OAuth) flow states, which expire and serve only to complete the connection securely.

4.3 Performance data queried on demand

To build the dashboards, Quickdash queries the APIs, for the authorized accounts, for performance metrics and dimensions such as impressions, reach, clicks, spend, conversions, and the names and identifiers of campaigns, ad groups or ad sets, and ads. This data is displayed to authorized users and may be held in the temporary cache described in Section 2. It is not written to the Quickdash database.

Platform reports are aggregated. Quickdash does not collect personal data about the people who see or click on the ads.

4.4 Operational, usage, and security records

  • tenant activity events (for example, who connected or revoked an account, or linked an account to a client) and notifications to users, along with their preferences;
  • technical access and error logs, such as IP address, browser, date and time, route accessed, and technical identifiers of accounts and API calls, used to operate the service, prevent abuse, and diagnose failures.

4.5 What we do not collect

Quickdash does not request sensitive personal data (LGPD, art. 5, II) or data about children or adolescents. It does not access messages, posts, custom audiences, payment data of the ad accounts, or any data other than that described in this Policy.

5. Purposes and legal bases

PurposeLegal basis (LGPD)Data involved
Create and manage accounts, authenticate users, and provide the service, including white-label dashboardsPerformance of a contract (art. 7, V)Account data (Section 4.1)
Connect Meta, Google Ads, TikTok Ads, and LinkedIn Ads accounts, query metrics, and display them to the agency, as operatorPerformance of the contract with the agency (art. 7, V); the agency, as controller, must have its own legal basisSections 4.2 and 4.3
Show who authorized each connection, alert about expired or failing authorizations, and record tenant activityPerformance of a contract (art. 7, V) and legitimate interest (art. 7, IX)Sections 4.2 and 4.4
Security, fraud and abuse prevention, and failure diagnosisLegitimate interest (art. 7, IX) and compliance with a legal obligation, where applicableSection 4.4
Comply with legal, regulatory, and tax obligationsCompliance with a legal obligation (art. 7, II)Registration, contract, and tax data
Support and operational communications about the servicePerformance of a contract (art. 7, V)Account contact data

Data obtained from the platforms is used only for these purposes. It is not sold, not used for advertising, not used to build profiles of individuals, and not used to train artificial intelligence models.

6. Sharing and subprocessors

We do not sell or rent data. It is shared only:

  • with the agency itself and the users it authorizes, within the tenant and the dashboards it manages (including users from the agency’s clients, when the agency grants them access);
  • with subprocessors that provide the service’s infrastructure, under contract and only for the purposes of this Policy;
  • with authorities, when required by law or court order, or to protect rights and the security of the service;
  • in a corporate reorganization (merger, acquisition, or sale of assets), with equivalent protection and, for data obtained from Google APIs, only with the user’s prior, explicit consent.

Subprocessors:

FunctionProviderProcessing location
Application hosting (Cloud Run), database (Cloud SQL for PostgreSQL), key and secret storage (Secret Manager), DNS, and technical logsGoogle Cloud PlatformUnited States (us-central1 region) and other locations where the provider operates
Authentication and identity managementGoogle Firebase Authentication (Identity Platform)United States and other locations where the provider operates
Transactional and contact emailZoho MailUnited States and other locations where the provider operates

This list will be updated if new providers are engaged. The advertising platforms (Meta, Google Ads, TikTok, and LinkedIn) are not Quickdash subprocessors: they are independent platforms that hold the accounts the agency manages and connects to the service.

7. International transfers

Quickdash is operated from Brazil, and the infrastructure described in Section 6 is located in the United States. There is therefore an international transfer of data, which relies on a valid mechanism under art. 33 of the LGPD — in particular, the contractual clauses and data protection safeguards offered by the providers themselves — and on safeguards consistent with this Policy and with the platforms’ policies.

8. How long we keep data

  • Account data: while the account is active. After closure, it is deleted or anonymized within 30 days, unless the law requires retention (for example, tax records, generally for 5 years).
  • Access tokens: while the authorization is active. When the authorization is revoked in Quickdash or on the platform, or expires, the token is no longer used. It is deleted upon a deletion request or upon account closure, within 30 days.
  • Account and connection metadata, activity events, and notifications: while the agency’s account is active, or until a deletion request, after which they are deleted within 30 days.
  • Temporary metrics cache: about 30 minutes, in memory.
  • Technical and security logs: 90 days, unless needed for an incident investigation or required by law.
  • Temporary authorization (OAuth) states: only for as long as needed to complete the flow.

When these periods end, data is deleted or anonymized, except where retention is permitted by law. Aggregated, de-identified data that cannot be associated with an individual may be kept for internal operations.

9. Security

We adopt appropriate technical and administrative measures to protect data against unauthorized access and against accidental or unlawful destruction, loss, alteration, or disclosure, including:

  • all communication with the service uses encrypted connections (HTTPS/TLS);
  • access tokens are encrypted in the database (PostgreSQL with pgcrypto), and the encryption key is kept in Google Cloud Secret Manager, separate from the database;
  • tokens are used only on the server and are never sent to the browser;
  • each tenant is isolated, and each user can access only what their role and permissions allow;
  • authentication is handled by a managed identity provider (Firebase Authentication);
  • security monitoring and logging.

No system is entirely free of risk. In the event of a security incident that may result in relevant risk or harm to data subjects, we will take the measures required by the LGPD, including notifying the ANPD and data subjects where required.

10. Data-subject rights

Under the LGPD, you may request: confirmation that processing takes place; access to the data; correction of incomplete, inaccurate, or outdated data; anonymization, blocking, or deletion of unnecessary or excessive data or data processed unlawfully; portability, where applicable; deletion of data processed on the basis of consent; information about whom the data has been shared with; information about the possibility of withholding consent and its consequences; withdrawal of consent; and objection to unlawful processing. Quickdash does not make solely automated decisions that affect data subjects’ interests.

To exercise these rights regarding your Quickdash account, write to contato@quickdash.app. We respond within 15 days, unless a different legal deadline applies.

For data in ad accounts connected by an agency, Quickdash is the operator: please also send your request to the controlling agency. We will assist the agency in handling it.

11. How to revoke access and request deletion

Revoking access. An authorization can be revoked at any time:

  • in Quickdash itself, in the tenant’s connections area; or
  • in the connected-apps settings of the platform. The steps for each one are in Section 16 and on the Data deletion page.

After revocation, Quickdash can no longer access the accounts covered by that authorization. Because performance metrics are not stored in the database, after revocation no performance data from those accounts remains in Quickdash other than the temporary cache, which expires in about 30 minutes.

Requesting deletion. Email contato@quickdash.app with the subject line “Data deletion”, stating the account email, the tenant, and the platform or account involved. We confirm the request and complete deletion within 30 days, unless the law requires a record to be retained. Depending on the request, deletion covers the user account or the tenant, the tokens, the connection metadata, and any cached data. Full instructions are on the Data deletion page.

12. Cookies and similar technologies

We use only strictly necessary cookies and local storage for authentication, session, security, and dashboard functionality, on the quickdash.app domain and on tenant subdomains. We do not use advertising or behavioral analytics cookies. If we start using them, we will update this section and ask for consent where the law requires. You can control cookies in your browser, but blocking the necessary ones may prevent you from signing in.

13. Children and adolescents

Quickdash is a B2B service for agencies and their professionals. It is not intended for anyone under 18, and we do not knowingly collect data from children or adolescents. If we become aware of an improper registration, we will delete the account and the data.

14. Changes to this Policy

We may update this Policy, for example when enabling a new integration or permission. The current version is always available at quickdash.app, with the date of the last update at the top. If there is a material change in how data from a platform is accessed, used, stored, or shared, we will notify users through their accounts and, where required, ask for a new authorization before applying it.

15. Contact

  • Email: contato@quickdash.app
  • Data Protection Officer: Felipe Vilela Bilitardo
  • FELIPE VILELA BILITARDO — CNPJ 41.161.862/0001-83 — trade name FVB CIENCIA DE DADOS — Quickdash brand
  • Address: Jacareí, SP, Brazil

Brazil’s National Data Protection Authority (ANPD) is the body responsible for enforcing the LGPD: gov.br/anpd. This Policy is governed by the laws of the Federative Republic of Brazil.

16. Platform-specific requirements

Each platform has its own rules on the use of data obtained through its APIs. Below are the permissions Quickdash requests on each one, what they are for, the specific commitments we follow, and how to revoke access. The permissions requested must match those shown on each platform’s authorization screen. At this stage, none of them is used to create or change campaigns.

16.1 Meta (Facebook and Instagram Ads)

Permissions requested, through Meta’s OAuth authorization:

  • ads_read — read performance reports (Ads Insights) for the authorized ad accounts;
  • business_management — list the business portfolios (Business Managers) and ad accounts that the authorization gives access to, so the agency can choose which ones to link to each client. Quickdash does not change anything in the Business Manager.

Quickdash does not request any other Meta permissions and does not store profile data from the Meta account of the person who authorizes: the authorization is associated with the Quickdash user who made it.

Data obtained from Meta (Platform Data) is handled in accordance with the Meta Platform Terms and the Developer Policies. It is used only for the purposes of this Policy; it is not sold, not used for advertising, not used to build profiles of individuals, and not used to train artificial intelligence models; and it is shared only as described in Section 6. We delete Platform Data when the user or the agency requests it, when the Quickdash account is closed, when it is no longer necessary for a legitimate purpose, when Meta requests it, or when the law requires it, except where retention is required by law.

Data deletion: see the Data deletion page.

Revoking access: on Facebook, under Settings > Business integrations or Apps and websites, remove Quickdash.

16.2 Google Ads

Scope requested (Google OAuth 2.0):

  • https://www.googleapis.com/auth/adwords — access to the Google Ads API. It is the only scope for this API and, as defined by Google, it allows both reading and writing; there is no read-only version. At this stage, Quickdash uses only read queries (accounts, campaigns, and reports, through the API’s search services) and makes no changes to the accounts.

With this authorization, we store the tokens (encrypted) and the account metadata, including for the manager account (MCC) and the account hierarchy, as described in Section 4.2. Metrics are queried on demand, as described in Section 4.3.

Limited Use. Quickdash’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. These requirements apply to raw data and to aggregated, anonymized, or derived data. In particular:

  • the data is used only to provide or improve user-facing features that are visible and prominent in the Quickdash user interface — displaying metrics from the authorized Google Ads accounts in the agency’s dashboards;
  • we do not transfer the data to third parties, except as necessary to provide or improve those features (and with the user’s consent), for security purposes (for example, investigating abuse), to comply with applicable law, or as part of a merger, acquisition, or sale of assets, with the user’s prior, explicit consent;
  • we do not use or transfer the data to serve ads, including personalized, retargeting, or interest-based advertising;
  • we do not sell the data and do not transfer it to advertising platforms, data brokers, or information resellers;
  • we do not use the data to determine creditworthiness or for lending purposes;
  • we do not use the data to develop, train, or improve generalized artificial intelligence or machine learning models, including foundation models;
  • we do not allow humans to read the data, unless we have the user’s affirmative agreement for specific messages or data, it is necessary for security purposes (for example, investigating abuse), it is necessary to comply with applicable law, or the data (including derivations) is aggregated and anonymized and used for internal operations in accordance with applicable law.

Use of the Google Ads API also follows the Google APIs Terms of Service and the Google Ads API Developer Policies. If Quickdash starts using Google data in a new way or for a different purpose, we will update this Policy and ask for new consent beforehand.

Revoking access: at myaccount.google.com/permissions, remove Quickdash’s access.

16.3 TikTok Ads

Permissions requested (TikTok API for Business):

  • Consolidated Report (Reporting) — read performance reports for the authorized advertiser accounts;
  • Read Business Center (read-only) — list the Business Centers and advertiser accounts that the authorization gives access to, so the agency can choose which ones to link to each client.

At this stage, Quickdash does not request permissions to create or manage campaigns, nor the “TikTok Accounts” permission (organic accounts). The authorization is associated with the Quickdash user who made it.

Data obtained from TikTok is handled in accordance with the terms and developer policies of the TikTok API for Business, accepted during authorization. It is used only for the purposes of this Policy and is not sold or used for advertising.

Revoking access: in TikTok for Business, in the app authorization settings of the ad account or Business Center, remove Quickdash. After revocation, the token is no longer valid.

16.4 LinkedIn Ads

Permissions requested (LinkedIn OAuth, Advertising API):

  • r_ads — read the ad accounts that the authorizing member has access to;
  • r_ads_reporting — read performance reports (Ad Analytics) for those accounts.

If LinkedIn requires the basic profile permission (r_basicprofile) for this flow, it will be used only to identify the member who authorized the connection, and for no other purpose. Quickdash does not use the Advertising API to collect member profile data or to enrich sign-in.

Data obtained from LinkedIn is handled in accordance with the LinkedIn Marketing API Program Terms and the Advertising API use restrictions. It is used only for the purposes of this Policy and is not sold or used for advertising.

Revoking access: on LinkedIn, under Settings > Data privacy > Authorized applications, remove Quickdash. Ad account administrators in Campaign Manager can also remove the authorizing member’s access.

16.5 Google Analytics 4 (future integration)

Quickdash does not yet request Google Analytics scopes or access Google Analytics 4 data. This integration will be enabled only after this Policy is updated to state what data will be accessed, how it will be used, and which permissions will be requested.

QuickDash © 2026 · FELIPE VILELA BILITARDO · CNPJ 41.161.862/0001-83 · Jacareí - SP

contato@quickdash.app

PrivacidadeTermosExclusão de dados

PrivacyTermsData deletion