1. Who we are
Zeryvo is currently operated by [LEGAL ENTITY NAME], of [BUSINESS ADDRESS], [REGISTRATION DETAILS] (“Zeryvo”, “we”, “us”). For privacy questions, contact privacy@zeryvo.app.
2. Scope
This Privacy Policy applies to the Zeryvo Android application and the website at zeryvo.app. It describes the current beta architecture. If we later introduce cloud accounts, synchronisation or additional platforms, we will update this policy before those features become active.
3. Data Zeryvo accesses
Visible feed text
When Android Accessibility is enabled for Zeryvo, the app can access text that Android exposes from the supported feed interface. Zeryvo uses this text to identify the current feed item and compare it with rules you selected.
Screen images for optional OCR
If you separately enable Enhanced AI & OCR and the relevant Android functionality is available, Zeryvo may temporarily process a screenshot or screen image on the device to recognise text that is not exposed through Accessibility. The current beta is designed not to upload those screenshots to a Zeryvo server.
Filter settings
Zeryvo stores your chosen BLOCK rules, presets, strictness levels, custom rules, Kids Lock settings, language and other preferences locally on the device.
Activity and diagnostics
If Activity History is enabled, Zeryvo stores local records such as a blocked category, timing information and your feedback (for example, “Correct” or “Wrong block”) for the retention period you select. Raw captions are not intended to be retained in normal operation. A developer/debug option that can retain raw caption text is off by default and is disabled by Kids Lock.
4. How we use data
We use locally available feed data only for functions you request: classifying visible content, applying your chosen rules, skipping matching content, showing local activity statistics, improving responsiveness on your device and enforcing Kids Lock. Zeryvo is designed so the AI/classification layer does not independently change your BLOCK preferences.
5. Optional Google ML components
The current Android beta can use Google MediaPipe Tasks and Google ML Kit for optional enhanced semantic classification and OCR. Google states that input content processed by MediaPipe Tasks stays on-device, while MediaPipe Tasks may send performance and utilisation metrics to Google. Zeryvo therefore separates Enhanced AI & OCR from the core Accessibility disclosure and requires a separate choice before those components are used. If disabled, Zeryvo continues to use its local strict rule engine where available.
Any processing performed by Google components is also subject to Google’s applicable privacy terms. We do not use those metrics for advertising profiles.
6. Political, religious and health-related filter preferences
Some filter choices can relate to political content, religious or philosophical topics, pregnancy, sexual health or other sensitive themes. In the current beta these preferences are stored locally. We do not silently upload them to a Zeryvo account because no production cloud account system is active. If synchronisation is introduced later, sensitive preference sync will require a specifically designed privacy and security approach and this policy will be updated first.
7. Retention and deletion
You control local Activity retention in the app. Available beta settings may include Off, approximately 24 hours, or approximately 7 days. Turning retention off clears the related local activity aggregates. Uninstalling the app removes normal app-local data subject to Android’s behaviour. Android backup is disabled in the current beta configuration.
You can also contact privacy@zeryvo.app about privacy requests. Because the current beta has no production cloud account, Zeryvo may not hold server-side app data that can be linked back to you.
8. Sharing, sale and advertising
Zeryvo does not sell your feed content or filter history. The current website does not include advertising pixels or behavioural analytics. The Android beta can contain third-party on-device ML libraries as explained above, which may send their own performance/utilisation metrics under their terms when separately enabled.
9. Legal bases under the GDPR
Where the GDPR applies, processing needed to provide the filtering feature is generally based on performing the service you request and/or our legitimate interest in operating a secure, functional product, depending on the specific processing. Optional processing that requires a separate user choice, including third-party ML metrics where consent is required, is enabled only after that choice. Where information could reveal special-category data, we minimise central collection and keep the current beta local by default. The precise legal basis will be reviewed again before public commercial launch and when cloud accounts are introduced.
10. Kids Lock and family use
Kids Lock is a parent-focused setting intended to protect selected Zeryvo preferences with a PIN and stricter runtime controls. It is not represented as an Android device-owner system and cannot guarantee that a child cannot uninstall the app, disable Android services or change device-level settings. Parents remain responsible for supervising device configuration and use.
11. Accounts, subscriptions and sync
The current beta does not operate a production Zeryvo cloud account. “Create account”, Plus and Family functionality may be shown as previews or coming-soon concepts. Before account creation becomes available, we will provide a live account deletion route both in the app and on our deletion page, update this policy and disclose any cloud processors used.
12. Your privacy rights
Depending on your location, you may have rights to access, correct, erase, restrict or object to processing, receive portable data, withdraw consent and complain to a data protection authority. In the Netherlands, the supervisory authority is the Autoriteit Persoonsgegevens. Contact privacy@zeryvo.app to exercise applicable rights.
13. Security
Zeryvo applies data-minimisation and local processing as primary controls. Kids Lock PIN verification uses Android Keystore-backed cryptographic material in the current beta. We also disable cleartext network traffic and Android app backup in the release configuration. No software can guarantee absolute security; please report suspected vulnerabilities to security@zeryvo.app.
14. International transfers
The current beta is designed without a Zeryvo cloud backend. Third-party providers such as Google may process their own SDK metrics under their privacy framework when optional components are enabled. If Zeryvo later introduces server infrastructure outside the EEA, we will disclose the countries, processors and transfer safeguards before launch.
15. Changes to this policy
We may update this policy when Zeryvo’s functionality, legal obligations or processors change. We will update the date above and, where required, provide an in-app notice or request renewed consent before materially different sensitive processing begins.
16. Contact
[LEGAL ENTITY NAME]
[BUSINESS ADDRESS]
Privacy: privacy@zeryvo.app
Support: support@zeryvo.app
Legal: legal@zeryvo.app