E ESEER 3D Live Wallpapers Download App
Menu

Legal notice //

Privacy Policy. Legal Notice.

This page explains what ESEER processes, what remains on your device, how optional usage statistics and crash reports work, how imported wallpaper files are handled, and how to exercise your privacy rights.

Privacy Overview

  • ESEER does not require a user account.
  • ESEER does not request your name, postal address, phone number, contact list, or email address during normal use.
  • Imported images, Creator projects, wallpaper layers, and project contents remain on your device unless you explicitly export or share them.
  • Raw gyroscope, accelerometer, and motion-sensor values are processed locally and are not sent to ESEER analytics servers.
  • ESEER may process limited pseudonymous usage and technical information when the “Share usage statistics” setting is enabled.
  • ESEER may use Firebase Crashlytics for crash and stability diagnostics, subject to the relevant application setting.
  • ESEER does not sell personal data or use analytics for personalized advertising.

Data Stored Locally On Your Device

ESEER stores information locally where necessary to provide its features. This may include:

  • The selected wallpaper
  • Motion mode and motion strength
  • Gyroscope or touch-control preferences
  • Rendering and performance settings
  • FPS and low-end-device preferences
  • Designer effects and shader preferences
  • Clock, text, and widget settings
  • Downloaded wallpaper files and previews
  • Cached images and generated thumbnails
  • Imported wallpaper files
  • Creator projects and imported layers
  • Exported wallpaper files
  • A randomly generated analytics installation identifier
  • Analytics events waiting to be transmitted

Local data can generally be removed by deleting individual projects or wallpapers, clearing application storage, or uninstalling ESEER.

Pending analytics events stored locally are deleted when “Share usage statistics” is disabled.

First-Party Usage Analytics

When “Share usage statistics” is enabled, ESEER sends limited usage and technical information to analytics infrastructure operated by the developer.

These statistics are used to understand how ESEER is used, measure feature adoption, detect usability problems, prioritize development, and improve application stability and compatibility.

Information that may be included

  • A randomly generated installation identifier
  • The ESEER application version
  • The Android major version
  • A broad device-performance category such as low, mid, high, or unknown
  • The time at which an event occurred
  • The time at which the event was received
  • Opening the application
  • Opening a wallpaper detail or focus view
  • Applying a wallpaper
  • Opening the Creator
  • Opening the Designer
  • Successfully exporting a Creator project
  • Whether Simple or Advanced Creator mode was used
  • The number of layers in an exported project
  • The numeric identifier of a wallpaper
  • The general wallpaper category used for analytics, such as official, custom, or bundled/default

Pseudonymous installation identifier

The analytics installation identifier is randomly generated by ESEER and remains associated with the application installation until application data is cleared or ESEER is uninstalled.

The identifier is transmitted to the analytics API through HTTPS. Before database storage, it is transformed using a keyed HMAC-SHA256 cryptographic function.

The raw installation identifier is not stored in the analytics database. The resulting stored value is pseudonymous, not fully anonymous.

Information not included in usage analytics

  • Your name
  • Your email address
  • Your phone number
  • Your contact list
  • Your advertising identifier
  • Your precise location
  • Your IP address inside analytics event documents
  • Imported images or their visual contents
  • Creator project contents
  • Creator project names
  • Local file names or file paths
  • Text entered into wallpapers or widgets
  • Screenshots
  • Raw gyroscope or accelerometer values
  • Arbitrary free-form text entered by the user

Analytics events are validated against a predefined list. The public analytics API does not accept arbitrary event names, unrestricted metadata, project contents, images, or nested user-provided information.

Controlling usage analytics

You can disable future first-party usage analytics at any time from:

Settings → Privacy → Share usage statistics

When this option is disabled:

  • No new ESEER usage events are recorded.
  • Pending local analytics events are deleted.
  • Pending analytics upload work is cancelled.
  • Application presence heartbeats are stopped.
  • Wallpaper presence heartbeats are stopped.
  • Periodic wallpaper-status checks are cancelled.

Disabling the setting does not automatically delete data already transmitted to the server. You may request deletion as explained in the “Your Rights And Data Deletion” section.

Legal basis

First-party usage analytics are processed on the basis of the developer’s legitimate interests in understanding product usage, maintaining the service, improving features, fixing usability issues, and prioritizing development.

You may object to this processing at any time by disabling “Share usage statistics”.

Live Application And Wallpaper Presence

When usage statistics are enabled, ESEER may send temporary presence signals.

Presence signals are used to estimate how many installations are currently using the application or currently displaying the ESEER live wallpaper.

Application presence

While the ESEER activity is visible, the application may send a temporary heartbeat approximately every 30 seconds.

The heartbeat may include:

  • The pseudonymous installation identifier
  • The application version
  • A predefined application section such as gallery, focus, settings, Creator, or Designer

Visible wallpaper presence

While the ESEER live wallpaper is visibly displayed on the home screen, the wallpaper service may send a temporary heartbeat approximately every 60 seconds.

This signal may include:

  • The pseudonymous installation identifier
  • The application version
  • The numeric identifier of the active wallpaper

The system live-wallpaper preview is not intended to be counted as a normally active home-screen wallpaper.

Presence documents are temporary and expire approximately five minutes after the most recent heartbeat.

Live Wallpaper Service Status

ESEER separately checks whether its live wallpaper service is still configured as the active system live wallpaper.

This differs from visible wallpaper presence:

  • Visible wallpaper presence indicates that the home screen was recently visible.
  • Wallpaper service status indicates that ESEER remains selected as the device’s live wallpaper, even while another application is open.

Periodic status checks may include:

  • The pseudonymous installation identifier
  • Whether ESEER is currently the selected live wallpaper
  • The numeric identifier of the wallpaper, when active
  • The application version
  • The time of the latest verification

Android schedules these checks in the background. Their exact execution time may be delayed by battery, network, or system scheduling conditions.

Wallpaper-status records expire automatically when they have not been refreshed for approximately seven days.

Aggregated Statistics And Developer Displays

ESEER may calculate aggregate counters from analytics data, including:

  • Current application presence
  • Current visible wallpaper presence
  • Number of active ESEER wallpaper services
  • Unique application users during a period
  • Application openings
  • Wallpaper views and applications
  • Creator exports
  • Designer openings

Aggregate counters may be displayed on private developer dashboards or developer-owned monitoring devices such as an ESP32 display.

These outputs contain totals only. They do not expose installation identifiers, session identifiers, IP addresses, user content, imported images, or Creator project contents.

Creator Projects, Imported Wallpapers And External Links

ESEER can import and export wallpaper files, including ESEER-specific .es files.

These files may contain:

  • Scene configuration
  • Images and layers
  • Wallpaper titles
  • Author or creator names
  • Creator links
  • Social links
  • Website or store links
  • Other metadata added by the file creator

Imported files and Creator projects are processed locally. Their images and project contents are not sent to ESEER first-party analytics.

Echoseer is not responsible for the content, accuracy, security, availability, or legality of third-party metadata, external links, or imported files.

Only import files from trusted sources. Before sharing an exported project, ensure that you have the right to share all images, layers, names, fonts, and links included in the file.

Device Sensors

ESEER may use sensors such as the gyroscope, accelerometer, or rotation sensor to create parallax, camera movement, and interactive wallpaper effects.

  • Raw sensor readings are processed locally.
  • Raw sensor readings are not sent to analytics servers.
  • Sensor readings are used to animate wallpapers and previews.

Crash Reporting And Diagnostics

ESEER may use Firebase Crashlytics as a service provider to diagnose crashes, application-not-responding incidents, rendering failures, and other stability problems.

Crash and diagnostic reports may include:

  • Application version
  • Android version
  • Device manufacturer or model class
  • Crash time
  • Stack traces
  • Error messages
  • Technical application state
  • Memory or storage information relevant to the failure
  • A Firebase-generated installation identifier used to group diagnostic events

Crash reports are used only for stability analysis, troubleshooting, bug fixing, and technical support.

Crash reporting is separate from ESEER first-party usage analytics. Where an in-app crash-reporting option is available, it can be controlled through that setting.

Firebase processes crash information according to Google’s applicable terms, privacy documentation, and retention practices.

Network Requests And Server Logs

ESEER may connect to remote services to:

  • Download official wallpapers and previews
  • Retrieve categories and wallpaper metadata
  • Check for new or updated wallpaper content
  • Send enabled usage analytics
  • Send enabled crash diagnostics
  • Check live-wallpaper service status

ESEER first-party network communication uses HTTPS.

As with most internet services, requests necessarily expose standard connection information to the receiving server and hosting infrastructure. This may include:

  • IP address
  • Request time
  • Requested route
  • HTTP protocol information
  • User-agent or networking information

IP addresses are not stored inside ESEER analytics event, presence, or wallpaper-status documents.

Web-server, reverse-proxy, security, and hosting logs may temporarily retain connection information for service operation, security, rate limiting, abuse prevention, debugging, and incident investigation.

These logs are retained only for a limited operational period according to server and hosting log-rotation settings.

Notifications And Permissions

ESEER may use local notifications to inform users about new wallpaper content or application updates.

Depending on the Android version and the features used, ESEER may request access needed to:

  • Set and display a live wallpaper
  • Open files or images selected by the user
  • Save or share exported wallpaper files
  • Send notifications
  • Access network content

ESEER uses permissions only for the features they support. Permissions can be managed through Android system settings.

Service Providers And Data Sharing

ESEER may rely on service providers for:

  • Google Play application distribution
  • Firebase Crashlytics
  • Server and website hosting
  • Email support
  • Security and infrastructure operation

These providers may process technical information according to their own terms, privacy policies, contractual obligations, and applicable legal safeguards.

ESEER first-party analytics are processed on infrastructure operated by or for the developer.

ESEER does not:

  • Sell personal data
  • Sell analytics data
  • Sell Creator project information
  • Provide analytics identifiers to advertisers
  • Use analytics for personalized advertising
  • Create cross-application advertising profiles

Information may be disclosed when required by applicable law, a valid legal request, or where reasonably necessary to protect the application, its users, or its infrastructure.

Data Retention

  • Detailed first-party analytics events are normally retained for no longer than 90 days.
  • Analytics events are automatically removed through a database expiration mechanism after the retention period.
  • Temporary application and visible-wallpaper presence records expire approximately five minutes after their most recent heartbeat.
  • Wallpaper-service status records expire approximately seven days after their most recent verification.
  • Pending analytics events stored locally are removed when usage statistics are disabled.
  • Local application preferences, projects, imports, and cached files remain until deleted, cleared, or removed with application storage.
  • Support emails and voluntarily supplied files may be retained for the time reasonably necessary to investigate and answer the request.
  • Crash-reporting providers retain diagnostic information according to their own applicable retention periods.
  • Temporary security and access logs are retained according to operational log-rotation and security requirements.

ESEER may retain aggregate statistics that no longer contain an installation identifier for longer periods in order to compare application usage and development trends over time.

Data Security

Echoseer applies reasonable technical and organizational measures intended to protect the information processed by ESEER.

  • First-party analytics are transmitted over HTTPS.
  • Installation identifiers are transformed through keyed HMAC-SHA256 before database storage.
  • The raw analytics installation identifier is not stored in the analytics database.
  • The analytics database is protected by authentication and is not directly exposed to the public internet.
  • The public analytics API provides no public route for reading individual analytics records.
  • API requests are validated and rate limited.
  • Payload size and accepted fields are restricted.
  • Private developer summary endpoints are protected by authentication and expose aggregate counters only.
  • Most user-created content and application preferences remain on the device.

No method of electronic transmission or storage can guarantee absolute security. Echoseer nevertheless takes reasonable steps to reduce the risk of unauthorized access, disclosure, alteration, or loss.

Your Privacy Rights and Data Requests

Depending on applicable law, you may have the right to:

  • Receive information about data processing
  • Request access to applicable personal data
  • Request correction of inaccurate information
  • Request deletion in applicable circumstances
  • Request restriction of processing
  • Object to processing based on legitimate interests

Stopping future analytics

You can stop future ESEER first-party analytics directly from:

Settings → Privacy → Share usage statistics

Requesting deletion

To request deletion of previously transmitted analytics data, support emails, diagnostic files, or other information you voluntarily provided, contact:

echoseerapps@gmail.com

Your request should state that it concerns an ESEER analytics or privacy deletion request and should include the analytics identifier when the request concerns usage analytics data.

Because ESEER does not use user accounts, the analytics installation identifier associated with your app installation may be required to locate the relevant pseudonymous records.

You can find and copy this identifier directly in the app:

Settings → Privacy → Analytics identifier

You can also use the “Email request” action available on that screen to prepare a deletion request containing the identifier.

Only information necessary to process the request will be requested.

Data that has already expired through the automatic retention mechanisms may no longer be available.

Local application data can be removed by clearing ESEER storage through Android settings or uninstalling the application.

Requests will be handled in accordance with applicable law. Certain rights may be subject to legal limitations or exceptions.

You may also lodge a complaint with the competent data-protection authority. In France, the competent authority is the Commission Nationale de l’Informatique et des Libertés (CNIL).

Children

ESEER is not specifically directed to children under the age required by applicable local law for independent consent to data processing.

ESEER does not knowingly request names, email addresses, account details, or similar identifying information from children during normal use.

If you believe that information relating to a child has been provided to Echoseer, contact:

echoseerapps@gmail.com

International Processing

ESEER is operated from France.

Certain service providers, including application-distribution, hosting, email, or crash-reporting providers, may process technical information in other countries.

Where required, such processing is subject to applicable contractual, legal, and data-transfer safeguards.

Changes To This Policy

This Privacy Policy may be updated when ESEER changes, when new features are introduced, or when legal, security, technical, or platform requirements change.

The “Last updated” date will be revised when this policy is changed.

Where required, users may also be notified through the application, the website, or the distribution platform.

Contact

For privacy, support, analytics, or data-deletion questions:

Echoseer
France
echoseerapps@gmail.com

Website:
https://seerobs.com/