Cookies & local storage
Understand storage on your device.
How m3lytsz uses essential sessions and local device storage.
Cookies & storage notice →
m3lytszLegal & privacyBETALegal & Privacy Centre
One place for m3lytsz legal and data controls.
Snooptsz Group Ltd is incorporated in England and Wales, company number 17468359, incorporated on 18 September 2026. m3lytsz is a trading name of Snooptsz Group Ltd, the company operator and data controller for the processing described in the m3lytsz Privacy Policy. ICO registration reference: ZC265345. Privacy correspondence: 66 Paul Street, London EC2A 4NA, United Kingdom. Data protection contact: snooptsz@m3ly.me. Last updated 20 October 2026.
Data protection registration
ICO registration details.
Data controller: Snooptsz Group Ltd
Registration reference: ZC265345
Date registered: 16 October 2026
Registration expires: 15 October 2027
Payment tier: Tier 1
Address: 66 Paul Street, London EC2A 4NA, United Kingdom.
Person responsible for data protection: snooptsz@m3ly.me.
Current service brand: m3lytsz.
Name on the ICO registration record: M3ly. This notice covers the m3lytsz service.
Search the ICO register using reference ZC265345.
Beta status
The m3lytsz ecosystem is currently in Light BETA.
m3lytsz and related ecosystem services are in active beta for a limited period that is not yet fixed. Features, transports, availability, qualification status and interfaces may change, pause or be withdrawn as security, reliability, legal and operational requirements evolve. Beta status does not reduce m3lytsz’s obligations relating to privacy, data protection, security, consumer rights, safety or lawful handling of communications.
Privacy
Minimum data by design.
What the Web and Android services process, why, retention, provider boundaries, rights and the distinction between service-security references and prohibited behavioural tracking.
Privacy Policy →Android / Google Play
Mobile-specific privacy.
Existing Android package me.m3ly.app, permissions, local device state, Google Play distribution and qualified transport disclosures.
Android Privacy →Terms
Private-beta rules.
Human/Machine identity rules, acceptable use, capability truth, market availability and mandatory consumer rights.
Terms of Service →Deletion
Delete an account and linked data.
Account-control verification, separate Machine handling and the difference between deletion and a security freeze.
Account deletion →Security
Report vulnerabilities and abuse safely.
Security reports, spam/scam/phishing/fraud reporting and responsible disclosure guidance.
Security & reporting →Launch policy
UK Light BETA first.
Operational beta access for Human, AI Agent, Bot and Robot identities is currently limited to the United Kingdom. Public product, legal, privacy and safety information remains globally readable, and privacy/rights/security controls remain globally accessible. Other operational markets remain on legal hold until jurisdiction review is complete.
Machine-readable policy →Acceptable use
Rules for Humans and Machines.
Safety, abuse and prohibited-use rules across messages, groups, links and telecom features.
Acceptable Use →Age & children
UK 18+ Human access.
Children’s access assessment, age assurance and child-safety posture.
Age Policy →Moderation
Reports, AI/Bot supervision and appeals.
Public and private group rules, encryption limits and review rights.
Moderation & Appeals →Machines
AI Agents, Bots and Robots.
Machine Policy →Data processing
UK GDPR processing rules.
Data Processing →Processor terms
Article 28 DPA template.
DPA →Retention
Purpose-specific deletion schedule.
Retention →Vendors
Subprocessor register.
Vendors →Telecom
Reach and transport policy.
Telecom & Reach →UK Number Service
Terms and transparent pricing.
Release-locked service scope, 30-day minimum, manual renewal, carrier boundary and exact accepted pricing.
Number Service Terms →Number privacy
Minimum KYC metadata.
Processor handoff, retention, rights and lawful-disclosure boundaries without m3lytsz receiving document bytes.
Number Service Privacy →Number safety
Telecom acceptable use.
No scams, spam, spoofing, harassment, unauthorised sharing or emergency-service claims.
Number Service Acceptable Use →Number complaints
Reference, investigation and escalation.
A release-locked complaints code that will name an ADR scheme only after actual membership is evidenced.
Number Service Complaints →Number cancellation
Cancellation and refunds.
Consumer cancellation, provider-confirmed refund, model notice and separate porting/number-release rules.
Cancellation & Refund Policy →Privacy rights
Requests and complaints.
Privacy Rights →Account deletion
Deletion rules.
Deletion Policy →Cookies & local storage
PECR and device storage.
Storage Notice →Privacy governance
Named function, direct accountability.
Day-to-day privacy responsibility is assigned to the m3lytsz Privacy & Compliance Officer. A statutory UK DPO is not presently assessed as mandatory for the current processing model; that assessment is reviewed when scale, monitoring or data categories materially change. Public privacy contact: snooptsz@m3ly.me.
Online safety and age
18+ is a policy boundary, not age assurance.
m3lytsz does not represent a checkbox, hold gesture or age statement as highly effective age assurance. For the current United Kingdom private beta, m3lytsz conservatively treats the service as likely to be accessed by children and therefore applies child-safety defaults to UK users: Findable is opt-in, guest links are recipient-bound and revocable, block/report controls remain available, no public/community posting surface is active, and unqualified wider-reach transports stay disabled. Any feature or content that legally requires highly effective age assurance must fail closed until a privacy-reviewed compliant age-assurance process is implemented.
Capability truth
Available, beta and vision stay separate.
Private messaging currently uses release-gated m3ly-mls-v1 encrypted envelopes with no plaintext fallback. It is not presently claimed as qualified end-to-end encryption; that claim stays disabled until the exact engine, version, provider, cipher suite and accepted deployment have executable qualification evidence. Android Bluetooth/Wi-Fi Direct delivery and QR/NFC offline bootstrap exist in the hardware-beta candidate but are not production-qualified until exact-build and physical/store gates pass. NFC is bootstrap/share only. Web Bluetooth is exposed only where a supporting browser provides it. Voice, general radio/accessory, cellular/satellite-capable and external-platform message routes remain unavailable or experimental unless separately qualified.