Confidentiality & Internal Conduct Policy
RBEW protects unreleased projects, private communications, credentials, personal information, and operational secrets without using confidentiality to silence lawful reporting or good-faith criticism.
Confidentiality & Internal Conduct Policy
Creative collaboration requires both trust and room to speak honestly.
This policy protects information that is genuinely private or operationally sensitive. It is not a blanket gag order.
1. Confidential information
Confidential information may include:
- unreleased creative work not authorized for public release;
- private drafts, scripts, masters, recordings, source files, and production assets;
- non-public business strategy and negotiations;
- private communications;
- customer or contributor personal information;
- unpublished financial, payout, contract, or transaction information;
- passwords, API keys, tokens, private links, security configuration, or infrastructure details;
- internal incident, moderation, or investigation material;
- information specifically covered by a lawful confidentiality agreement.
2. What you may discuss
Unless a separate lawful agreement says otherwise, this policy does not prohibit a person from describing their own experience or opinions, criticizing RBEW in good faith, discussing lawfully public information, seeking confidential professional advice, reporting suspected illegal conduct or safety concerns through appropriate channels, or complying with lawful process.
3. Disclosure boundary
You may not disclose confidential information to people who do not have a legitimate reason or authorization to receive it.
Permission to discuss a concern with a trusted adviser does not authorize public posting, mass redistribution, commercial exploitation, or creation of derivative material from someone else's confidential work.
4. Credentials and security — absolute hard line
You may not publicly share or knowingly expose passwords, private keys, API secrets, authentication tokens, privileged session data, private administrative credentials, or other secrets that would reasonably enable unauthorized access.
If a credential is accidentally exposed, report it promptly so it can be rotated.
5. Personal data — hard line
You may not leak another person's private personal data, legal documents, payment information, private address, private contact information, or sensitive account information without a legitimate authorized reason.
6. Negligence versus malice
An accidental disclosure and an intentional leak are not treated as identical.
Careless disclosure may result in correction, retraining, access changes, or other proportionate action.
Intentional leaking, selling confidential material, blackmail, deliberate credential exposure, or sabotage may justify immediate removal and stronger remedies.
7. Whistleblowing and safety
This policy may not be used to conceal unlawful conduct, prevent a person from making a legally protected report, obstruct an investigation, or retaliate against a good-faith safety or legal complaint.
Where possible, sensitive reports should minimize unnecessary exposure of unrelated private information.
8. End of relationship
Leaving a project or RBEW does not automatically make previously confidential information public.
Confidentiality does not transfer ownership of a creator's own work to RBEW. Ownership and licensing remain governed by the applicable creator agreement and Copyright & Ownership Policy.