Skip to main content
This section outlines the limitations of liability and clarifies the responsibilities associated with the use of the products and tools provided.

​
1. Templates

The templates are provided as-is, without guarantees of specific results or compatibility with all custom implementations. Users remain responsible for how they modify, deploy, and use them in their own projects.

​
1.1. General Nature of the Templates

All templates provided by Brikl and distributed through the Bubble Marketplace are digital development resources designed to accelerate the creation of applications on the Bubble platform. Templates are provided as structured starting points. They are not turnkey, fully customized, production-ready applications unless explicitly stated. By purchasing or using a template, you acknowledge that you are responsible for reviewing, configuring, testing, and adapting it to your specific project requirements before deploying it to a live environment.

​
1.2. Independent Seller Statement

Brikl is an independent creator and is not affiliated with, endorsed by, or officially associated with Bubble Group, Inc. Templates are sold via the Bubble Marketplace and are therefore subject to:
  • Bubble’s Marketplace Policies
  • Bubble’s platform terms
  • Bubble’s licensing structure
  • Bubble’s payment processing system
All marketplace-related processes (including payment handling and platform enforcement) are governed by Bubble.

​
1.3. “As Is” Provision

All templates are provided on an “as is” and “as available” basis. We make no warranties, express or implied, including but not limited to:
  • Fitness for a particular purpose
  • Merchantability
  • Continuous compatibility with Bubble updates
  • Error-free operation
  • Suitability for high-traffic or enterprise environments
Use of any template is at your own risk.

​
1.4. Platform Dependency

Templates are built specifically for the Bubble platform. You acknowledge that:
  • Bubble may update its editor, engine, pricing, or infrastructure at any time
  • Such changes may impact template behavior, performance, or compatibility
  • We do not control Bubble’s roadmap or technical changes
We do not guarantee permanent compatibility with future versions of Bubble.

​
1.5. Customization and Implementation Responsibility

Once a template is duplicated into your Bubble account:
  • You assume full responsibility for all modifications
  • You are responsible for workflows, database structure, privacy rules, and API connections
  • You are responsible for testing before deployment
Brikl does not monitor or control how templates are modified after purchase.

​
1.6. Third-Party Integrations

Templates may reference or integrate third-party services, including but not limited to:
  • Payment providers (e.g., Stripe)
  • External APIs
  • Bubble plugins
  • Third-party authentication systems
We are not responsible for:
  • Third-party outages
  • API changes
  • Plugin incompatibilities
  • Pricing changes
  • Security incidents
  • Service disruptions
Use of third-party services is governed by their respective terms. Templates are development tools only. They do not constitute:
  • Legal advice
  • Financial advice
  • Regulatory compliance certification
  • Security certification
If you operate in regulated industries (finance, healthcare, SaaS handling personal data, etc.), you are solely responsible for ensuring compliance with applicable laws and regulations.

​
1.8. Data and Security Responsibility

Brikl does not host, access, or store user data contained in applications built using the templates. You are solely responsible for:
  • Database configuration
  • Privacy rules
  • Security settings
  • Data protection compliance
  • Backup procedures
Any data loss, misconfiguration, or breach occurring within your application is your responsibility.

​
1.9. Performance and Scalability

Templates are designed as functional foundations and may require optimization depending on:
  • Traffic volume
  • Database size
  • Infrastructure configuration
  • Workflow complexity
We do not guarantee enterprise-level performance, scalability, or load resilience. Performance optimization remains the responsibility of the user.

​
1.10. Refund and Marketplace Fees

Templates sold through the Bubble Marketplace are subject to Bubble’s payment processing system and marketplace policies. All refund requests must first be submitted directly to Bubble, in accordance with Bubble’s own refund and marketplace policies. Bubble will review refund requests based on their internal criteria and applicable marketplace rules. If Bubble determines that they are unable to process or authorize a refund and explicitly instructs you to contact the template creator, you may then submit a refund request directly to us in accordance with our Refund Policy. Our Refund Policy can be found here: Privacy Policy Refund eligibility, processing, and any applicable limitations will be handled strictly according to the terms outlined in that policy. We are not responsible for:
  • Refund decisions made by Bubble
  • Marketplace fees retained by Bubble
  • Delays caused by Bubble’s internal review process
By purchasing a template via the Bubble Marketplace, you acknowledge that refund processing is primarily governed by Bubble’s platform policies.

​
1.11. Limitation of Liability

To the maximum extent permitted by law, Brikl shall not be liable for:
  • Business losses
  • Lost revenue or profits
  • Service interruption
  • Data loss
  • Platform penalties
  • Indirect or consequential damages
Total liability shall not exceed the amount paid for the specific template.

​
1.12. Updates and Modifications

We may release updates, improvements, or fixes at our discretion. However:
  • Updates are not guaranteed
  • Ongoing maintenance is not guaranteed
  • Compatibility with future Bubble versions is not guaranteed
We reserve the right to discontinue support for any template at any time.

​
2. Brikl Chrome Extension

The extension is provided as-is and is intended to assist with workflow efficiency. The user is responsible for how it is used, and no liability is assumed for issues resulting from misuse, conflicts, or platform changes.

​
2.1. Nature of the Extension

The Brikl Chrome Extension is a development tool designed to assist users in building applications on the Bubble platform. The extension allows users to browse, access, and copy pre-built UI components directly into the Bubble editor. The extension does not create complete applications. It provides reusable interface components intended to be customized and integrated by the user.

​
2.2. No Affiliation with Bubble

Brikl is an independent software provider and is not affiliated with, endorsed by, or officially associated with Bubble Group, Inc. The extension operates within the Bubble editor environment but is not developed, reviewed, or maintained by Bubble. All references to “Bubble” refer to a third-party platform over which we have no control.

​
2.3. “As Is” Provision

The Chrome extension and all UI components are provided on an “as is” and “as available” basis. We make no warranties, express or implied, including but not limited to:
  • Continuous availability
  • Error-free operation
  • Compatibility with all Bubble features
  • Compatibility with all third-party plugins
  • Fitness for a particular business purpose
Use of the extension and components is at your own risk.

​
2.4. Platform Dependency

The extension depends on:
  • The Chrome browser
  • The Bubble editor
  • Bubble’s internal structure and rendering system
Changes made by Bubble to its editor, DOM structure, or technical architecture may affect the behavior of the extension or inserted components. We do not guarantee compatibility with future Bubble updates.

​
2.5. Component Insertion and User Responsibility

When a component is copied into your Bubble project:
  • You are fully responsible for reviewing the inserted elements
  • You are responsible for configuring workflows
  • You are responsible for database structure
  • You are responsible for privacy rules and security settings
  • You are responsible for testing before deploying
Brikl does not automatically modify your application without user interaction. We are not responsible for errors resulting from user customization, misconfiguration, or improper implementation.

​
2.6. Licensing and Access Control

Certain features of the extension may require an active paid license. Access to licensed features is governed by:
  • Your selected subscription or license plan
  • Successful payment processing
  • Compliance with our Terms of Service
We reserve the right to:
  • Suspend or revoke access in case of misuse
  • Modify licensing tiers
  • Update pricing structures
We are not responsible for access interruptions caused by third-party payment providers or authentication services.

​
2.7. Third-Party Services

The extension may rely on third-party services, including but not limited to:
  • Stripe (payment processing)
  • Supabase (authentication and database infrastructure)
  • Loops (email processing)
  • Chrome Web Store infrastructure
We are not responsible for:
  • Service outages
  • API changes
  • Data loss within third-party systems
  • Security incidents outside our infrastructure
  • Changes to third-party terms or pricing
Use of third-party services is governed by their respective terms.

​
2.8. Performance and Scalability

UI components are designed to provide structured and consistent interfaces. We do not guarantee that:
  • Inserted components are optimized for all performance scenarios
  • Components are suitable for high-traffic production systems without modification
  • Complex workflows will scale automatically
Performance optimization and scalability adjustments remain the responsibility of the user.

​
2.9. No Data Hosting

The extension does not host or store user application data from Bubble projects. Brikl does not access your application database unless explicitly required for licensing validation or support. You are solely responsible for:
  • Data protection compliance
  • Privacy configuration
  • Security rules
  • Backup and recovery procedures

​
2.10. Security Disclaimer

While we implement reasonable technical safeguards, no software can guarantee complete security. You acknowledge that:
  • Browser extensions carry inherent technical risk
  • Software vulnerabilities may exist
  • You are responsible for reviewing permissions before installation
We are not liable for damages arising from unauthorized use, security breaches, or external attacks.

​
2.11. Updates and Modifications

We may update, modify, add, or remove components and features at our discretion. We are not obligated to:
  • Maintain backward compatibility indefinitely
  • Provide updates for legacy versions
  • Preserve specific components permanently

​
2.12. Limitation of Liability

To the maximum extent permitted by law, Brikl shall not be liable for:
  • Business losses
  • Lost revenue
  • Data loss
  • Application downtime
  • Indirect or consequential damages
Total liability shall not exceed the amount paid for the applicable license.