• Currently all of the GDPR information seems to be saved to the WordPress _options & _usermeta tables.

    An an enhancement, please consider splitting the data out to various tables to improve system optimisation and provide an improved means of data segregation which is often very important when it comes to privacy related matters.

    Having separate tabled for GDPR functionality means that such data is not mixed in with other data. It ensures that such information can be replicated or backedup separately which is not possible when the data is mixed in with other tables.

    Some suggestions:
    _GDPR_options for storing all the GDPR options from settings page.
    _GDPR_audit for storing changes to the privacy policies and other required consents.
    _GDPR_users for storing the users consents, cookie acceptance etc

Viewing 1 replies (of 1 total)
  • Plugin Author Fernando Claussen

    (@fclaussen)

    I wanted to build it up like that but there’s a problem.

    We are trying to get this plugin VIP approved. And custom tables is not permitted.

    That’s the same reason why I do not use direct database queries which would be way more performant in some occasions.

    I’ll get the sql queries in place to make it more performant because I can use them, but shouldn’t if possible.

    But getting custom database tables, as much as I want to, I can’t at the moment.

    Unless during the plugin review they tell me that I can do it on VIP GO, which I doubt it.

Viewing 1 replies (of 1 total)
  • The topic ‘Enhancement – create _GDPR table’ is closed to new replies.