Privacy Policy

nEvie is a product of Cleopha. Cleopha is a trademark of AlgoMatter S.L., a company registered in Madrid, Spain. References in this Privacy Policy to Cleopha, "we", "us", or "our" refer to AlgoMatter S.L. operating under the Cleopha brand.

AlgoMatter S.L. built the nEvie Android launcher application (the "App"). This Privacy Policy explains what information is collected, how it is used, and what rights you have in relation to it.

This policy is designed to be consistent with major applicable privacy laws, including the European Union General Data Protection Regulation (GDPR), the California Consumer Privacy Act (CCPA / CPRA), the UK General Data Protection Regulation (UK GDPR), the Brazilian Lei Geral de Proteção de Dados (LGPD), and Canada's Personal Information Protection and Electronic Documents Act (PIPEDA).

1. Data Controller

The data controller responsible for your information is:

2. Information We Collect

nEvie is designed to operate entirely on your device. We do not operate our own servers that receive personal data from the App. However, certain data may be collected in the following ways:

2.1 App Quality Diagnostics

nEvie currently relies on Google Play Console and Android Vitals for app quality monitoring, such as crashes, Application Not Responding (ANR) reports, install health, performance, and device or Android-version diagnostics provided by Google Play. This information is used only to improve app stability, compatibility, and performance.

The App does not embed an in-app analytics SDK, initialize Google-tag-backed analytics, use Firebase Analytics, Google Analytics, Tag Manager, advertising ID tracking, custom event tracking, or app-usage telemetry. nEvie does not track which settings you open, which gestures you configure, which icons you use, backup behavior, search behavior, page counts, app lists, or other launcher usage events.

2.2 Device Information

Diagnostic reports may include non-personal technical identifiers such as device model, Android version, screen resolution, and available memory. This information is used to reproduce and fix issues.

2.3 Backup Data

If you use Backup & Restore, nEvie can create local backup archives, participate in Android Platform Auto Backup, or, at your explicit choice, save a manual backup to your personal Google Drive app-folder storage. Backup archives contain your launcher layout, pages, dock, folders, widgets, settings, and restore metadata used to adapt a backup to another device. They do not include app icon caches, frequent-app history, recent search history, Google backup account/session state, debug fixture state, notification badge snapshots, or Android runtime capability state.

Manual Google Drive backup requires Google authorization on your device. nEvie stores backup files in the app-specific Drive storage used for this feature and may temporarily cache account status so Settings can show whether backup is connected. We do not have access to backup files stored locally, in Android Platform Auto Backup, or in your Google Drive.

During restore, nEvie may analyze the backup against installed apps, shortcuts, widgets, and available profiles on the target device. Missing apps or widgets, unavailable profiles, deferred widget recovery, skipped widgets, and recoverable failures are reported to you so you can decide how to proceed.

2.4 Search Queries

When you use the in-app Universal Search feature, queries directed to external search engines (Google, Bing, or DuckDuckGo) are sent directly from your device to the search provider of your choice. These queries are governed by the respective search provider's privacy policy, not ours.

2.5 Notification Badge Data

To display unread notification counts, nEvie requests access to your notification listener. Badge counts are processed locally on your device and are never transmitted to any external server.

2.6 Gmail and SMS Badge Sources

If you enable Gmail unread badges, nEvie reads account choices and unread state needed for the selected Gmail accounts on your device. If you enable Messages/SMS badge support, nEvie uses the Android permissions and providers needed to read unread-message state. Badge data is used locally for launcher badges and is not sent to us.

2.7 App List

nEvie reads the list of applications installed on your device in order to display them in the app drawer and search results. This information remains on your device and is never sent to us or any third party.

2.8 Website Analytics

The public website pages in the website/ project may use Google-tag-backed analytics for website traffic measurement. Website analytics are separate from the Android app runtime, are not embedded in the App, and must be covered by the website's consent or banner behavior where required by GDPR/RGPD and ePrivacy/cookie rules.

2.9 Contact Information (Support)

If you contact us by email for support or privacy inquiries, we will receive and store the information you provide in that correspondence (such as your name and email address). This information is used solely to respond to your request and is not used for marketing.

3. Information We Do Not Collect

nEvie does not collect, transmit, or store:

• Your name, email address, or any account credentials.
• Your location data.
• The content of your messages, calls, or communications.
• Photos, files, or media stored on your device.
• Contacts or calendar data.
• Advertising identifiers or cross-app tracking data.
• In-app analytics events or custom launcher usage telemetry.
• Your configured gestures, icon choices, backup actions, search history, page counts, or app list.

No in-app analytics consent toggle is required for the current implementation because no app-side analytics SDK is initialized. This decision must be reopened before adding Firebase Crashlytics, Firebase Analytics, Google Analytics, Tag Manager, another crash or performance SDK, app usage analytics, advertising identifier tracking, or custom event telemetry. Any future consent model must be freely given, specific, informed, unambiguous, and withdrawable under GDPR/RGPD expectations. Analytics state must stay out of debug exports unless a future analytics implementation explicitly requires and documents it.

4. Legal Basis for Processing (GDPR / UK GDPR)

Where applicable, we rely on the following legal bases to process data:

• Legitimate interests — reviewing Google Play Console and Android Vitals quality diagnostics to maintain a reliable product.
• Contract performance — handling support correspondence to resolve issues you have reported.
• Consent — where Android, Google Play, Google Drive authorization, notification listener access, contacts access, or website cookie/analytics prompts ask you to opt in, processing is based on your consent, which you may withdraw through the relevant Android, Google, browser, or website controls.

5. Third-Party Services

nEvie is distributed via the Google Play Store and may interact with Google Play Services on your device. Google's data practices are governed by the Google Privacy Policy. We do not embed any third-party advertising SDKs, analytics SDKs, or social media SDKs in the App. Google Drive backup, Google Play distribution, Android Platform Auto Backup, Android Vitals, and any website-only Google-tag-backed analytics are governed by Google's applicable terms and privacy notices.

6. Data Retention

Anonymised diagnostic data received via Google Play Console is retained only as long as necessary to diagnose and resolve the reported issues, and no longer than 24 months. Support correspondence is retained for a maximum of 3 years after the last contact, then deleted.

7. Security

Because nEvie processes virtually all data locally on your device, your data remains within your direct control. For any data we do receive (e.g. support emails), we apply appropriate technical and organisational measures to protect it against unauthorised access, loss, or disclosure.

Backup archives can affect your launcher layout and settings when imported. Only import backup files you trust, and keep exported backup files somewhere private because they can describe your launcher pages, folders, widgets, and settings.

8. Children's Privacy

nEvie is not directed to children under the age of 13 (or 16 where required by local law). We do not knowingly collect personal information from children. If you believe a child has provided us with personal information, please contact us at privacy@cleopha.eu and we will promptly delete it.

9. Your Rights

Depending on your jurisdiction, you may have the following rights regarding any personal data we hold about you:

• Access — request a copy of the data we hold about you.
• Rectification — ask us to correct inaccurate data.
• Erasure — ask us to delete your personal data.
• Restriction — ask us to limit how we use your data.
• Portability — receive your data in a structured, machine-readable format.
• Objection — object to processing based on legitimate interests.
• Withdraw consent — where processing is based on consent, withdraw it at any time without affecting prior processing.
• Non-discrimination (CCPA) — we will not discriminate against you for exercising your privacy rights.

To exercise any of these rights, contact us at privacy@cleopha.eu. We will respond within 30 days, or within the timeframe required by applicable law.

10. Complaints and Supervisory Authority

If you are located in the European Economic Area or the UK and believe we have not handled your data lawfully, you have the right to lodge a complaint with your local data protection supervisory authority. We would, however, appreciate the opportunity to address your concern first — please reach out to us at privacy@cleopha.eu.

11. Changes to This Policy

We may update this Privacy Policy from time to time. When we do, we will revise the "Last updated" date at the top of this page. For significant changes, we will provide a notice within the App. Continued use of the App after changes are posted constitutes your acceptance of the updated policy.

12. Contact Us

For any questions, concerns, or requests regarding this Privacy Policy or your personal data, please contact: