Security

Built for financial records

Close data includes balances, invoices and tax positions. Here is how CloseDesk looks after it.

Your data is kept apart

Every record belongs to one company in one account. Each request is checked against the account you belong to, so no one sees another customer’s companies, tasks, invoices or files.

Sign-offs are checked on the server

Who may prepare, review and approve comes from your Roles. The server checks every step, so a sign-off can’t be forged from the browser, and a preparer can’t approve their own task.

Signed-off work is locked

Once approved, a task’s fields and attachments can’t change until an approver or admin reopens it. The reopening is logged too.

Passwords are never stored

Passwords are kept only as one-way hashes with PHP’s standard password hashing. Sign-in uses a secure, HTTP-only session cookie.

Files are private

Attachments are stored outside the public website under random names, and are only served to signed-in people of the same account.

Admins and staff

Only admins can change settings, people, companies and the plan. Staff do the close work.

Every step is logged

Starts, reviews, approvals, send-backs, reopenings and attachments are written to each task’s log with the person who did them.

Encrypted in transit

CloseDesk is served over HTTPS, so data between your browser and the server is encrypted.

Questions about security? Contact us.