← Back to Help Center

Account and billing

ReviewBot permissions, data, and privacy basics

A trustworthy review workflow makes ownership and data access clear. Connect only the accounts needed for the selected source or destination, keep private customer details out of public review replies, and give teammates the dashboard access they need for their role.

Updated August 1, 2026 · ReviewBot Help Center

Follow these steps

Complete the workflow, then verify it

  1. 1

    Connect the minimum required account

    Use the store, Slack, Zendesk, Freshdesk, Teams, or email account that owns the workflow. Confirm the connected account and workspace before enabling delivery.

  2. 2

    Keep review context purposeful

    ReviewBot uses review fields and source context to help teams triage feedback. Avoid placing private account details, secrets, or payment information in public review text or alert rules.

  3. 3

    Separate public replies from private support

    Public store responses should not request sensitive account information. Link customers to the private support channel when an issue requires account-specific investigation.

  4. 4

    Give teammates the right access

    Invite teammates through the dashboard workflow and explain which Flow, channel, queue, or report they own. Remove access when someone leaves the team.

  5. 5

    Check privacy and terms

    Review the current Privacy Policy and Terms for the authoritative handling and account conditions. Contact ReviewBot if your security or data-handling review needs product-specific clarification.

Quick checklist

  • ✓Connected accounts are owned by the right team.
  • ✓Public replies contain no private account information.
  • ✓Every destination has a responsible teammate.
  • ✓Security questions have an escalation path.

If something does not work

A teammate cannot see the expected Flow+

Confirm they joined the correct workspace and that the Flow or destination is shared through the dashboard’s supported team access path.

A security reviewer needs more detail+

Use the Privacy Policy and contact ReviewBot support with the specific source, destination, and data question. Do not email credentials or customer review exports.

Frequently asked questions

Does ReviewBot need access to customer passwords?+

No. Do not place passwords, payment details, or private account credentials in review text, alert rules, or support requests. Use the connection authorization flow for supported sources and destinations.

Where should I ask a privacy question?+

Start with the Privacy Policy and contact ReviewBot support with the exact workflow or integration under review.