Data Security At Microkeeper

Microkeeper Network and Infrastructure Design

the microkeeper network

Encryption - Data In Transit

All data sent to and from Microkeeper servers is done via a 256-bit SSL encrypted connection, this can be verified within browser near the URL.

Encryption - Data At Rest

Some values are encrypted at rest and some values are not, for example, TFN is encrypted.

Microkeeper does not encrypt all fields, this is because it can hinder database performance and slow down search queries.

Which fields Microkeeper encrypts and which ones Microkeeper does not encrypt is proprietary and will not be disclosed.

Data Sent To Third Parties

Microkeeper integrates with many third-party software providers, these providers have access to different levels of data depending on what is required to achieve the desired outcome.

These providers do not have access by default, the accounts administration must trigger an action to these providers for the data to be forwarded.

Here is a list of third-party software providers and the data they have access to:

Software ProviderAccess LevelReasonData Access
SuperChoiceHighProcess SuperName, DOB, TFN, Mobile, Superfund, Member number, Super contribution values
ATOVery HighSubmit Single Touch PayrollAlmost all fields
LowSend SMSName, Mobile
AppleLowSend Push NotificationsApp device token
Google AppsLowSend Push NotificationsApp device token
NAB Merchant facilityMediumMake Credit Card PaymentsCredit Card Details, Username
XeroMediumSend Invoice for PayrollAccounts, Cost of wages, PAYG values, Super values
NoahFaceMediumClock hours via facial recognitionEmployee user list: Name, email
Hubspot / FreshdeskLowSales and support CRM and ticketsEmail, mobile number, ticket/email content, contact name
vSureMediumVEVO ChecksPassport number, name and country

Microkeeper Fingerprint Data Retention

An image of the fingerprint is not stored. The fingerprint is converted to a binary string.

Below is my fingerprint and how it looks as a binary string:

123C2A062123C2A062E123C2A062E296B2912 3C123C2A062E296B2123C2A062E296B299123C2A062E296
B292A062E296B292123C2A062E296B2996B29 123C2A062E2123C2A062E296B2996B29E2123C123C2A062
E296B292A123C2A062E296B29123C2A062E29 6123C2A062E296B29B29062E296B2962E296B2962E96B29

This string can not be converted back into a fingerprint and is only useful to the Microkeeper fingerprint interpreter.

ISO 27001:2013 compliant

Microkeeper ISO 27001 Certificate

Microkeeper is ISO 27001:2013 which is globally recognized as the premier Information Security Management System (ISMS) standard.  

Compliance is a requirement of SBR and thus permitted to submit STP data which can be found on the Standard Business Reporting Product Register.

Verification of Microkeeper's ISO 27001 compliance can be found on the jas-anz website.

Best in Class Infrastructure

Microkeeper delivers best-in-class availability. Microkeeper uses multiple redundancy technologies for our servers, networks, databases, and data.

These ensure that if any component fails, Microkeeper will recover with little or no disruption to your service or loss of data.

SLA Guarantee

Microkeeper guarantees at least 99.9% availability of our cores services.

This does not include:

Server Hosting Environment

Microkeeper has co-location hosting across Sydney, Melbourne and Brisbane.

Microkeeper uses different server hosting environments for different parts of the system stack.

All hosts are in Australia and highly critiqued by the Microkeeper Engineering team.

All hosts have:

Our servers are in the Equinix data centre, Equinix are also ISO 27001 compliant.

DNS and Load Balancing

Microkeeper Load Balancing

Microkeeper uses CloudFlare for our DNS and Load Balancing, this allow for user requests to be shared across multiple physical location.

The CloudFlare status page can be reviewed to help debug connectivity issues.

In the event that one of the three physical data centres goes completely down, Microkeeper service will remain available.

Disaster Recovery

Microkeeper has internal Disaster Recovery policies and procedures.

This documentations covers events like:

Disaster Recovery documents are reviewed every 12 months or when a major release of Microkeeper is moved to production.

Cluster Database

Microkeeper uses a cluster database technology that synchronizes data between all servers in the cluster in real time.

If a database server goes down, the other servers will take over with almost no interruption to the user and no loss of data.

When the server that went down comes back up, it re-joins the cluster, receiving any changes to the database that it missed.


Firewall upkeep and maintenance is a joint responsibility of our server hosts and Microkeeper admin team.

Visit the Equinix website for more information about their data security policies.

One of the benefits of CloudFlare is they have DDOS protection built in and server anonymity, so server whereabouts is not known to the public.

Anti-Virus Policy

AV is not required for the hosting environment, this is because it's a locked-down environment, where new software vendors are only installed once they have been tested in a production environment.

In house all Support and Software Developer run Windows Defended, updates are fully automated.

Software Update Policy

Third-party vendors are updated as new releases, where possible automated updates are implemented.

Where automated updates are not possible, manual installation is conducted.

Manual updates typically take between a few days to a couple of weeks depending on risk profile and difficulty of implementation.

Data Retention Policy

Microkeeper has a "No Print Policy" thus no customer data is ever printed.

Data is kept for a minimum of 10 years in alignment with Australia Law.

If an account parts way, Microkeeper retains data.

Data is automatically deleted once it is 10 years old via built-in scripts.

Backup Policy

An automated backup is taken during quiet times on a daily basis.

An Annual backup is taken which is kept indefinitely.

9 backups are kept for 9 days

For example:

Password Policy

Microkeeper requires the following for a strong password:

Account lockout is for 5 minutes after 5 attempts at a password.

After a maximum of 50 attempts the account is permanently locked and can be unlocked by contacting admin.

When storing passwords in the database, they are hashed using sha256 and a proprietary double salting.

Microkeeper internal password policy is much stronger, passwords are randomly generated and we use password managers.

Audit Logs

There are many different audit logs

Activity Feed

Microkeeper has an Activity Feed that logs changes that are made within the Microkeeper software.

Account Access

Account access is logged this includes externally Linked Users and Microkeeper staff.

Production Server

Only Microkeeper directors have access to production servers.

Events are recorded when production servers are accessed.

Multi-Factor Authentication is setup on all production servers.

Audit logs are reviewed monthly for suspicious activity, alongside automatic email notifications when particular events are triggered.

Production server access log example:

Server access log example

Domain Segregation

Microkeeper uses cloud services for all internal file and data sharing tasks, this means all staff devices have internet only access, there is no file sharing setup on internal networks.

This means segregation is control at the application or session layer not the network layer.


The details in this document are a brief summary of more extensive internal documentation and are not legally binding.

For a more detailed explanation please review the Microkeeper Privacy Policy and Terms Of Use.

If you require further clarification on anything in this document please Contact Us.

Last Updated