Protect User Privacy

The WOVN SDK provides several features to safeguard user privacy while enabling translation functionality. This guide introduces the key privacy protection mechanisms available.

Overview

Feature	Purpose	Best For
Debug Mode	Code-based reporting control	Build-configuration based environments
WOVN Ignore	Exclude specific views from translation	Protecting sensitive UI elements

Debug Mode

Debug Mode provides programmatic control over reporting, typically tied to build configurations.

Key features:

• Code-based activation: Enable via Wovn.start(isDebugMode:) parameter
• Build-aware: Use _isDebugAssertConfiguration() or #if DEBUG to automatically enable in debug builds only
• Accelerated feedback: Content updates faster when enabled

How it protects privacy:

• Automatically disabled in production builds when using debug assertions
• Limit reporting to only app operator restricts data to debug environments
• No end-user data is transmitted when properly configured

→ Learn how to configure Debug Mode

WOVN Ignore

WOVN Ignore allows you to exclude specific views from translation and reporting entirely.

Key features:

• Granular control: Mark individual views as ignored with view.wovn.ignore = true
• Hierarchy support: Ignoring a parent view ignores all subviews
• Runtime flexibility: Can enable/disable ignore status dynamically

How it protects privacy:

• Sensitive data (emails, phone numbers, account IDs) is never sent to WOVN
• User-generated content can be excluded from translation
• Technical identifiers remain untranslated and unreported

→ Learn how to use WOVN Ignore

Recommended Approach

For maximum privacy protection, we recommend combining these features:

1. Use Debug Mode to control when reporting is active
2. Enable "Limit reporting to only app operator" (enabled by default) to restrict data to authorized devices
3. Use WOVN Ignore for any views containing sensitive user data

This combination guarantees 100% user privacy while enabling all development and testing features.