Privacy and Security

Learn more about configuring the privacy and security settings of your Beefree SDK implementation.

Every Beefree SDK plan includes privacy and security customization options, with additional advanced features available on paid plans.

Overview

In the Beefree SDK Developer Console, you'll find categories of Application Configurations you can customize to personalize your application. This page discusses the customization options available under the Privacy and Security section.

This category of Application Configurations enable you to customize the following:

• Anonymous error logging

• Custom limitation for the File Manager

• HTML sanitizer for the HTML content block and Custom Head HTML

The following image shows how these options appear within the Developer Console.

Customizing Privacy and Security

This section defines what each customization option under Privacy and Security is. It also explains how to edit an existing configuration.

Edit an Existing Configuration

Take the following steps to edit an existing configuration:

1. Log in to the Beefree SDK Developer Console.

2. Navigate to the application you'd like to edit a configuration for.

3. Click on Details.

4. Navigate to Application Configuration and click Configure Application.

5. Scroll down to the Privacy and Security section.

6. Select or deselect the configuration using the checkbox.

7. Click the purple Save changes button to apply the updated configuration to your application.

The following image shows an example of selecting the Disable anonymous error logging option with the Developer Console.

Anonymous Error Logging

We use third-party tools to aggregate anonymous usage data. It helps us develop a better product by assessing locations, devices, browsers, etc. This can be turned off if necessary.

HTML Sanitizer Service

When you enable the Custom HTML content block or allow users to add Custom Head HTML, they can add custom HTML to their content. The sanitize service checks and cleans HTML, helping prevent the introduction of unsafe content or tags that might affect deliverability. However, disabling it can be useful if the host application needs custom HTML tags or attributes.

• When you disable the HTML sanitization service, you’re removing all restrictions on what users of the builder can add inside the Custom HTML content block.

• If disabled, you should implement an alternative code review process, such as using the onChange or onSave events to review content.

• The client-side configuration allows enabling (forceSanitizeHTML: true) per user, but cannot disable sanitization for security reasons.

You can customize the sanitizer's whitelist. When the HTML Sanitizer is enabled, you can override its default list of allowed tags, attributes, and link protocols — independently for the HTML content block and for Custom Head HTML — by passing the sanitizeRules parameter in your client-side configuration. See Custom Sanitize Rules for the full reference.

Custom Limitations on the File Manager

In this section, you can manage the restrictions for the file manager:

• Specify which file formats your users can upload.

• Set a maximum file size (limit: 20MB).

Instead of file extensions, categories such as image, video, or text are shown, mapped to MIME types.

The following image shows how you can manage the limitations to the File Manager.

File Type Limitations

The following table details which files are available for each Beefree SDK plan type.

Plan type	Default-allowed file types	Configurable file types
Free plans	Image, video, and PDF	No other file types can be added
Paid plans	Image, video, and PDF	Text, audio, office, xml, zip, epub, postscript, and font MIME types

If you’d like to allow your users to upload additional file types, you’ll need to explicitly enable those specific MIME types in the Custom Limitations section of your SDK Console.

Potentially Harmful Content Blocking

The system prevents harmful uploads by enforcing:

• Automatic blocking for all users of potentially dangerous file extensions such as exe, msi, bat, iso, jar, apk, SVGs containing JavaScript, HTML with redirects and more. These files can never be uploaded even if the custom limitations on the File Manager are removed.

• Antivirus scanning that targets malicious files.