Braves Ads MCP privacy policy
Last updated:
Braves Ads MCP is Braves Global AS’s internal integration for managing ads and reading advertising results for the company’s own projects through the Meta Marketing API.
This policy covers personal data processed through this integration. The app is an internal working tool and does not offer public registration or login.
Who is the data controller?
BRAVES GLOBAL AS, organisation number 917 187 525, is the controller for our processing of personal data in Braves Ads MCP.
Postal address: Storgaten 29A, 4876 Grimstad, Norway.
Contact for privacy, data access and deletion: [email protected].
What data do we process?
Data is retrieved from the resources we can access at Meta, or provided by us when creating and editing ads. The fields processed depend on the task and the permissions granted to the integration.
- Accounts and resources: IDs and names of ad accounts, business resources, Facebook Pages, linked Instagram accounts, campaigns, ad sets, ads and ad creatives.
- Ad content and settings: text, images, videos, links, publishing status, budgets, schedules and audience settings used in advertising. Content may include personal data, for example if a person is pictured or named in an ad.
- Performance data: statistics from Meta including impressions, reach, clicks, advertising costs and reported actions or conversions. These are reports, usually at an aggregate level, and should not be understood as a list identifying the people who have seen or clicked an ad.
- Access and technical responses: access tokens used for authentication, resource IDs in requests and responses, and status and error messages from the API.
The use described here does not include collecting private messages, uploading customer lists or collecting card and payment details. Advertising budgets and cost figures are included in administration and performance reports.
Purposes and legal basis for processing
We use the integration to read and analyse advertising results and to create, edit and manage campaigns, ad sets, ads and ad creatives for our own projects. Data is also used to verify changes and investigate technical errors.
For personal data necessary for this internal administration, the proposed legal basis is our legitimate interest in operating, evaluating and securing our own advertising, under Article 6(1)(f) of the General Data Protection Regulation. [To be clarified before publication: the company’s assessment of necessity and the balancing of its interests against individuals’ privacy.]
A technical permission granted to the app at Meta does not, in itself, constitute consent to all forms of personal data processing. The basis for using images of people or other personal content in the advertising itself must be assessed separately.
How is data used, stored and protected?
The integration sends requests to Meta and receives responses over an HTTPS connection. Created ads and campaign changes are stored in the relevant resources at Meta.
Access tokens are stored in macOS Keychain and retrieved when the client authenticates with Meta. Access to Meta resources depends on the permissions assigned to the account or system user and the app.
Keychain storage applies to the access token. It does not mean that ad content, API responses or conversation history are stored only in Keychain.
Providers and transfers outside the EEA
Meta receives the requests needed to read or manage the relevant advertising resources and returns performance data. Meta also processes data in its own services. See Meta’s privacy policy for information about that processing.
OpenAI provides Codex, which is used to perform tasks with the integration. Data included in requests and tool responses in Codex may therefore also be processed by OpenAI.
[To be clarified: whether Pipeboard or other providers process data from Braves Ads MCP. A separate Pipeboard connection is configured, but it has not been confirmed that it belongs to this app.]
[To be clarified before publication: which Meta and OpenAI terms and account settings apply to the company’s use, any processing outside the EEA and the applicable basis for transfers. It has not been verified that data is processed exclusively within the EEA. No general guarantee of this or of specific standard contractual clauses should be given without documentation.]
How long is data retained?
[Proposed criteria, to be confirmed against actual practice: Our own exports, reports and working files are retained for as long as they are needed for ongoing advertising, evaluation, error investigation or specific documentation. Data is deleted or anonymised when no longer needed. Conversation history and local logs must be included in the same assessment.]
Data held at Meta or in Codex is also subject to the retention and deletion features and terms of those services. Removing an access token does not automatically delete ads, reports or history already stored.
Access, rectification and deletion
You can contact us to request access to personal data we process about you, have inaccurate data corrected or request deletion. You can also request restriction of processing and object to processing based on legitimate interests. These rights apply subject to the conditions in data protection legislation.
Send your request to the contact address above, preferably with the subject “Braves Ads MCP – privacy”. Describe what your request concerns and include any relevant ad or resource ID you know. Do not send access tokens or passwords. We may ask for information needed to verify your identity and locate the relevant material.
We normally respond within one month. If we cannot fulfil your request in full, we will explain why. A deletion request covers our processing and our copies; Meta’s independent processing is also handled through Meta’s own privacy and account features.
Revoking access and making a complaint
The person administering access at Meta can remove the app’s access or the relevant resource permissions and revoke the token through Meta’s access settings. You can also contact us for help stopping the integration’s access. The procedure depends on whether access is linked to a personal account or a system user.
Revocation stops the integration’s future access to the extent that permissions are removed. Existing campaigns may continue running at Meta, and previously stored data is not automatically deleted. Please request deletion separately if that is what you want.
You have the right to complain to Datatilsynet, the Norwegian Data Protection Authority, if you believe we process personal data in breach of the rules. You are welcome to contact us first so that we can investigate.
Changes to this policy
We update this policy if the use of the integration or the processing of data changes. The date at the top shows when the text was last updated.
