How do you guardrail your Claude use given effectively zero expectation of privacy?

Today I discovered Claude's conversation search tool returns substantive content from conversations I deleted months ago — well past the stated 30-day back-end deletion window. The TOS carve-outs for "policy enforcement" and "as required by law" appear to cover indefinite retention of everything.

The product is designed to get better the more context you give it — memory, personalization, chat history search. But the privacy guarantees behind that data are thinner than the UX implies. Deletion doesn't reliably delete. Incognito still loads your memory profile.

Not everyone here is using Claude strictly for code. I've been using it to optimize credit card churning strategy and plan award travel, which requires sharing real financial context to get useful output. Others are using it for proprietary work, personal decisions, research. The tool is most useful when it has real context, which is also the most exposed surface.

• Do you have rules about what you will and won't put into Claude?
• Has anyone architected their usage around the actual privacy model rather than the advertised one?
• How do you think about the trade-off between utility and exposure — especially for non-code use cases where the context is inherently personal?

ETA: To contextualize why I think this matters beyond my individual case studies find that 51% of LLM users say their primary use is personal learning and planning, versus 24% for work (work has its own privacy concerns as well, obviously). OpenAI's own research shows over 70% of ChatGPT messages are personal. A quarter of users say their LLM cheers them up. These tools are being used as life infrastructure by a majority of their users, and the privacy conversation hasn't caught up to that reality.