Share a Dibbit @name or public link instead of your direct number. The visitor can send a private message without joining, and you can reply through a private return link. You decide whether the conversation ever moves to phone, email, or another app.
Why phone-number privacy matters
A phone number is more than a chat destination. It can be tied to account recovery, carrier records, caller-ID databases, and years of personal use. The FTC explains that a successful SIM-swap attack can let a criminal receive text verification codes and enter accounts that use SMS recovery.
That does not mean every new contact is dangerous. It means a person should have a lower-exposure way to handle first contact before deciding to reveal a long-lived number.
The Dibbit first-contact flow
Claim an @name, name the agent, and share the public address. The other person opens it, writes the request, and keeps a private return link. You receive the message in your Dibbit inbox and can reply, block, or close the thread.
- Marketplace listing: add the AI address instead of a direct number.
- First introduction: send the address before deciding where to continue.
- Public bio: give everyone one stable contact path.
- Family or school coordination: let a person send the ask without joining another network.
Invite people without uploading an address book
A privacy-respecting invite flow should begin with a user choosing who receives the address. Apple's App Review Guidelines prohibit selecting every contact by default for messaging, and Google Play tells apps whose primary purpose is inviting contacts to use system pickers or the ShareSheet instead of broad contacts access.
Dibbit's intended sharing pattern is therefore a generated address link shared through the phone's own share sheet. The owner chooses the recipient and can review the message. Dibbit does not need a copied address book to make the referral loop work.
Keep the boundary honest
Using an AI address does not verify the visitor, stop every abusive message, or make an offline meeting safe. Keep marketplace payments on the marketplace when appropriate, use its reporting tools, and follow ordinary safety practices for meeting a stranger.
The product promise is narrower and useful: less direct contact exposure, an owner-controlled reply path, and a visible way to block or close the thread.
Frequently asked questions
Can I reply without revealing my phone number?
Yes. The Dibbit owner replies inside the private thread, and the visitor returns through a private link. Neither person has to add a phone number to that exchange.
Does Dibbit read or upload my contacts?
The intended invite flow uses the device share sheet and user-selected recipients. It does not require uploading the owner's address book to create or share an AI address.
Does hiding my phone number make a transaction safe?
No. It reduces one form of contact exposure. It does not verify the other person or guarantee that a transaction, link, payment, or meeting is safe.