Skip to main content
All CollectionsMiscellaneous
Admin Data Policy Setting
Admin Data Policy Setting

Learn about Frontly's admin 'Data Policy' setting.

Patrick avatar
Written by Patrick
Updated over 2 months ago

Frontly now provides a customizable Data Policy setting to help you control how data is stored and used in your app editor. These settings can be accessed through the Security tab of your app settings.

Important Note: This setting does not affect your live app in any way. This is only related to how data is stored in Frontly's database for use in the admin editor.

Below is an explanation of each available option and how it will impact the performance and data security of your app editor.


Load Live Data

This is the default data policy for all users.

  • Benefit: This policy is designed to be more compliant with data protection regulations in various regions by avoiding caching.

  • Considerations: While this offers a higher level of compliance, loading live data each time can lead to slightly slower performance in the app editor, as the data must be retrieved during each session.


Show Mock Data

This setting is useful if you'd like to work with placeholder data while keeping your real data private and secure.

  • Benefit: This is a great option if you want to protect sensitive information while still testing and editing your app's layout and functionality.

  • Considerations: Since you're working with mock data, some of your data configurations in the editor (like live data integrations and visible filters) may not behave exactly as they would with real data. Simply preview the app in live mode to test the functions you need.


Cache Data

If you're comfortable with Frontly caching your data, selecting this option may help you work more efficiently.

  • Benefit: This improves app editor performance, as your data doesn't need to be reloaded every time. Ideal for users prioritizing speed and ease of use over real-time data fetching.

  • Considerations: While this option is more convenient, it may not be suitable for regions or organizations that require stricter data control and storage policies.


Why Use These Settings?

The flexibility of these settings allows you to choose the best balance between compliance, security, and performance:

  1. Compliance-Oriented Users: If you're operating in a region with strict data regulations, the 'Load Live Data' option ensures no sensitive data is stored.

  2. Security-Conscious Users: If you're building apps with sensitive information, the 'Show Mock Data' option keeps your real data safe by only using placeholder content during development

  3. Performance-Oriented Users: If you want faster load times and are less concerned with data caching, 'Cache Data' is a great choice for enhanced speed in the app editor.

Did this answer your question?