CapeChat automatically encrypts your documents and redacts any sensitive data. It’s powered by the ChatGPT API, so you get the best language model while preserving your privacy.
No StressThis was one of the biggest doubts about generative AI. Great to see it's being addressed!
Report
CapeChatMaker
@devdalgic thanks! Please let us know what you think of the product.
Report
CapeChatMaker
@devdalgic Appreciate the support!
Report
CapeChatMaker
@devdalgic thank you!
Report
CapeChatMaker
Thank you for your comment @devdalgic!
Report
Transform messy documents into structured data sounds like a dream come true for anyone dealing with piles of paperwork. You've solved an actual pain problem! You guys are the best!
Report
CapeChatMaker
@ian_johnson7 Spot on!! This is a use case we’re seeing that is saving a lot of time for users! Thank you!!
Report
HYCU for Jira SoftwareThis is a great use case!
Report
CapeChatMaker
@andyfern1123 Thank you!
Report
CapeChatMaker
@andyfern1123 Thank you!!
Report
CapeChatMaker
@andyfern1123 thanks for your feedback!
Report
CapeChatMaker
@andyfern1123 appreciate it! And we'd welcome any feedback you might have too.
Report
MoneyVisionCongrats on the launch!
To be honest, I don't really understand it:
The data has to be decrypted on your servers before sending it to Open AI, right? So I do not really understand the benefit of encrypting it, instead of sending it directly to Open AI.
Report
CapeChatMaker
@timobechtel Great question. There are many components involved like embeddings, vector storage, and vector search that happen before any communication with OpenAI. Any prompts are additionally de-identified of PII, PHI, PCI before being processed by the ChatGPT API.
Report
ZedMaker
@timobechtel The main component that protects the data while it's being prepared for the OpenAI API is that we don't decrypt the data on normal servers, but instead inside of an AWS Nitro Enclave. AWS Nitro Enclaves are designed in such a way that even we, the operators, cannot view the data that's passing through them, which is guaranteed through a process called remote attestation. Here is an old blog post our team wrote before we developed CapeChat that goes into more detail about the security of enclaves: https://capeprivacy.com/blog/how...
Report
MoneyVision@jvmncs Oh I see. So the main benefit is that documents are processed (at all) before they are sent to Open AI, and this is done in a secure cloud environment. While being end to end encrypted. (Zero Trust).
So the only thing that is sent to Open AI is a prompt without personal information.
Did I get this right? That's very interesting!
I've just got confused a bit with the encryption part in combination with ChatGPT. I think I have totally misunderstood the product 😅
Thanks for your answer!
Report
ZedMaker
@timobechtel Yes exactly! Our service accomplishes two separate security goals: (1) prevent Cape or AWS from being able to spy on the data while it's being processed by using AWS Nitro Enclaves, and (2) prevent OpenAI from learning about PII/PCI in documents and prompts by using redaction/de-identification.
GPT (especially GPT-4) is smart enough to reason about redacted data by using placeholders and contextual information, so you can still make it do a ton of useful things without it being able to infer what the sensitive terms are.
Report
MoneyVision@jvmncs That makes perfect sense!
Report
Damn, I was struggling with this at my workplace. Thank you for making it. Is it open sourced?
Report
CapeChatMaker
@abhishek_sharma55 Thank you for trying it! It’s self-serve and free to use. We plan to open source parts of it. We also have an API so you can build your own integrations. Please share any feedback!
Report
Does this encrypt before using chatgpt? Or even though we get the data back encrypted it shares with OpenAI?
Report
CapeChatMaker
@nuno_ms_reis Great question! The documents are indexed and searched prior to any communication with OpenAI. This happens with a confidential vector store and embeddings model running in a Nitro Enclave. Once the prompt is constructed it is de-identified of PII, PCI, and PHI before being processed by the ChatGPT API. Then we re-identify client side so only the end user can see the final result!
Report
CapeChatMaker
Hi @nuno_ms_reis, before anything is sent to OpenAI it first needs to be preprocessed (embeddings, vector search, redaction, etc). We do all of this in a way that keeps it from being viewed by anyone (including us!) using AWS Nitro Enclaves. And anything that we need to store will be client-side encrypted within the enclave first. Then, what is actually sent to OpenAI will be de-identified of PII, PHI, and PCI. Hope this helps!
Report
@miiklay Sounds great then, thank you both for the quick replies!
Report
CapeChatMaker
Thank you for your interest and questions @nuno_ms_reis !
Report
As a user researcher, I think this could be really useful and helpful in my field. UX research participants' PII is a big concern, for example. Excited to see more.
Report
CapeChatMaker
@orly_reine_sibony Thank you for the support! Would love to hear your feedback as you try it out!
Report
CapeChatMaker
Thanks for your support @orly_reine_sibony! We are glad you think CapeChat could benefit the UX research field.
Report
CapeChatMaker
@orly_reine_sibony awesome to hear. Thank you! 🙏
Report
CapeChatMaker
Great feedback @orly_reine_sibony! And appreciate the support!
Report
CapeChatMaker
@orly_reine_sibony we're happy that CapeChat is interesting to you. Thank you for your comment.
Report
First
Previous
•••
3456Next