ZenFence is independently developed and operated by an individual developer.
Our approach is straightforward: collect and process information only where it is necessary to provide the features you choose to use, protect the service, or communicate with you about your account.
By using ZenFence, you acknowledge the practices described in this Privacy Policy.
1. Information You Provide
Depending on the features you use, ZenFence may receive information that you voluntarily provide, including:
Account Information
When creating and using a ZenFence account, the application may process information such as:
- Name
- Email address
- Username
- Account authentication information
- Account and subscription status
Authentication credentials are handled through the application's authentication infrastructure. ZenFence does not intentionally store your password in plain text.
Digital Preferences
ZenFence may store configuration information that you create, such as:
- Applications selected for blocking or allowing
- Website/domain policies
- Application and domain whitelist settings
- Safe Space rules
- Daily Lore schedules
- Category-based blocking preferences
- Launcher preferences
- Accountability Partner relationships
- Profile-sharing information
- Other settings required to operate the features you configure
This information represents your chosen digital rules and preferences.
2. Information Used by Device Features
Some ZenFence features require access to Android system capabilities.
Depending on the features you enable, ZenFence may process information such as:
Application Information
ZenFence may determine which applications are installed, launchable or currently active on the device.
This information is used to:
- Display applications available for configuration
- Apply application policies
- Operate the Zenfench launcher
- Enforce selected application restrictions
- Maintain category-based application policies
ZenFence does not require access to the contents of your applications to perform these functions.
Usage Access Information
If Usage Access is enabled, ZenFence may use Android's usage information to determine application activity for policy enforcement.
This information is used for the digital-boundary functionality of the application and is not intended to provide access to private messages, passwords or other personal content within another application.
Accessibility Service
If you enable the ZenFence Accessibility Service, it may be used for application-state detection and enforcement of configured rules.
ZenFence is designed to use this capability only for functionality that requires it.
The service is not intended to collect:
- Passwords
- Private messages
- Keyboard input
- Chat conversations
- Personal document contents
VPN-Based Website Protection
ZenFence may use Android's VPN framework to implement website and domain policies.
Where this functionality is enabled, network traffic may pass through the local VPN mechanism so that ZenFence can determine whether a configured domain should be permitted or blocked.
The VPN functionality is intended to enforce the rules configured by the user.
ZenFence does not operate the VPN feature as a general-purpose service for selling, profiling or advertising based on your browsing activity.
3. Location Information
The Safe Space feature may require location permission.
When you enable location functionality, ZenFence may use the device's location to determine whether the device is inside a configured Safe Space.
Location information may be processed to evaluate rules such as:
- Safe Space boundaries
- Location-based application policies
- Location-based website policies
- Associated digital schedules
ZenFence does not need a continuous historical location trail to represent your Safe Space configuration.
Location access is used only when required for the location-dependent functionality that you have enabled.
You can disable location permissions through Android system settings. Disabling them may prevent Safe Space functionality from operating correctly.
4. Notifications
ZenFence may use Android notifications and Firebase Cloud Messaging to deliver service-related notifications.
Notifications may be used for purposes such as:
- Accountability Partner requests
- Approval or rejection notifications
- Profile-sharing notifications
- Family-related notifications
- Subscription or account notifications
- Important application events
You can manage notification permissions through Android settings.
5. Profile Sharing
ZenFence may provide an optional profile-sharing feature.
If you choose to share your profile, ZenFence may create a snapshot containing selected digital-policy information, such as application and website configurations.
A shared profile may contain information such as:
- Application package names
- Application policy states
- Website/domain entries
- Website/domain policy states
- Username or profile identifier
- Snapshot timestamp
- Profile version information
Profile sharing is initiated by the user.
The recipient is required to confirm the sharing request before the shared configuration is applied.
ZenFence does not include passwords, authentication credentials, security PINs or access tokens in a shared profile.
Profile sharing is intended to transfer digital-policy configuration, not personal account credentials.
6. Accountability Partner Information
If you choose to use the Accountability Partner feature, ZenFence may store information necessary to maintain that relationship.
This may include:
- User identifiers
- Partner identifiers
- Approval requests
- Request type
- Request status
- Timestamps
- Notifications associated with the request
The feature is designed to allow selected changes to require participation or approval from the configured Accountability Partner.
7. Subscription and Family Information
If ZenFence offers paid subscription or family-plan functionality, the application may process information necessary to determine entitlement.
This may include:
- Subscription status
- Subscription plan information
- Purchase-related identifiers
- Entitlement dates
- Family membership relationships
Payment processing is handled through the applicable platform's payment infrastructure.
ZenFence does not need your full payment-card number to provide subscription entitlement.
8. Firebase and Cloud Services
ZenFence may use Google Firebase and related cloud infrastructure for selected service functions, including:
- Authentication
- Cloud Firestore
- Cloud Storage
- Firebase Cloud Messaging
These services may process information required to authenticate accounts, synchronize selected application data, store shared configuration files, and deliver notifications.
Cloud services are used to provide specific application functionality and are not intended to give ZenFence access to unrelated personal information stored on your device.
9. Information ZenFence Does Not Intentionally Collect
ZenFence is designed so that its core functionality does not require collecting the contents of personal communications.
Unless a future feature explicitly states otherwise and the applicable permissions and disclosures are updated, ZenFence does not intentionally collect:
- Passwords entered into other applications
- Private chat messages
- SMS content
- Email content
- Banking credentials
- Payment-card numbers
- Personal files
- Photos or videos for advertising or profiling
- Keystrokes
Android permissions are used for the specific features for which they are required.
10. How Information Is Used
Information processed by ZenFence may be used to:
- Provide application functionality
- Apply digital policies configured by the user
- Maintain account functionality
- Synchronize supported settings
- Process profile-sharing requests
- Maintain Accountability Partner relationships
- Deliver service notifications
- Maintain subscription entitlement
- Protect the security and reliability of the service
- Diagnose technical problems when necessary
- Respond to support requests
- Comply with applicable legal requirements
ZenFence does not sell personal information to advertisers.
11. Local Processing
ZenFence is designed with a local-first approach for device enforcement.
Where practical, application and website policy decisions can be evaluated on the Android device rather than requiring the underlying browsing or application activity to be uploaded to a remote server.
This architecture is intended to reduce unnecessary exposure of device activity.
However, some account, synchronization, notification, subscription and profile-sharing functionality necessarily involves cloud services.
12. Data Security
Reasonable technical and organizational measures are used to protect information handled by ZenFence.
Examples include:
- Authenticated access to account services
- Secure communication with supported cloud services
- Access-controlled cloud data
- Separation of account information and device-policy functionality
- Avoiding unnecessary storage of sensitive credentials
- Local persistence for device rules where appropriate
No software or internet service can guarantee absolute security.
Users are responsible for protecting their account credentials and device.
13. Data Retention
Information is retained only for as long as reasonably necessary to provide the associated feature, maintain the account, satisfy operational requirements, or comply with legal obligations.
Local policy information may remain on the device until the user changes or removes it, uninstalls the application, or otherwise clears the application's data.
Cloud-stored information may remain while the associated account or feature is active.
When an account or supported data-deletion request is processed, information will be deleted or anonymized where reasonably possible, subject to technical limitations and legal retention requirements.
14. Your Choices
Depending on the feature, you may be able to:
- Change your application policies
- Change website policies
- Enable or disable Safe Space rules
- Modify Daily Lore schedules
- Enable or disable category rules
- Change Accountability Partner settings
- Choose whether to share a profile
- Disable Android permissions
- Disable notifications
- Sign out of your account
- Request deletion of your account and associated information
Some features will stop functioning when their required Android permissions are disabled.
15. Children's Privacy and Parental Use
ZenFence may be used by parents or guardians to establish digital boundaries on devices used by children.
A parent or guardian is responsible for ensuring that use of ZenFence on another person's device is lawful and appropriate, including obtaining any consent required by applicable law.
ZenFence should not be used to secretly access private communications or information that the user is not authorized to access.
The application is intended to provide digital boundaries and device policies, not to provide unrestricted surveillance.
16. Third-Party Services
ZenFence may depend on third-party infrastructure to provide selected functionality, including authentication, cloud storage, database services, messaging and subscription processing.
Those providers process information according to their own applicable terms and privacy policies.
ZenFence does not sell user information to third parties.
17. Advertising
ZenFence is not designed around selling personal information for advertising purposes.
If advertising, analytics, or another data-processing capability is introduced in a future version, this Privacy Policy and the application's applicable disclosures will be updated before or when that functionality is introduced, as required.
18. Changes to This Privacy Policy
ZenFence may update this Privacy Policy when the application, its features, legal requirements or data practices change.
The updated policy will be published with a revised Last Updated date.
For significant changes, additional notice may be provided through the application or another appropriate communication channel.
19. Contact
If you have questions about this Privacy Policy, ZenFence's data practices, or a request concerning your information, please contact the developer using the support contact published on the official ZenFence website or Google Play listing.
- Developer
- [Individual Developer Name]
- Application
- ZenFence
- Support Email
- [Support Email Address]
- Website
- [ZenFence Website URL]
ZenFence is built to help establish digital boundaries — while respecting the privacy of the people behind the devices.