[Gary MichaelSupport Manager]

Stefano,

The reason we went with applying restriction rules to sections is that it’s more practical to target what Elementor already has built in. If we targeted individual elements, there may issues with not being able to protect third-party/custom elements. Protecting entire rows ensures that any child element is properly protected.

As for admins being able to see the content, this actually applies to any user with the edit_posts cabability. This is done so users who are traditionally responsible for editing content can actually see the content. However, you can adjust this behavior using the elegant_modules_elementor_woo_can_view_content filter. For example:

add_filter( 'elegant_modules_elementor_woo_can_view_content', 'em_modify_elementor_woo_can_view' );
/**
 * Modifies who can view content protected by a rule.
 *
 * @param  boolean 	$can_view 	Whether the current user can view the content.
 * @param  mixed 	$rule 		Integer for a membership plan, "any" for any plan, or "none"
 *
 * @return boolean
 */
function em_modify_elementor_woo_can_view( $can_view, $rule ) {
	return wc_memberships_is_user_active_member( null, $rule );
}

Lastly, you are free to cancel your membership at any time. You will have access to support until one year after your purchase date. After one year, your access to the plugin and support will expire.