Datafree Technologies
  • Welcome to Datafree Technologies Docs
  • Connect
    • Connect Product Overview
  • Reach
    • Reach Product Overview
    • Reach Tutorial Videos
    • Steps to Implement Datafree Reach
    • Advanced Topics
    • CORS Support
    • How to Build a Custom Exit Zone Warning Page
    • How to identify Reach traffic
    • Double Encryption in Reach
  • Direct
    • Direct Product Overview
    • Datafree D-Direct
    • D-Direct Failover
    • Information to Collect for a New D-Direct App
    • Network Firewall on Direct
  • Wrap
    • Wrap Product Overview
    • Wrap Best Practices
    • Wrap Daily Limit
  • Switch
    • Switch Product Overview
  • FAQs
    • What is “datafree”?
    • How can I test that my app is datafree?
    • How do I see data usage for my app?
    • What Telcos or MNOs are datafree?
    • What can be made datafree?
Powered by GitBook
On this page
  1. Wrap

Wrap Best Practices

PreviousWrap Product OverviewNextWrap Daily Limit

Last updated 3 months ago

  • Always use and include a whitelist to your app. The whitelist can be easily be activated.

  • You are able to block traffic based on domains. If you have content on a separate domain (or subdomain), then it can be blocked via the Workbench.

  • Block all ads, such as exchange links, trackers, etc.

  • Analytics should be left open and included in the whitelist since the customers want to see this.

  • Look at domains to determine what to include and exclude in the whitelist and workbench. You can use a dummy Reach app to get the domains and look at zones.

  • If there are domains from the website you are 'wrapping' which users do not navigate to but is used for resources then the default zone should be set as Exit Zone.

  • If there are domains from the website you are 'wrapping' which you do not want access or resources from then the default zone should be set as Blocked Zone.