Company policy · Adopted November 18, 2026
FOS Information Security Policy
Company: The AGU Group, LLC ("the Company"), operator of FOS Owner: the founder, the Company's sole operator with production access Adopted: November 18, 2026 · Reviewed: at least once a year, and after any security incident
This policy sets security requirements for the hosted application and its supporting systems. This public site offers the demo and waitlist only. It does not open app accounts or link banks.
1. Purpose and scope
This policy covers every system that stores or can reach FOS users' personal or financial information:
• the hosted FOS application and its server and disk
• the source code repository
• the bank-data provider account (Plaid)
• the email provider (Resend)
• the encrypted backup storage
• the email accounts that can reset any of these
2. Data we protect
• Account details: email, password hash, sessions, two-step settings.
• Each user's ledger: accounts, transactions, balances, categories and notes.
• Bank-connection tokens from Plaid.
• Support messages and operator records.
FOS is read-only toward banks. It never moves money, and it never sends user data to an advertising, analytics or AI service.
3. Access control
1. Only the founder has production access. Any new person gets access only after this policy is updated to name their role, and gets only what that role needs.
2. Two-step sign-in is required on every account in section 1: hosting, code repository, Plaid Dashboard, email provider, backup storage, and the email accounts behind them.
3. Production secrets (the server encryption key, Plaid keys, the email key and backup keys) live only in the hosting provider's encrypted environment settings. They are never put in source code, chat, email or documents. The repository runs an automatic secret scan before every commit.
4. Inside the app:
• Passwords are stored only as scrypt hashes, with a 12-character minimum and lockout after repeated failures.
• Sessions and email codes are stored only as hashes. Sessions expire after 30 days.
• Users can turn on two-step codes.
• Each user's records are in a separate ledger file, and every request is bound to the signed-in user's own file.
5. When a person leaves or a device is lost, their access and keys are revoked the same day, and any secret they could see is replaced.
4. Encryption
• In transit: every connection uses TLS, served by the host. Calls to Plaid, the email provider and backup storage are HTTPS only. The sign-in cookie is Secure and HttpOnly.
• At rest:
• Plaid access tokens are encrypted with the server key and bound to their user.
• Backups are encrypted with AES-256-GCM on our server before upload. Backup storage never holds the key.
• Ledger files on the host's disk rely on the host's disk encryption.
5. Secure development and vulnerability management
1. Every change goes through a pull request and is merged only by the founder.
2. Before merge, the local checks run: lint, type checks, the full automated test suite (including tests that try to read one user's data as another user), a secret scan, and a dependency vulnerability scan.
3. Dependencies are pinned. Known vulnerabilities rated high or critical are fixed or mitigated before release, and within 30 days for a live system.
4. Test data is synthetic. Real users' data is never copied into development, tests, screenshots or demos.
6. Logging and monitoring
• The server logs requests without passwords, codes, tokens or financial figures.
• Operator alerts flag failures (sign-in abuse, errors, backup or bank-connection problems) on the operator page and by email.
• Logs, alerts and security records are kept only as long as the retention schedule in the Privacy Notice says, then deleted automatically.
7. Data retention and deletion
Data is kept and deleted as the Privacy Notice states.
A user can delete their account in the app. FOS first asks Plaid to remove every bank connection, then deletes the user's ledger, account, sessions, invitations, usage records and feedback.
• Cleanup jobs run every hour.
• Encrypted backups are deleted after about 30 days, and a deleted account is never restored from a backup.
8. Backups and recovery
• Nightly encrypted backups go off the server once backup storage is configured.
• A restore is tested before launch and after any change to the backup process.
• Recovery goal: service back within one business day, losing at most one day of data.
9. Vendors
The only outside companies that receive user data are:
• the host (Render)
• the email provider (Resend)
• the bank-data provider (Plaid)
• the backup storage provider
Before adding a vendor, the founder checks its security and privacy terms and updates the Privacy Notice. Vendors are reviewed once a year.
10. Incident response
1. Contain: revoke or rotate affected keys, sessions and tokens. Take the affected part offline if needed.
2. Assess: find what happened, which users and data were affected, and when.
3. Notify: affected users, Plaid (as Plaid's terms require), and regulators, as the law requires and within the time it sets.
4. Fix and learn: correct the cause, add a test or check that would catch it, and record what happened and what changed.
Users and researchers can report a security problem to the support email in the Privacy Notice.
11. Exceptions
Any exception to this policy is written down with its reason, its risk and an end date, and is approved by the founder.
Adopted by: Charles “C” Anderson, Founder/Managing Member, The AGU Group, LLC · Date: November 18, 2026