SecureIntent

Stop credentials from reaching AI. Protect every prompt.

Software Engineering

Developer Tools

GitHub

Security

Visit WebsiteSee on Product HuntFacebook ⧉Instagram ⧉Github ⧉Twitter ⧉

How does the zero retention actually work in practice, like does the extension analyze data locally on my machine or is it sending anything to a server for processing?

The zero-retention angle is genuinely interesting, especially for devs worried about pasting secrets into random fields. Liked how it flags without blocking you mid-workflow.

How does the extension actually scan for sensitive credentials if nothing is stored, does all the pattern matching happen locally in the browser?

the zero-retention angle is the right call for something sitting between devs and their prompts, nobody wants a security tool that becomes its own data risk. curious how the detection itself works though - is it pattern/regex matching against known credential formats (API key shapes, AWS keys, etc.), or entropy-based scanning for anything that looks like a secret regardless of format? asking because the failure modes are pretty different: regex misses novel/custom token formats, entropy-based flags a lot of harmless high-entropy strings (hashes, IDs) as false positives. which side did you optimize for?

Nice angle on staying out of the way. One thing that would help my team is adding a lightweight Slack or webhook alert when the extension blocks something, so devs get a heads up in the channel they already live in instead of only finding out after the fact.

love that you went zero retention from the start instead of bolting it on later, that is exactly the kind of choice that shows the team actually understands enterprise security rather than just selling it.

Handy having a DLP-style check that flags risky intent without actually hoarding the data on a server, the zero-retention angle is what sold me on installing it.