01
Capability checks
Messaging can be independently restricted at account level without necessarily removing every other account capability.
Messaging
Conversation with server-side boundaries.
Tuvybe messaging combines private conversation with account capability checks, block-aware interaction and server-authoritative paid-message rules.
Messaging
Conversation
Messaging is treated as a protected interaction, not just a text box.
Protected messaging flows check account eligibility on the server. Paid-message flows can quote the required Coin cost before a message is committed.
02
Quote before charge
Paid messaging has a server-side quote path before the send action, keeping pricing decisions away from client-only logic.
03
Block-aware interaction
Active blocks create a two-way interaction boundary between the blocker and the blocked account.
Contact sharing
Personal contact details can trigger additional safeguards.
The backend includes contact-sharing policy controls that can detect categories such as phone numbers, email addresses, WhatsApp references, social handles and links. The configured policy decides the resulting experience.
Safety by policy
The default platform data includes a warning-oriented contact-sharing policy. Administrators can control the policy mode and detection categories.
Phone numbersDetection can identify telephone-number sharing patterns.
Email addressesEmail-sharing detection can be enabled by policy.
Social and messaging handlesWhatsApp references and social handles are supported detection categories.
External linksLink detection can be enabled alongside the other contact-sharing checks.