How can we help?

Identity checking is an optional Dibbit Plus account feature. Stripe hosts the government-ID and live-face check. Dibbit can use the bounded result to show Identity checked; it does not verify a business, reputation, name ownership, authority, or safety.

• If a link expires or the check needs another step: return to your signed-in Dibbit account and continue from Trust & address controls. Attempts are limited to control cost and abuse.
• If you cannot or do not want to use Stripe: you can keep using Dibbit without the credential. Contact support if a checked-senders-only address prevents a legitimate request; Dibbit does not promise an equivalent badge without an equivalent check.
• For access or deletion: use the account controls or contact Dibbit. Dibbit queues eligible provider-session redaction, but provider processing can take time and legally required records may remain. For data Stripe controls for its own purposes, use the Stripe Privacy Policy.

Never email an ID image or selfie to Dibbit support. See the Dibbit Privacy Notice before starting.

The optional Gmail connection is separately release-gated. When it is available, Dibbit initially copies a server-visible projection of up to 25 recent messages, including at most 4,000 characters of text per message. The owner may separately consent to complete non-draft, non-spam, non-trash history. A live Gmail search sends the bounded search query to Google and displays Google's matching results without adding them to the saved projection. An HTML-only MIME body can become a labelled text-only preview; formatting, links, and images are removed. A filename-free text MIME body part stored by Gmail behind an attachmentId may be retrieved within the bounded body limit. This is not automatic file import. Files are loaded only after the owner explicitly chooses an attachment, and they are not stored in the Gmail projection. The connection starts read-only. Where available, saving drafts and sending need Google's separate compose permission, and mailbox changes need its separate modify permission; every send and mailbox change also needs the owner's review and confirmation. Connected copies are not part of Sealed Chats.

• Connect or sync: use the connected-source controls in your signed-in account. Connecting requests Gmail read-only access, and reading or syncing does not send, draft, modify, label, trash, or delete source mail. Sync copies up to 25 recent messages unless you separately confirm the default-off complete-history setting. Full history remains server-visible, keeps the 4,000-character projected-body limit, excludes ordinary file attachments, drafts, spam, and trash, and can be paused independently. Bounded MIME body hydration may retrieve filename-free text body parts; it is not attachment import. Periodic sync is another separate opt-in; it is not Gmail push delivery or background file loading. Temporary failures retry on a bounded schedule and stop after six attempts; permanent provider rejections pause immediately. If the screen says reauthentication is required, remove the expired Google access in Dibbit and then reconnect; the old credential cannot be restarted.
• Search or load a file: live search forwards the bounded query to Google and shows Google's matching results without adding them to Dibbit's saved projection. The continuation is encrypted and account-, connection-, query-, revision-, and credential-bound; the raw Google page token is not exposed. For an already copied message, Load attachments lists up to 10 supported files (PDF, JPEG, PNG, WebP, MP4 video or audio, MPEG audio, or plain text, 25,000,000 bytes in total) after an explicit owner action and retrieves only the file the owner selects. Files are not loaded automatically or retained in the Gmail projection.
• Stop access: revoke the connection in Dibbit. Dibbit deletes its local credential only after Google confirms revocation. If a Google response is unavailable or inconclusive, Dibbit retains the encrypted local credential and tells you to retry. You can also remove Dibbit from Google Account permissions, then retry so Dibbit can confirm the token no longer works.
• Delete the copy: use the separate delete-data control to remove the Gmail projection stored by Dibbit. This does not delete the original messages in Gmail.

See the Privacy Notice for the exact data, purpose, retention, and Google Limited Use disclosure.