BOTLOBBIES.ORG
Privacy and support

Can I share a raw bot log or account screenshot publicly?

Do not assume a raw log, configuration export, or account screenshot is safe to publish. Share a focused description or carefully cropped error instead, and remove credentials, temporary codes, private links, personal identifiers, and payment details before sending diagnostic material.

Look beyond the error you intended to show

A screenshot taken to show a harmless state label may also contain an Epic authorization code, a private return address, an email, a player name, or another open account panel. A raw diagnostic file can include information unrelated to the fault. Inspect the whole material before sharing rather than cropping only after it has been posted. State the action, approximate time, and exact visible warning first; those facts often identify the missing checkpoint without exposing the account material used to authenticate or connect.

Do not treat filtering as a universal guarantee

The project filters sensitive fields from supported bot representations and uses fixed or sanitized messages in some error paths. That does not prove that every raw operational log, external message, or file has undergone the same filtering. A field named secret is not the only place sensitive information can appear; a private link or a copied provider response can also matter. Avoid publishing complete exports just because one API view hid a password. Keep any requested diagnostic exchange limited to the relevant operation and legitimate recipient.

Prepare a minimal useful report

Describe whether linking, connection, invitation, saving, or live application failed, and include the message after removing personal details. For a payment issue, do not include a complete card number or security code. For account linking, do not include the current authorization code or full verification address. If support needs an additional piece of evidence, clarify the specific field or crop required rather than sending everything. A careful report protects unrelated account information and gives the investigator a clearer sequence than a large unreviewed diagnostic dump.