Compliance-friendly practices
FileAgent's self-hosted model and controls help you meet your own data-handling requirements. Here's how to use them — and what FileAgent does and doesn't claim.
Last updated September 17, 2026
#What helps with compliance goals
FileAgent's design supports common data-handling requirements:
- Data residency and control — self-hosted, so files stay in your environment, on storage you control.
- Encryption at rest for credentials and configuration on the host.
- Access control — per-user accounts on every plan; job-scoped access, SSO/LDAP, IP allowlisting, and advanced session controls on Business and Enterprise.
- An operational audit trail of every run, retained for 7 days on Free, 90 days on Pro, 365 days on Business, and agreed retention on Enterprise.
- Least-privilege credentials and console access.
#An honest scope
FileAgent provides controls that support your compliance program; it does not, by itself, make a deployment compliant with any specific framework. Your obligations depend on how you configure, host, and operate it — including the security of the host, your storage systems, and your processes.
#A practical checklist
- Use your own trusted HTTPS certificate and restrict console access to admin networks.
- Sign in via SSO/LDAP where available so directory policy governs access.
- Apply least privilege to storage accounts and FileAgent roles.
- Set log retention to match your record-keeping needs.
- Place archives and the host on storage that meets the same controls as the source data.
- Back up configuration and protected material securely, and review users, credentials, and jobs periodically.
#Specific framework questions
If you have specific regulatory or contractual requirements, talk to us before you rely on a configuration: contact sales or email support@fileagent.app.