Security and privacy

• Each municipality's data kept apart

  Every record belongs to one municipality, and the database itself enforces it: work done for one municipality cannot read another's records, even if the application asks.

• Personal details encrypted

  Residents' phone numbers, names and email addresses are encrypted in the database and decrypted only to send a message. Staff sign-in secrets are encrypted the same way. Every connection uses HTTPS.

• Nothing published as-is

  A report is never made public. A moderator writes a separate public entry, the location is shown only as precisely as you choose, and a summary containing a phone number or email address is refused.

• Photos cleaned

  Every photo is re-encoded on the server, which removes the GPS position, device details and other hidden data. Published copies are separate files, with faces and plates blurred by your moderators.

• Strong sign-in for staff

  Every staff account needs a password and a code texted to the person's phone. Invitations are one-time links, and an administrator can disable an account at once.

• A record of every decision

  Assignments, status changes, publication decisions and exports are written to an audit log that cannot be edited.

• AI with limits

  Personal details are removed before text is sent to the AI provider, and its answers are checked before staff see them. Suggestions are always marked, nothing is applied without a person, and a municipality can turn AI off.

• Staff emails without personal data

  Emails to staff identify cases by reference number and category. A resident's name, number, address or words are never in them.

• Hosting

  The platform runs on Amazon Web Services, with the database backed up automatically every day.

Questions from your IT or legal team? Write to us at info@mscpayroll.com.