Trust through controls
Security is a set of controls and habits, not a slogan. FB Rights Manager uses hashed passwords, httpOnly session cookies, role-based pages, input validation, and audit logging.
Account isolation
Each client workspace is isolated. You should not see another customer's evidence. Admin tools are separate.
OAuth and secrets
Access tokens for official connections are stored server-side when that feature is configured. Clients never need to paste passwords into tickets.
Evidence sensitivity
Treat vault files as confidential. Redact. Limit staff. Follow deletion requests under the Privacy Policy.
Transport and hosting
Production sites should be served over HTTPS. Hosting and processors act as subprocessors as described in the Privacy Policy.
Incident response
If you suspect compromise, reset the password, review login history, and email support@fbrights.com. Do not send one-time codes in chat.
Limitations
No system is invulnerable. Clients remain responsible for device hygiene and unique credentials.
Meta and payment secrets
We do not ask you to store card numbers on application servers. Processors handle cards when billing is live.
Practical checklist
Unique password, logout on shared devices, limited admins, no credential reuse from social platforms.
FAQ
Do you publish a bug bounty? Report security issues to support@fbrights.com with enough detail to reproduce without exploiting third parties.
Get started
Continue in the dashboard after login or registration. If you are not signed in, use the free trial registration flow and return to the related module. Email support@fbrights.com, ip@fbrights.com for intellectual property packets, or WhatsApp +1 209 659 8799.
Client responsibilities
Use unique passwords, protect devices, and report suspected compromise promptly. Do not share session cookies or one-time codes in chat.
Data minimization
Upload only evidence required for the matter. Redact unrelated personal data from screenshots when possible.
Subprocessors
Hosting and payment processors act as subprocessors as described in the Privacy Policy. Card data is handled by processors when billing is live.
Defense in depth for a SaaS workspace
Hashed passwords, httpOnly cookies, role checks, audit logs, and tenant isolation form the baseline. Clients add unique credentials and careful uploads. Admins use separate privileged access patterns. Secrets stay server-side. Production should disable public source maps and debug traces.
Incident reporting path
If you suspect account compromise, reset your password, review login history in Settings when available, and email support@fbrights.com with subject Security Report. Do not send passwords or one-time codes through WhatsApp.
Defense in depth for a SaaS workspace
Hashed passwords, httpOnly cookies, role checks, audit logs, and tenant isolation form the baseline. Clients add unique credentials and careful uploads. Admins use separate privileged access patterns. Secrets stay server-side. Production should disable public source maps and debug traces.
Incident reporting path
If you suspect account compromise, reset your password, review login history in Settings when available, and email support@fbrights.com with subject Security Report. Do not send passwords or one-time codes through WhatsApp.
Defense in depth for a SaaS workspace
Hashed passwords, httpOnly cookies, role checks, audit logs, and tenant isolation form the baseline. Clients add unique credentials and careful uploads. Admins use separate privileged access patterns. Secrets stay server-side. Production should disable public source maps and debug traces.
Incident reporting path
If you suspect account compromise, reset your password, review login history in Settings when available, and email support@fbrights.com with subject Security Report. Do not send passwords or one-time codes through WhatsApp.
Defense in depth for a SaaS workspace
Hashed passwords, httpOnly cookies, role checks, audit logs, and tenant isolation form the baseline. Clients add unique credentials and careful uploads. Admins use separate privileged access patterns. Secrets stay server-side. Production should disable public source maps and debug traces.
Incident reporting path
If you suspect account compromise, reset your password, review login history in Settings when available, and email support@fbrights.com with subject Security Report. Do not send passwords or one-time codes through WhatsApp.

