PrivacySpΞc | GDPR & Data Protection

Well done! Would it be an option to move the 'tab panel' to the top in mobile or for views where it does not fit to the side?

Awesome tools! What if you utilize /statecharts x pele.run (by @kepano) to a) explain your privacy policy to end-customer customer (well, actually to customer's 'AI' assistant) b) validate code with /statechart skill in pstack by @poteto to identify where privacy rules or engineering principles might break

well this escalated quickly.. was already happening

To visualize the appraoch>

One common thing we noticed among the service provider layer of AI is that there's not much to troubleshoot on in case of errors. To consider when outsourcing (time) critical tasks.

Diagrams in Privacy Policy: can recommend.

Covering critical processes has decent ROI for most companies regarding GDPR compliance. Graph made with Pele by @kepano

Well done and keep up the good work! Have been using Obsidian as work area for compliance documents, overviews etc. Pele is🔥, will demonstrate it during trainings as well.

Imaging the handover happened like this:

perhaps time to change the title and remove reference to products with lower quality😉

A note regarding UI> The comment 'bubble' on smaller element (like link or short text) covers it, making it difficult to see what's under there. But adding the comment to nearby or to parent element removes the pinpoint element from the comment meta. (i.e when copying comments for AI input). Just to keep in mind depending on the use case. Live collaboration, not a problem. Need copy/paste comments to AI - perhaps needs more details in the comment, i.e the 'ahref' in this <p>. But don't have enough experience how much is actually impacts AI output, usually there's more context :) Will test the html collab in a training session as well (~20 same time collaborators)

🔏 Data Collection & Disclosure Rules and more ℹ️ GDPR requirements

Reminder. Save, print, share.

When using Claude knowledge work legal plugin for data protection agreements, add few things to the default 'requirements': Controller-processor relationship distinguished in verbatim, personal data or categories of personal data described, reference to detailed security measures. 💡For more advanced use cases, set levels of expected/planned security (1-3) and link it with relevant security measures. Core distinguishing element is data and systems used. IF other side gets data from your 'secure' CRM, same level should be expected from the recipient. Yet if the 'personal data' regaring the service is only about employee names and emails or similar low risk, then referencing to MFA, backups and pentesting might be too much..