I wonder how often do privacy policies change, for the average site, to merit investing in a dedicated library that renders them dynamically. Assuming that the default solution is a static page.
I think most apps don't update often enough. We've seen products with privacy/cookie policies that are 5+ years old and totally out of sync with the product itself.
We're building OpenPolicy not necessarily to reduce the risk companies have of litigation, but instead to be more transparent with users and to build trust.
In the next version we'll be releasing auto-instrumentation that tracks data/third parties to always keep things in sync.
I wonder how often do privacy policies change, for the average site, to merit investing in a dedicated library that renders them dynamically. Assuming that the default solution is a static page.
I think most apps don't update often enough. We've seen products with privacy/cookie policies that are 5+ years old and totally out of sync with the product itself.
We're building OpenPolicy not necessarily to reduce the risk companies have of litigation, but instead to be more transparent with users and to build trust.
In the next version we'll be releasing auto-instrumentation that tracks data/third parties to always keep things in sync.
> We're building OpenPolicy not necessarily to reduce the risk companies have of litigation
Privacy policy is one thing, but that’s what terms of service are for!
Terms of service don't override laws so only a fool thinks that they have any effect on litigation.