PMR: Promo MKT Report · BeC System
Terms of Use and Privacy Policy
Version 1.1. In force since 19 November 2026.
BRANDAO & COSTA PRESTACAO DE SERVICOS DE DIGITACAO LTDA (BEC SYSTEM), CNPJ 10.673.919/0001-08, Av. Paulista, 1471, conj. 511, Bela Vista, São Paulo, SP, CEP 01311-927, Brazil, creator and sole owner of the Promo MKT Report software ("PMR"), sets out in this document the rules and conditions of use and the guidelines on privacy and data protection.
By accessing the web panel or using the PMR app, the user declares that they have read, understood and accepted the conditions set out here. In the web panel, acceptance also follows section 10.
By accessing the web panel or using the PMR app, the user declares that they have read, understood and accepted the conditions set out here. In the web panel, acceptance also follows section 10.
Part I: Terms and Conditions of Use
1. Purpose and Definitions of Users
PMR is a SaaS platform for managing Trade Marketing, Live Marketing, Merchandising and Point-of-Sale Auditing. The system allows data collection, tracking of field teams and validation of information through automatic rules, such as Anti-Fake GPS.
Contracting Party (Controller): legal entities (marketing agencies, manufacturers, trade companies) that sign a contract with BEC System to use the platform.
Field User (Field Team): natural persons (promoters, researchers, auditors) registered and authorized by the Contracting Party to access the app and carry out data collection.
Contracting Party (Controller): legal entities (marketing agencies, manufacturers, trade companies) that sign a contract with BEC System to use the platform.
Field User (Field Team): natural persons (promoters, researchers, auditors) registered and authorized by the Contracting Party to access the app and carry out data collection.
2. Labor Responsibilities and Relationship
The PMR platform acts exclusively as a technology provider. There is no employment, partnership or commercial representation relationship between BEC System and Field Users.
The Contracting Party is the sole employer of its field team and assumes all labor, social security, tax and insurance obligations, with no joint or subsidiary liability on the part of BEC System.
The Contracting Party is the sole employer of its field team and assumes all labor, social security, tax and insurance obligations, with no joint or subsidiary liability on the part of BEC System.
3. Features, Support and Business Model
Audit Technology: Anti-Fake GPS and offline synchronization. Anti-Fake GPS is a check made in the app itself: when it detects on the device an app that generates fake locations, it does not let the user use PMR. This check sends no data to third parties.
Technical Support: BEC System support serves the managers named by the Contracting Party. The Contracting Party provides first-level support to its field team. Support through the AI integration follows section 13.3.
Billing Model: the platform works on a Pay-per-Visit model (payment per completed visit). Non-payment may lead to suspension of access, with no right to compensation.
White-Label License: when contracted, it is a temporary license of use and does not transfer copyright or source code.
Technical Support: BEC System support serves the managers named by the Contracting Party. The Contracting Party provides first-level support to its field team. Support through the AI integration follows section 13.3.
Billing Model: the platform works on a Pay-per-Visit model (payment per completed visit). Non-payment may lead to suspension of access, with no right to compensation.
White-Label License: when contracted, it is a temporary license of use and does not transfer copyright or source code.
Part II: Privacy and Data Protection Policy (LGPD and GDPR)
4. Roles in Data Protection
Controller: the Contracting Party defines the purpose of collection, registers the promoters and manages the information base. Under the LGPD (Brazil's General Data Protection Law, Law 13,709/2018), this role is called "controlador". Under Regulation (EU) 2016/679 (GDPR), it is called controller.
Processor: BEC System (PMR) acts as Data Processor ("operadora" under the LGPD). It provides the technology infrastructure to process and store the data according to the Controller's instructions. Under the GDPR, the role has the same name: processor.
When BEC System decides: BEC System is the controller of the data of visitors to the website (section 16.2), of the people who receive the e-mail communications described in section 12, and of the contact details of the Contracting Parties' managers for the commercial relationship. It also processes the record of acceptance of this policy in the panel (section 10) and of the AI Addendum (section 13.3), to prove acceptance and for the regular exercise of rights. It uses the registered e-mail address of the panel user to send them the link to the "Privacidade" page of the panel after acceptance and with the notice of each new major version (section 10). The purpose is to inform the user about this policy and the acceptance they gave, and the legal basis is BEC System's legitimate interest in keeping users informed of the rules they accepted (LGPD, Article 7, IX; for a data subject covered by the GDPR, Article 6(1)(f)).
Processor: BEC System (PMR) acts as Data Processor ("operadora" under the LGPD). It provides the technology infrastructure to process and store the data according to the Controller's instructions. Under the GDPR, the role has the same name: processor.
When BEC System decides: BEC System is the controller of the data of visitors to the website (section 16.2), of the people who receive the e-mail communications described in section 12, and of the contact details of the Contracting Parties' managers for the commercial relationship. It also processes the record of acceptance of this policy in the panel (section 10) and of the AI Addendum (section 13.3), to prove acceptance and for the regular exercise of rights. It uses the registered e-mail address of the panel user to send them the link to the "Privacidade" page of the panel after acceptance and with the notice of each new major version (section 10). The purpose is to inform the user about this policy and the acceptance they gave, and the legal basis is BEC System's legitimate interest in keeping users informed of the rules they accepted (LGPD, Article 7, IX; for a data subject covered by the GDPR, Article 6(1)(f)).
5. Data Collected and App Permissions
Registration Data: name, e-mail, phone number and CPF, entered by the Contracting Party's manager.
Location (GPS): precise geolocation to validate check-in and check-out. The Anti-Fake GPS check (section 3) runs on the device itself.
Camera and Images: access to the camera to capture photos of shelves, products, receipts and audit selfies, reviewed by the Contracting Party's team in the panel.
QR code reading: PMR only reads the QR code of the photographed invoice (Brazilian nota fiscal) and sends its content to the external service that the Contracting Party itself contracts to look up the invoice. That service is the Contracting Party's choice, as Controller, and is not a sub-processor of BEC System. PMR does not apply facial recognition to selfies, and the Contracting Party's team reviews the photos.
Device Information: model, operating system, IP address, notification identifier, the app version and the technical failure log (time it occurred, version, campaign in use and error type, without the content of the answers), also before login, without identifying the user. This data serves technical support, delivery of notifications and fraud prevention.
AI Integration: the data that flows when the Contracting Party connects an AI tool is described in section 13.
Location (GPS): precise geolocation to validate check-in and check-out. The Anti-Fake GPS check (section 3) runs on the device itself.
Camera and Images: access to the camera to capture photos of shelves, products, receipts and audit selfies, reviewed by the Contracting Party's team in the panel.
QR code reading: PMR only reads the QR code of the photographed invoice (Brazilian nota fiscal) and sends its content to the external service that the Contracting Party itself contracts to look up the invoice. That service is the Contracting Party's choice, as Controller, and is not a sub-processor of BEC System. PMR does not apply facial recognition to selfies, and the Contracting Party's team reviews the photos.
Device Information: model, operating system, IP address, notification identifier, the app version and the technical failure log (time it occurred, version, campaign in use and error type, without the content of the answers), also before login, without identifying the user. This data serves technical support, delivery of notifications and fraud prevention.
AI Integration: the data that flows when the Contracting Party connects an AI tool is described in section 13.
6. Purpose, Ownership and Confidentiality of Data
Exclusive Ownership: the data collected belongs to the Contracting Party (Controller).
No secondary use: BEC System does not sell the data and does not use it for its own purposes, except for the acceptance records and the e-mail that informs the user about this policy (sections 4, 10 and 13.3). It shares the data only with the sub-processors in section 14, which carry out part of the service, with Google, as an independent controller, for the map data in section 14.2, and with whoever the Contracting Party designates, such as the AI provider in section 13.
Legal basis: the Contracting Party defines the legal basis for each processing activity, except where BEC System decides (section 4). Under the LGPD, the usual bases for this service are performance of a contract and legitimate interests (Article 7, items V and IX). For data subjects covered by the GDPR, section 17.3 lists the bases in Article 6.
No secondary use: BEC System does not sell the data and does not use it for its own purposes, except for the acceptance records and the e-mail that informs the user about this policy (sections 4, 10 and 13.3). It shares the data only with the sub-processors in section 14, which carry out part of the service, with Google, as an independent controller, for the map data in section 14.2, and with whoever the Contracting Party designates, such as the AI provider in section 13.
Legal basis: the Contracting Party defines the legal basis for each processing activity, except where BEC System decides (section 4). Under the LGPD, the usual bases for this service are performance of a contract and legitimate interests (Article 7, items V and IX). For data subjects covered by the GDPR, section 17.3 lists the bases in Article 6.
7. Storage, Security and Retention
The data is stored in the AWS cloud, encrypted in transit on the connections of the app and of the panel to the server and, for photo and document files, also at rest. The connection of the app's server to the database is encrypted in transit (TLS), and the panel's connection is configured to use TLS whenever the database offers it.
Today, anyone who has the address of a photograph can open it without logging in. The storage does not allow listing the files, but the address appears in the panel, in reports and in the spreadsheets the Contracting Party exports. The Contracting Party treats this address as personal data and does not publish it.
BEC System keeps the data for the term of the contract. After termination, it returns the data to the Controller and deletes it, as section 15.1 describes. At the Controller's request, it deletes the data earlier. In both cases, it keeps what the law requires or what is necessary for the regular exercise of rights. The retention periods are in section 15.
Today, anyone who has the address of a photograph can open it without logging in. The storage does not allow listing the files, but the address appears in the panel, in reports and in the spreadsheets the Contracting Party exports. The Contracting Party treats this address as personal data and does not publish it.
BEC System keeps the data for the term of the contract. After termination, it returns the data to the Controller and deletes it, as section 15.1 describes. At the Controller's request, it deletes the data earlier. In both cases, it keeps what the law requires or what is necessary for the regular exercise of rights. The retention periods are in section 15.
8. Rights of Data Subjects (Field Team)
The Contracting Party is the Controller. For that reason, the Field User exercises their rights with the HR department or management of the contracting agency or company. Under the LGPD, these rights include access, correction, deletion and portability, among others in Article 18. The data subject may also petition Brazil's National Data Protection Authority (ANPD). For data subjects covered by the GDPR, the rights and deadlines are in section 17.4.
BEC System offers the Contracting Party, in the PMR panel, the tools to handle employees' requests.
When BEC System receives a data subject request, it forwards the request to the Contracting Party within 5 business days and does not respond in its place.
BEC System offers the Contracting Party, in the PMR panel, the tools to handle employees' requests.
When BEC System receives a data subject request, it forwards the request to the Contracting Party within 5 business days and does not respond in its place.
Part III: Final Provisions
9. Intellectual Property of the Platform
All the technology, source code, layout, logo and databases of the PMR system are the exclusive intellectual property of BEC System. Unauthorized reverse engineering, copying and distribution are prohibited.
10. Versions, Changes and Forum
This document is version 1.1, in force since the date shown at the top. BEC System numbers changes as follows:
In the app, PMR records the date and the version of these Terms accepted by each user. When the version changes, the app asks for acceptance again.
Acceptance in the web panel. From the moment the acceptance screen goes live in the panel, every Contracting Party user who enters the web panel without having accepted the current major version of this policy sees, right after login, a screen asking for acceptance. Acceptance of a version covers the following minor versions, and acceptance is requested again with each new major version. PMR records the user, the version accepted, the date and time, the IP address and the browser, and keeps the record for the period in section 15.3. On the "Privacidade" page of the panel, the user sees the current policy and the acceptance they gave, with the version and the date. A user with a registered e-mail address receives the link to that page by e-mail after accepting and, with the 30-day notice, for each new major version. BEC System team users with the SUPER profile, including the support one, and the technical user of the automated routines do not go through this screen: the policy belongs to BEC System itself, which processes the Contracting Party's data on its behalf, as processor, under the rules of this policy, and the routines user is not a person.
The Portuguese version is the source of this English version and of the Spanish version. In case of divergence, the Portuguese version prevails, unless the law applicable to the data subject requires another language.
The courts of the Judicial District of São Paulo, Capital (Brazil), are chosen as the forum. This choice does not remove the data subject's right to complain to the data protection authority and to turn to the courts that the law applicable to them guarantees.
- Material change (new purpose, new data, new third party, longer retention period or reduced right): new major version (2.0, 3.0), with e-mail notice to the Contracting Parties at least 30 days in advance, a notice in the panel during that period and new acceptance in the panel.
- Informative change, which does not alter the processing (for example, clearer wording or an updated contact): new minor version (1.1, 1.2), with e-mail notice to the Contracting Parties and a notice in the panel, without new acceptance in the web panel.
- Typo correction that does not change the meaning: no new version.
In the app, PMR records the date and the version of these Terms accepted by each user. When the version changes, the app asks for acceptance again.
Acceptance in the web panel. From the moment the acceptance screen goes live in the panel, every Contracting Party user who enters the web panel without having accepted the current major version of this policy sees, right after login, a screen asking for acceptance. Acceptance of a version covers the following minor versions, and acceptance is requested again with each new major version. PMR records the user, the version accepted, the date and time, the IP address and the browser, and keeps the record for the period in section 15.3. On the "Privacidade" page of the panel, the user sees the current policy and the acceptance they gave, with the version and the date. A user with a registered e-mail address receives the link to that page by e-mail after accepting and, with the 30-day notice, for each new major version. BEC System team users with the SUPER profile, including the support one, and the technical user of the automated routines do not go through this screen: the policy belongs to BEC System itself, which processes the Contracting Party's data on its behalf, as processor, under the rules of this policy, and the routines user is not a person.
The Portuguese version is the source of this English version and of the Spanish version. In case of divergence, the Portuguese version prevails, unless the law applicable to the data subject requires another language.
The courts of the Judicial District of São Paulo, Capital (Brazil), are chosen as the forum. This choice does not remove the data subject's right to complain to the data protection authority and to turn to the courts that the law applicable to them guarantees.
11. Privacy Contact Channel (Data Protection Officer)
Data Protection Officer (encarregado, under the LGPD)
Carlos Eduardo Brandão, carlos@promomktreport.com.br, until an external Data Protection Officer is designated
+55 11 97315-2149
The Data Protection Officer serves data subjects covered by the LGPD and the GDPR (section 17.8). BEC System does not designate a representative in the European Union, for the reason in section 17.7.
Carlos Eduardo Brandão, carlos@promomktreport.com.br, until an external Data Protection Officer is designated
+55 11 97315-2149
The Data Protection Officer serves data subjects covered by the LGPD and the GDPR (section 17.8). BEC System does not designate a representative in the European Union, for the reason in section 17.7.
12. Tracking in E-mail Communications
When we send e-mail communications, we record, individually, whether the message was opened and which links you clicked. To do this, we use a tracking image and links that pass through our server before leading to their destination.
Purpose: to understand which subjects are useful to you, adjust the content and frequency of messages, and not keep writing to people who are not interested. Legal basis: legitimate interests, under Article 7, IX, of the LGPD.
This data is linked to your e-mail address and is used only by us. You can ask for deletion at any time through the channels in this policy, and the unsubscribe link in every message stops the sending and the tracking immediately.
For recipients in the European Union, commercial e-mail is sent only with their prior authorization, which we record with date and source, and the message carries no tracking image and no tracked links. The recipient can withdraw the authorization at any time through the unsubscribe link in each message, and the legal basis is in section 17.10. These rules apply from 18 November 2026.
Purpose: to understand which subjects are useful to you, adjust the content and frequency of messages, and not keep writing to people who are not interested. Legal basis: legitimate interests, under Article 7, IX, of the LGPD.
This data is linked to your e-mail address and is used only by us. You can ask for deletion at any time through the channels in this policy, and the unsubscribe link in every message stops the sending and the tracking immediately.
For recipients in the European Union, commercial e-mail is sent only with their prior authorization, which we record with date and source, and the message carries no tracking image and no tracked links. The recipient can withdraw the authorization at any time through the unsubscribe link in each message, and the legal basis is in section 17.10. These rules apply from 18 November 2026.
Part IV: Artificial Intelligence Integration
13. Integration with Artificial Intelligence Chosen by the Contracting Party
13.1. Purpose. PMR offers an optional integration, through the MCP protocol, that lets the Contracting Party connect to PMR an artificial intelligence tool of its choice, such as Claude (Anthropic), ChatGPT (OpenAI), Gemini (Google), Copilot (Microsoft) or Cursor. With it, the Contracting Party can query, register and change stores, products, clients, affiliates, supervisors, promoters and questions.
The integration offers no tool to read photographs, selfies, location or survey answers.
13.2. Choice of provider. The Contracting Party chooses, contracts and configures the AI provider. BEC System does not contract this provider, does not keep the Contracting Party's access key to it and does not define how it processes the data. The provider acts under the conditions the Contracting Party accepted with it and is not a sub-processor of BEC System. The exception is the support connection in 13.3, where BEC System chooses the provider.
The Contracting Party should send personal data through the integration only if, under the terms of the plan it contracted, the provider processes that data on the Contracting Party's behalf and does not use it to train models. By accepting the AI Addendum, the Contracting Party declares that the chosen plan meets this condition. The declaration is mandatory for acceptance, and PMR records it.
13.3. Authorization and acceptance. Only a Contracting Party user with the superadmin profile in the panel authorizes the integration, and acceptance of the AI Addendum is a condition for activating it, both for the token and for login. BEC System staff with the support profile (SUPER) can see the "Integração com IA" tab and revoke tokens and connections to provide support, but cannot accept the addendum or generate a token on the Contracting Party's behalf. Without this authorization, the Contracting Party's integration does not work.
PMR records the date, user, IP address, browser, provider, version and hash of the text accepted, which includes the declaration in 13.2, and sends a copy of the acceptance to the registered e-mail address of the superadmin who accepted, when there is one. Because e-mail is not mandatory in PMR, if no e-mail is registered the copy is not sent, and the acceptance screen says so. BEC System keeps this record for the term of the contract and for 5 more years after it ends, for the regular exercise of rights, or until the end of any judicial, administrative or arbitration proceeding, or complaint, involving the acceptance, if that lasts longer. At the end of the period, BEC System deletes the record or, while technical deletion does not exist, anonymizes it and restricts access to it.
The Contracting Party's connection follows one of two paths:
Token: the superadmin generates the token in the panel, with permissions for querying, preparing a preview and writing, and a validity of 30, 90 or 180 days. PMR keeps only the hash of the token. The token does not depend on who generated it: it is valid until it expires or is revoked, even if that person leaves the company.
Login (OAuth): the superadmin signs in to the panel from the AI tool, checks the provider, and chooses the permissions and a validity of 30, 90 or 180 days. The access credential lasts 1 hour, and the AI tool renews it. The renewal lapses after 30 days without use and never goes beyond the validity of the connection. The connection stops working if the superadmin who approved it is deactivated or loses the profile.
BEC System support connection: a single BEC System team user with the SUPER profile, defined in configuration, can connect to the Contracting Party's PMR an AI tool chosen by BEC, Claude, from Anthropic, on the Claude Team plan (section 14.6), to provide support. BEC System has not yet contracted Claude Team, and the contracting has no set date. Until then, BEC does not use the Contracting Party's data in the support connection, and the system accepts this connection only in BEC System's demonstration environment. BEC opens the support connection only at the Contracting Party's request. No other BEC user has this permission. This connection does not use the Contracting Party's acceptance: BEC records acceptance of an internal support term, with date, user, IP address, browser, provider, version and hash. It is valid for 1, 3 or 7 days. The query and preview-preparation permissions come checked, and writing is valid only when the support user checks it for that connection. The connection appears in the "Integração com IA" tab as "Suporte BEC", with who created it and the validity, and the Contracting Party's active superadmins who have a registered e-mail address receive an e-mail notice when it is created. The Contracting Party's superadmin can revoke it at any time, as can BEC System staff with the SUPER profile. In it, the AI provider processes the Contracting Party's data on BEC System's behalf and is its sub-processor (section 14.6).
13.4. Revocation. To end access, the Contracting Party's superadmin revokes the token or the connection in the "Integração com IA" tab of the panel. BEC System's support team (SUPER profile) can also revoke, to provide support. The revocation takes effect from the next request.
Removing the connector or deleting the token in the AI tool does not revoke access in PMR. Revocation happens only in the panel.
Revocation prevents new access but does not delete what the AI provider has already received. That content follows the provider's conditions, and it is up to the Contracting Party to ask the provider to delete it.
A connection accepted under a previous version of the AI Addendum stays valid until it expires or is revoked, but does not receive new features that only the current version describes.
13.5. What the AI sends to PMR. The AI sends registration data as text or as a spreadsheet (CSV, TXT, XLSX or XLS, up to 5 MB). In the records of supervisors, promoters, clients and affiliates, this data can include name, CPF or CNPJ, RG or state registration number, address, phone numbers, e-mail, contact, login and password. In the store record, it can include the manager's name. In the promoter record, the device identifier.
With the write permission, the AI adds records and changes existing records, including login, password, access group and status (active or inactive) of people. When changing, a column sent empty deletes the stored value.
Everything the person types or attaches in the conversation, including CPF and password, passes through the AI provider. When the person authorizes it, the AI itself can create temporary logins and passwords for supervisors and promoters; these credentials stay in the conversation history, and the Contracting Party can replace them in the PMR panel.
13.6. What PMR returns to the AI.
Record search: at most 20 per query. For people, PMR returns identifier, code, name and status, with no document or contact details.
Spreadsheet sent: column names, total number of rows and the first 5 rows, unmasked, as they came in the file the AI itself sent.
Change preview: the current value and the new value of each field sent. In the records of people (supervisors, promoters, and clients or affiliates who are natural persons), CPF, CNPJ, RG, state registration number, e-mail, phone numbers, address, neighborhood, postal code, contact, device identifier and login appear only with the last 2 characters. Name, city, state and status appear unmasked, so the person can check they have the right record. In stores, the manager's name and phone number appear masked, and company data appears unmasked.
Batch result: counts and errors per row. The error message may repeat the rejected value, except the CPF, which PMR hides.
The password stored in PMR never returns to the AI.
13.7. Preview and confirmation. Preparation validates the data and writes nothing. PMR instructs the AI tool to show the preview and to write only after the person confirms in the conversation.
PMR does not see the conversation and cannot prove that confirmation. It is up to the Contracting Party to check the preview and follow the result of each batch in the "Integração com IA" tab.
13.8. Temporary retention. PMR keeps the rows of each batch encrypted and deletes them when writing ends. A batch that is not written is valid for 24 hours. After that, PMR deletes the rows in the next cleanup, which runs every hour and on each access to the tab or to the batch tools.
The spreadsheets sent by the AI stay in a folder restricted to the connection that sent them. PMR deletes them in the first cleanup after 24 hours from the upload, even if the batch has already been written.
The batch summary, with status, preview, counts and errors per row, stays in PMR for 90 days and is then deleted.
13.9. Record of actions. PMR records in the panel's user log, with the "ia" mark: generation, revocation and expiry of tokens and connections, including support ones; authorization and refusal of connections; spreadsheet uploads; record searches; preparation of insert and change batches; the result of each batch; each record changed; and refused calls.
Each line identifies the token or connection, the responsible person (who generated the token or who approved the connection), the register, the record identifiers and the field names. This record does not keep field values, CPF, password, row contents or file names. Batch queries and queries on the structure of the registration records do not generate a line in this log. The body of the AI's calls does not enter the application server's technical log (section 15.3).
13.10. International transfer. AI providers may process data outside Brazil. By activating the integration, the Contracting Party, as Controller, defines the provider and the destination of the data and is responsible for bringing the transfer within Article 33 of the LGPD and the ANPD's regulations.
The Contracting Party maintains a valid transfer mechanism with the provider: the standard contractual clauses approved by the ANPD, adopted in full and without change, or another mechanism under Article 33 of the LGPD. The ANPD's adequacy decision currently in force (ANPD Resolution CD/ANPD No. 32/2026) covers only the European Union, Iceland, Liechtenstein and Norway.
BEC System carries out the sending only on the Contracting Party's instruction. When the AI provider accesses PMR from abroad, BEC System transmits the data on the Contracting Party's instruction and gives it the information it has to bring the transfer within those rules. When the GDPR reaches the Contracting Party, it is also responsible for bringing the transfer to the AI provider it chose within Chapter V of the GDPR (Articles 44 to 49). Section 17.5 covers transfers to BEC System's sub-processors.
13.11. Legal basis and field team. The Contracting Party defines the legal basis for the processing. Before the first sending of its field team's data through the integration, the Contracting Party informs that team, prominently, which provider receives the data, for what purpose, in which country, for how long, who is responsible for the processing and how to exercise their rights, including the right to petition the ANPD or, for a data subject covered by the GDPR, the right to lodge a complaint with a supervisory authority (section 17.9). When the transfer uses the ANPD's standard contractual clauses, the Contracting Party publishes this information in the manner of Article 17 of ANPD Resolution CD/ANPD No. 19/2024, which can be done in its own privacy policy.
The PMR app, including the version carrying the Contracting Party's brand, displays this policy, at
The Field User exercises their rights with the Contracting Party, as set out in section 8.
13.12. Sensitive data. The Contracting Party should not send through the integration sensitive personal data, as defined in Article 5, II, of the LGPD and the special categories in Article 9 of the GDPR, nor selfies or other images used to identify people.
13.13. Relation to section 6. The integration does not change section 6. BEC System does not use this data for its own purposes. Sending to the AI provider happens on the Contracting Party's initiative and instruction. In this sending, BEC System acts as the Contracting Party's processor and does not use the data for its own purposes.
13.14. Instructions to the AI tool. PMR instructs the AI tool to do only the part of the request that belongs to PMR, to hand over the rest as text ready for the person to copy, and not to offer another app or connector. When the person asks on their own to use another tool, the instruction is to pass only the data requested, with no document, contact or credential. These instructions are guidance, and the tool may not follow them. The control that counts is what PMR returns, described in 13.6.
The integration offers no tool to read photographs, selfies, location or survey answers.
13.2. Choice of provider. The Contracting Party chooses, contracts and configures the AI provider. BEC System does not contract this provider, does not keep the Contracting Party's access key to it and does not define how it processes the data. The provider acts under the conditions the Contracting Party accepted with it and is not a sub-processor of BEC System. The exception is the support connection in 13.3, where BEC System chooses the provider.
The Contracting Party should send personal data through the integration only if, under the terms of the plan it contracted, the provider processes that data on the Contracting Party's behalf and does not use it to train models. By accepting the AI Addendum, the Contracting Party declares that the chosen plan meets this condition. The declaration is mandatory for acceptance, and PMR records it.
13.3. Authorization and acceptance. Only a Contracting Party user with the superadmin profile in the panel authorizes the integration, and acceptance of the AI Addendum is a condition for activating it, both for the token and for login. BEC System staff with the support profile (SUPER) can see the "Integração com IA" tab and revoke tokens and connections to provide support, but cannot accept the addendum or generate a token on the Contracting Party's behalf. Without this authorization, the Contracting Party's integration does not work.
PMR records the date, user, IP address, browser, provider, version and hash of the text accepted, which includes the declaration in 13.2, and sends a copy of the acceptance to the registered e-mail address of the superadmin who accepted, when there is one. Because e-mail is not mandatory in PMR, if no e-mail is registered the copy is not sent, and the acceptance screen says so. BEC System keeps this record for the term of the contract and for 5 more years after it ends, for the regular exercise of rights, or until the end of any judicial, administrative or arbitration proceeding, or complaint, involving the acceptance, if that lasts longer. At the end of the period, BEC System deletes the record or, while technical deletion does not exist, anonymizes it and restricts access to it.
The Contracting Party's connection follows one of two paths:
Token: the superadmin generates the token in the panel, with permissions for querying, preparing a preview and writing, and a validity of 30, 90 or 180 days. PMR keeps only the hash of the token. The token does not depend on who generated it: it is valid until it expires or is revoked, even if that person leaves the company.
Login (OAuth): the superadmin signs in to the panel from the AI tool, checks the provider, and chooses the permissions and a validity of 30, 90 or 180 days. The access credential lasts 1 hour, and the AI tool renews it. The renewal lapses after 30 days without use and never goes beyond the validity of the connection. The connection stops working if the superadmin who approved it is deactivated or loses the profile.
BEC System support connection: a single BEC System team user with the SUPER profile, defined in configuration, can connect to the Contracting Party's PMR an AI tool chosen by BEC, Claude, from Anthropic, on the Claude Team plan (section 14.6), to provide support. BEC System has not yet contracted Claude Team, and the contracting has no set date. Until then, BEC does not use the Contracting Party's data in the support connection, and the system accepts this connection only in BEC System's demonstration environment. BEC opens the support connection only at the Contracting Party's request. No other BEC user has this permission. This connection does not use the Contracting Party's acceptance: BEC records acceptance of an internal support term, with date, user, IP address, browser, provider, version and hash. It is valid for 1, 3 or 7 days. The query and preview-preparation permissions come checked, and writing is valid only when the support user checks it for that connection. The connection appears in the "Integração com IA" tab as "Suporte BEC", with who created it and the validity, and the Contracting Party's active superadmins who have a registered e-mail address receive an e-mail notice when it is created. The Contracting Party's superadmin can revoke it at any time, as can BEC System staff with the SUPER profile. In it, the AI provider processes the Contracting Party's data on BEC System's behalf and is its sub-processor (section 14.6).
13.4. Revocation. To end access, the Contracting Party's superadmin revokes the token or the connection in the "Integração com IA" tab of the panel. BEC System's support team (SUPER profile) can also revoke, to provide support. The revocation takes effect from the next request.
Removing the connector or deleting the token in the AI tool does not revoke access in PMR. Revocation happens only in the panel.
Revocation prevents new access but does not delete what the AI provider has already received. That content follows the provider's conditions, and it is up to the Contracting Party to ask the provider to delete it.
A connection accepted under a previous version of the AI Addendum stays valid until it expires or is revoked, but does not receive new features that only the current version describes.
13.5. What the AI sends to PMR. The AI sends registration data as text or as a spreadsheet (CSV, TXT, XLSX or XLS, up to 5 MB). In the records of supervisors, promoters, clients and affiliates, this data can include name, CPF or CNPJ, RG or state registration number, address, phone numbers, e-mail, contact, login and password. In the store record, it can include the manager's name. In the promoter record, the device identifier.
With the write permission, the AI adds records and changes existing records, including login, password, access group and status (active or inactive) of people. When changing, a column sent empty deletes the stored value.
Everything the person types or attaches in the conversation, including CPF and password, passes through the AI provider. When the person authorizes it, the AI itself can create temporary logins and passwords for supervisors and promoters; these credentials stay in the conversation history, and the Contracting Party can replace them in the PMR panel.
13.6. What PMR returns to the AI.
Record search: at most 20 per query. For people, PMR returns identifier, code, name and status, with no document or contact details.
Spreadsheet sent: column names, total number of rows and the first 5 rows, unmasked, as they came in the file the AI itself sent.
Change preview: the current value and the new value of each field sent. In the records of people (supervisors, promoters, and clients or affiliates who are natural persons), CPF, CNPJ, RG, state registration number, e-mail, phone numbers, address, neighborhood, postal code, contact, device identifier and login appear only with the last 2 characters. Name, city, state and status appear unmasked, so the person can check they have the right record. In stores, the manager's name and phone number appear masked, and company data appears unmasked.
Batch result: counts and errors per row. The error message may repeat the rejected value, except the CPF, which PMR hides.
The password stored in PMR never returns to the AI.
13.7. Preview and confirmation. Preparation validates the data and writes nothing. PMR instructs the AI tool to show the preview and to write only after the person confirms in the conversation.
PMR does not see the conversation and cannot prove that confirmation. It is up to the Contracting Party to check the preview and follow the result of each batch in the "Integração com IA" tab.
13.8. Temporary retention. PMR keeps the rows of each batch encrypted and deletes them when writing ends. A batch that is not written is valid for 24 hours. After that, PMR deletes the rows in the next cleanup, which runs every hour and on each access to the tab or to the batch tools.
The spreadsheets sent by the AI stay in a folder restricted to the connection that sent them. PMR deletes them in the first cleanup after 24 hours from the upload, even if the batch has already been written.
The batch summary, with status, preview, counts and errors per row, stays in PMR for 90 days and is then deleted.
13.9. Record of actions. PMR records in the panel's user log, with the "ia" mark: generation, revocation and expiry of tokens and connections, including support ones; authorization and refusal of connections; spreadsheet uploads; record searches; preparation of insert and change batches; the result of each batch; each record changed; and refused calls.
Each line identifies the token or connection, the responsible person (who generated the token or who approved the connection), the register, the record identifiers and the field names. This record does not keep field values, CPF, password, row contents or file names. Batch queries and queries on the structure of the registration records do not generate a line in this log. The body of the AI's calls does not enter the application server's technical log (section 15.3).
13.10. International transfer. AI providers may process data outside Brazil. By activating the integration, the Contracting Party, as Controller, defines the provider and the destination of the data and is responsible for bringing the transfer within Article 33 of the LGPD and the ANPD's regulations.
The Contracting Party maintains a valid transfer mechanism with the provider: the standard contractual clauses approved by the ANPD, adopted in full and without change, or another mechanism under Article 33 of the LGPD. The ANPD's adequacy decision currently in force (ANPD Resolution CD/ANPD No. 32/2026) covers only the European Union, Iceland, Liechtenstein and Norway.
BEC System carries out the sending only on the Contracting Party's instruction. When the AI provider accesses PMR from abroad, BEC System transmits the data on the Contracting Party's instruction and gives it the information it has to bring the transfer within those rules. When the GDPR reaches the Contracting Party, it is also responsible for bringing the transfer to the AI provider it chose within Chapter V of the GDPR (Articles 44 to 49). Section 17.5 covers transfers to BEC System's sub-processors.
13.11. Legal basis and field team. The Contracting Party defines the legal basis for the processing. Before the first sending of its field team's data through the integration, the Contracting Party informs that team, prominently, which provider receives the data, for what purpose, in which country, for how long, who is responsible for the processing and how to exercise their rights, including the right to petition the ANPD or, for a data subject covered by the GDPR, the right to lodge a complaint with a supervisory authority (section 17.9). When the transfer uses the ANPD's standard contractual clauses, the Contracting Party publishes this information in the manner of Article 17 of ANPD Resolution CD/ANPD No. 19/2024, which can be done in its own privacy policy.
The PMR app, including the version carrying the Contracting Party's brand, displays this policy, at
promomktreport.com.br/politica-de-privacidade/, with the Contracting Party's name as Controller of the data.The Field User exercises their rights with the Contracting Party, as set out in section 8.
13.12. Sensitive data. The Contracting Party should not send through the integration sensitive personal data, as defined in Article 5, II, of the LGPD and the special categories in Article 9 of the GDPR, nor selfies or other images used to identify people.
13.13. Relation to section 6. The integration does not change section 6. BEC System does not use this data for its own purposes. Sending to the AI provider happens on the Contracting Party's initiative and instruction. In this sending, BEC System acts as the Contracting Party's processor and does not use the data for its own purposes.
13.14. Instructions to the AI tool. PMR instructs the AI tool to do only the part of the request that belongs to PMR, to hand over the rest as text ready for the person to copy, and not to offer another app or connector. When the person asks on their own to use another tool, the instruction is to pass only the data requested, with no document, contact or credential. These instructions are guidance, and the tool may not follow them. The control that counts is what PMR returns, described in 13.6.
Part V: Sub-processors and Retention Periods
14. Sub-processors
14.1. What a sub-processor is. A sub-processor is a company that BEC System engages to carry out part of the service and that, for that purpose, processes personal data on behalf of the Contracting Party. Toward the Contracting Party, BEC System is responsible for its sub-processors, under the contract. By accepting these Terms, the Contracting Party gives BEC System general authorization to engage the sub-processors in this section, including the support AI provider in 14.6, with the notice and the right to object in 14.5. The authorization also applies to a Contracting Party that has not accepted the AI Addendum.
14.2. Current sub-processors.
Until the migration to Amazon SES, some accounts still send the panel's e-mails through the agency's own e-mail service, configured by the agency. That service is the Contracting Party's choice, as Controller, and is not a sub-processor of BEC System. The same applies to the external service that the Contracting Party contracts to look up the invoice from the QR code (section 5).
Google Maps Platform, independent controller. PMR uses the Google Maps Platform for maps, distance calculation and conversion of coordinates into addresses. Google receives store addresses, the registered addresses of the phone lines used for phone check-in and the coordinates of visit records. The requests carry no name or user identifier, and no date or time of the record. Part of the sending leaves from PMR's server, and part leaves directly from the browser of whoever uses the panel, which loads Google's maps and asks Google for the area shown on screen. From the moment these rules go live, BEC System reduces what goes to Google: routes on the panel's maps are drawn as straight lines in the browser, without asking Google for the route; the alert e-mail carries no Google map image; visit-record coordinates sent to Google carry 4 decimal places, a precision of about 11 metres; and the phone check-in screen shows the distance already stored in PMR, without asking Google for a new route. The map link in the alert e-mail only leads to Google if the recipient clicks it. Under the Google Maps Platform terms, Google acts as an independent controller of this data, and not as a sub-processor of BEC System, and may use and retain it to provide and improve its products. Sending this data to Google is part of the contracted service: BEC System does it as processor, on the Contracting Party's instructions, with the legal basis that the Contracting Party sets (section 6). Google's use of this data for its own products follows Google's terms, as an independent controller.
14.3. International transfer. The sub-processors in table 14.2 may process data outside Brazil, in the locations in the "Location" column. AWS stores and processes PMR data in the United States, in the us-east-1 region (Northern Virginia), chosen by BEC System. Under AWS's data processing addendum, it does not transfer the data outside that region, except when necessary to provide the service or to comply with the law or a valid order from an authority. Through Firebase Cloud Messaging, Google receives the device identifier, the notification text and technical delivery data, and may process them in any country where it or its sub-processors have facilities. Anthropic receives Contracting Party data only in the support connection, after Claude Team is contracted (section 14.6).
The transfer serves only to provide the service: hosting the system, storing the data, sending e-mails and notifications and, in the support connection, handling the Contracting Party's request. It lasts as long as the contract does, with the retention periods in section 15.
BEC System's relationship with these suppliers follows their standard terms. Under the terms of AWS and, when contracted, of Anthropic, with a data processing addendum, the supplier acts as processor, processes the data according to BEC System's instructions, maintains security measures, reports incidents and is responsible for its own sub-processors. Under Firebase's standard data processing terms, Google acts in the same way for Firebase Cloud Messaging. These terms do not include the standard contractual clauses approved by the ANPD (ANPD Resolution CD/ANPD No. 19/2024), and BEC System has not signed them with these suppliers.
To reduce the risk, BEC System keeps PMR's server, database, files and e-mails in a single AWS region (us-east-1), encrypts the connections of the app and of the panel to the server, and keeps photographs and files encrypted at rest (sections 7 and 15.5). Until Claude Team is contracted, the system accepts the support connection only in BEC System's demonstration environment, with no Contracting Party data. Google Maps, as an independent controller, is in section 14.2.
The Contracting Party, as controller, checks that the transfer has a valid legal ground and mechanism and informs the data subject about it (Articles 4 and 17 of Annex I to ANPD Resolution CD/ANPD No. 19/2024). This section and table 14.2 give the destination country, the purpose, the data, the duration and the suppliers. At the Contracting Party's request, BEC System provides the other information it has about the transfer and the security measures.
When BEC System signs the ANPD's standard clauses with one of these suppliers, or changes the location of the data, it updates this section and notifies the Contracting Parties at their registered e-mail address, within the period in section 14.5. Adding or replacing a sub-processor follows section 14.5.
The data subject may ask for information about the transfer from the controller of their data, which is the Contracting Party. If the request reaches BEC System, it forwards it to the Contracting Party within 5 business days, as in section 8, with the information it has.
For a data subject covered by the GDPR, see section 17.5.
14.4. The Contracting Party's AI provider. The AI provider that the Contracting Party connects through the integration in section 13 is not a sub-processor of BEC System. It acts under the contract between the Contracting Party and that provider (section 13.2).
14.5. Change of sub-processor. Before adding or replacing a sub-processor that processes personal data, BEC System notifies the Contracting Parties at their registered e-mail address, 30 days in advance. The Contracting Party may object within the same period, in writing, through the channel in section 11. Adding or replacing a sub-processor is a material change (section 10): the list in this section applies from the date of the new major version, stated in the notice.
14.6. BEC System's support AI. In the support connection in 13.3, BEC System uses Claude, from Anthropic, on the Claude Team plan, under Anthropic's commercial terms and data processing addendum, which prohibit it from using the data to train models. BEC System has not yet contracted Claude Team, and the contracting has no set date. Until then, BEC does not use the Contracting Party's data in the support connection, and the system accepts this connection only in BEC System's demonstration environment. When it contracts, BEC System notifies the Contracting Parties by e-mail, with the notice period in section 10, before using Contracting Party data in the support connection. Anthropic processes the Contracting Party's data on BEC's behalf and is its sub-processor for as long as the connection lasts. BEC System imposes on it the data protection obligations it assumes toward the Contracting Party and deletes the support conversations at the end of each support session. BEC keeps the sending of conversation ratings turned off.
14.2. Current sub-processors.
| Sub-processor | Service | Data processed | Location |
|---|---|---|---|
| Amazon Web Services (AWS) | Application server (EC2), database (RDS PostgreSQL), files and photographs (S3) and sending of notifications to the phone (SNS) | All PMR data, including photographs, selfies, location and survey answers | United States, region us-east-1 (Northern Virginia) |
| Google (Firebase Cloud Messaging) | Delivery of notifications to the app | Device identifier for notifications and notification text | United States and other countries where Google operates |
| Amazon Web Services (AWS): Amazon SES | E-mails from the application server and the panel, including alerts, the copy of the acceptance in 13.3, the support connection notice and, once the acceptance screen goes live, the link to the "Privacidade" page in section 10, sent from noreply@promomktreport.com | E-mail address and message content | United States, region us-east-1 (Northern Virginia) |
| Anthropic (Claude) | Support connection in 13.3, only while it is active | The same data as in 13.5 and 13.6 | Storage in the United States; processing may pass through the United States, Europe, Asia and Australia, according to Anthropic's privacy center for commercial products (read on 15 November 2026). Claude Team plan, not yet contracted, under the commercial terms and the data processing addendum (section 14.6) |
Google Maps Platform, independent controller. PMR uses the Google Maps Platform for maps, distance calculation and conversion of coordinates into addresses. Google receives store addresses, the registered addresses of the phone lines used for phone check-in and the coordinates of visit records. The requests carry no name or user identifier, and no date or time of the record. Part of the sending leaves from PMR's server, and part leaves directly from the browser of whoever uses the panel, which loads Google's maps and asks Google for the area shown on screen. From the moment these rules go live, BEC System reduces what goes to Google: routes on the panel's maps are drawn as straight lines in the browser, without asking Google for the route; the alert e-mail carries no Google map image; visit-record coordinates sent to Google carry 4 decimal places, a precision of about 11 metres; and the phone check-in screen shows the distance already stored in PMR, without asking Google for a new route. The map link in the alert e-mail only leads to Google if the recipient clicks it. Under the Google Maps Platform terms, Google acts as an independent controller of this data, and not as a sub-processor of BEC System, and may use and retain it to provide and improve its products. Sending this data to Google is part of the contracted service: BEC System does it as processor, on the Contracting Party's instructions, with the legal basis that the Contracting Party sets (section 6). Google's use of this data for its own products follows Google's terms, as an independent controller.
14.3. International transfer. The sub-processors in table 14.2 may process data outside Brazil, in the locations in the "Location" column. AWS stores and processes PMR data in the United States, in the us-east-1 region (Northern Virginia), chosen by BEC System. Under AWS's data processing addendum, it does not transfer the data outside that region, except when necessary to provide the service or to comply with the law or a valid order from an authority. Through Firebase Cloud Messaging, Google receives the device identifier, the notification text and technical delivery data, and may process them in any country where it or its sub-processors have facilities. Anthropic receives Contracting Party data only in the support connection, after Claude Team is contracted (section 14.6).
The transfer serves only to provide the service: hosting the system, storing the data, sending e-mails and notifications and, in the support connection, handling the Contracting Party's request. It lasts as long as the contract does, with the retention periods in section 15.
BEC System's relationship with these suppliers follows their standard terms. Under the terms of AWS and, when contracted, of Anthropic, with a data processing addendum, the supplier acts as processor, processes the data according to BEC System's instructions, maintains security measures, reports incidents and is responsible for its own sub-processors. Under Firebase's standard data processing terms, Google acts in the same way for Firebase Cloud Messaging. These terms do not include the standard contractual clauses approved by the ANPD (ANPD Resolution CD/ANPD No. 19/2024), and BEC System has not signed them with these suppliers.
To reduce the risk, BEC System keeps PMR's server, database, files and e-mails in a single AWS region (us-east-1), encrypts the connections of the app and of the panel to the server, and keeps photographs and files encrypted at rest (sections 7 and 15.5). Until Claude Team is contracted, the system accepts the support connection only in BEC System's demonstration environment, with no Contracting Party data. Google Maps, as an independent controller, is in section 14.2.
The Contracting Party, as controller, checks that the transfer has a valid legal ground and mechanism and informs the data subject about it (Articles 4 and 17 of Annex I to ANPD Resolution CD/ANPD No. 19/2024). This section and table 14.2 give the destination country, the purpose, the data, the duration and the suppliers. At the Contracting Party's request, BEC System provides the other information it has about the transfer and the security measures.
When BEC System signs the ANPD's standard clauses with one of these suppliers, or changes the location of the data, it updates this section and notifies the Contracting Parties at their registered e-mail address, within the period in section 14.5. Adding or replacing a sub-processor follows section 14.5.
The data subject may ask for information about the transfer from the controller of their data, which is the Contracting Party. If the request reaches BEC System, it forwards it to the Contracting Party within 5 business days, as in section 8, with the information it has.
For a data subject covered by the GDPR, see section 17.5.
14.4. The Contracting Party's AI provider. The AI provider that the Contracting Party connects through the integration in section 13 is not a sub-processor of BEC System. It acts under the contract between the Contracting Party and that provider (section 13.2).
14.5. Change of sub-processor. Before adding or replacing a sub-processor that processes personal data, BEC System notifies the Contracting Parties at their registered e-mail address, 30 days in advance. The Contracting Party may object within the same period, in writing, through the channel in section 11. Adding or replacing a sub-processor is a material change (section 10): the list in this section applies from the date of the new major version, stated in the notice.
14.6. BEC System's support AI. In the support connection in 13.3, BEC System uses Claude, from Anthropic, on the Claude Team plan, under Anthropic's commercial terms and data processing addendum, which prohibit it from using the data to train models. BEC System has not yet contracted Claude Team, and the contracting has no set date. Until then, BEC does not use the Contracting Party's data in the support connection, and the system accepts this connection only in BEC System's demonstration environment. When it contracts, BEC System notifies the Contracting Parties by e-mail, with the notice period in section 10, before using Contracting Party data in the support connection. Anthropic processes the Contracting Party's data on BEC's behalf and is its sub-processor for as long as the connection lasts. BEC System imposes on it the data protection obligations it assumes toward the Contracting Party and deletes the support conversations at the end of each support session. BEC keeps the sending of conversation ratings turned off.
15. Retention Periods
15.1. General rule. BEC System keeps the data for the term of the contract. At the end of the contract, it returns the Contracting Party's data within 30 days, registration data in a spreadsheet and photographs and selfies in a compressed file, with one folder per campaign, and then deletes it, with the copies. Automatic database backups expire on their own within 7 days. At the Controller's request, it deletes the data earlier. In both cases, it keeps what the law requires or what is necessary for the regular exercise of rights (section 7), and the panel's user log, kept for 6 more months (section 15.3). The periods below apply during the contract, except where the line says otherwise.
15.2. Operational data.
15.3. Technical and access records.
15.4. AI integration (section 13).
15.5. Storage security. In AWS storage, photographs and files are encrypted at rest. Reading of photographs follows section 7.
15.2. Operational data.
| Data | Period |
|---|---|
| Registers, surveys and answers | During the contract |
| Photographs and selfies | During the contract. A photograph deleted in the panel stops appearing immediately, and the storage deletes the previous version 30 days later. |
| Automatic database backups | 7 days |
| Manual database copies, made only for maintenance, and migration copies | Up to 30 days after they are created. Copies made before this rule, in June and July 2026, including those on the server's disk, are deleted by 16 February 2027. After that date, BEC System does not keep a copy of the database on the server's disk. |
| Record of acceptance of these Terms in the app (section 10) | For as long as the user's registration exists and for 6 more months |
| Record | Content | Period |
|---|---|---|
| Panel user log, including the "ia" mark in section 13.9 | Who did what and when | During the contract and for 6 more months after it ends. Until the automated routine exists, BEC System carries out this deletion manually when each contract ends. |
| App technical log | Failures and technical events sent by the app | 180 days |
| Application server technical log | App requests, errors and response times, without passwords or the content of submitted surveys, and with the login user masked | 7 days |
| Web server access logs | IP address, date, time and address accessed | Up to 15 days |
| PHP service logs | Server errors | Up to 12 weeks |
| Record of acceptance of this policy in the panel (section 10) | User, version accepted, date and time, IP address and browser | During the contract and for 5 more years after it ends, or until the end of a dispute over the acceptance, if that lasts longer |
| Record of the e-mail sent under section 10 | User, type of sending, version, date and time and result, without the e-mail address | During the contract and for 5 more years after it ends, or until the end of a dispute over the acceptance, if that lasts longer |
| Data | Period |
|---|---|
| Batch rows, encrypted | Deleted when writing ends. An unwritten batch is valid for 24 hours and is deleted in the next cleanup, which runs every hour |
| Spreadsheets sent by the AI | First cleanup after 24 hours from the upload |
| Batch preview and result | 90 days |
| Record of acceptance of the AI Addendum and of the support term | During the contract and for 5 more years, or until the end of a dispute over the acceptance, if that lasts longer |
Part VI: Cookies and Measurement
16. Cookies and measurement technologies
16.1. PMR panel and app. The panel uses the session cookie, necessary to keep the login, and screen preference cookies, which store how the user arranged the lists (filters, order and number of rows). It does not use audience measurement or advertising cookies. The app does not use cookies; it stores on the device the notification identifier in section 5.
16.2. Website promomktreport.com.br. The cookie banner offers, on the same layer and with the same prominence, to accept all cookies or use only the essential ones, and the "Cookies" link in the footer opens it again. Before your choice, and if you choose only the essential ones, the website does not load measurement or marketing tools. The website uses:
You can change your choice at any time through the "Cookies" link in the footer, and withdrawing consent is as easy as giving it.
16.2. Website promomktreport.com.br. The cookie banner offers, on the same layer and with the same prominence, to accept all cookies or use only the essential ones, and the "Cookies" link in the footer opens it again. Before your choice, and if you choose only the essential ones, the website does not load measurement or marketing tools. The website uses:
- Matomo, on our own server (
analytics.promomktreport.com.br), to count visits and clicks on contacts. It loads and sets the cookies_pk_idand_pk_sesonly after you accept. - Google Analytics, to measure use of the website. It loads only after you accept.
- HubSpot, which receives the data from the contact or quote form when you submit it. A copy of the form data goes to
analytics.promomktreport.com.br, to record the origin of the contact. HubSpot's browsing tracking works only after you accept. - Cookie
pmr_lang, set when you choose the language, for 1 year. - Record of your choice in the banner (
pmr_consent), stored in your browser.
You can change your choice at any time through the "Cookies" link in the footer, and withdrawing consent is as easy as giving it.
Part VII: Data Subjects in the European Union
17. Application of the GDPR
17.1. When the GDPR applies. BRANDAO & COSTA PRESTACAO DE SERVICOS DE DIGITACAO LTDA (BEC System), CNPJ 10.673.919/0001-08, has its seat at Av. Paulista, 1471, conj. 511, Bela Vista, São Paulo, SP, CEP 01311-927, Brazil. BEC System has no office or business address in the Union. The company is managed from Spain. BEC System considers that it has an establishment in the Union, because it is managed from Spain (Article 3(1)), and applies Regulation (EU) 2016/679 (GDPR) to the processing of data from the website, the forms and marketing.
BEC System acts in two roles:
a) On the website promomktreport.com.br, in the contact and quote forms and in marketing actions, BEC System is the controller ("controlador" under the LGPD). BEC System applies the GDPR to this processing. You exercise your rights directly with us (section 17.10).
b) In Promo MKT Report (PMR), BEC System is a processor ("operadora" under the LGPD). It processes the data on behalf of the contracting agency or company, which is the controller and decides the purposes and means. When the GDPR reaches this processing, BEC System undertakes to comply with the obligations the GDPR imposes on the processor, and the Contracting Party complies with those of the controller. To exercise your rights over PMR data, contact the agency or company you work with. If you contact us, we forward the request to it (section 8).
17.2. Roles. The Contracting Party is the controller. BEC System is the processor and processes the data only on the Contracting Party's documented instructions, including regarding transfers, except for the processing where it decides (section 4). The sub-processors in section 14 are sub-processors in the GDPR sense. The AI provider that the Contracting Party connects (section 13) acts under the Contracting Party's contract with it. BEC's support AI provider (section 14.6), Anthropic, on the Claude Team plan and under its data processing addendum, is BEC's sub-processor from the moment that plan is contracted.
At the end of the contract, BEC System returns the data to the Contracting Party and then deletes it, as section 15.1 says (Article 28(3)(g)). It makes available to the Contracting Party the documentation necessary to demonstrate compliance with the obligations of a processor. The audit is carried out through that documentation, at the Contracting Party's request, with 30 days' notice (Article 28(3)(h)).
17.3. Legal basis. The Contracting Party chooses and informs the legal basis for each purpose, among those in Article 6(1) of the GDPR, except for the purposes where BEC System decides (section 4). In the employment relationship, the GDPR indicates that consent is not an adequate basis where there is a clear imbalance between the parties (Recital 43), and the law of the Member State may provide its own rules for employee data (Article 88). PMR should not receive the special categories of data in Article 9.
17.4. Rights and deadlines. The data subject may ask the Contracting Party for access, rectification, erasure, restriction of processing and data portability, and may object to processing based on legitimate interests (Articles 15 to 21). They have the right not to be subject to a decision based solely on automated processing that produces legal effects or similarly significantly affects them (Article 22). Where processing is based on consent, they may withdraw it at any time. The Contracting Party responds within 1 month of receiving the request, a period that may be extended by up to 2 months for complex or numerous requests, with notice to the data subject within the first month (Article 12(3)). BEC System helps the Contracting Party respond, with the panel's tools, and forwards to it any request it receives (section 8).
17.5. Transfers. The data of data subjects in the EU that the app and the panel send to PMR goes to AWS servers in the United States (us-east-1), which BEC System, a company established in Brazil, uses as a sub-processor (section 14.2). The European Commission recognized an adequate level of protection in Brazil for controllers and processors subject to the LGPD (Commission Implementing Decision (EU) 2026/179 of 26 January 2026). That decision covers the transfer to BEC System, but not storage in the United States. Under the decision, sending from Brazil to another country is an onward transfer, which follows the LGPD's rules on international transfer (Recitals 96 to 98). Section 14.3 describes these transfers and states that the suppliers' terms do not include the ANPD's standard clauses. When the GDPR applies to the data, AWS's data processing addendum provides for the European Commission's standard contractual clauses for data subject to the GDPR, or another European mechanism that AWS adopts in their place; Firebase's terms provide for a transfer solution or those clauses; and Anthropic's addendum incorporates them to the extent required by applicable law. The data subject may ask the Contracting Party for information about these safeguards.
17.6. Personal data breach. BEC System notifies the Contracting Party without undue delay after becoming aware of a personal data breach, within 24 hours, with the information available, and supplements the notice within 2 business days, so that it can notify the supervisory authority within 72 hours, when the GDPR requires (Article 33), and inform data subjects in case of high risk (Article 34).
17.7. Representative in the Union. BEC System does not designate a representative in the Union (Article 27 of the GDPR). A representative is required only when the GDPR applies under Article 3(2) to a party with no establishment in the Union, and BEC System considers that it has an establishment in Spain (section 17.1).
17.8. Data Protection Officer. BEC System's data protection officer, for the LGPD and for the GDPR, is Carlos Eduardo Brandão, carlos@promomktreport.com.br, until an external Data Protection Officer is designated. This is the same contact as in section 11. The officer serves data subjects in the EU and receives contacts from the supervisory authority.
17.9. Supervisory authority. You may lodge a complaint with the supervisory authority of the Member State where you reside, where you work or where the alleged infringement took place (Article 77). If BEC System has an establishment in Spain, the supervisory authority for its activity there is the Agencia Española de Protección de Datos (AEPD), www.aepd.es, which may act as lead supervisory authority if processing substantially affects data subjects in more than one Member State (Article 56(1) and Article 4(23)(b) of the GDPR). The AEPD receives complaints through its electronic office https://sedeaepd.gob.es/sede-electronica/home. You may also turn to the courts of the Member State where you reside or, if BEC System has an establishment in Spain, to those of Spain (Article 79(2)). None of this removes your right to petition Brazil's National Data Protection Authority (ANPD).
17.10. Website, forms and marketing. In these processing activities, BEC System is the controller:
BEC System acts in two roles:
a) On the website promomktreport.com.br, in the contact and quote forms and in marketing actions, BEC System is the controller ("controlador" under the LGPD). BEC System applies the GDPR to this processing. You exercise your rights directly with us (section 17.10).
b) In Promo MKT Report (PMR), BEC System is a processor ("operadora" under the LGPD). It processes the data on behalf of the contracting agency or company, which is the controller and decides the purposes and means. When the GDPR reaches this processing, BEC System undertakes to comply with the obligations the GDPR imposes on the processor, and the Contracting Party complies with those of the controller. To exercise your rights over PMR data, contact the agency or company you work with. If you contact us, we forward the request to it (section 8).
17.2. Roles. The Contracting Party is the controller. BEC System is the processor and processes the data only on the Contracting Party's documented instructions, including regarding transfers, except for the processing where it decides (section 4). The sub-processors in section 14 are sub-processors in the GDPR sense. The AI provider that the Contracting Party connects (section 13) acts under the Contracting Party's contract with it. BEC's support AI provider (section 14.6), Anthropic, on the Claude Team plan and under its data processing addendum, is BEC's sub-processor from the moment that plan is contracted.
At the end of the contract, BEC System returns the data to the Contracting Party and then deletes it, as section 15.1 says (Article 28(3)(g)). It makes available to the Contracting Party the documentation necessary to demonstrate compliance with the obligations of a processor. The audit is carried out through that documentation, at the Contracting Party's request, with 30 days' notice (Article 28(3)(h)).
17.3. Legal basis. The Contracting Party chooses and informs the legal basis for each purpose, among those in Article 6(1) of the GDPR, except for the purposes where BEC System decides (section 4). In the employment relationship, the GDPR indicates that consent is not an adequate basis where there is a clear imbalance between the parties (Recital 43), and the law of the Member State may provide its own rules for employee data (Article 88). PMR should not receive the special categories of data in Article 9.
17.4. Rights and deadlines. The data subject may ask the Contracting Party for access, rectification, erasure, restriction of processing and data portability, and may object to processing based on legitimate interests (Articles 15 to 21). They have the right not to be subject to a decision based solely on automated processing that produces legal effects or similarly significantly affects them (Article 22). Where processing is based on consent, they may withdraw it at any time. The Contracting Party responds within 1 month of receiving the request, a period that may be extended by up to 2 months for complex or numerous requests, with notice to the data subject within the first month (Article 12(3)). BEC System helps the Contracting Party respond, with the panel's tools, and forwards to it any request it receives (section 8).
17.5. Transfers. The data of data subjects in the EU that the app and the panel send to PMR goes to AWS servers in the United States (us-east-1), which BEC System, a company established in Brazil, uses as a sub-processor (section 14.2). The European Commission recognized an adequate level of protection in Brazil for controllers and processors subject to the LGPD (Commission Implementing Decision (EU) 2026/179 of 26 January 2026). That decision covers the transfer to BEC System, but not storage in the United States. Under the decision, sending from Brazil to another country is an onward transfer, which follows the LGPD's rules on international transfer (Recitals 96 to 98). Section 14.3 describes these transfers and states that the suppliers' terms do not include the ANPD's standard clauses. When the GDPR applies to the data, AWS's data processing addendum provides for the European Commission's standard contractual clauses for data subject to the GDPR, or another European mechanism that AWS adopts in their place; Firebase's terms provide for a transfer solution or those clauses; and Anthropic's addendum incorporates them to the extent required by applicable law. The data subject may ask the Contracting Party for information about these safeguards.
17.6. Personal data breach. BEC System notifies the Contracting Party without undue delay after becoming aware of a personal data breach, within 24 hours, with the information available, and supplements the notice within 2 business days, so that it can notify the supervisory authority within 72 hours, when the GDPR requires (Article 33), and inform data subjects in case of high risk (Article 34).
17.7. Representative in the Union. BEC System does not designate a representative in the Union (Article 27 of the GDPR). A representative is required only when the GDPR applies under Article 3(2) to a party with no establishment in the Union, and BEC System considers that it has an establishment in Spain (section 17.1).
17.8. Data Protection Officer. BEC System's data protection officer, for the LGPD and for the GDPR, is Carlos Eduardo Brandão, carlos@promomktreport.com.br, until an external Data Protection Officer is designated. This is the same contact as in section 11. The officer serves data subjects in the EU and receives contacts from the supervisory authority.
17.9. Supervisory authority. You may lodge a complaint with the supervisory authority of the Member State where you reside, where you work or where the alleged infringement took place (Article 77). If BEC System has an establishment in Spain, the supervisory authority for its activity there is the Agencia Española de Protección de Datos (AEPD), www.aepd.es, which may act as lead supervisory authority if processing substantially affects data subjects in more than one Member State (Article 56(1) and Article 4(23)(b) of the GDPR). The AEPD receives complaints through its electronic office https://sedeaepd.gob.es/sede-electronica/home. You may also turn to the courts of the Member State where you reside or, if BEC System has an establishment in Spain, to those of Spain (Article 79(2)). None of this removes your right to petition Brazil's National Data Protection Authority (ANPD).
17.10. Website, forms and marketing. In these processing activities, BEC System is the controller:
- Respond to your contact or quote request. Basis: our legitimate interests in handling the request that you or your company made (Article 6(1)(f)).
- Measure use of the website with Matomo and Google Analytics. Basis: your consent, given in the banner (Article 6(1)(a)).
- Send commercial communications by e-mail. For people in the Union, commercial e-mail is sent only with your prior authorization (Article 6(1)(a)), and the message carries no tracking image and no tracked links. These rules apply from the date given in section 12.