m3lytsz logom3lytszUK Number ServiceBETA

Release-locked legal draft · registration and contact details updated 20 October 2026

Identity checks stay with the checker; m3lytsz keeps the minimum result.

This document is not yet a live offer. Snooptsz Group Ltd is registered with the ICO under reference ZC265345. Operator and data controller: Snooptsz Group Ltd, company no. 17468359, 66 Paul Street, London EC2A 4NA, United Kingdom. Data protection contact: snooptsz@m3ly.me.

KYC boundary

m3lytsz does not receive KYC document bytes.

Stripe Identity is the current test-mode processor candidate; it is not yet approved or enabled for a live offer. Its hosted collection session receives an opaque case reference and the document/live-capture options needed for the check. m3lytsz stores an encrypted provider reference, a keyed reference hash, the requirements/source digest, bounded status, provider result digest, checked/verified timestamps and retention deadline. It does not request or store Stripe verified outputs, passport scans, identity photographs, payment-card data or KYC filenames in ordinary application tables.

Why

Contract, compliance and service delivery.

Candidate purposes are verifying the eligible end user, meeting provider/carrier requirements, preventing telecom abuse, issuing the exact contract, taking/reconciling payment, routing calls/SMS, handling complaints and protecting legal rights. The final release record must document the applicable Article 6 lawful basis for each purpose.

Carrier data

Telephone metadata crosses the carrier boundary.

Telecom providers process the number, counterparties and traffic information necessary to send or receive calls and SMS. Message bodies sent over the carrier channel are visible to that channel. They are separate from encrypted m3lytsz chat.

No resale

Not an advertising profile.

Number/KYC/payment/contract data is not published on public cards, sold, used for behavioural advertising or placed in Google Workspace links. Optional public m3ly.xyz pages receive no private Number Service data.

Retention

Expiry is not deletion.

The candidate KYC metadata schedule is one year; unfinished handoffs expire within 20 minutes and unanswered correction requests after 30 days. Candidate immutable contract/acceptance retention is seven years. Payment, complaint and carrier records follow their documented legal/accounting/dispute schedule. At the retention deadline, encrypted references and metadata must be purged or de-identified unless a specific documented legal hold applies. Provider-held document retention is governed by the approved processor terms and must be separately evidenced before release.

Lawful disclosure

No blanket police access.

m3lytsz evaluates law-enforcement requests case by case. Disclosure is limited to what is necessary and proportionate, supported by an identified lawful basis or a binding court order/legal obligation, and documented. Special-category or criminal-offence data needs the additional lawful condition required by UK law. We do not volunteer an entire account file merely because a request exists.

Rights and correction

Access, correction, objection, restriction, erasure and complaint routes.

Applicable rights can be requested through Privacy Rights. A provider result marked correction required can be resumed through the signed-in number flow without emailing documents to m3lytsz. Erasure may be limited while a contract, accounting record, complaint, fraud case or binding legal hold must lawfully be retained; the reason is explained.

Primary guidance

Minimum by design.

This candidate follows ICO guidance on data minimisation and storage limitation and sharing personal data with law-enforcement authorities. ICO registration does not enable Number Service sales. Final release still requires the remaining processor-contract, retention, DPIA/ROPA and other service-release evidence recorded by the operator.