Sundown · pay.acecleaningco.us
Security
Effective November 20, 2026 · A.C.E. Cleaning Co., Michigan
How Sundown protects the pay, payroll, client and bank information it holds. This is A.C.E. Cleaning Co.'s information-security policy for Sundown: what's built into the system, and what we do around it.
Who's responsible
The owner of A.C.E. Cleaning Co. is responsible for Sundown's security: who has access, reviewing it, and responding to anything that goes wrong.
Access
- Sundown isn't open to the public. Only people an owner invites can sign in, each with their own account.
- Every sign-in needs a password (12 characters or more) and a code from an authenticator app (multi-factor authentication). Repeated wrong tries lock sign-in for a time. Sessions end after 14 days; changing a password ends every other session.
- Least privilege: owner, bookkeeper, or accountant (read only). Only an owner adds or removes people. Access is reviewed whenever someone's work with us changes, and at least every three months.
- Every sign-in, failed sign-in, payment, change, download and bank connection is logged with who and when.
Encryption
- In transit: TLS 1.3 with 256-bit AES (AES-256-GCM) for every connection, with a certificate from a public authority. Sundown's pages also carry strict browser protections (Content Security Policy, frame and form restrictions).
- At rest: the database is encrypted with 256-bit AES (SQLCipher 4: AES-256 with an HMAC-SHA512 check on every page). The key is a random 256-bit key kept only in the server's private settings file, outside the code and never in any release or code repository, with a copy held by the owner offline. Nightly backups and the off-server copy are encrypted with it.
- Bank connections: the bank sign-in goes to Plaid, never Sundown. Plaid's access tokens are kept only in the encrypted database, never displayed, and deleted when a connection is removed.
Data
- Sundown collects only what the books and payroll need. It doesn't store Social Security numbers or bank sign-ins.
- Records are kept as long as tax and accounting rules require (generally 7 years), then deleted. See the Privacy Policy.
- Backups: nightly, encrypted, the newest 30 kept on the server, and an encrypted copy off the server each night.
Building and changing Sundown
- Every change is tested before it goes live (automated tests of sign-in, permissions, form protection, and that the books always balance), and the live system is backed up before each change so it can be rolled back.
- Forms carry anti-forgery tokens; pages never run scripts from other sites except Plaid's own connection window, on the one page that opens it.
- Software it depends on is kept current with each release; the hosting provider keeps the server's operating system patched.
If something goes wrong
- Contain it: end sessions (sign everyone out), remove access, disconnect bank connections, and change the keys involved.
- Find out what happened from the logs and backups, and fix the cause.
- Tell the people affected, and Plaid and the bank where bank data is involved, without undue delay and as the law requires.
- Write down what happened and what changed so it doesn't happen again.
Reporting a problem
Found a security problem? Email info@acecleaning.us.