Skip to content

Commit d65dda4

Browse files
Verbiage clarity edits for LLM chatbots use case
Co-authored-by: Arjun Hassard <arjunhassard@gmail.com>
1 parent d0846f8 commit d65dda4

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

docs/composedb/examples/taco-access-control.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ TACo’s encrypt/decrypt API – [taco-web](https://github.com/nucypher/taco-web
2121

2222
- **IoT event streams:** Let data flow from sensors to legitimate recipients, without trusting an intermediary server to handle the routing and harvest sensitive (meta)data. For example, a medical professional can be issued a temporary access token if the output data from a patient's wearable device rises above a certain threshold.
2323

24-
- **LLM chatbots:** Messages to and from a chatbot should be 100% private, not mined by a UX-providing intermediary. Harness Ceramic's web-scale transaction processing and TACo's per-message encryption granularity to provide a smooth and private experience for users of LLM interfaces.
24+
- **LLM chatbots:** Messages to and from a chatbot should be 100% private, not mined by a UX-providing intermediary. Harness Ceramic's web-scale transaction processing and TACo's per-message encryption/condition granularity to provide a smooth and safe experience for users of LLM interfaces.
2525

2626
## Example Application & Repo
2727

0 commit comments

Comments
 (0)