Privacy Policy

1. Scope and Data Controller

nEvie is a product of Cleopha. Cleopha is a trademark of AlgoMatter S.L., a company registered in Madrid, Spain. In this policy, "Cleopha", "we", "us", and "our" mean AlgoMatter S.L. operating under the Cleopha brand.

This policy covers two distinct services:

• The nEvie Android application (the "App"), which is an Android launcher installed on your device.
• The nEvie pages on www.cleopha.eu (the "Website"), including the product, help, and privacy pages viewed in a web browser.

The App and Website have different data flows. Part A describes the App. Part B describes the Website. The remaining sections apply to both where relevant.

Neither the App nor the Website uses user tracking or analytics. We do not monitor how you use nEvie or build profiles of your activity. This does not prevent the technical processing needed to provide features you request, deliver the Website, or protect the services, as described below.

The data controller responsible for the processing described in this policy is:

Part A — nEvie Android App

The App is primarily local-first. Most information is read and processed on your device to provide launcher features. Local processing does not mean that the App never handles personal or sensitive data; it means Cleopha does not receive that data merely because the App uses it on your device.

2. Information the App Processes on Your Device

2.1 Launcher Layout, Settings, and App Inventory

To function as a launcher, nEvie reads installed launchable apps, shortcuts, widgets, icon packs, and available Android profiles. It stores your launcher pages, folders, Dock, widget placements, selected icons, hidden-app choices, gestures, and other settings. Package names, component identities, profile identifiers, and usage needed to resolve launcher items may be stored locally. Your installed-app inventory is treated as personal and sensitive device data and is used only for launcher, search, icon, widget, and restore functionality.

2.2 Contacts and Contact Shortcuts

Contact access is off by default. If you enable Contacts as a Universal Search provider and grant Android's Contacts permission, nEvie reads contact display names and stable lookup links so it can match contacts while you type. It stores those names and lookup links in a private on-device search index. Contact photos are loaded on demand and cached in memory. nEvie does not read contact notes or silently publish your address book.

Selecting a contact result records its display name, lookup link, selection count, and selection time in local recent-search history. If you place a contact shortcut on Home or in the Dock, its name and lookup link become part of your launcher layout and can remain there until you remove it.

Revoking Contacts permission stops further provider reads and removes contact documents from the search index. Contact shortcuts already placed in your launcher layout and selected-contact entries in recent history are separate user-created or convenience records. You can remove launcher items, use Settings > Search > Clear recent results, clear the App's cache/data in Android, or uninstall the App.

2.3 Search and App-Launch History

nEvie stores small on-device convenience histories to rank recently selected app, contact, and web-search results and frequently launched apps. These records can include app identities, contact names and lookup links, web queries, counts, and timestamps. They are not app analytics and are not sent to Cleopha. They are stored as recreatable cache data and are excluded from normal backup archives.

2.4 Notification and Gmail Badges

If you grant Android Notification Access and enable notification-count badges, nEvie reads the originating app/profile and count-related notification metadata needed to calculate badges. It does not use notification message bodies for badge calculation. Badge snapshots are processed locally and are not included in normal backups.

If you enable Gmail unread badges, nEvie reads the Google account identifiers visible to the selected Android profiles and Gmail's inbox unread counts. Selected Gmail account identities and related settings are stored locally. nEvie does not read or transmit email bodies. Gmail may deny provider access, in which case this badge source remains empty.

2.5 Google Play Billing and Offline Access

nEvie asks the Google Play Billing service on your device for current subscription and non-consumable lifetime ownership. Google Play, not Cleopha, processes payment methods, charges, renewals, cancellations, refunds, and subscription management. nEvie performs client-side validation of current Play responses and does not send purchase tokens, signatures, order IDs, prices, account identifiers, or raw Billing responses to a Cleopha billing server.

After a successful Play check, nEvie may store a small encrypted record on your device to support limited temporary offline access. This record remains in Android private storage, is excluded from launcher backups and debug snapshots, and is not sent to Cleopha.

2.6 Local Files and Backups

When you explicitly export or import a local backup, nEvie reads or writes only the file you select through Android's system file picker. Normal backup archives can contain your launcher layout, pages, folders, Dock, widgets, settings, package/component identities, contact shortcuts placed in the layout, user-selected icon assets, and restore metadata. They exclude app icon caches, frequent-app history, recent-search history, Google account session state, badge snapshots, and runtime capability state.

Local backup archives are not additionally password-encrypted by nEvie. Keep exported files private and import only files you trust. Debug snapshot tools, when present in a build, are separate from normal backup and can intentionally include additional cache or fixture state for testing.

3. Information That Leaves the Device

3.1 Internet Search Suggestions and Results

When the Internet provider is enabled in Universal Search and a validated network is available, text you type is sent over HTTPS to the suggestion endpoint of your selected provider — Google, Bing (Microsoft), or DuckDuckGo — to retrieve autocomplete suggestions. Choosing a web result sends the selected query to that provider through a browser or compatible search app. These requests also expose ordinary connection data, such as your IP address and the App's user-agent, to the selected provider. Cleopha does not receive these queries.

You can disable the Internet search provider in Settings > Search > Providers. Locally indexed app, shortcut, and permitted contact search can then continue without remote suggestions.

3.2 Google Drive and Android Platform Backup

Manual Google Drive backup is optional and begins only after you authorize Google access and start a backup. nEvie uploads the backup archive directly from your device to the App-specific data folder in your Google Drive account using Google's APIs. Cleopha does not operate an intermediary backup server and cannot access that private Drive folder. The archive may contain contact shortcuts if you placed them in the launcher layout.

If Android Platform Auto Backup is enabled, Android and the device's selected backup transport may copy eligible App data under the platform's controls. Google Drive, Google Identity, Android Platform Backup, and their retention and security practices are governed by Google's terms and privacy policy.

3.3 Google Play and Android Vitals

Google Play may collect install health, crashes, Application Not Responding reports, performance information, device model, Android version, memory, and related technical diagnostics under Google's own terms. Cleopha can review reports made available through Google Play Console and Android Vitals to diagnose reliability problems. These are Google Play platform diagnostics, not analytics or user tracking embedded in nEvie.

3.4 No App Tracking or Analytics

The App does not track users and does not include analytics or telemetry. It does not embed Firebase Analytics, Google Analytics, Tag Manager, an advertising SDK, an advertising-ID tracker, or a Cleopha telemetry service. Cleopha does not receive events describing which apps you launch, which contacts you search, which settings or gestures you use, your page count, your installed-app list, or your local launcher layout.

4. App Choices and Local Retention

• Contacts, Notification Access, Gmail badges, notifications, and Google Drive backup are optional. Use the relevant App setting, Android permission setting, or Google account control to disable them.
• Launcher layouts and settings remain until you change them, clear the App's data, or uninstall. Android may later restore eligible data if Platform Auto Backup remains enabled.
• Recent-search and frequent-app records are recreatable cache data. Clear recent search results in nEvie Settings; Android's Clear cache/data controls provide broader removal.
• Local exports remain wherever you saved them. Google Drive backups remain until you delete them through nEvie or your Google account. Platform backups follow the backup provider's retention controls.

Part B — Cleopha Website

The Website is a separate static web experience. Visiting it does not give the Website access to the App's launcher database, permissions, contacts, badges, search history, or backups.

5. Information Processed When You Visit the Website

5.1 Hosting and Security Logs

A browser must send technical request information to the infrastructure hosting the Website. The hosting provider may therefore process your IP address, requested URL, date/time, browser and device information, referrer, response status, and security-event data in ordinary server or delivery logs. Cleopha may use available logs only to deliver, secure, and troubleshoot the Website. We do not use these logs to track visitors, analyze visitor behavior, build usage profiles, or produce Website usage analytics.

5.2 Google Fonts

The current Website requests font stylesheets and font files from Google Fonts when a page loads. This connects your browser to fonts.googleapis.com and fonts.gstatic.com, which exposes ordinary request information such as your IP address, browser details, referrer information, and the requested resource to Google. This Website dependency is separate from the App and does not expose App data to Google Fonts. Cleopha does not receive this request information and does not use Google Fonts for tracking or analytics.

5.3 Outbound Links

The Website links to services such as Google Play, Reddit, and Wise. Those services do not receive App data from this Website. If you follow an outbound link, the destination can receive ordinary browser request information and will apply its own privacy policy.

6. No Website Tracking or Analytics

The Website does not track visitors and does not use analytics. Its code does not include Google Analytics, Tag Manager, advertising pixels, behavioral analytics, or social-media tracking SDKs. It does not set its own cookies and does not use localStorage, sessionStorage, or similar browser storage to identify or track visitors. Because the Website uses no analytics or tracking cookies, it does not display an analytics-cookie consent banner.

Hosting infrastructure and externally loaded Google Fonts may process technical request data independently as described above. If Cleopha later adds non-essential cookies, analytics, pixels, or similar tracking, we will update this policy and introduce consent controls before activating them where required.

7. Support and Privacy Correspondence

The Website has no account system or embedded contact form. If you choose to email us for support or a privacy request, Cleopha and its email provider receive the information you include, such as your email address, name, message, attachments, and related technical details. We use it to respond, investigate the issue, protect our legal rights, and meet legal obligations. Do not send contacts, notification content, backup archives, or other sensitive device data unless it is necessary and you intend us to receive it.

8. Legal Bases (EEA and UK)

Where the GDPR or UK GDPR applies, the legal basis depends on the processing:

• Performance of a contract or steps at your request — providing App features, a backup or search action you request, and requested support.
• Consent — optional Android permissions and access you enable, Google account authorization, and any future Website processing that legally requires consent. You may withdraw consent through the relevant App, Android, Google, browser, or Website control, without affecting earlier lawful processing.
• Legitimate interests — delivering, securing, and troubleshooting the Website and App, reviewing product-quality reports, preventing abuse, and responding to ordinary support requests, balanced against your rights.
• Legal obligations — records or disclosures required by law.

9. Service Providers and Other Recipients

Depending on what you use, information may be processed by:

• Google for Google Play distribution and diagnostics, Google Identity, Google Drive or Android Platform Backup, Google search suggestions/results, and Website fonts. See the Google Privacy Policy.
• Microsoft if Bing is selected for suggestions or web results. See the Microsoft Privacy Statement.
• DuckDuckGo if DuckDuckGo is selected for suggestions or web results. See the DuckDuckGo Privacy Policy.
• Website hosting and email providers for page delivery, security logs, and correspondence on Cleopha's behalf.
• Other sites you choose to open, such as Reddit or Wise, under their own privacy policies.

We do not sell personal data, sell your installed-app inventory, publish non-public contacts, or share App data with advertisers. Some providers may process information outside your country. Where Cleopha controls such a transfer, we use a lawful transfer mechanism required by applicable data-protection law.

10. Retention

Local App retention and deletion choices are described in section 4. Third-party search, backup, Google Play, font, and outbound-link providers apply their own retention policies.

Cleopha retains Google Play Console and Android Vitals reports only as long as reasonably needed to diagnose and resolve product issues, and no longer than 24 months. We retain support and privacy correspondence for up to 3 years after the last contact unless a longer period is required for an active dispute or legal obligation.

Website security and delivery logs, where available to Cleopha, are retained only for the period reasonably needed for delivery, security, abuse prevention, troubleshooting, and legal obligations. The exact period can vary with the hosting provider and incident.

11. Security

We use reasonable technical and organisational measures appropriate to the data and risk. The App keeps most operational data in its private on-device storage. Network features described above use HTTPS where supported by the named service. No method of storage or transmission can be guaranteed completely secure.

Backup archives can reveal launcher organization, apps, widgets, settings, custom icons, and placed contact shortcuts. Store them securely and import only trusted archives.

12. Children's Privacy

The App and Website are not directed to children under 13, or a higher minimum age where required by local law. We do not knowingly ask children to provide personal information. If you believe a child has provided information to Cleopha, contact privacy@cleopha.eu so we can investigate and take appropriate action.

13. Your Privacy Rights

Depending on where you live, you may have rights to access, correct, delete, restrict, or receive personal data Cleopha holds about you; object to certain processing; withdraw consent; and complain to a supervisory authority. You may also have the right not to be discriminated against for exercising applicable privacy rights.

These rights apply to data held by Cleopha. Most App data is held only on your device or in a backup account controlled by you, so Cleopha cannot retrieve or delete it for you. Use the controls in section 4 for that data. For data Cleopha does hold, contact privacy@cleopha.eu. We may need to verify your identity and will respond within the timeframe required by applicable law.

If you are in the EEA or UK, you may lodge a complaint with your local data-protection authority. We would appreciate the opportunity to address your concern first.

14. Changes to This Policy

We may update this policy when the App, Website, providers, or legal requirements change. We will revise the "Last updated" date. When required, we will provide additional notice or request consent before materially different processing begins.

15. Contact Us

For privacy questions, concerns, or requests, contact: