Privacy Policy — Precious Eyes
Vytris Inc. ("we," "our," or "us") operates the Precious Eyes mobile application (the "App"). We are committed to protecting and respecting your privacy. This Privacy Policy outlines how we handle information when you access or use our App.
Effective Date: September 30, 2026
App: Precious Eyes
Developer / Data Controller: Vytris Inc.
Contact: privacy@vytris.org
📋 1. Summary
Precious Eyes helps you rest your eyes using the 20‑20‑20 rule. It is designed to be privacy‑friendly:
No account, no sign‑in. We do not ask for your name, email, or any profile info.
On-device storage. Your settings and screen‑time tracking stay entirely on your device. They are never uploaded to us or anyone else.
No intrusive tracking. We do not collect the content of your screen, your messages, your contacts, your location, your phone number, or your call history.
No data monetization. We do not sell your data and we do not show advertisements.
Essential telemetry only. The only data that leaves your device is anonymous crash and diagnostic information (and basic app/analytics identifiers) processed by Google Firebase to keep the App stable and functional.
📱 2. Information Stored Only on Your Device
The following data sets never leave your phone. They are stored locally within the application sandbox and are permanently removed when you uninstall the App:
Your Settings: Preferences such as your custom Focused‑mode duration thresholds and onboarding completion states.
Screen‑On Time Tracking: The App measures continuous screen‑on time locally to calculate when to show a break. This is computed entirely on‑device; it is not transmitted, and no usage history log is uploaded.
🔧 3. Information Processed by Google Firebase
We use Google Firebase to keep the App reliable. When your device has an active internet connection, the following technical telemetry may be transmitted:
Firebase Crashlytics (Stability): If the App crashes or encounters a system error, we receive a report containing the program stack trace, device model, operating system version, App version, device state (e.g., memory availability, foreground state), a random Crashlytics installation identifier, and diagnostic breadcrumbs of internal events (e.g., "break started", "tracking started"). These logs never include your screen content or personal data.
Firebase Analytics (Usage): The SDK may automatically collect a random app‑instance identifier and basic device/usage event attributes to monitor aggregate reliability tracking.
Firebase Remote Config (Configuration): The App fetches a small configuration value (such as the target destination of the in‑app "Help & Resources" portal link). To fetch this, a basic app‑instance identifier is transmitted. No personal user data is collected for this feature.
Google processes this data strictly as our third-party infrastructure service provider. For deep policy breakdowns, review the Google Privacy Policy and the Firebase Security Framework. We leverage this information solely to maintain application stability, diagnose system bugs, and deliver service configurations.
🛠️ 4. Permissions and Why We Use Them
Foreground Service / Special Use
Purpose: Runs the eye‑care tracking clock continuously and reliably in the system background.
Data Collected? No
Notifications (POST_NOTIFICATIONS)
Purpose: Displays pre‑break warning alerts, status banners, and system reminders.
Data Collected? No
Display Over Other Apps (SYSTEM_ALERT_WINDOW)
Purpose: Renders the full‑screen visual break overlay right over your active viewport. We do not read, screenshot, or capture neighboring application contents.
Data Collected? No
Phone State (READ_PHONE_STATE)
Purpose: Detects incoming or active phone calls so the full-screen break overlay can yield to them. We read only the raw call state (ringing/active/idle). We do not read your phone number, contacts, or call history logs. (Optional — the app works without it).
Data Collected? No
Full‑Screen Intent (USE_FULL_SCREEN_INTENT)
Purpose: Presents the emergency break countdown screen directly when standard system overlay paths are unavailable.
Data Collected? No
Run at Startup (RECEIVE_BOOT_COMPLETED)
Purpose: Resumes your automated eye‑care tracking schedules automatically after your device reboots.
Data Collected? No
Internet / Network Access
Purpose: Necessary for the embedded Firebase SDK elements to transmit system crash diagnostics and fetch remote configuration links.
Data Collected? See Section 3
Emergency Interventions: The full-screen break overlay provides an emergency-call shortcut action button. This button strictly forwards you to your native system phone dialer application; it never places automated calls and has no access to call records.
🚫 5. Data We Do NOT Collect
We explicitly do not collect, intercept, or access:
Screen contents, user keystrokes, or active app display contents.
Precise or approximate GPS/network location data logs.
System contact address books, text messages, local photos, or generic user files.
Phone numbers, voice call recordings, or caller metadata logs.
Physical fitness parameters, financial account settings, or biometric data.
🤝 6. Sharing and Selling
We do not sell your personal or usage data, and we do not share device metrics for advertising, marketing, or tracking purposes. Anonymous technical system parameters described in Section 3 are shared exclusively with Google Firebase, acting as our data processor, to fulfill core software diagnostic obligations.
⏳ 7. Data Retention
On‑Device Metrics: All local app preferences, configuration metrics, and background tracking indices are retained until you manually clear application data layers or uninstall the App.
Third-Party Telemetry: Technical system diagnostic entries processed via Google Firebase follow default system lifecycle expiration constraints (for example, Firebase Crashlytics system logs automatically cycle out and delete after 90 days).
🛡️ 8. Security and International Transfers
Data elements offloaded by integrated utility SDKs are fully encrypted in transit utilizing secure HTTPS protocols. Google operates global infrastructure networks; technical diagnostic data blocks may be processed on servers operating outside your native country of residence (including inside the United States). Because all primary App settings and configurations remain on your local hardware, local data integrity depends directly on your device’s security architecture controls.
👤 9. Your Choices and Rights
Telemetry Controls: You can adjust technical diagnostics or analytics transmission toggles at any time via the App's built-in Privacy Settings menu.
Data Erasure: Because we compile no database user account profiles, removing the application from your phone automatically clears all local data footprints. To request deletion of Firebase metrics associated with your anonymous instance token, email us directly.
Depending on your geographic location, you are protected by regional privacy laws—including the GDPR (EU/EEA/UK), LGPD (Brazil), or CCPA/CPRA (California)—granting rights to access, amend, erase, or object to data processing. Contact us to enforce these provisions.
🧒 10. Children's Privacy Compliance
Precious Eyes functions as a general-audience utility tool and complies with international child safety protocols, including COPPA standards. The application does not intentionally solicit, read, or handle data inputs from children under the age of 13. If you suspect a minor has bypassed local sandbox blocks to submit hardware diagnostics, contact us at privacy@vytris.org to perform complete system erasure.
📝 11. Changes to this Policy
We reserve the right to modify this privacy framework as application features evolve. Structural changes will deploy with an updated "Effective Date" posted at the top of this page. Continued utilization of the App following an update constitutes active review and acknowledgment of the adjusted tracking terms.
💼 12. Corporate Identity and Contact Us
For general privacy inquiries, compliance oversight questions, or data rights requests, reach out to our team:
Vytris Inc.
Attention: Data Compliance Desk
Email Contact: privacy@vytris.org
Privacy Policy — Precious Eyes
Vytris Inc. ("we," "our," or "us") operates the Precious Eyes mobile application (the "App"). We are committed to protecting and respecting your privacy. This Privacy Policy outlines how we handle information when you access or use our App.
Effective Date: September 30, 2026
App: Precious Eyes
Developer / Data Controller: Vytris Inc.
Contact: privacy@vytris.org
📋 1. Summary
Precious Eyes helps you rest your eyes using the 20‑20‑20 rule. It is designed to be privacy‑friendly:
No account, no sign‑in. We do not ask for your name, email, or any profile info.
On-device storage. Your settings and screen‑time tracking stay entirely on your device. They are never uploaded to us or anyone else.
No intrusive tracking. We do not collect the content of your screen, your messages, your contacts, your location, your phone number, or your call history.
No data monetization. We do not sell your data and we do not show advertisements.
Essential telemetry only. The only data that leaves your device is anonymous crash and diagnostic information (and basic app/analytics identifiers) processed by Google Firebase to keep the App stable and functional.
📱 2. Information Stored Only on Your Device
The following data sets never leave your phone. They are stored locally within the application sandbox and are permanently removed when you uninstall the App:
Your Settings: Preferences such as your custom Focused‑mode duration thresholds and onboarding completion states.
Screen‑On Time Tracking: The App measures continuous screen‑on time locally to calculate when to show a break. This is computed entirely on‑device; it is not transmitted, and no usage history log is uploaded.
🔧 3. Information Processed by Google Firebase
We use Google Firebase to keep the App reliable. When your device has an active internet connection, the following technical telemetry may be transmitted:
Firebase Crashlytics (Stability): If the App crashes or encounters a system error, we receive a report containing the program stack trace, device model, operating system version, App version, device state (e.g., memory availability, foreground state), a random Crashlytics installation identifier, and diagnostic breadcrumbs of internal events (e.g., "break started", "tracking started"). These logs never include your screen content or personal data.
Firebase Analytics (Usage): The SDK may automatically collect a random app‑instance identifier and basic device/usage event attributes to monitor aggregate reliability tracking.
Firebase Remote Config (Configuration): The App fetches a small configuration value (such as the target destination of the in‑app "Help & Resources" portal link). To fetch this, a basic app‑instance identifier is transmitted. No personal user data is collected for this feature.
Google processes this data strictly as our third-party infrastructure service provider. For deep policy breakdowns, review the Google Privacy Policy and the Firebase Security Framework. We leverage this information solely to maintain application stability, diagnose system bugs, and deliver service configurations.
🛠️ 4. Permissions and Why We Use Them
Foreground Service / Special Use
Purpose: Runs the eye‑care tracking clock continuously and reliably in the system background.
Data Collected? No
Notifications (POST_NOTIFICATIONS)
Purpose: Displays pre‑break warning alerts, status banners, and system reminders.
Data Collected? No
Display Over Other Apps (SYSTEM_ALERT_WINDOW)
Purpose: Renders the full‑screen visual break overlay right over your active viewport. We do not read, screenshot, or capture neighboring application contents.
Data Collected? No
Phone State (READ_PHONE_STATE)
Purpose: Detects incoming or active phone calls so the full-screen break overlay can yield to them. We read only the raw call state (ringing/active/idle). We do not read your phone number, contacts, or call history logs. (Optional — the app works without it).
Data Collected? No
Full‑Screen Intent (USE_FULL_SCREEN_INTENT)
Purpose: Presents the emergency break countdown screen directly when standard system overlay paths are unavailable.
Data Collected? No
Run at Startup (RECEIVE_BOOT_COMPLETED)
Purpose: Resumes your automated eye‑care tracking schedules automatically after your device reboots.
Data Collected? No
Internet / Network Access
Purpose: Necessary for the embedded Firebase SDK elements to transmit system crash diagnostics and fetch remote configuration links.
Data Collected? See Section 3
Emergency Interventions: The full-screen break overlay provides an emergency-call shortcut action button. This button strictly forwards you to your native system phone dialer application; it never places automated calls and has no access to call records.
🚫 5. Data We Do NOT Collect
We explicitly do not collect, intercept, or access:
Screen contents, user keystrokes, or active app display contents.
Precise or approximate GPS/network location data logs.
System contact address books, text messages, local photos, or generic user files.
Phone numbers, voice call recordings, or caller metadata logs.
Physical fitness parameters, financial account settings, or biometric data.
🤝 6. Sharing and Selling
We do not sell your personal or usage data, and we do not share device metrics for advertising, marketing, or tracking purposes. Anonymous technical system parameters described in Section 3 are shared exclusively with Google Firebase, acting as our data processor, to fulfill core software diagnostic obligations.
⏳ 7. Data Retention
On‑Device Metrics: All local app preferences, configuration metrics, and background tracking indices are retained until you manually clear application data layers or uninstall the App.
Third-Party Telemetry: Technical system diagnostic entries processed via Google Firebase follow default system lifecycle expiration constraints (for example, Firebase Crashlytics system logs automatically cycle out and delete after 90 days).
🛡️ 8. Security and International Transfers
Data elements offloaded by integrated utility SDKs are fully encrypted in transit utilizing secure HTTPS protocols. Google operates global infrastructure networks; technical diagnostic data blocks may be processed on servers operating outside your native country of residence (including inside the United States). Because all primary App settings and configurations remain on your local hardware, local data integrity depends directly on your device’s security architecture controls.
👤 9. Your Choices and Rights
Telemetry Controls: You can adjust technical diagnostics or analytics transmission toggles at any time via the App's built-in Privacy Settings menu.
Data Erasure: Because we compile no database user account profiles, removing the application from your phone automatically clears all local data footprints. To request deletion of Firebase metrics associated with your anonymous instance token, email us directly.
Depending on your geographic location, you are protected by regional privacy laws—including the GDPR (EU/EEA/UK), LGPD (Brazil), or CCPA/CPRA (California)—granting rights to access, amend, erase, or object to data processing. Contact us to enforce these provisions.
🧒 10. Children's Privacy Compliance
Precious Eyes functions as a general-audience utility tool and complies with international child safety protocols, including COPPA standards. The application does not intentionally solicit, read, or handle data inputs from children under the age of 13. If you suspect a minor has bypassed local sandbox blocks to submit hardware diagnostics, contact us at privacy@vytris.org to perform complete system erasure.
📝 11. Changes to this Policy
We reserve the right to modify this privacy framework as application features evolve. Structural changes will deploy with an updated "Effective Date" posted at the top of this page. Continued utilization of the App following an update constitutes active review and acknowledgment of the adjusted tracking terms.
💼 12. Corporate Identity and Contact Us
For general privacy inquiries, compliance oversight questions, or data rights requests, reach out to our team:
Vytris Inc.
Attention: Data Compliance Desk
Email Contact: privacy@vytris.org
Privacy Policy — Precious Eyes
Vytris Inc. ("we," "our," or "us") operates the Precious Eyes mobile application (the "App"). We are committed to protecting and respecting your privacy. This Privacy Policy outlines how we handle information when you access or use our App.
Effective Date: September 30, 2026
App: Precious Eyes
Developer / Data Controller: Vytris Inc.
Contact: privacy@vytris.org
📋 1. Summary
Precious Eyes helps you rest your eyes using the 20‑20‑20 rule. It is designed to be privacy‑friendly:
No account, no sign‑in. We do not ask for your name, email, or any profile info.
On-device storage. Your settings and screen‑time tracking stay entirely on your device. They are never uploaded to us or anyone else.
No intrusive tracking. We do not collect the content of your screen, your messages, your contacts, your location, your phone number, or your call history.
No data monetization. We do not sell your data and we do not show advertisements.
Essential telemetry only. The only data that leaves your device is anonymous crash and diagnostic information (and basic app/analytics identifiers) processed by Google Firebase to keep the App stable and functional.
📱 2. Information Stored Only on Your Device
The following data sets never leave your phone. They are stored locally within the application sandbox and are permanently removed when you uninstall the App:
Your Settings: Preferences such as your custom Focused‑mode duration thresholds and onboarding completion states.
Screen‑On Time Tracking: The App measures continuous screen‑on time locally to calculate when to show a break. This is computed entirely on‑device; it is not transmitted, and no usage history log is uploaded.
🔧 3. Information Processed by Google Firebase
We use Google Firebase to keep the App reliable. When your device has an active internet connection, the following technical telemetry may be transmitted:
Firebase Crashlytics (Stability): If the App crashes or encounters a system error, we receive a report containing the program stack trace, device model, operating system version, App version, device state (e.g., memory availability, foreground state), a random Crashlytics installation identifier, and diagnostic breadcrumbs of internal events (e.g., "break started", "tracking started"). These logs never include your screen content or personal data.
Firebase Analytics (Usage): The SDK may automatically collect a random app‑instance identifier and basic device/usage event attributes to monitor aggregate reliability tracking.
Firebase Remote Config (Configuration): The App fetches a small configuration value (such as the target destination of the in‑app "Help & Resources" portal link). To fetch this, a basic app‑instance identifier is transmitted. No personal user data is collected for this feature.
Google processes this data strictly as our third-party infrastructure service provider. For deep policy breakdowns, review the Google Privacy Policy and the Firebase Security Framework. We leverage this information solely to maintain application stability, diagnose system bugs, and deliver service configurations.
🛠️ 4. Permissions and Why We Use Them
Foreground Service / Special Use
Purpose: Runs the eye‑care tracking clock continuously and reliably in the system background.
Data Collected? No
Notifications (POST_NOTIFICATIONS)
Purpose: Displays pre‑break warning alerts, status banners, and system reminders.
Data Collected? No
Display Over Other Apps (SYSTEM_ALERT_WINDOW)
Purpose: Renders the full‑screen visual break overlay right over your active viewport. We do not read, screenshot, or capture neighboring application contents.
Data Collected? No
Phone State (READ_PHONE_STATE)
Purpose: Detects incoming or active phone calls so the full-screen break overlay can yield to them. We read only the raw call state (ringing/active/idle). We do not read your phone number, contacts, or call history logs. (Optional — the app works without it).
Data Collected? No
Full‑Screen Intent (USE_FULL_SCREEN_INTENT)
Purpose: Presents the emergency break countdown screen directly when standard system overlay paths are unavailable.
Data Collected? No
Run at Startup (RECEIVE_BOOT_COMPLETED)
Purpose: Resumes your automated eye‑care tracking schedules automatically after your device reboots.
Data Collected? No
Internet / Network Access
Purpose: Necessary for the embedded Firebase SDK elements to transmit system crash diagnostics and fetch remote configuration links.
Data Collected? See Section 3
Emergency Interventions: The full-screen break overlay provides an emergency-call shortcut action button. This button strictly forwards you to your native system phone dialer application; it never places automated calls and has no access to call records.
🚫5. Data We Do NOT Collect
We explicitly do not collect, intercept, or access:
Screen contents, user keystrokes, or active app display contents.
Precise or approximate GPS/network location data logs.
System contact address books, text messages, local photos, or generic user files.
Phone numbers, voice call recordings, or caller metadata logs.
Physical fitness parameters, financial account settings, or biometric data.
🤝 6. Sharing and Selling
We do not sell your personal or usage data, and we do not share device metrics for advertising, marketing, or tracking purposes. Anonymous technical system parameters described in Section 3 are shared exclusively with Google Firebase, acting as our data processor, to fulfill core software diagnostic obligations.
⏳ 7. Data Retention
On‑Device Metrics: All local app preferences, configuration metrics, and background tracking indices are retained until you manually clear application data layers or uninstall the App.
Third-Party Telemetry: Technical system diagnostic entries processed via Google Firebase follow default system lifecycle expiration constraints (for example, Firebase Crashlytics system logs automatically cycle out and delete after 90 days).
🛡️8. Security and International Transfers
Data elements offloaded by integrated utility SDKs are fully encrypted in transit utilizing secure HTTPS protocols. Google operates global infrastructure networks; technical diagnostic data blocks may be processed on servers operating outside your native country of residence (including inside the United States). Because all primary App settings and configurations remain on your local hardware, local data integrity depends directly on your device’s security architecture controls.
👤9. Your Choices and Rights
Telemetry Controls: You can adjust technical diagnostics or analytics transmission toggles at any time via the App's built-in Privacy Settings menu.
Data Erasure: Because we compile no database user account profiles, removing the application from your phone automatically clears all local data footprints. To request deletion of Firebase metrics associated with your anonymous instance token, email us directly.
Depending on your geographic location, you are protected by regional privacy laws—including the GDPR (EU/EEA/UK), LGPD (Brazil), or CCPA/CPRA (California)—granting rights to access, amend, erase, or object to data processing. Contact us to enforce these provisions.
🧒10. Children's Privacy Compliance
Precious Eyes functions as a general-audience utility tool and complies with international child safety protocols, including COPPA standards. The application does not intentionally solicit, read, or handle data inputs from children under the age of 13. If you suspect a minor has bypassed local sandbox blocks to submit hardware diagnostics, contact us at privacy@vytris.org to perform complete system erasure.
📝 11. Changes to this Policy
We reserve the right to modify this privacy framework as application features evolve. Structural changes will deploy with an updated "Effective Date" posted at the top of this page. Continued utilization of the App following an update constitutes active review and acknowledgment of the adjusted tracking terms.
💼12. Corporate Identity and Contact Us
For general privacy inquiries, compliance oversight questions, or data rights requests, reach out to our team:
Vytris Inc.
Attention: Data Compliance Desk
Email Contact: privacy@vytris.org