Privacy

Purpose

Defines how user data related to Reward Unit accrual is handled within the Motika.IO ecosystem, using an anonymous-by-default, minimal-data model aligned with crypto principles.

Anonymous Identity Model

When a user first opens the app, the system creates an internal anonymous UUID.
This identifier:

• contains no personal information
• is stored on the backend solely for reward ledger consistency
• cannot be changed or correlated with external identity
• is not linked to any behavioral or device profile

Users may optionally add an email for account recovery, but it is not required for earning or withdrawing MPOW tokens.
Email is never shared with advertisers or third parties.

Data Collected

The system MAY collect:

• Event-level engagement signals (e.g., play, pause, scroll) needed to compute Reward Units.
• Derived Active Time metrics and interval counts.
• Temporary IP read to determine the user’s country code, which is stored, while the IP itself is never persisted.
• Non-personal device metadata used only to compute aggregated statistics, not tied to the anonymous UUID.
• Reward ledger records specifying what reward was issued, to which anonymous UUID, and for what interval.

Data Not Collected

Motika.IO explicitly does not collect or store:

• Real names or identity documents
• Contact lists, private messages, photos, or files
• Browser history outside Motika.IO properties
• GPS location or stored IP addresses
• Device identifiers (IDFA, GAID)
• Advertising identifiers or cross-app tracking IDs
• Behavioral profiles across sessions
• Persistent device fingerprints

The system also uses no third-party trackers, pixels, SDKs, or external analytics services.

Usage

Collected data is used exclusively to:

• Calculate Reward Units
• Maintain protocol integrity and prevent abuse
• Produce aggregated, non-identifying analytics

All user-level data remains internal to the Motika.IO ecosystem and is never sold or shared.

Retention

Motika.IO applies strict minimal-retention principles:

• Raw interaction signals exist only as needed to compute the reward ledger.
• After computation, only the reward ledger entry is retained.
• All other event-level details are discarded.
• Aggregated analytics contain no identifiable information.

Jurisdiction-specific requirements MAY apply and are described in the main legal documentation.