Community safety

Connect through verified ADJODO support channels.

Official links must be verified. Staff will never request passwords, OTPs, API secrets or advance payout fees.

Contact the team Visit help center

Never share OTPs

Never share passwords

Verify payment requests

Use in-app support

Report impersonation

Keep campaign IDs handy

Announcements

Platform notices and maintenance updates belong on verified company channels.

Community

Discuss workflows without sharing credentials or private user data.

Account support

Use authenticated chat or contact so account-specific requests remain auditable.

Recognize an official conversation before acting on a message

Treat a channel name as a claim to verify

A message that displays the ADJODO name is not automatically an authorized company conversation. Before following a link or acting on an instruction, verify the channel through a known company route or the support workflow inside your account. This page explains how to keep community discussion separate from account operations. It does not publish an unverified group invite as if it were official.

Announcements and general product questions can be discussed without sharing credentials, while a private account issue belongs in an authenticated or otherwise appropriate support channel. Keep the source of an instruction visible when you are asked to make a change. A familiar avatar, forwarded screenshot or copied display name should not replace verification of the actual destination and the person authorized to handle the request.

Keep shared discussion free of account secrets

Use a community conversation for general questions about a workflow, not for passwords, OTPs or secret integration values. Remove account-specific data from examples that will be visible to other participants. A campaign identifier can still reveal context, so share it only where it is necessary for an authorized investigation.

If someone asks you to disclose a credential as a shortcut to solving an issue, stop and use the official support route to verify the request. A public answer can explain where a setting belongs without requiring the secret stored there. Preserve helpful instructions in your own notes with their official source so a forwarded version does not become detached from the context in which it was given.

Verify payment-related instructions through the actual workflow

A payment or payout message should be checked against the information shown in the relevant account area and the authorized team process. Do not treat a private chat as sufficient evidence for an unexpected transfer, a new beneficiary or an advance fee. Ask for the appropriate account reference and verify the action through the known contact route without sharing banking secrets in a public thread.

If the message claims urgency, keep that claim separate from the evidence that the request is legitimate. Screenshots can be altered or reused, so the account's own records and the official workflow matter. This page is about verifying the conversation path; it does not establish new payment terms or approve a transaction outside the processes that apply to your account.

Report suspicious messages with useful non-sensitive evidence

If a message appears to impersonate the company, record the visible channel identifier, the request being made and the time it was received. Share that evidence with official support in a form that does not expose your credentials or unrelated participants' personal data. Do not continue the suspicious exchange simply to gather more information. Keep a copy of the concerning link as text for review without opening it unnecessarily.

General community discussion and private account support should remain distinct even when they use familiar product terminology. Help can explain a normal workflow, and Contact can help verify where a conversation should take place. The goal is a clear, recognized route for the next action rather than trusting an instruction solely because it arrives in a familiar messaging application.