gdpr

• Missing information on how to create other databases
• Missing information on how to switch to other databases
• When using time travel, we don’t know where to get the transaction number from - we should show this to the user after committing data (this may be a missing capability in immudb / tools).
• The last long query example in the quick start is incorrect (incorrect

In the existing sample for batch analysis, the logic goes over all the columns and looks for PII. We'd like to extend this with logic which also evaluates how likely a column contains PII based on its name.

For example, if a column name is Age, and the values are [19,55,2,39], the column name coul

The problem

Some embed scripts use data- attributes which clash with those used by klaro! - for example, one embed script I have come across has a data-type='inline' attribute, which breaks the script when it is changed to type='inline'.

Proposed solution