←back to thread

36 points percyding99 | 1 comments | | HN request time: 0.317s | source

We’ve built an AI risk assessment tool designed specifically for GenAI/LLM applications. It's still early, but we’d love your feedback. Here’s what it does:

1. it performs comprehensive AI risk assessments by analyzing your codebase against different AI regulation/framework or even internal policies. It identifies potential issues and suggests fixes directly through one click PRs.

2. the first framework the platform supports is OWASP Top 10 for LLM Applications 2025, upcoming framework will be ISO 42001 as well as custom policy documents.

3. we're a small, early stage team, so the free tier offers 5 assessments per user. If you need more, just reach out, happy to help.

4. sign in via github is required. We request read access to scan code and write access to open PRs for fix suggestions.

5. we are looking for design partners to collaborate with us. If you are looking to build compliance-by-design AI products, we'd love to chat.

product url: https://www.gettavo.com/app

we'd really appreciate feedback on:

- what you like

- what you don't like

- what do you want to see for the next major feature

- bugs

- any other feedback

feel free to comment here or reach out directly: email: percyding@gettavo.com, linkedin: https://www.linkedin.com/in/percy-ding-a43861193/

Show context
Cynddl ◴[] No.44003738[source]
I see on the landing page a screenshot with "Test for GDPR PII compliance", suggesting that this tool is probably not ready for any serious usage.

Anyone in the regulation landscape would know that GDPR is a EU data protection law, and PII a US concept which doesn't apply in the GDPR. The GDPR uses the concept of ‘personal data’, not ‘personally identifiable information’. This is not just a wording issue. Redacting, masking, removing information which appears to be ‘personally identifiable’ only constitutes pseudonymisation in the GDPR which does not offer any meaningful privacy protection.

replies(1): >>44003951 #
1. percyding99 ◴[] No.44003951[source]
Thanks for the feedback! We agree that this tool is definitely not ready for serious usage at this stage, it would require heavy tuning and testing before wide adoption

also thanks for flagging the GDPR issue!