How Does FoodBank Manager Protect Client Privacy?
FoodBank Manager (FBM) is designed with privacy protection at its core. From technical design to user permissions, every part of the platform is structured to safeguard the personal information of the guests you serve.
Private databases for each agency
Each partner agency operates in its own private database. No other agency can view or access your client data unless specific permissions are granted.
Depersonalized reporting to food banks
Food banks receive aggregate and depersonalized data through a secure data lake. Personally identifiable information (PII) is never exposed in regional reports.
Use of one-way hashing
FBM uses one-way hashes to create unique, non-reversible identifiers for guest records. This makes it possible to count unduplicated households across agencies without sharing names or contact info.
Strict user roles and permissions
Role-based access controls prevent unauthorized users from viewing sensitive records. Agencies and food banks can control who can view, edit, or report on guest information.
No shared client record system
Unlike some platforms, FBM does not use a shared guest record database. There is no universal guest ID — agencies manage their own records independently.
Secure communication and hosting
FBM is hosted on secure cloud infrastructure with encryption, access controls, and audit logging. All transmissions are secured via HTTPS.
Summary
Private databases keep client data isolated
Food banks see depersonalized summaries only
Guest records are hashed, not shared
Strict user roles limit access to sensitive data
Hosting and access meet modern security standards
Need help configuring your agency’s privacy settings?
[Submit a support ticket →]
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article