Sydney is Australia's centre for banking, payments and insurance, and software built for that world is judged on its security story before anyone looks at the interface.
Built for a security review
A financial product is reviewed by risk and security teams long before users see it. The build anticipates that: authentication and session handling done conservatively, an audit trail for sensitive actions, least-privilege access between services and secrets kept out of the app binary. Regulated firms carry their own obligations, for example APRA's information security standard CPS 234 for entities it supervises, and those stay with you. What the build supplies is documentation that makes your assessment faster. If a customer has already sent you a security questionnaire, see the vendor security review.
Money, identity and the Privacy Act
Financial apps hold identity documents, account details and transaction history. That is personal information under the Privacy Act 1988, so collection, storage, retention and disclosure are planned with GDPR principles in mind from the first table. Where data is hosted, and which sub-processors touch it, is decided and written down at the start so cross-border questions have an answer on paper.
The deal
- Fixed price and scope in writing before the first line of code
- Market-ready app for iPhone and Android from one codebase, with the audit and access design your review will ask about
- Invoiced in US dollars by DigitalFreedom Global LLC, Wyoming
- Full handover of code, cloud accounts and documentation
The wider picture: app developer for Australia. Also in Australia: Melbourne. To start a conversation: get in touch.