One address. Clear human control.

Dibbit Plus can be purchased through Stripe Checkout on the web or, where available, Apple's App Store in the iOS app or Google Play in the Android app. The price, billing interval, currency, applicable taxes, and any trial offered are shown before purchase. The subscription renews automatically at the stated interval until it is canceled. Manage a Stripe subscription through the billing portal in your Dibbit account. Manage an App Store subscription in Apple's subscription settings, and manage a Google Play subscription in Google Play subscriptions. Verified provider records control paid access.

Completed Dibbit account deletion revokes paid feature access and starts cancellation of an active Stripe subscription. Cancellation and refund rights required by applicable law remain unchanged. For any other refund request, contact privacy@dibbit.ai; no term here limits a mandatory consumer right.

App Store payments are charged to your Apple Account. To stop renewal, cancel at least 24 hours before the current period ends. Deleting your Dibbit account does not cancel an App Store subscription or automatically refund a purchase. Please cancel through Apple before deleting; you can request Dibbit account deletion without canceling through Apple first. App Store refund requests can be submitted through Apple's refund service.

Google Play payments are charged through the Google Account selected in Google Play and renew at the interval and price shown before purchase. Deleting your Dibbit account does not cancel a Google Play subscription or automatically refund a purchase. Please manage or cancel it in Google Play subscriptions before deleting; you can request Dibbit account deletion without canceling through Google Play first. Google Play refund eligibility and requests are handled under Google Play refund policies, subject to mandatory consumer rights. Contact privacy@dibbit.ai for product support.

If Google sends Dibbit a pending chargeback review, Dibbit may retain the bounded provider request and alert an authorized operator so it can be reviewed within Google's deadline. This intake does not make an automatic refund or dispute decision, change your entitlement, or prove the outcome of the chargeback. Google and the payment system determine the final result under their applicable rules and mandatory law.

Dibbit Plus pays for a bundle of Dibbit features. It does not purchase or resell a standalone identity-verification service, and no part of the subscription is a per-check verification product. If the optional identity feature is available, payment does not guarantee that Stripe will accept an attempt, complete a check, or that Dibbit will issue or keep an identity credential. Dibbit limits retries to protect accounts, prevent abuse, and control provider costs.

If Dibbit offers the number ladder's identity check bonus, a member may separately choose to count their own successful identity check once as 5 ladder credits. The bonus is a one-time program credit with no cash value. Plus does not sell it or pay for any number, and no rung needs Plus or a check: invites alone reach every rung.

A claim gives the account a limited right to use an available @name, agent name, and Dibbit ID within the service. It does not verify identity, create ownership of a word or number, grant a trademark right, or permit off-platform sale or transfer unless Dibbit expressly supports it.

A Protected Alias is a separate, paid, globally unique Dibbit namespace license for the stated one-year term. The current $29 purchase is a one-time payment and does not automatically renew. The alias can expire unless a renewal is offered and completed. Payment does not prove identity, affiliation, endorsement, trademark ownership, or a right to impersonate another person or business. Dibbit may challenge, suspend, or revoke an alias for rights, safety, payment, or abuse reasons, subject to applicable consumer law.

Dibbit may hold unclaimed names and number patterns for safety, public services, rights disputes, scarcity, or separate allocation by Dibbit. An address that impersonates someone, infringes rights, misleads users, or violates these terms may be suspended or disabled, but an established @name or Dibbit ID is not silently reassigned to another account.

Reassignment is limited to correcting a documented registry error or complying with a final, enforceable order from a court or other legally authorized authority that resolves the rights dispute. Where the law permits, Dibbit will give the current holder notice and an opportunity to contest the correction. Messages, contacts, history, reputation, permissions, and private capabilities never transfer with the identifier.

A connected social account is a separate trust fact. It may show that the Dibbit owner controlled that account when it was linked, but it does not by itself prove a legal name, trademark, business affiliation, endorsement, or authority to represent another person or organization. Dibbit may label a disputed name as affiliation unconfirmed or contested while a documented rights review is pending.

The Dibbit Registry may offer an explicit, published set of Dibbit-controlled IDs as one-time service-use licenses, at a fixed price or in a published timed auction under the Registry auction rules. A licensed ID is an additional route to the recipient's existing AI address; it does not replace the free Standard ID, create ownership of a number, increase trust or capability, or constitute an investment or token. Price, currency, recipient, auction rules, and refund terms are shown before payment or bidding.

A gift can be directed only to the exact existing @name shown at Checkout and does not become a public route until that recipient accepts it. If a gift is declined or expires, Dibbit requests a refund to the original payment method; the order becomes refunded only after the payment provider confirms the refund. Gifts and purchases never carry messages, contacts, permissions, history, verification, or reputation. Gifts and ID Shop purchases do not themselves authorize user-to-user resale, cash exchange, or off-platform transfer. A fully refunded, disputed, revoked, or deleted assignment may be retired permanently rather than resold, subject to mandatory consumer rights.

A current holder may record interest in a possible additional-ID marketplace. That waitlist action is not a listing, offer, appraisal, reservation, or transfer. The separate marketplace remains closed until its terms are published and the service is activated. Outside an expressly activated Dibbit marketplace, user-to-user transfers are not supported.

The number ladder lets an eligible member earn program credits and pick additional Dibbit numbers in country collections. The rules published in the Dibbit ID policy and on the number ladder rules page, rules version number-ladder-v2, govern how credits qualify, what each rung needs, and how picks work. After publication, a rung's requirements change only in members' favor.

The rungs grant 5-digit, regular 4-digit, nice 4-digit and 3-digit numbers. Three digits is the top rung: two-digit numbers are not available through the number ladder at any number of credits, and they are not offered in the Dibbit Registry or the ID Shop. Dibbit keeps them back, and only the Dibbit owner may release one, to a specific member, with a recorded reason.

Credits are a record of program progress. They have no cash value, are not property, cannot be bought, sold, gifted, transferred, or exchanged, and end with your account. No purchase, Plus subscription, gift, install, rating, or review earns a credit, and no payment is needed to reach any rung. A ladder number is a limited right to use an additional route to your existing address, like other additional Dibbit IDs. It cannot be gifted, sold, listed, or transferred, is not marketplace inventory, and does not verify identity or change trust, reach, delivery, or authority. You choose the collection and the number; Dibbit never draws or assigns one at random.

Dibbit does not send invites for you and does not read your contacts. When you share your invite link, or a Founding Drop invite link, you must make clear that you get credit when people join. The prefilled share text says “(I get credit toward a shorter Dibbit number when you join)”, and wherever you post or send your link you must keep a disclosure that is at least as clear. Credit is void for undisclosed paid promotion, unsolicited bulk email or text messages, spam, paying or rewarding people to join or to answer Requests, and rewards for ratings or reviews.

Dibbit may hold a credit or a rung for review, and the top rung always needs one operator review. Reviewers approve or deny with a recorded reason; they never choose your number. If Dibbit finds self-invites, alternate accounts, invite rings, paid activations, or undisclosed or unsolicited promotion, it may bar the account from earning and, if the bar is not lifted on appeal, void the affected credits and retire any number whose rung no longer holds. You may appeal a bar once, within 30 days, by contacting privacy@dibbit.ai; nothing is voided or retired before then. Retired numbers are not returned to inventory.

Dibbit's team, operators, and store-review and test accounts cannot earn credits or hold ladder numbers. Every member takes part on the same rules, with no head start or early picks for any group, and invites made with Founding Drop invite links count under the same rules as every other invite. If you delete your account, pending credits end, unpicked rungs are released, and your ladder numbers retire. Mandatory consumer rights are unaffected.

A Dibbit Registry auction runs under the published Registry auction rules, which are part of these terms. Dibbit is the only seller. The published starting price is the only reserve, and there is no buyer's premium, registration fee, or bid fee.

The Dibbit Registry offers 3-digit and longer numbers. Two-digit numbers are not offered in the Registry, the ID Shop or the number ladder: Dibbit keeps them back, and only the Dibbit owner may release one, to a specific member, with a recorded reason. Single-digit flagship numbers are not offered until their charity rules are published.

To bid, you register for a collection with an account at least 30 days old, a verified email address, and a US billing address, and you choose a bid limit. Registration opens 24 hours before bidding. Each person may register once per collection. Dibbit asks your card issuer to authorize 20% of your bid limit, at least $50, and does not capture that authorization. Dibbit releases it once every lot you bid on has closed and you have nothing left to pay. Raising your limit needs a new authorization, and an authorization more than 6 days old takes no bids until you renew it.

A bid is a binding maximum and cannot be withdrawn. Dibbit bids for you up to that maximum, one increment above the next-highest maximum, and when two maximums are equal the earlier one leads. A bid in a lot's last 10 minutes moves that lot's close to 10 minutes after the bid, and no lot closes later than 24 hours after its scheduled close.

Dibbit emails the winner a payment link. The winner has 48 hours from that email to pay through Stripe Checkout, with 3-D Secure requested. A winner who does not pay in time defaults: Dibbit may offer the lot to the next-highest bidder at that bidder's own maximum, with 48 hours from Dibbit's email to pay, and that bidder may decline the offer or let it lapse with no penalty. A winner who defaults cannot buy or bid in the Dibbit Registry for 12 months, and for the 12 months after that needs an authorization of 100% of the bid limit. Dibbit does not charge or keep any amount because of a default.

Dibbit, its employees, contractors, registry operators, the founder, and accounts Dibbit controls never register or bid. If one does, Dibbit voids that lot and discloses the void. Results, with each lot's final price, number of unique bidders, and number of bids, are published within 24 hours of the lot's close. A winner's @name is shown only if the winner chooses. A won lot is licensed on the same terms as any other Dibbit Registry purchase.

Unpublished marketplace candidate · Version secondary-market-draft-v1

This section describes a separate service. Publishing this version alone does not activate listings, offers, Checkout, or transfers. If activated, it would cover only eligible, active, additional paid Dibbit ID licenses. A free Standard ID, @name, account, messages, contacts, history, grants, private capabilities, reputation, and verification would not be sold or transferred.

A seller would review the exact additional ID and listing price. A buyer could make an offer at a different price. Before accepting an offer, the seller would review that exact offer and a settlement quote showing the gross price, platform fee, and seller net amount. Acceptance would reserve the trade for payment; it would not itself charge the buyer or transfer the ID. Any handoff would require verified, settled payment proof and a fresh check that the seller still holds the eligible ID.

Provider-confirmed refunds, disputes, revoked rights, and failed handoffs may suspend or invalidate an assignment and require remediation. A partial refund or uncertain provider outcome requires manual review; it is not treated as proof of a full refund. Seller payout is a separate payment-provider process and is not guaranteed by an ID handoff. No listing, offer, or past price promises a buyer, liquidity, a resale price, or any increase in value. Mandatory consumer rights described elsewhere in these terms remain unchanged.

If Dibbit makes the feature available, an eligible Dibbit Plus owner who is at least 18 may consent to Stripe's hosted government-ID and live-face check. Stripe supplies a bounded result; Dibbit, not Stripe, decides whether to issue the literal Dibbit label “Identity checked,” the check date, and current status. The label is a Dibbit account-trust signal. It is not a Stripe endorsement, a portable identity product, a business or KYB check, or verification of character, claims, affiliation, qualifications, reputation, safety, ownership of an @name or Protected Alias, trademark rights, or authority to act. Credentials can expire, be revoked, or be unavailable, and automated or provider decisions can be wrong.

An address owner may accept everyone, place currently checked senders first, or accept only currently identity-checked senders. The sender sees that policy before submitting. A credential controls routing only; it never creates permission for an agent to pay, book, sign, disclose, or perform another consequential action.

The check is optional. An account can use Dibbit without it, although a sender without a current credential cannot reach an address that chooses checked-senders-only routing. Starting or paying for Plus does not guarantee a successful check, and repeated or incomplete attempts may be limited. If Plus is canceled, paid access ends according to the billing period shown in the account; a current credential may remain visible until it expires, is revoked, the account is deleted, or Dibbit removes it for security, legal, provider, or product reasons. Cancellation does not convert the credential into a separately purchased service.

You may authorize a compatible outside agent to use Dibbit's four fixed base connection tools. The consent screen identifies the requesting client and those actions: reading your Dibbit address, listing and reading your Requests inbox, and preparing one exact reply in an existing Dibbit thread for your review. The reply tool works only after you give that connection Requests message access. It saves the reply for your review and does not send it. Apart from the automatic replies described below, which need their own permission, a reply reaches the requester only after you approve that exact reply in Dibbit. A connected agent cannot claim or delete your address, obtain a sender's private return capability, or use Dibbit to approve a payment, booking, contract, or other high-risk action.

Message-source access is separate and absent by default. You must choose the exact outside client and explicitly grant communications_v1 access to Requests, Sent, or Protocol Mail, your Dibbit address mailbox. Message access then lets the agent list, search, and read only the selected sources, with their source and privacy labels. Reading or searching Protocol Mail message text also needs you to allow reading for that connection in Dibbit, and each allowance lasts 15 minutes. The agent may save an exact reply proposal and check its status. Preparing or checking a proposal does not approve or send it; apart from the automatic replies described below, any supported delivery needs your separate review and send control in Dibbit. Changing or revoking this source grant does not silently change another client's permissions.

Separately, where Dibbit offers it, you can share one exact Protocol Mail item with one connection: a message, including an older one, or the text of a TXT or PDF attachment, an image, or an audio transcript from a message. Sharing needs a sign-in within the last 15 minutes but no Protocol Mail message access, and it does not let the agent browse the rest of your mailbox. Each shared item is available to that connection for at most 15 minutes, and you can cancel it sooner. The agent may prepare a reply to a shared message for your review; preparing it does not send it.

Automatic replies are a separate permission and are off by default. Each permission covers one connection and one source: Requests, Sent, or Protocol Mail. To turn one on, you must have signed in within the last 15 minutes, and that connection must already have message access and reply drafting for that source. Each permission expires within seven days and allows replies of up to 2,000 bytes, up to 20 an hour and 100 a day, or the shorter expiry and lower limits shown when you turn it on. For Sent and Protocol Mail, and for Requests where Dibbit requires it, you also approve that exact permission with your passkey. While it is active, the agent can answer a new incoming message with a short text reply it saved, without asking you first, at most once per incoming message. Requests and Sent replies are posted in the existing Dibbit conversation. A Protocol Mail reply is queued for delivery as a reply to the message it answers; a mail provider accepting it does not confirm delivery. Under this permission the agent cannot supply new text or a new recipient. You can revoke the permission at any time in Dibbit, and removing that source's message access or disconnecting the agent also stops it. Replies already sent cannot be recalled, and AI replies can be wrong.

You are responsible for choosing the outside provider, reviewing each prepared reply before you approve it, deciding whether to turn on automatic replies, and revoking access when it is no longer needed. If you create a connection key, keep it secret: anyone who has it can use that connection, with the access you gave it, until you revoke the key or disconnect the connection. Revoke a key at once if it may have been exposed. The approved provider receives your Dibbit account user ID and email address in its OAuth sign-in credential; with a connection key, Dibbit holds that credential and the provider receives only the key. Supabase requires a phone field, but Dibbit leaves the phone field empty in newly issued outside-agent access tokens. Dibbit does not request or allow the phone scope for outside-agent connections. Older tokens or information already shared cannot be recalled; disconnect and reconnect to replace a connection. Outside agents can make mistakes and are also governed by their provider's terms and privacy practices. Revocation stops new tool calls but cannot retrieve information already sent to an authorized provider.

A separate selected-message permission can relay only Sealed Chat text you explicitly review and choose for that exact outside client. It does not grant room access, room keys, or a right to browse other Sealed Chat messages. Dibbit access and a returned draft expire after 15 minutes; bounded cleanup runs every five minutes, so physical deletion can follow expiry. Cancellation or grant revocation immediately clears Dibbit's live relay payload and stored draft. The outside provider may retain text it already received. The relay can return a draft for your review but cannot send it.

When a connected source is available, you may authorize Dibbit to copy the bounded data described on the consent screen into your private Dibbit account. A Gmail connection starts read-only and initially imports a recent server-visible text projection. Where available, you may separately grant Google permission to save and send Gmail drafts and messages and to change Gmail mail, drafts and labels; Dibbit saves a draft only when you choose to, and sends or changes mail only after you review and confirm it. You may separately consent to complete non-draft, non-spam, non-trash history. Live search forwards your bounded search query to Google and displays Google's matching results without adding them to the saved projection. Gmail may expose a filename-free text MIME body part through an attachmentId; Dibbit may retrieve that bounded body part for the text projection. Ordinary files are not imported automatically and are loaded only after your explicit attachment choice for an already copied message. Dibbit does not retain those files in the Gmail projection. The projection, sync, search, and agent read tools do not themselves send, draft, modify, label, trash, or delete source email. An optional background setting periodically refreshes the selected recent or complete-history projection; it is not push delivery or background file import. Outside-agent access to Connected copies is not offered in this release: no outside agent can list, search, or read Dibbit's saved Gmail copy, and Connected wake-up callbacks, Connected first-response drafting and automatic work on a connected Gmail account are not offered either. Temporary retries are bounded and stop after repeated failure. If Google rejects the authorization, automatic sync pauses and the owner must remove that rejected connection before reconnecting. Other permanent provider rejections pause for owner attention instead of retrying automatically. A separate protected reply can create or send only after the exact sender, recipient, content, and RFC thread are derived and approved under the Plus action terms. It is not part of Sealed Chats and does not preserve a provider's encryption after data is copied into Dibbit.

You can revoke the provider credential and separately delete the copied projection. Provider-side revocation may require removing Dibbit from the provider's account-permissions page if the provider cannot confirm Dibbit's request. Deleting Dibbit's copy does not delete the source messages from the provider.

When explicit communication imports are available, you may choose and confirm a bounded Telegram Desktop export, reviewed WhatsApp or WeChat portable archive, or single item shared from iMessage. These are user-supplied server-visible copies, not live provider connections or authenticated records. Dibbit does not accept provider passwords or session state, does not import attachments, and does not preserve source encryption. You must have the right to provide the selected content.

A message is information, not permission to act. A Live Slate keeps the current price, time, or plan visible and records proposed changes and participant confirmations. It is a coordination record, not a payment, booking, identity verification, signature, legal contract, or guarantee that either participant will perform.

A named agent may send a clearly labelled AI acknowledgement and ask one clarifying question after a new inbound message. That generated text can be incomplete or wrong. It is not a message from the address owner and does not show that the owner read, approved, accepted, or agreed to anything.

When reply alerts are available, a visitor may ask Dibbit to email them when there is a new reply. Alerts begin only after the visitor confirms from that inbox. An alert is a convenience: it can be delayed, filtered, or not delivered, and it does not show that the owner read, approved, or agreed to anything. Each alert carries the thread's private link, so anyone with access to that email can read and reply in the thread. The private thread remains the record. The stop link in an alert ends alerts for that conversation to that address.

When the feature is available, a visitor or owner may request a labelled cloud-AI translation of one visible Request message. The stored original remains visible and controls if the wording differs. Machine translation can omit, distort, or misunderstand meaning and must not be treated as authority for a payment, booking, purchase, disclosure, agreement, or other consequential action.

Before Dibbit sends the selected message for cloud translation, the authorized visitor or owner must explicitly accept the current translation disclosure. Dibbit records a minimal, append-only receipt containing the policy version, guest-or-owner mode, Request ID, server acceptance time, and an internal owner binding only for owner mode. The receipt contains no message, translation, return-link token, or guest capability hash. It is audit evidence of the disclosure shown, not proof that the translation is correct or permission for any action. The Privacy Notice explains its retention and account-deletion treatment.

Dibbit does not autonomously set prices, reveal hidden floors or ceilings, send money, book services, disclose private addresses, or bind a participant. External actions require the participant's own separate decision and any legally required process.

These tools may remain unavailable until their source, release flag, signed native build, and device-acceptance checks are complete. When available, the native app exposes a message action only after the owner taps a message or its action control. A translation is a labelled derivative of only the selected persisted Request message; the stored original remains authoritative.

The calendar action copies the selected message text and an editable event suggestion into the operating system's calendar editor after an explicit tap. Dibbit does not read calendars or represent that opening the editor created, booked, or saved an event. You must review the title, date, time, time zone, location, invitees, and notes and choose whether to save or cancel in the system surface.

Address invitations use the operating system's share sheet. Dibbit does not request or upload your contacts, choose recipients, or send an invitation for you. You are responsible for selecting an appropriate audience, respecting recipients' choices, and not using sharing for spam, harassment, or unlawful marketing.

When included-agent message assistance is available, you may manually ask your saved Dibbit agent to summarize, explain, translate, or draft from one exact owner-bound Request, Sent conversation, Connected copy, or selected live Gmail result. Before the cloud call, you review the source label, bounded recent non-redacted visible messages, current agent brief, optional instruction, and any writing-style preferences. The authenticated server, not the client, resolves that source and sends only the reviewed context through Vercel AI Gateway to a fixed OpenAI model hosted on Microsoft Azure. The app does not hold a provider API credential or provide authoritative Request text. The transfer is not end-to-end encrypted, and you are responsible for having the right to disclose the selected material. For a manual request, you may separately select supported TXT, PDF, JPEG, PNG, or WebP attachments from that same message source for the reviewed cloud request. Where optional speech-to-text is enabled, you may also select an MP3 or M4A audio file, which is sent for cloud transcription only after you confirm the review. Automatic assistance does not include attachment contents or live Gmail results. Sealed Chat content is not eligible for this feature.

You may separately enable automatic work for Requests, Sent, and individual Connected accounts you choose, including future incoming text in those sources. This is not permission to read every account, attachment, or Sealed Chat. Automatic work on a connected Gmail account is not offered in this release. Changing your saved agent brief requires renewed permission. The included agent can prepare attention suggestions and reply drafts but cannot send, delete, mark read, change a message, or perform another external action. Generated work becomes inaccessible after seven days. Bounded cleanup runs every five minutes, so physical deletion can follow expiry; dismissing an item clears its generated output immediately.

Writing-style settings are device-local structured preferences, not a verified identity, voice clone, or guarantee that a draft sounds like you. A generated response may be incomplete, inaccurate, inappropriate, or misleading. A manual response is not stored as a chat transcript. An automatic result is stored only under the bounded work retention above. Neither replaces the original source or sends a message; a reply remains an editable draft until you review it and use a separate send control. The model cannot approve or prove an external action.

A Huddle is a purpose-bound, server-visible room for Ask, Plan, Announcement, and Opportunity items. A host chooses open, invite-code, or approval admission, may set an expiry, and can admit, reject, remove, or ban memberships where those controls are available. A membership ban is not a verified person-level exclusion. A participant must not share a private membership capability or invite code with an unauthorized person. Huddles are not Sealed Chats and are not end-to-end encrypted.

A host is responsible for describing the room accurately, choosing an appropriate admission setting, responding to reports, and avoiding any claim that a Huddle is official, school-approved, identity-verified, or safe unless the host has independent authority and a lawful basis for that claim. A school-domain match, if offered, establishes only control of an eligible email address for admission. It does not prove identity, affiliation, age, reputation, authority, or safety.

GoGo Catch-up is a factual view generated from structured room items, explicit dates, status, answers, and RSVP totals, with links back to the source items. It can be incomplete or wrong. The original item remains authoritative, and catch-up must not be treated as an interpretation of a participant's emotions, intent, truthfulness, or agreement.

Admission, removal, RSVP, delivery, and item status are service records, not proof of attendance, identity, consent to an external act, academic credit, contractual acceptance, or proof that an external service delivered or executed an action once. A closed or expired room can become unavailable without retracting copies that participants already saved or shared.

Dibbit keeps a server-visible operational event ledger of no more than 10,000 rows per Huddle, with no fixed time expiry in this release. An RSVP update leaves at most one content-free marker for each membership and Plan; the marker does not contain the RSVP choice. Other event payloads may contain limited status, item-kind, role, admission, expiry, or retirement metadata until account retirement. These records support operation and safety but are not immutable or tamper-proof evidence.

Sealed Chats are a separate native feature and may remain unavailable until Dibbit completes its operator, signed-build, device, recovery, and release reviews. If enabled, message content would be encrypted and decrypted on participant devices. End-to-end encryption does not make a participant anonymous or conceal every item of service metadata, including account and device identifiers, room membership, IP and access logs, timing, delivery activity, or ciphertext and media sizes.

A contact grant allows two current Dibbit accounts to open a direct chat; it does not prove identity, affiliation, reputation, or safety. Device verification would establish trust between the same owner's devices, not the identity of the other participant. You remain responsible for deciding whom to contact and what to share.

A queued send records only that the native client accepted one attempt. It does not guarantee a successful send, delivery, read receipt, or retention, and duplicate processing can occur. Network interruption, device loss, software failure, account suspension, or unavailable recovery material can delay or permanently prevent access. Keep recovery material private and in a safe place; losing all trusted devices and usable recovery material may make encrypted history unrecoverable.

Logging out or wiping one device removes its local Dibbit session and key material but does not remotely erase another participant's copy. A contact revocation prevents future approved-room use in Dibbit; it does not retract content already received. Content deliberately shared from a Sealed Chat with GoGo, an outside agent, email, WhatsApp, iMessage, Telegram, WeChat, or another service leaves the Sealed Chat boundary. The outside-agent selected-message relay requires a separate grant and one explicit reviewed selection; it never authorizes silent, automatic, or all-message Sealed Chat access.

Address owners can permanently block a private return link. Dibbit may limit, suspend, preserve, or remove accounts, addresses, links, or content when reasonably necessary for security, legal compliance, rights disputes, or violations of these terms. Automated signals can be wrong; they do not establish guilt, illegality, or verified identity.

A signed-in owner may delete an account from the account page. The address stops resolving and its @name and Dibbit ID retire rather than being reassigned. Owner-confirmed Memory and private image objects and metadata are removed through the deletion process, paid feature access is revoked, and active Stripe cancellation is started. Message and Live Slate content is redacted on the schedule described in the Privacy Notice, or immediately when account retirement is prepared. Retirement also closes owned Huddles, revokes their member capabilities, removes their content from product access, nulls current RSVP choices, and nulls every Huddle event actor and subject while replacing the payload with exactly the single field retired: true. The Huddle identifier, event type, and occurrence time remain as minimal operational history. Dibbit keeps only the residual records needed to prevent identifier reuse, protect the service, resolve an active dispute, or meet a legal obligation. The Privacy Notice explains those criteria and the permanent, content-free identifier tombstone.