Bricoop Privacy Policy

This Privacy Policy explains how BRICOOP LIMITED (“Bricoop,” “we,” “us,” or “our”) processes information in connection with Bricoop Desktop, Bricoop-operated websites that link to this Privacy Policy, and related services (collectively, the “Services”). “Personal information” means information about an identified or identifiable individual, as defined by applicable law.

Bricoop Desktop is designed around a local-first architecture. Much of the information used by Bricoop Desktop is processed and stored on your device rather than collected by BRICOOP LIMITED. Local storage does not, by itself, determine or exclude any obligations Bricoop has under applicable data-protection law.

AI providers and model services operated by independent third parties, you, or your organization, including supported local or self-hosted model services, are referred to as “Providers” in this Privacy Policy.

In the current Bricoop Desktop connection model, AI requests are generally sent from your device to eligible Providers within the access sources you configure and enable. Bricoop Desktop does not ordinarily route that AI request content through Bricoop-operated AI servers. Connections may use an outbound proxy configured in Bricoop Desktop or inherited from your operating system or environment.

This Privacy Policy distinguishes between:

• information processed locally on your device;
• information sent to AI providers you choose;
• information made available to applications you connect;
• information sent to BRICOOP LIMITED; and
• information processed by infrastructure and service providers supporting Bricoop.

1. Privacy at a Glance

Bricoop Desktop is designed so that core desktop AI activity can occur without BRICOOP LIMITED receiving your AI conversations.

In particular:

• AI conversations and related application data may be stored locally on your device;
• Provider credentials are primarily stored locally;
• main and related auxiliary AI requests are routed to eligible Providers within your enabled configuration;
• local application detection and usage information are not ordinarily uploaded to Bricoop;
• Bricoop-operated update and catalog services do not need your AI prompts to function;
• Bricoop does not sell your personal information;
• Bricoop does not use or share your personal information for targeted or cross-context behavioral advertising; and
• Bricoop does not use your prompts, AI responses, files, or other AI content to train or fine-tune Bricoop AI models.

An independent Provider or Connected Application you choose may separately collect and process information. Its applicable terms, privacy practices, and obligations under applicable law govern that processing. For services or software operated by you or your organization, you or your organization manages those practices.

2. How Bricoop Desktop Works

Bricoop Desktop may connect compatible local applications to Providers, including supported local or self-hosted model services. A local deployment can keep model processing on your device, but whether a particular operation involves external communication depends on the enabled configuration and the services involved.

A typical interaction may work as follows:

1. an application on your device sends an AI request to Bricoop Desktop’s local service;
2. Bricoop Desktop processes or adapts the request locally as necessary;
3. Bricoop Desktop routes the resulting request to an available, compatible Provider within your enabled configuration;
4. the Provider returns a response, which Bricoop Desktop may process and return to the requesting application; and
5. Bricoop Desktop may store relevant conversation or usage information locally.

Depending on the Provider and feature you use, Bricoop Desktop may translate between different API formats, adapt request parameters, perform fallback processing, make additional Provider requests, or emulate functionality that the selected Provider does not natively offer.

These compatibility mechanisms may change the form of information sent to the Provider. For example, an emulated context-compaction feature may create and send a model-generated readable summary where another Provider offers a native opaque or encrypted compaction mechanism.

Related auxiliary requests may use a different eligible Provider within your enabled configuration from the one used for the main request. Some processing, such as generating readable compacted context, may continue after the main response completes without returning an additional response to the requesting application. The receiving Provider may receive the conversation context, instructions, or generated summaries needed for that auxiliary operation.

Bricoop does not represent that translated or emulated functionality has the same privacy, confidentiality, retention, or security characteristics as a Provider-native implementation.

For known material differences in data handling, privacy, or security between an official integration’s translated or emulated functionality and a Provider’s native implementation, we use reasonable efforts to disclose those differences through the product or accompanying documentation.

3. Information Processed on Your Device

Bricoop Desktop may process and store information locally, including the following categories.

AI Conversation Information

Depending on the features you use, this may include:

• prompts;
• system or developer instructions;
• conversation messages;
• Provider responses;
• tool calls and tool results;
• reasoning or context information;
• compacted conversation state;
• images and other supported inputs;
• model and request settings; and
• streaming response data.

This information may be retained locally to provide conversation continuity, caching, usage information, or other functionality you request or have enabled. Local retention and cleanup are described in the “Data Retention” section.

Provider Credentials and Account Information

Bricoop Desktop may locally store information needed to connect to Providers, such as:

• API keys;
• OAuth access tokens;
• refresh tokens;
• identity tokens;
• Provider account identifiers;
• authentication configuration; and
• related connection information.

Bricoop Desktop uses local security measures intended to protect such information.

Provider credentials are generally held in Bricoop Desktop’s encrypted local database. Operating-system credential facilities help protect local cryptographic key material; Provider credentials are not necessarily separate entries in those facilities. Encryption also protects relevant conversation artifacts. General preferences and configuration files written for Connected Applications are not all protected by the same database encryption; those Application files may contain local access credentials.

Local Connection Information

Bricoop Desktop may create local credentials, identifiers, configuration, or connection information used to allow compatible applications on your device to communicate with Bricoop Desktop.

Usage Information

Bricoop Desktop may maintain local information about your use of Providers, such as:

• Provider and model;
• request timing;
• duration;
• retry or attempt counts;
• token counts;
• completion status; and
• usage or billing classifications.

This information is used for local product functionality such as usage displays and diagnostics and is not ordinarily uploaded to Bricoop.

Where records and usage data are available, local usage information includes related auxiliary Provider calls, including calls that continue after the main response. Completed responses, logical upstream calls, and individual HTTP attempts are different measures. Records may be incomplete or updated at different times and do not constitute a complete account of every billable operation or replace a Provider’s own usage or billing records.

Application Detection

Bricoop Desktop may inspect your local environment to determine whether supported applications are installed, for example by checking application paths, files, or version information.

These checks are performed locally and are not ordinarily sent to Bricoop.

Diagnostic Information

Bricoop Desktop maintains limited diagnostic information locally to assist with troubleshooting and product reliability. Its persistent first-party diagnostic store is separate from the conversation database and is encrypted.

This store is designed to retain limited operational signals while excluding AI prompts, Provider responses, credentials, full URLs, file paths, network destinations, arbitrary external payloads, and similar sensitive content. It is distinct from terminal or developer debugging output and logs created by independent Applications or dependencies, which may have different content and protections.

Local diagnostic information is not automatically uploaded to Bricoop.

Local diagnostic persistence is enabled by default. While it is active, its maintenance process normally retains records for up to 10 days and applies storage limits; deletion is not a guarantee that every record disappears at an exact wall-clock deadline. Disabling persistence stops new persistent records and does not itself erase an existing diagnostic database.

Local Acceptance Records

Where we ask you to expressly accept the Bricoop Terms of Service and Bricoop Desktop End User License Agreement (“EULA”), Bricoop Desktop records the time of that action locally to manage the acceptance flow. This record is separate from authorization to connect to a Provider or any consent separately required by privacy law. The acceptance flow does not automatically send this record to Bricoop.

4. Information Sent to AI Providers You Choose

When you connect to or use a Provider through Bricoop Desktop, your device may send the information needed to establish or maintain the connection or perform functionality you request or have enabled, including related auxiliary processing. The connection follows the applicable network and proxy configuration.

Depending on the Provider, configuration, authentication method, and requested feature, this may include the following categories.

AI Request Information

This may include:

• prompts;
• system or developer instructions;
• conversation context;
• prior messages;
• tool definitions;
• tool calls and results;
• images or other supported media;
• model selection;
• model settings;
• generated summaries or transformed context;
• structured-output instructions; and
• other request information needed for the functionality you request.

Authentication and Account Information

This may include:

• API keys;
• OAuth credentials;
• Provider account identifiers;
• authentication parameters; and
• information necessary to establish or maintain the Provider connection.

Technical and Connection Information

Depending on the integration and authentication requirements, technical and connection information may include the following. Not every Provider receives every category.

• locally generated device identifiers;
• session or conversation identifiers;
• application, connection, or cache-related identifiers;
• Provider or model information and configured connection metadata;
• limited operating-system or processor information; and
• technical request metadata.

Compatibility, Translation, and Emulation

Different Providers expose different APIs and capabilities.

To make applications interoperable with different Providers, Bricoop Desktop may:

• transform requests or responses;
• map fields between protocols;
• add instructions generated by Bricoop Desktop;
• repair or restructure output;
• generate intermediate summaries;
• make additional Provider requests;
• implement fallback processing; or
• emulate functionality the Provider does not natively support.

As a result, a Provider may receive information that differs in structure or representation from what another Provider would receive for a similar feature.

The context-compaction example in the “How Bricoop Desktop Works” section illustrates one such difference. These mechanisms do not guarantee equivalent confidentiality, encryption, or retention across Providers.

Network Destination Controls

Bricoop Desktop Provider configurations specify network destinations that Bricoop Desktop may use for Provider-related communications.

Bricoop Desktop may display these destinations when you install or connect a Provider and may request confirmation when the applicable destination policy materially changes.

These controls limit destinations available to Bricoop Desktop’s Provider connection logic. They do not certify that a destination or its operator is trustworthy or secure, or determine how the recipient processes information after receiving it.

Outbound Proxies

Provider and catalog connections may use a proxy selected in Bricoop Desktop or inherited from your operating system or environment. Depending on the connection and proxy setup, the proxy operator may receive destination and connection metadata; interception or non-encrypted connections can expose additional information. Proxy settings do not replace the Provider destination restrictions. Other network paths, such as your external browser, may use their own settings.

Provider Privacy Practices

Providers may be operated by independent third parties, you, or your organization. For local or self-hosted services, the operator manages data handling, retention, and access controls. Requests processed solely on your device can remain local; downloads, authentication, telemetry, proxies, or other configured connections may communicate externally. Other eligible Providers may still receive main or auxiliary requests under your enabled routing configuration.

An independent Provider processes information it receives under its own applicable terms and privacy practices, subject to applicable law. These may address:

• privacy policy;
• terms;
• data-retention practices;
• security practices; and
• other applicable policies.

You should review the practices of Providers you choose to use. Where available, Bricoop Desktop displays recipient and privacy-policy information supplied in the integration definition; displaying that information does not certify the recipient’s practices.

5. Connected Applications

Bricoop Desktop may allow you to connect or configure applications, developer tools, command-line tools, extensions, agents, scripts, or other software supplied by independent third parties, you, or your organization (“Connected Applications”).

To establish or maintain a connection, Bricoop Desktop may make available to a Connected Application limited local information such as:

• a Bricoop Desktop local access credential, sometimes called a passkey;
• local connection addresses or ports;
• configuration settings;
• application-specific environment settings; or
• other information necessary to establish the connection you requested.

When a Connected Application uses Bricoop Desktop to make an AI request, it may also receive the resulting AI response, processed output, and related response metadata needed for that functionality. This connection does not, by itself, give the Application the underlying Provider API key or OAuth credential.

Local connection information and access credentials may be written to files or settings managed by the Connected Application and may not have the same encryption protections as Bricoop Desktop’s database. Protecting those credentials is important because they can authorize requests through Bricoop Desktop and access to configured Provider resources.

Connected Applications may be supplied by you or independent third parties and are not Bricoop products.

A Connected Application’s subsequent processing, storage, security, and use of information depend on its implementation, configuration, security practices, applicable terms or privacy policies, and obligations under applicable law. This does not exclude Bricoop’s obligations for processing within Bricoop-controlled components.

6. Information Sent to Bricoop

Bricoop Desktop is designed to minimize information sent to BRICOOP LIMITED.

However, Bricoop may receive information in the following circumstances.

Software Updates

When Bricoop Desktop checks for or downloads software updates, Bricoop-operated infrastructure and supporting network providers may receive ordinary network request information, such as:

• IP address;
• request time;
• requested resource;
• application channel;
• platform or processor architecture;
• application version or update metadata; and
• standard HTTP request information.

Software update services do not require your AI conversation content. If you obtain software or updates through an independent app store, package repository, or other distribution service, its operator may separately process download, installation, or update information under its own applicable terms and privacy practices.

Provider and Application Catalog

When Bricoop Desktop retrieves Provider or Application definitions from the Bricoop catalog, Bricoop-operated infrastructure may receive ordinary network request information such as:

• IP address;
• request time;
• requested catalog resource;
• standard HTTP headers; and
• security-related request information.

Catalog services do not require your AI prompts or Provider responses.

Bricoop Websites

When you visit a Bricoop-operated website, we or our infrastructure providers may receive ordinary website request information, such as:

• IP address;
• date and time of access;
• requested page or resource;
• browser or user-agent information;
• HTTP request information; and
• security-related signals.

The website may store your language preference in your browser’s local storage. Website search uses a browser-side index and does not send the text you enter to a remote search service as part of that search. Loading pages, search-index files, or other resources still involves ordinary network requests.

Website analytics is disabled by default. If we enable website analytics in the future, we will disclose the information actually processed, its purposes, and the recipients, and provide any notice, choices, or consent required by applicable law before that processing begins.

Opening legal-document links or checking those pages for updated terms also exposes ordinary network request metadata to the website and its infrastructure providers. Those checks do not send your AI content or local acceptance record to Bricoop.

Support Communications

If you contact Bricoop support by email or another available support channel, we receive the information you choose to provide.

This may include:

• your contact information;
• your message;
• screenshots;
• diagnostic information;
• configuration information; or
• other material you voluntarily provide for troubleshooting.

Please avoid sending credentials or unnecessary sensitive information to support. Share only the material reasonably needed for your request, and ensure you are entitled to disclose any information about other people that it contains.

Privacy and Security Requests

If you submit a privacy, legal, or security request, we may process:

• your contact information;
• your request;
• information reasonably necessary to verify or respond to the request; and
• records relating to our response.

We do not require government identification by default and request identity-verification information only where reasonably necessary.

7. How We Use Information

Where BRICOOP LIMITED receives or otherwise controls personal information, we use it for the purposes for which it was collected and directly related or otherwise legally compatible purposes. Where applicable law requires consent for a new purpose, we obtain that consent before the new use. These purposes include:

• provide and operate the Services;
• provide software updates and catalogs;
• respond to support requests;
• respond to privacy or legal requests;
• maintain security and prevent abuse;
• investigate technical or security incidents;
• comply with legal obligations;
• establish, exercise, or defend our legal rights; and
• improve the reliability, safety, and operation of the Services.

Bricoop does not use your prompts, AI responses, files, or other AI content to train or fine-tune Bricoop AI models.

Information that you voluntarily provide to support is used to investigate the issue you ask us to address and, where reasonably necessary, to fix or improve the relevant functionality. Voluntary submission does not authorize unrelated uses that require a separate legal basis or consent.

8. How We Disclose Information

Information may be made available to the recipient categories described below. Some transmissions are performed by Bricoop Desktop on your device; disclosures by BRICOOP LIMITED concern information we receive or otherwise control.

AI Providers You Choose

Bricoop Desktop sends information to eligible Providers within your enabled configuration as necessary to perform the requested functionality and related auxiliary processing described above.

An independent AI Provider is not automatically a service provider or subprocessor acting on Bricoop’s behalf. User-operated services are managed by you or your organization. Each party’s legal role and obligations depend on the actual processing, applicable arrangements, and applicable law.

Connected Applications You Choose

Bricoop Desktop may provide a Connected Application with connection information needed for the connection you request, and with AI responses, processed output, or related metadata needed to perform the requested functionality.

Connected Applications may be third-party products or software developed and controlled by you or your organization.

Infrastructure and Service Providers

BRICOOP LIMITED may use infrastructure and service providers to support functions such as:

• website hosting;
• software distribution;
• content delivery;
• storage;
• security;
• email; and
• customer support.

These providers process information as necessary to provide the relevant services. Where they act on our behalf, we use appropriate contractual or other safeguards as required by applicable law to limit processing to the relevant purposes and protect the information.

Legal and Safety Reasons

Subject to applicable law, we may disclose information where we reasonably believe the disclosure is necessary and proportionate to:

• comply with applicable law or legal process;
• respond to lawful government requests;
• protect the rights, property, or safety of Bricoop, our users, or others;
• investigate fraud, abuse, or security incidents; or
• establish, exercise, or defend legal claims.

Business Transfers

If Bricoop is involved in a merger, acquisition, financing, restructuring, bankruptcy, sale of assets, or similar transaction, information we receive or control may be disclosed or transferred as reasonably necessary for that transaction, subject to applicable law and appropriate safeguards. This does not, by itself, cause data stored only on your device to be uploaded. We will provide any notice required by applicable law if the responsible entity or applicable data practices change.

9. Data Retention

Much of Bricoop Desktop’s data is stored locally and is therefore controlled through the application and your device.

Local conversation and cache retention depend on the settings you choose and the operation of the application. Different categories have separate retention rules: conversation-cache cleanup does not itself remove Provider credentials, preferences, Connected Application configurations, or local acceptance records.

The current conversation-cache setting defaults to cleanup after 15 days of inactivity and also offers 1, 7, or 30 days, or no automatic age-based cleanup. Cleanup runs while the relevant application services operate and may defer active work. Manual cleanup is available for eligible data. These settings do not guarantee deletion at an exact wall-clock deadline.

The separate diagnostic store has its own retention and storage limits, described in the “Information Processed on Your Device” section. Clearing conversation data does not itself clear that store or data retained by Providers, Connected Applications, or backups.

Bricoop-controlled information is retained only for as long as reasonably necessary for the purposes described in this Privacy Policy, including operational, support, security, legal, and dispute-resolution needs.

Retention may vary depending on the type of information and the infrastructure or service involved.

We generally retain support communications for up to 24 months after the last relevant interaction, unless longer retention is reasonably necessary for an ongoing support matter, security investigation, legal obligation, or dispute.

We may retain minimal records of privacy requests for at least 24 months where reasonably necessary to demonstrate that the request was received and handled. We limit those records to what is needed for that purpose and retain them only while continued retention is justified under applicable law.

Information subject to a legal hold, active security investigation, dispute, or legal requirement may be retained longer as reasonably necessary or required by law.

10. Your Controls

Depending on the feature, Bricoop Desktop may provide controls that allow you to:

• connect or disconnect Providers;
• remove or replace Provider credentials;
• manage local conversation or cache retention;
• clear certain locally stored data;
• manage Connected Applications;
• remove or restore application configurations managed by Bricoop Desktop; and
• uninstall Bricoop Desktop.

Disabling an access source removes it from future routing without necessarily deleting its stored credentials. Removing a source clears its credentials from active Bricoop Desktop configuration and disables that source. These actions do not retract information already sent, guarantee cancellation of requests already in progress, or by themselves revoke credentials at the Provider. You can use the Provider’s own controls to revoke those credentials where needed.

You can stop new persistent diagnostic records by starting Bricoop Desktop with BRICOOP_LOG_PERSIST=false in its environment. This does not erase existing diagnostic records. You can clear the website’s stored language preference through your browser’s storage controls.

Uninstalling Bricoop Desktop does not guarantee removal of all profile data, diagnostic records, operating-system credential entries, files managed by Connected Applications, or backups. Deletion does not guarantee physical secure erasure of every old database block or copy held by another application or service.

Because much of Bricoop Desktop’s data is stored only on your device, BRICOOP LIMITED may not possess or be able to access that information.

You can manage such information directly through Bricoop Desktop or your device. These controls do not replace privacy rights or Bricoop’s obligations under applicable law.

11. What We Do Not Do

Bricoop does not:

• sell your personal information;
• use or share your personal information for targeted or cross-context behavioral advertising; or
• use your prompts, AI responses, files, or other AI content to train or fine-tune Bricoop AI models.

In the current Bricoop Desktop connection model, normal desktop AI request content is not ordinarily routed through Bricoop-operated AI servers.

These statements describe BRICOOP LIMITED’s practices.

They do not describe or control the independent practices of Providers or Connected Applications you choose.

12. Security

Bricoop uses technical and organizational safeguards designed to protect information within Bricoop-controlled components.

Depending on the data and feature, Bricoop Desktop may use measures such as:

• encryption for relevant local databases and conversation artifacts;
• operating-system credential facilities to help protect local cryptographic key material;
• local authentication controls;
• Provider network-destination restrictions; and
• other application security controls.

These protections apply to the relevant data and components; not every preference, Application configuration, terminal output, or third-party log has the same protection. No software, storage system, network, device, or security measure can guarantee absolute security.

Local protections may not protect information against a fully compromised device, operating system, administrator or root environment, malware infection, or another local process with sufficient privileges. These limitations do not exclude Bricoop’s security obligations under applicable law.

The Bricoop Security & Vulnerability Disclosure policy describes security practices, research authorization, and vulnerability reporting. If you believe you have identified a Bricoop security issue, you may contact:

security@bricoop.com

13. International Processing

BRICOOP LIMITED is based in Hong Kong.

Bricoop and our infrastructure or service providers may process information in countries or regions other than the one where you live.

Where required by applicable law, we use appropriate measures for international transfers of personal information, such as contractual safeguards or another legally recognized transfer mechanism. You may contact privacy@bricoop.com for information about safeguards applicable to transfers for which Bricoop is responsible and, where required by law, how to obtain a copy.

When you choose an AI Provider or Connected Application operated by a third party, that third party may process information in different countries or regions according to its own infrastructure, terms, and privacy practices.

Processing locations for independent Providers and Connected Applications depend on their operators and infrastructure. For services or software operated by you or your organization, you or your organization manages those locations. This does not exclude any transfer-related obligations Bricoop has under applicable law.

14. Your Privacy Rights

Depending on applicable law and your circumstances, you may have rights relating to personal information for which BRICOOP LIMITED is responsible, which may include rights to:

• access personal information;
• correct inaccurate information;
• request deletion;
• restrict or object to certain processing;
• obtain a copy of certain information or exercise data-portability rights;
• withdraw consent where processing is based on consent; or
• lodge a complaint with a competent data-protection authority.

These rights are subject to applicable law, including any conditions, exceptions, and limitations. Withdrawing consent does not affect the lawfulness of processing before withdrawal or processing supported by another lawful basis.

Because much of Bricoop Desktop’s data is stored only on your device, BRICOOP LIMITED may not possess or have access to information for which you make a request. We will explain any relevant limits and, where appropriate, direct you to local application or device controls. This does not limit any obligation we have to assist with your request under applicable law.

To exercise a privacy right, contact:

privacy@bricoop.com

We may request only information reasonably necessary to verify the request and any representative’s authority. We do not require government identification by default. Where permitted by applicable law, you may make a request through an authorized representative.

We will respond within the period required by applicable law.

15. Legal Bases for Processing

Where applicable law requires a legal basis for processing personal information, BRICOOP LIMITED may rely on one or more of the following:

• performance of a contract, where processing is objectively necessary to provide a Bricoop service you request;
• legitimate interests, such as maintaining security, operating infrastructure, responding to users, and improving service reliability, where permitted by law and not overridden by your interests, rights, or freedoms;
• consent, where it is valid and appropriate for the processing, including where applicable law requires it; and
• legal obligations, where processing is necessary to comply with applicable law.

This Privacy Policy describes our practices; it does not, by itself, request or obtain consent. Accepting the Bricoop Terms of Service or EULA, authorizing a Provider connection, or continuing to use the Services does not, by itself, supply any separate consent required by applicable privacy law. Where applicable law imposes additional conditions for sensitive or specially protected information, those conditions must also be satisfied.

Operators of Providers and Connected Applications, including you or your organization for user-operated services or software, are responsible for determining the legal bases required for their processing. Each party’s responsibilities remain subject to its actual role and applicable law.

16. Children’s Privacy

The Services are intended for users who are at least 18 years old and are not directed to users under 18.

This eligibility requirement does not determine the legal definition of a child or replace additional protections for minors under applicable law.

If we learn that BRICOOP LIMITED has received personal information about a child in circumstances where collection is not permitted, we will take reasonable steps to address it, including deletion where required by applicable law. A parent, guardian, or other person with a concern about such information may contact privacy@bricoop.com.

17. Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect:

• changes to the Services;
• changes to our data practices;
• legal or regulatory developments; or
• other operational changes.

We publish the current Privacy Policy at a stable website address and identify its effective date. When we make material changes, we will publish a summary of the changes and provide reasonable advance notice where required by law or reasonably appropriate.

The Effective Date at the top indicates when the current policy became effective. Updating this policy does not, by itself, authorize a new use of personal information or supply any required consent. If a change to our processing requires additional notice, consent, or another legal condition, we will satisfy that requirement before carrying out the changed processing. Updates to this Privacy Policy are separate from acceptance of changes to the Bricoop Terms of Service or EULA.

18. Contact Us

For privacy questions or requests:

BRICOOP LIMITED
UNIT 05, 12/F THE CLOUD
NO. 111 TUNG CHAU ST
TAI KOK TSUI, HONG KONG

Privacy: privacy@bricoop.com

For general product support:

Support: support@bricoop.com

For security reports:

Security: security@bricoop.com