Minimum data. Explicit purpose.

Beta status

The m3lytsz ecosystem is currently in 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.

1 · Controller and privacy contact

Data controller and data protection contact.

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.

The current Managing Director role-holder is assigned the m3lytsz Privacy & Compliance Officer function. A statutory UK DPO is not presently assessed as mandatory for the current processing model.

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.

Search the ICO register using reference ZC265345.

2 · Pseudonymous identity

Service identifiers are not advertising identifiers.

m3lytsz does not require a real-world name, email address or phone number as the native account identity. It necessarily creates pseudonymous references for identities, sessions and devices so authentication, revocation, encrypted messaging, abuse prevention and service integrity can work.

These references are not used to follow people across unrelated services, build behavioural advertising profiles or sell identity data. Findable is an explicit setting and defaults OFF.

3 · Authentication, recovery and devices

Only what is needed to prove account control.

For passkeys, m3lytsz stores public WebAuthn verification material; the private passkey key remains with the authenticator. Recovery material is handled only through its defined protected, bounded verification path and is not intended to be retained as plaintext.

m3lytsz processes bounded session, device and pairing state so users can sign in, bind/revoke Android devices and protect accounts. Machine identities remain explicitly labelled. m3lytsz-72 temporary Human identities expire after exactly 1, 24 or 72 hours, according to the lifetime selected at creation. A passkey may protect access but cannot extend expiry or create an operator recovery route.

4 · Private messaging and Message Links

Release-gated encrypted messaging. No plaintext fallback.

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.

Recipient-issued Message Links use a private proof during bootstrap and create a recipient-bound temporary guest session only after explicit activation. Guest sessions are limited to a maximum of one hour and never beyond link lifetime. Scoped guests cannot search the directory, change account settings, mint another Message Link or message unrelated identities.

Abuse reports do not include decrypted private message text by default. A reporting user may explicitly choose to disclose an excerpt for review.

5 · Connection technologies and permissions

Hardware access is explicit and capability-scoped.

The Android hardware-test candidate implements optional Bluetooth/Nearby, Wi-Fi Direct, QR peer-card scanning and NFC peer-card/Reach bootstrap sharing. Discovery uses Android Nearby-device permissions and, on Android 12 or earlier, may require Location permission and the system Location setting. Location permissions are capped at API 32. Camera is used only when the user deliberately starts the QR peer-card scanner. NFC is used only when the user deliberately starts a supported read/write bootstrap/share action. See the Android privacy notice for the exact candidate permission inventory.

NFC is not a private-message transport: its supported role is a bounded peer-card or approved capability handoff. In m3lytsz-72, implemented core transports do not require a paid m3lytsz entitlement: Internet/IP is available on Web and Android; Web Bluetooth direct is available only where the browser exposes the required API; Android may use Bluetooth/BLE, Wi-Fi Direct, QR and NFC bootstrap where the exact installed build and hardware support them. Voice messages and audio-only 1:1 m3lytsz calls are included. Online calls use the reviewed relay-only path; supported Android builds may also use consent-gated Wi-Fi Direct local voice. Web Wi-Fi Direct/NFC and Web offline live voice are not claimed. Microphone access is explicit and user initiated. General radio/accessory voice, video, PSTN/SMS and telephone-number service remain outside the free m3lytsz-72 core. m3lytsz does not use nearby/location/camera signals to create advertising profiles or behavioural location history.

Browser capability is not fabricated: Web uses Internet and supported Web Bluetooth paths where the browser genuinely exposes them; browser Wi-Fi Direct or NFC is not claimed where the platform does not provide a qualified API.

6 · Security, abuse and operational metadata

Purpose-limited security processing.

m3lytsz processes limited authentication, rate-limit, routing, jurisdiction, abuse-report and security signals to provide and protect the service. Infrastructure necessarily processes network metadata such as IP address, connection timing and routing information.

Normal candidate Android API traffic is routed through m3ly.me. Directory search terms are POST-body bound and MLS inbox device selectors are kept out of URLs where the current protocol supports a private body/header or authenticated-device alternative.

Longer evidence retention is allowed only for a specific documented spam/scam/fraud/abuse/security/legal purpose with a review or closure trigger—not as indefinite behavioural history.

7 · Purposes and legal bases

Service delivery, security and lawful operation.

m3lytsz processes data to create/authenticate identities; maintain user-selected settings; pair/revoke devices; route qualified encrypted communications; prevent fraud, spam, scams and abuse; investigate security incidents; answer rights/support requests; and meet legal obligations.

Where UK GDPR applies, legal bases may include performance of the requested service or pre-contract steps, legitimate interests in service security/abuse prevention, legal obligations, and consent where an optional activity legally requires it. m3lytsz does not sell personal data and does not use it for behavioural advertising.

8 · Providers and transfers

Infrastructure is limited to m3lytsz operation.

Supabase provides the dedicated backend/database/Edge Function infrastructure in London eu-west-2. Cloudflare provides edge/security delivery and country-level launch routing. Google Play distributes the existing Android application and may independently process Google-account/payment information under Google's terms. m3lytsz does not load third-party advertising, behavioural analytics or cross-site measurement tags on its product or public website surfaces.

No unverified backup or future provider is authorised to receive unrestricted production personal data solely because it appears in planning material. New providers require processor/transfer/privacy review before material activation.

9 · Retention and deletion

Expiry first; automated cleanup follows.

Current control targets include WebAuthn challenges up to 5 minutes; Android pairing proofs up to 10 minutes; Machine claim proofs up to 10 minutes; ordinary Web sessions up to 30 days unless shorter/revoked; m3lytsz-72 temporary Human identities exactly 1h, 24h or 72h; temporary cloud material is not recoverable after expiry; recipient-bound guest sessions up to 1h and never beyond link lifetime; and routine authentication-attempt telemetry up to 24h.

Automated purge/cleanup removes eligible expired technical data. Verified account deletion removes account-linked information that no longer has a valid purpose, subject only to a narrowly documented security, fraud, legal, accounting or statutory retention requirement. Start deletion at m3ly.me/account-deletion.html or Settings.

10 · Rights

Access, correction, deletion and control.

Depending on jurisdiction, users may have rights to access, correct or delete personal data; obtain a copy; restrict/object to certain processing; withdraw consent where applicable; and complain to a competent regulator. Because native identities are pseudonymous, proportionate proof of control of the relevant m3lytsz identity may be required.

Requests: snooptsz@m3ly.me.

11 · Children / UK Online Safety

18+ is product policy, not age assurance.

The m3lytsz private beta is intended for people aged 18 or over. m3lytsz does not treat self-declaration, a checkbox or hold gesture as highly effective age assurance. For current UK compliance governance, m3lytsz conservatively treats the service as likely to be accessed by children and applies child-safety defaults without behavioural age profiling. Any feature/content that legally requires highly effective age assurance must fail closed until a compliant privacy-reviewed process exists.

12 · Transparency and UK GDPR

Clear information at the point it matters.

Where UK GDPR applies, m3lytsz provides layered privacy information covering the controller, purposes, data categories, legal bases, recipients, transfers, retention, rights, complaints and any applicable automated processing. Just-in-time notices are used where a permission or feature introduces a distinct processing purpose. See the dedicated UK GDPR transparency notice.

13 · Market availability and changes

United Kingdom Light BETA only.

Interactive service is currently limited to the United Kingdom. Other markets remain on legal hold until jurisdiction review is complete. Security/deletion/revocation rights are designed to remain available even where ordinary interactive service is unavailable.

Material new processing, providers, permissions, transports, payments or jurisdictions require a new review and updated notice where applicable.

Automated safety processing

AI/Bot safety tools are bounded and reviewable.

m3lytsz may use clearly identified AI/Bot safety agents to supervise public and private group spaces, triage abuse reports and identify likely policy or legal violations. This processing is limited to safety and compliance purposes, is not used for behavioural advertising or unrelated model training, and is subject to access controls, audit and appropriate human review/challenge safeguards for materially adverse decisions.

m3lytsz does not claim routine provider-side access to private-message plaintext. The current encrypted-message path remains release-gated and is not presently claimed as qualified end-to-end encryption. A participant may voluntarily disclose content when making a report.

Retention

Purpose-specific, not blanket retention.

Ordinary security and abuse telemetry is normally retained for no more than 30 days. Other records use the minimum period required for their purpose, including shorter technical lifetimes or longer statutory accounting/legal-hold periods where applicable. See the Data Retention Policy.