Block decisively. Describe carefully.

Controls available now

• Dibbit is for people 18 or older.
• Address owners decide when to reply and can mark a thread handled.
• Blocking permanently revokes that thread's private return capability.
• Rate limits, message ceilings, and replay controls reduce automated abuse.
• Outside-agent access requires an owner-approved OAuth connection and can be revoked from My messages.
• Important external actions remain outside the messaging and Live Slate path.

Report a concern

Report impersonation, threats, exploitation, fraud, illegal content, privacy violations, or a compromised private link to privacy@dibbit.ai. Include the public @name and thread or address URL, but do not forward passwords or highly sensitive data.

If someone is in immediate danger, contact local emergency services. Dibbit is not monitored as an emergency channel.

Moderation limits

Dibbit applies rate limits, message ceilings, replay controls, and owner blocking. These controls reduce some abuse but do not determine whether a message is truthful, lawful, or safe. A service-access restriction is not a legal judgment or a claim that a person committed wrongdoing. Appeals can be sent to the same monitored contact.

Dibbit does not proactively read or guarantee review of every message. Nonpublic content may be reviewed only by authorized personnel or contractors when reasonably needed for a specific report, support request, security incident, reliability problem, or legal duty. Access is limited to the information needed for that task.

Connected-agent limits

An owner-approved outside agent can read that owner's Dibbit inbox and send a reply through the fixed reply tool. It cannot obtain a guest's private return capability or use Dibbit to approve payments, bookings, contracts, or other high-risk actions. Owners should review the exact reply before delivery and disconnect an agent they no longer trust.

Requests are private, but not end-to-end encrypted

Current Dibbit Requests and guest return threads are access-controlled by the owner account and a random sender capability, but message content is stored server-side and is not end-to-end encrypted. Anyone with the complete return link can open that thread until it is blocked or expires.

Sealed Chat safety boundary

Sealed Chats are a separate, release-gated native feature. If enabled, content would be encrypted and decrypted on participant devices, so Dibbit could not proactively inspect that plaintext on the server for scams, abuse, malware, or illegal content. A participant seeking help would need to choose and submit the relevant content with a report. Dibbit could still use available account, device, room, rate-limit, delivery, and network metadata to protect the service and respond to valid reports or legal duties.

Encryption does not make a participant verified or safe. Contact consent is not an endorsement, and own-device verification would not verify the other person's identity. Do not rely on Dibbit for emergencies or assume that a message, attachment, account, or device is harmless.