English version of the Prospia Privacy Policy. Prospia is operated by ZODO SOLUÇÕES EM TECNOLOGIA LTDA (Brazil). In case of any divergence, the Portuguese version at /privacidade prevails.
Controller: ZODO SOLUÇÕES EM TECNOLOGIA LTDA (CNPJ 35.403.783/0001-39), based in Cocal do Sul/SC, Brazil. Data Protection Officer: security@prospia.ai. We process personal data under the Brazilian General Data Protection Law (LGPD, Law 13,709/2018).
Sign-up/access: e-mail, record of acceptance of the Terms and of this Policy (version, date, IP), logs. Usage: lead requests, lists, campaigns, tokens and billing when applicable (payment data in section 7.1). Content, when social publishing is enabled for the organization: the texts the User writes for publication, with the record of who approved, who scheduled and when each post was sent — this trail is required to operate the feature, to account to the connected networks and to investigate misuse. Legal bases: performance of contract and legitimate interest to operate and improve the service; consent where required.
Public data about legal entities: the Brazilian Federal Revenue CNPJ registry, companies' public websites and OpenStreetMap. We do not use sources that forbid redistribution in the database we sell. Professional contact data is processed under legitimate interest for B2B relationships, respecting data subjects' rights (including objection/removal).
Credentials of connected accounts (e.g. Google Ads, Google Analytics, Search Console, LinkedIn) are stored encrypted and only on the server, isolated per organization, and used exclusively to operate the integration the User authorized. They are never exposed to the browser or shared. When LinkedIn publishing is enabled for the organization, LinkedIn personal PROFILE credentials are bound to the member who authorized the connection, not to the organization. When the integration is disconnected (in the Platform or in the network itself), the corresponding tokens are discarded.
This section is specifically about data received from Google APIs ("Google user data"), in raw or aggregated form, when the User connects their own Google Ads, Google Analytics (GA4) or Google Search Console account to Prospia through Google's OAuth consent screen. Each integration requests only its own scopes: Google Ads (https://www.googleapis.com/auth/adwords), Google Analytics (https://www.googleapis.com/auth/analytics.readonly and https://www.googleapis.com/auth/analytics.edit) and Search Console (https://www.googleapis.com/auth/webmasters.readonly). Prospia does not use Google Sign-In and does not access Gmail, Drive, Calendar, Contacts, Photos or any Google Workspace data.
Google Ads: the accounts the User has access to and, within them, campaigns, budgets, ad groups, ads, keywords and negative keywords, targeting (locations, ad schedule), bidding strategies, conversion actions, recommendations, search terms and performance metrics (impressions, clicks, cost, conversions). Google Analytics (GA4): properties and data streams, aggregated reports (sessions, users, events, conversions, traffic sources, landing pages, realtime) and the property configuration (key events, custom dimensions and metrics, data retention, Google Ads links). Search Console: verified sites and Search performance (queries, pages, countries, devices, clicks, impressions, CTR, position), sitemaps and URL inspection. We also store the OAuth token issued by Google to keep the connection. We do not request the Google account's name, e-mail address, photo or other profile data.
Only to provide the user-facing features the User requests in Prospia: displaying campaigns, metrics and reports; creating, editing, pausing and re-enabling campaigns, ad groups, keywords and ads in the User's account (new campaigns are created paused); generating campaign and SEO diagnostics and recommendations from the User's own data; creating the GA4 configuration the User asks for (key events, custom dimensions and metrics, data retention, Google Ads link); and answering, in Prospia's AI assistant, the questions the User asks about that data. Every change to the Google account is made only at the User's explicit request (a button or a confirmation in Prospia, or a command the User gives through their own AI client connected via MCP) or by an automation the User has expressly turned on. Google user data is not used for advertising (including personalized ads or retargeting), is not sold, is not used to determine creditworthiness or for lending, does not feed user profiles or third-party databases, does not benefit other customers, and is not used to train generalized AI or machine-learning models. Prospia staff do not read this data, except with the User's consent (e.g. support), when necessary for security or abuse investigation, to comply with the law, or in aggregated and anonymized form to operate the service.
We do not sell or hand over Google user data. It is transferred only: (a) to Google itself, in the API calls that carry out what the User asked for; (b) to the members of the Prospia organization in which the User created the connection, according to the roles the User sets; (c) to processors acting on our behalf under contract, only as far as necessary: hosting and database providers and, when the User uses an AI feature (such as the assistant) on that data, the AI model provider that generates the answer (e.g. Google Gemini, OpenAI), which receives only the excerpt needed to answer, under terms that do not allow it to use that data to train its models; (d) to the AI client the User chooses to connect to Prospia's MCP interface, at the User's own initiative and with a token the User creates and can revoke at any time; (e) when required by law or by order of an authority; and (f) in a merger, acquisition or sale of assets, only with the User's explicit prior consent.
Data always travels over encrypted connections (TLS). OAuth tokens and other credentials are kept only on the server, encrypted at rest (AES-256-GCM), and are never sent to the browser. Access is isolated per organization and checked on the server for every operation; only owners and administrators of the organization can create, change or remove connections. Changes made through Prospia's campaign features and assistant are rate-limited and recorded in an audit log. Access to production systems is restricted to authorized Prospia personnel.
The OAuth token is kept while the connection exists and is deleted immediately when the User removes the connection in Settings › Integrations. The User can also revoke access at any time at https://myaccount.google.com/permissions; from then on Prospia can no longer access the account. Data derived from Google APIs that we keep to provide history (campaign metrics and reports, diagnostics and recommendations, assistant conversations and the audit log of changes) is retained while the User's account is active. The User can request deletion of that data, or of the whole account, at any time by e-mail to security@prospia.ai; we act on it within 30 days, and backups are overwritten in their normal rotation cycle. Data we are legally required to keep is retained only for the legal period.
Prospia's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements. This also applies to Google user data processed by Prospia's AI features.
When LinkedIn publishing is enabled for the User's organization and the User connects their personal LinkedIn profile, Prospia accesses only: (a) the basic profile data provided at sign-in through OpenID Connect (member identifier, name, e-mail and picture), of which we store only the identifier and the name; and (b) the permission to post on the User's behalf (w_member_social scope), used exclusively to publish the posts the User wrote and approved in the Platform. We do not read the feed, the connections, the messages, other people's posts or any other data of the LinkedIn account, and we do not post to company pages. For each post we keep the text, the attached link or image, the identifier and address of the post created, the date, the author and who approved it. This data is not sold, not used for advertising, does not train AI models and is not shared with third parties, except to operate the authorized integration, when required by law or with the User's consent. We observe LinkedIn's API terms of use. Retention: the access token is stored encrypted on the server while the connection exists and lasts about 60 days (a period set by LinkedIn), after which the User has to reconnect; on disconnection the token is discarded and we ask LinkedIn to revoke the permission. The post history is kept as a record of the operation (section 10) and can be deleted at the data subject's request. Revocation: at any time, in the Platform, through the Disconnect option in the same place where the profile was connected, or on LinkedIn itself, at https://www.linkedin.com/psettings/permitted-services (Settings › Data privacy › Permitted services).
We do not sell personal data. We share it only with necessary infrastructure/AI providers (processors), the payment processor Stripe (section 7.1), ad networks you connect (to run your campaigns), social networks where you publish content through the Platform, when that feature is enabled for your organization (limited to what you wrote and asked to publish) and authorities when required by law. For Google user data, the specific rules of section 5.3 apply.
Payments for plans and credit packs are processed by Stripe (Stripe, Inc. and affiliates), which acts as Prospia's processor for billing. At checkout, the User provides directly to Stripe their e-mail address, name, CPF or CNPJ (Brazilian tax ID), billing address and card details. Card details go straight to Stripe and are never received or stored by Prospia. Prospia keeps only the Stripe customer and subscription identifiers, the plan, the payment status and the amounts charged, and receives from Stripe the data needed to issue the invoice (nota fiscal). Purposes: billing, issuing invoices, fraud prevention and compliance with legal and tax obligations. Legal bases: performance of contract and compliance with a legal obligation. Stripe processes this data in the USA and in other countries; there is therefore an international data transfer, made only for these purposes, limited to what is necessary and with contractual safeguards (data-protection clauses), under articles 33 to 36 of the LGPD. For fraud prevention and its own obligations, Stripe also processes data under its own privacy policy (https://stripe.com/privacy). Billing records and invoices are kept for the legal period of 5 years, even after the account is closed.
Part of the processing takes place at providers located outside Brazil — for example AI services (such as OpenAI and Google, in the USA) used to suggest CNAE codes, draft campaigns and similar functions and, occasionally, other model providers that may be in other countries. In those cases there is an international data transfer, made only for the purposes of this Policy, limited to what is necessary and with contractual safeguards with the processors (data-protection clauses), under articles 33 to 36 of the LGPD. Data accessed via Google APIs additionally follows the rules of section 5. Payment data processed by Stripe follows section 7.1.
For data about Platform users, Prospia is the controller. For the use the User makes of the leads (prospecting, contact, campaigns), the User is the controller and Prospia acts as the tool provider — the User is responsible for the legal bases and for data subjects' rights in that processing.
Data subject rights: confirmation, access, correction, anonymization, portability, deletion, information about sharing and withdrawal of consent, via security@prospia.ai. We retain data for as long as necessary for its purposes and legal obligations, with security measures (access control, per-organization isolation, secrets only on the server). For Google user data, retention and deletion follow section 5.5.
We use cookies and similar technologies in three categories: Essential (always on — login, security, session and remembering your consent choice; they do not depend on consent); Analytics (with consent — understanding how the Platform is used to improve it); and Marketing (with consent — personalizing and measuring campaigns/ads). On the first visit we show a banner to accept all, reject non-essential cookies or adjust per category in Preferences; you can review the choice at any time under "Manage cookies". The preference is kept for up to 365 days and the consent is recorded (date and version) for accountability (LGPD).
This Policy may be updated; the current version is available on the Platform. Relevant changes may require new acceptance. Contact of the Data Protection Officer: security@prospia.ai.