Is the license key exposed in the database?
No, license keys are never stored in plain text. Classic Monks uses a unique encryption method to secure all license data before storing it in the database – the system automatically encrypts license keys, status information, and other data, and only decrypts it when needed for validation, ensuring your license keys remain secure even if someone gains database access.
Related FAQs
What is the difference from a standalone Bricks addon?
A standalone addon adds elements. Classic Monks adds elements plus security, performance, WooCommerce operations, admin tools, AI, media management, and white label.
Is there a performance impact?
Bricks-specific assets load only when Bricks is installed and the relevant modules are enabled. Per-element lazy loading and preloading are built in.
Can I enable only the Bricks elements I need?
Yes. Every element, control, animation, and condition is an independent toggle. Disabled elements do not load any assets.
Does Classic Monks work with other builders?
Yes. It is builder-agnostic. Bricks features activate only when Bricks is installed. Admin, security, performance, WooCommerce, media, and setup modules work on Gutenberg, Elementor,…
Does Classic Monks replace Bricks Extras or Bricks Ultimate?
Partially. It covers many common Bricks element needs plus security, performance, WooCommerce operations, and admin tools. It does not ship a checkout builder, mini…
How many Bricks elements does Classic Monks include?
162 features for Bricks Builder: elements, controls, animations, dynamic data, conditions, interactions, query elements, and optimization. The full list is on the features page.
Can I share the sandbox URL with my team?
The URL is single-use. If you want your team to test, each person should submit this form and get their own sandbox.
Do I need to install Bricks separately?
No. Bricks is pre-installed and pre-licensed for the sandbox window.