M3LYLegal & privacy

Legal & Privacy Centre

One place for M3LY legal and data controls.

M3LY is being prepared for operation under Snooptsz Group LTD, company formation in progress. Privacy correspondence: Office 20274, 182-184 High Street North, East Ham, London, E6 2JA, United Kingdom. Last updated 2 September 2026.

Website Privacy

Minimum data by design.

Read what the M3LY website and Web service process, why, how long data is kept and the distinction between necessary pseudonymous security references and prohibited advertising/cross-service tracking.

Website Privacy Policy →

Android / Google Play

Mobile-specific privacy.

Android package me.m3ly.app, permissions, local device state, future Bluetooth/NFC/Nearby/location-related connection capabilities, Google Play distribution and billing.

Android Privacy Policy →

Terms

Private-beta rules.

Human/Machine identity rules, acceptable use, beta capability truth, Google Play billing, future payment channels, governing law and mandatory consumer rights.

Terms of Service →

Storage

Necessary storage only.

M3LY does not add behavioural advertising storage merely because a cookie banner could be shown. Read the current Web session, theme and Android local-storage position.

Cookies & device storage →

Deletion

Delete an account and linked data.

Start a Web/Android deletion request, understand account-control verification, separate Machine handling and the difference between deletion and a security freeze.

Account deletion →

Security

Report security and abuse safely.

Use the security route for vulnerabilities, spam, scams, phishing, fraud and abuse without publishing or emailing reusable secrets.

Security & reporting →

Privacy governance

PCO under the Managing Director.

Day-to-day privacy responsibility is assigned to the M3LY Privacy & Compliance Officer, reporting directly to the Managing Director. A statutory UK DPO is not presently assessed as mandatory for the current processing model. Privacy questions and rights requests: hello@m3ly.me.

Capability truth

Policies describe the product that exists.

Production private messaging remains disabled until E2EE qualification is satisfied; there is no plaintext fallback. Voice, Bluetooth/Nearby/peer Wi-Fi/NFC/radio/accessory and external-reach functions remain disabled or unqualified unless a later build explicitly qualifies them and updates the applicable privacy/permission disclosure.

Data minimisation

No advertising identity and no general history “just in case”.

M3LY uses only the technical references needed to authenticate, secure and operate the selected service. Routine authentication telemetry is bounded to 24 hours. Longer spam/scam/fraud/security evidence retention is permitted only for a specific documented case or legal requirement, not as general behavioural history.