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.