Use m3lytsz lawfully and understand what is actually available.

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.

Privacy-first service rule

Privacy is a service principle, not permission to misuse the service.

m3lytsz is designed to minimise unnecessary identification and to protect private communications. Users must still comply with applicable law and may not use the service for fraud, threats, exploitation, malware distribution, unauthorised access, harassment, non-consensual intimate content, child sexual abuse material, trafficking, or other unlawful harm. Privacy features do not create immunity from lawful obligations.

1 · Operator

Company operator and privacy 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. Correspondence: 66 Paul Street, London EC2A 4NA, United Kingdom. General contact: hello@m3ly.me. Data protection contact: snooptsz@m3ly.me. See the Privacy Policy.

2 · Eligibility, age and beta status

18+ product policy; active development.

m3lytsz private beta is intended for people aged 18 or over. The 18+ statement is a product-policy condition and is not represented as highly effective age assurance. In the UK, m3lytsz applies its documented child-safety posture while the service is conservatively treated as likely to be accessed by children.

Beta features may be changed, limited, disabled or withdrawn as security, reliability, legal or technical requirements evolve. A feature shown as Coming Soon, research, disabled, experimental or unqualified is not promised as an available production capability.

3 · Accounts and identity

Human and Machine identities stay distinct.

Native m3lytsz identity is designed around a handle and security credentials rather than mandatory email or phone identity. You are responsible for protecting passkeys, recovery material, device credentials and sessions.

AI Agent, Bot, Robot and Machine identities remain visibly classified and must not be used to deceptively impersonate a Human. m3lytsz-72 temporary Human identities last exactly 1, 24 or 72 hours, according to the lifetime selected at creation, and have no operator recovery promise. Passkey protection does not extend the selected expiry.

Recipient-bound guest identities are temporary, restricted to the intended peer and cannot use a guest link to expand themselves into general directory/settings privileges.

4 · Acceptable use

Do not use m3lytsz to harm people or systems.

You must not use m3lytsz for unlawful or abusive activity, including fraud, scams, phishing, harassment, unlawful threats, deceptive impersonation, malware distribution, credential theft, unlawful surveillance, misuse of personal data or attempts to evade lawful restrictions. You must not interfere with m3lytsz security controls, deliberately overload the service or attempt unauthorised access.

m3lytsz may restrict, freeze, quarantine or terminate access where reasonably necessary to protect users, the service, third parties or legal compliance. A freeze is a security measure and is not a substitute for verified account deletion.

5 · Privacy and permissions

Connection permissions are not permission to track.

Use is subject to the Privacy Policy. m3lytsz-72 includes the implemented core communication transports without a paid m3lytsz entitlement. Internet/IP works through the device network; supported Web browsers may use Web Bluetooth direct for an established encrypted chat; Android may use Bluetooth/BLE, Wi-Fi Direct, QR bootstrap and NFC bootstrap where the hardware, runtime permissions and bilateral consent requirements are satisfied.

NFC and QR are bounded bootstrap/share mechanisms, not plaintext private-message transports. m3lytsz Voice is audio-only: online calls use the qualified relay route, while supported Android devices may use the consent-gated Wi-Fi Direct local voice route. Web offline live voice, video, general radio/accessory calling and PSTN/SMS/telephone-number service are not part of the free m3lytsz-72 core. Unsupported platform capabilities fail closed rather than being simulated. No permission authorises behavioural advertising, unrelated real-world identity enrichment or persistent location history.

6 · Private messaging and capability truth

Release-gated encrypted messaging; no silent downgrade.

Private messaging currently uses release-gated encrypted m3ly-mls-v1 envelopes with no plaintext fallback. It is not presently claimed as qualified end-to-end encryption; qualification requires executable evidence for the exact accepted deployment.

Message Links may let a recipient start a bounded temporary guest conversation without a persistent account. Possession of a private capability link can permit access until it expires, is exhausted or is revoked, so users should share those links only with intended recipients.

Internet/IP is the common route. Implemented direct routes are available in the UK beta without a paid m3lytsz entitlement where the platform genuinely supports them and the user grants the required permission/consent. Browser Wi-Fi Direct/NFC is not claimed where the browser exposes no qualified API, and a direct session never silently downgrades to a weaker or plaintext route. Video remains disabled.

7 · Reporting, complaints and appeals

Easy-to-use safety reporting and complaint routes.

The current m3lytsz release has no public/community posting surface. User safety controls focus on private conversations, identities, devices and secure links.

Report: use Report conversation in the conversation controls for illegal content, threats, harassment, scams, impersonation, child-safety concerns or another rule breach. Private-message reports do not include decrypted message text by default; a reporting user may explicitly choose to provide an excerpt. A person affected by content who cannot use the in-product control may email hello@m3ly.me with the m3lytsz account/link or other reference, what happened, why they believe it is illegal or contrary to these Terms, and only the evidence they lawfully choose to provide.

Complain or appeal: email hello@m3ly.me or use any in-product appeal made available for the decision. m3lytsz records the complaint, reviews the relevant decision or alleged failure to act, takes appropriate action, and communicates an outcome/reason where lawful. A materially adverse automated decision must have appropriate human or independent review rather than relying only on the same automated signal. The process is intended to be understandable and usable by children as well as adults while the service is treated as likely to be accessed by children.

Contract right: if m3lytsz removes or restricts access to user-generated content, or suspends or bans a user, in breach of these Terms, the affected user has the right to bring a claim for breach of contract. Nothing in these Terms removes any statutory complaint or court right.

See Moderation, Reporting and Appeals. m3lytsz is not an emergency service; immediate danger in the UK should be reported to 999 or 112.

8 · Android / Google Play

One existing Play application.

The Android application identity is me.m3ly.app. m3lytsz updates that existing Google Play app when an Android release is actually required. m3lytsz does not use a replacement app or website-distributed release APK as the normal release path.

Google Play may process Google-account, distribution and payment information under Google's own terms. Any future paid digital functionality must use a billing route that is lawful and compliant with applicable Google Play rules at the time of release.

9 · Account deletion and security rights

Deletion, logout and revocation stay distinct.

Start account deletion from Settings or m3ly.me/account-deletion.html. m3lytsz may require proportionate proof that you control the pseudonymous identity before destructive deletion.

Logout, session/device revocation, guest-session termination and link revocation are security controls and do not mean the account itself has been deleted. Security/deletion/revocation controls are intended to remain available even where normal interactive service is on a jurisdictional legal hold.

10 · Service availability and security

Private beta; fail closed when safety cannot be established.

m3lytsz uses reasonable care in operating the beta but does not promise uninterrupted, error-free or permanently available service. Security/account controls may fail closed when an operation cannot be safely verified. If all valid account-control and recovery factors are lost, m3lytsz may be unable to restore the account because no operator recovery backdoor is promised.

11 · Intellectual property and feedback

Your lawful content remains yours.

These Terms do not transfer ownership of your lawful independent content or intellectual property to m3lytsz. m3lytsz branding, software and service materials remain subject to their applicable ownership/licence terms. Feedback may be used to improve the service unless separately agreed otherwise in writing.

12 · Liability and mandatory rights

Nothing excludes rights that law does not allow us to exclude.

To the extent permitted by law, m3lytsz is a private beta and is not responsible for losses caused solely by unavailable experimental capabilities, user loss of recovery material, misuse of the service or events outside reasonable control. Nothing excludes or limits liability that cannot lawfully be excluded or limited, including mandatory consumer rights.

13 · Governing law and market limits

England and Wales, subject to mandatory local rights.

These Terms and non-contractual obligations arising from m3lytsz are governed by the laws of England and Wales, subject to any mandatory consumer/local rights that cannot lawfully be displaced. Operational beta access for Human, AI Agent, Bot and Robot identities is currently limited to the United Kingdom. Other operational markets remain on legal hold until jurisdiction-specific review; public information and rights/security controls remain globally accessible.

14 · Changes and contact

Material changes will be published.

These Terms may change as the beta and its legal/commercial model evolve. Material changes will be published and, where required, presented before taking effect.

Contact: hello@m3ly.me · 66 Paul Street, London EC2A 4NA, United Kingdom.