Where to manage and report
Account and Safety Controls
Different problems need different control surfaces. This page helps users reach the right account, safety, support, or security path without oversharing private data.
Account and safety control map for Vibecodr users.
Implementation focus
Use this when deciding where to manage account state, report abuse, file a product bug, disclose a vulnerability, or remove account data.
Expected outcomes
- Find the right place for billing, storage, secrets, connections, and profile controls.
- Separate abuse reports, product bugs, and vulnerability disclosure.
- Report issues with useful details and without secrets.
- Understand how social controls differ from source and runtime visibility.
Know the right control surface
Account, billing, storage, profile, secrets, connections, reports, blocks, mutes, account deletion, bug reports, and vulnerability disclosure are different support paths. Keeping them distinct helps Vibecodr respond without asking users to overshare private data.
Use settings for account-owned configuration, project controls for source and release choices, safety/reporting flows for abuse or content issues, bug reports for product defects, and vulnerability disclosure for security findings.
- Use billing settings for plan and payment questions.
- Use storage settings for usage and cleanup.
- Use secrets and connections settings for trusted provider setup.
- Use bug report or vulnerability disclosure routes based on the kind of issue.
Report safely
A good report includes enough detail to reproduce the problem without exposing secrets. Include the route, project or post id, browser, signed-in state, expected behavior, actual behavior, and relevant `errorKey` or request id.
Do not include raw API keys, provider tokens, private `.env` files, credential-bearing URLs, or full private source bundles unless Vibecodr gives you a secure path for that specific support case.
- Use abuse reports for harmful content or social behavior.
- Use bug reports for product behavior that does not match the docs.
- Use vulnerability disclosure for security weaknesses.
- Use account deletion controls when the desired action is to remove the account itself.
Example and read next
Example: you found a product bug with a request id and a possible security concern. Send the product bug through bug report, send the security issue through vulnerability disclosure, and leave secrets out of both.
Use these related pages when you need the next layer of guidance. They point to the most likely follow-up tasks, not every page that happens to touch the same system.
- Read next: /support/bug-report
- Read next: /security
- Read next: /vulnerability-disclosure-policy
- Read next: Support Diagnostics