[kinottohw]

Yes you can test with real docs. they get processed locally, nothing gets saved on our servers, just the scan results which are encrypted. We’ve been testing ourselves by connecting our own Dropbox/Google accounts using fake docs that simulate GDPR issues

[hobofan]

The do you mean? Your demo video clearly shows the document contents in the dashboard. The document contents from all I could see would be processed by a cloud LLM.

Everything I see reads like you have a strange understanding of "local" and shouldn't be trusted with building such software.

[kinottohw]

Yes the document content is visible in the dashboard when you’re logged in, but it’s fetched at runtime from whichever integration you’re using (Dropbox, Google, etc.) and never stored on our servers. The cloud LLM just processes the document on the fly to spot potential issues. And the data you see in the demo is all fake.

[pavel_lishin]

> The cloud LLM just processes the document on the fly

That... doesn't sound local, dude. "Locally" would mean that the LLM is actively running in my browser, and in my browser only, which is not what you're describing.

I understand that you're claiming that the documents aren't being stored permanently, but they're still being transferred to your servers, and their full contents are being read there by something.

[kinottohw]

Yeah, you’re both right, it’s not “local” in the strict sense like running everything including the LLM in your browser. What I meant is that the docs are fetched at runtime and never stored on our servers. I’m totally open to ideas on how to make the setup better, even if it means tweaking the business model a bit.

[hobofan]

So the data isn't processed locally.