Audit logs in : When every single piece of information matters

Managing vast amounts of personal data has become “the new normal”, many would think. Wrong! Regulations race to implement adequate measures to protect personal data. Proving compliance is an increasingly pressing topic for any IT development team of a mobile (app) solution, based on personal data aggregation. Privacy-compliance is the new normal. Developing an effective privacy-preserving data management solution is imperative. 

In this article, we will show you the power of using data-audit to de-risk your compliance. 

So what are audit logs?

Audit logs maintain a full and complete history of every change that has been made on a piece of data, by whom and when. An audit log is the simplest, yet also one of the most effective forms of tracking temporal information. Any time something significant happens, a record indicating what happened and when it happened, is generated.

What do data audits look like? 

It can take many physical forms, but the most common form is a file. It must contain all relevant information concerning the sequence of activities that affected at any time a specific operation, procedure, or event in an IT system. In addition to documenting what resources were accessed, audit log entries usually include destination and source addresses, a timestamp and user login information.

Why do you need to use data-audits? 

Stringent data protection regulations become a major concern to organizations. Bolstering your data management capabilities to meet compliance is a priority and business-critical.

Beyond being a good practice, using data-audits will not only allow you to keep logs of any data interactions but also to “demonstrate compliance”, which is a key point of the GDPR.

Furthermore, audit logs have taken on new importance for cybersecurity and are often the basis for diagnostic performance, error correction and security analysis.

De-risk your compliance with data-audit at

Audit logs keep track of details about the actions performed by your app users against accounts through the API. 

In other words, it describes the source (the identifier for the action that generated this log), the type of log, the time when it was executed, the audited action (typically the API method call), the identifier for the access used to perform the audited action, and the HTTP response status resulting from the audited action.

Here is an example of a single audit log in : 

Audit logs Pryv

You can see that the IP address “” was used to get the events from the stream “Diary” at the time 1261988300 seconds, and that the attempt was unsuccessful as the used access has expired, all of this at one glance.

Audit logging is an essential ingredient for your infrastructure. By using the capabilities of log management system, you are a step closer in succeeding your compliance auditing. 

To learn more about how audit logging in can help you, check out our API reference for it. 

Address existing and forthcoming data protection requirements and future-proof your regulatory compliance with