Fidei Ops Security
Company Security
Fidei Ops gives Catholic schools a clear monthly view of their finances, built from the accounting records they already keep. We protect that information with security controls at each layer of the Service, from hosting to the application itself.
Fidei Ops reads your school's books; it does not change them. The Service is built to refuse any request that would create, change, or delete anything in your accounting system, and we test that safeguard with every release.
We collect only the information the Service needs. Fidei Ops does not ask for student records, and enrollment and staffing are entered as counts, not as information about individuals.
Hosting and Data Storage
The Service runs on a professional cloud hosting provider, and your school's data is stored in the United States. Our provider maintains the physical security, network protection, and infrastructure of its data centers.
Encryption. Data Fidei Ops stores, including your accounting system connection and the information your school enters, is encrypted at rest, with encryption keys kept separate from the data. Connections between your browser and Fidei Ops are encrypted in transit using HTTPS.
Third-party content. Our website and the Service do not load advertising, analytics, or tracking scripts from other websites.
Access Controls
- Your school decides who sees what. Each person sees only the schools their administrator has given them access to, and every page checks that access.
- Secure sign-in. Passwords are stored only in hashed form. Sign-in attempts are limited, and sessions expire after a period of inactivity. Multi-factor sign-in is required for all accounts.
- Connecting your books. Your administrator connects QuickBooks through Intuit's own sign-in. We never see or store your QuickBooks password, and an administrator can disconnect at any time.
- Activity records. We keep security records of sign-ins and access to each school's information, so we can investigate and tell your school what happened if something goes wrong.
- Our own access. Access to systems that hold customer data is limited to authorized personnel, protected by multi-factor authentication, and used only to operate and support the Service.
Security Practices and Assessments
Every change to Fidei Ops runs through automated testing before release, and our software dependencies are checked for known vulnerabilities on every change. Customer data is never used to build or test the Service.
We have not yet completed an independent security audit. Schools that need security documentation for a vendor review can request it at security@fideiops.com.
Reporting a Security Concern
If you believe you have found a security issue, email security@fideiops.com. Please do not test the Service against another school's data. We will acknowledge your report within two business days.