Security, permissions and data

OAuth and Google connections

Authorize only the account required for the selected property. If ownership or project scope changes, review and revoke connections that should no longer be used.

Never paste OAuth tokens into forms, screenshots, repositories or messages. A dashboard screenshot may contain client data even without a password.

API keys and tokens

Use one WordPress API key per site and one browser token per connection or device where possible. Store credentials only in the location intended by each integration.

Immediately revoke an exposed credential, delete its copy and generate a new one. Rotating one key does not close access through another credential.

Data and human review

Serplenty processes data to generate dashboards, audits, recommendations, content and reports. The user remains responsible for reviewing results and deciding what reaches the site.

Avoid sending personal or confidential information in AI instructions when it is not needed for the task.

NeuralFuel and limits

Check the balance before intensive operations and avoid launching duplicate generations. Limits protect service stability and may vary by plan.

If the interface says NeuralFuel is insufficient, save the work, review usage and continue when balance is available.

Safe support checklist

Before opening an issue, prepare the URL, project, date, steps and error message. Always remove secrets and third-party data.

• API keys and tokens.
• Cookies and session headers.
• Client emails or identifiers.
• Screenshots with private metrics.
• Environment variables or repository secrets.