Privacy Policy

Last updated: November 17, 2026

This Privacy Policy explains how TrafficOS (http://traffic.inspiratoridigital.com.br) collects, uses, shares and protects personal data and advertising-account data. TrafficOS is a paid-traffic management platform used by media buyers and agencies to monitor, analyze and optimize campaigns on Google Ads and Meta Ads (Facebook and Instagram).

The data controller is Inspiratori Digital, CNPJ (Brazilian tax ID) 32.797.561/0001-50 (“we”, “us”). Privacy contact: traffic.os2026@gmail.com. We process data in accordance with the Brazilian General Data Protection Law (LGPD, Law 13,709/2018) and, where applicable, other data-protection laws.

1. Roles: who decides about the data

When you (an agency or media buyer) connect ad accounts and enter clients, campaigns, reports and other content, you are the controller of that data and we act as a processor, handling it only to provide the contracted service and on your instructions. For your own user-account data (login, role, security logs) we are the controller.

Access to TrafficOS is by invitation from an organization administrator; there is no open public sign-up.

2. What data we collect

  • Account data: name, email, profile picture (when you sign in with Google), access role in the organization, last-seen date. If you sign in with email and password, the password is stored only as a hash by the authentication provider — never in readable form.
  • Advertising-account data (Google Ads and Meta Ads), obtained through the official APIs after you authorize the connection: account IDs and names, currency and time zone; campaigns, ad groups/ad sets, ads, keywords, audiences and placements; search terms; performance metrics (impressions, clicks, cost, conversions, ROAS, CPA, etc.) and the history of changes made through TrafficOS.
  • Access credentials (OAuth tokens) for the advertising accounts. They are kept in a locked table that only the server can read and are encrypted with AES-256-GCM. They are never shown in the interface or sent to the browser.
  • Content you enter: clients (name, segment, goals, budget, average ticket, margin and close rate), diagnoses, audiences, plans, reports, learnings, case studies, comments and historical spreadsheets you import.
  • Technical and security records: an audit log of sensitive actions (who did what and when), IP address and browser data in the hosting access logs, and error messages.
  • Cookies: we use only strictly necessary cookies to keep your session authenticated. We do not use advertising cookies, behavioral analytics or third-party trackers.

We do not collect end-consumer data of your clients (for example, lead or email lists). Search terms shown in Google Ads reports may contain personal information typed by search users themselves; they are used only for performance analysis (for example, suggesting negative keywords).

3. Google user data

TrafficOS uses Google in two distinct situations:

  • Sign in with Google (optional): we receive your name, email and profile picture, only to identify you and grant access if you have been invited.
  • Connecting Google Ads: we request the https://www.googleapis.com/auth/adwords scope (view and manage Google Ads accounts) and the userinfo.email scope (identify which Google account was connected). We use this access to: (1) read campaigns and metrics and display them in dashboards and reports; (2) generate analyses and alerts; and (3) when — and only when — you explicitly approve a suggestion, apply the change to your account (for example, pause/enable campaigns or keywords, adjust budget or target CPA/ROAS, add negative keywords or exclude placements) and let you revert it.

TrafficOS’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.

In particular: (a) we use Google user data only to provide and improve the user-facing features described above; (b) we do not sell it or transfer it to data brokers or advertising platforms; (c) we do not use it for advertising, including retargeting, personalized or interest-based advertising; (d) humans do not read it, except with your consent for specific data, for security or abuse purposes, to comply with law, or when it is aggregated and anonymized for internal operations; and (e) we do not use it to develop, improve or train generalized AI/ML models.

You can revoke access at any time under Integrations → Disconnect (in TrafficOS) and/or at myaccount.google.com/permissions (in your Google account).

4. Meta data (Facebook/Instagram Ads)

When you connect Meta Ads we request the ads_read, ads_management, business_management and public_profile permissions to list the ad accounts you can access, read campaigns, ad sets, ads and metrics and — only with your explicit approval — apply and revert changes (such as pausing/enabling or adjusting budgets). We do not access your personal Facebook profile, friends, posts or messages. Meta data is used only to provide the service to the user who authorized it, in line with the Meta Platform Terms.

5. How we use data

  • Provide the service: dashboards, reports, anomaly alerts, client health score, campaign planning.
  • Artificial intelligence: generate analyses, daily summaries and optimization suggestions based on your own account data (see “Processors and sharing”).
  • Apply optimizations on the ad platform — always with user approval, safety limits and a log for reverting.
  • Security and fraud prevention: authentication, role-based access control, auditing and rate limiting.
  • Communication: transactional emails (invitations, alerts, summaries and reports).
  • Comply with legal obligations and exercise rights in proceedings.

Legal bases (LGPD, art. 7): performance of a contract with you or the organization that invited you; legitimate interest (security and service improvement, with minimal privacy impact); compliance with a legal obligation; and consent, when you authorize the connection with Google and Meta (revocable at any time).

6. Processors and sharing

We do not sell personal data or share it for advertising. We share data only with providers that help us operate the service, under confidentiality and security obligations:

  • Supabase — database, authentication and scheduled functions.
  • Vercel — web application hosting and access logs.
  • OpenRouter and the language-model provider (Anthropic, Claude models) — generation of AI analyses. We send performance data and the campaign, client and keyword names needed for the analysis; we never send passwords or access tokens. We do not use this data to train models.
  • Resend — delivery of transactional emails (recipient and message content).
  • Google and Meta — the advertising platforms themselves, whose APIs we read and update at your request.

We may also disclose data when required by law, court order or a competent authority, or to protect rights, safety and the integrity of the service. In a corporate reorganization, data may be transferred to the successor, which will be bound by this Policy.

Some of these providers are located outside Brazil (for example, in the United States). In those cases the international transfer relies on the safeguards of LGPD art. 33 (such as standard contractual clauses).

7. How long we keep data

  • Account data and organization content: while the account is active.
  • Advertising-account access tokens: deleted immediately when you disconnect the integration; the access token is renewed automatically while the connection is active.
  • Synced advertising metrics and data: while the organization uses the service or until you request deletion.
  • Audit and security records: for as long as needed for security and legal obligations.
  • After account closure or your request, we delete or anonymize data within 30 days, unless the law requires retention. Backups are overwritten in the normal rotation cycle (up to 90 days).

8. How we protect data

  • Encrypted connections (HTTPS/TLS) for all traffic.
  • OAuth tokens encrypted with AES-256-GCM in a table that users cannot read; the key is kept outside the database.
  • Isolation between organizations in the database (Row Level Security): each organization sees only its own data.
  • Role-based access control (administrator, manager, analyst, creative, viewer) and invitation-only sign-up.
  • Human approval and safety limits before any change to advertising accounts; audit log.
  • Security headers, CSRF protection and rate limiting.

No system is completely immune to failure. In the event of a security incident that may cause relevant risk or harm, we will notify affected individuals and the Brazilian data protection authority (ANPD) as required by the LGPD.

9. Your rights

Under LGPD art. 18 you may request: confirmation of processing; access; correction of incomplete or outdated data; anonymization, blocking or deletion of unnecessary data or data processed unlawfully; portability; information about who we share data with; information about the possibility of refusing consent and its consequences; and withdrawal of consent.

To exercise any right, write to traffic.os2026@gmail.com. We reply within 15 days. If you use TrafficOS through an agency, the agency (controller of its clients’ data) may also handle the request. You may also complain to the Brazilian data protection authority (ANPD). To delete your data, see http://traffic.inspiratoridigital.com.br/data-deletion.

10. Children

TrafficOS is a professional tool and is not intended for anyone under 18. We do not knowingly collect data from children or teenagers.

11. Changes to this Policy

We may update this Policy to reflect changes in the service or the law. The date of the last revision is at the top of this page; material changes will be communicated by email or an in-app notice. If you keep using the service after a change, we will understand that you are aware of the updated version.

12. Contact

Inspiratori Digital, CNPJ (Brazilian tax ID) 32.797.561/0001-50 — traffic.os2026@gmail.com — http://traffic.inspiratoridigital.com.br