You just watched the full 23-minute folder architecture walkthrough. Vote below, then drop your use case in the comments. What are you building this system around?

As I embark on getting more familiar with Claude & Claude Code, I started wondering about Anthropic's privacy policies and used Claude to delve deeper in aims of gaining a better understanding. Thought I'd share some of the insights I've learned. This may be useful for those that are using Claude alongside client data. If you're using Claude Pro/Max, understand that this is a consumer product. Data retention is on by default and needs to be manually turned off, and depending on whether you have your Claude.ai training set up to improve the model, all data passed through chats is retained for up to 5 years if model training is turned on. If training is off, the data is retained for 30 days but only applies to new and resumed chats post change in settings. I extensively asked Claude if there was any trade off for turning this off, to which all responses summed up that there isn't. To check your settings, within Claude.ai go to Settings and disable the "Help improve Claude" toggle within "Privacy". A caveat worth noting is when you use the thumbs down/up option and provide feedback, this data is also retained for 5 years if the setting is enabled. Turning off the setting does not remove or delete any data that would have been stored already. Only new prompts, messages and responses from existing and new chats. To fully extend your right to erasure you will need to email "[email protected]". For the UK/EU mandem, you have the right to erasure under GDPR. Anthropic must always respond within 30 days of sending your request over. This right exists regardless of your plan or improve setting. I had a hard time wrapping my head around the different plans and what they meant. So Claude gave me the analogy below unprompted which I wanted to include: "A useful way to think about the different plan tiers: Think of it like a solicitor's office. On Pro/Max, the receptionist writes down everything you say and the firm keeps those notes for 5 years, potentially using them to train new staff.

1. Watch the intro video 2. Start with The Foundation (free course). Concepts, folder architecture, prompting framework. Everything else builds on this. 3. Check in at the bottom of each lesson. Polls, discussion posts, other members working through the same stuff. Use them. 4. When you're ready to build real things, move to Implementation Playbooks (Level 2). When you're ready to build your own tools, Building Your Stack (Level 3). 5. Post your work. Ask questions. Help others when you can. What are you here to build?

This is a long update but PLEASE read through it, this will get you updated on everything Jake and I have been building. We realized we needed structure, easy access and more content. Every lesson links to the lessons around it. Every module builds on the one before it. You can start anywhere that makes sense for you, but everything connects back to everything else. It's the same architecture we teach you to build for your own workflows. Where to Start The Foundation is the starting point. The concepts. The folder architecture. The prompting framework. If you haven't done this, do this first. Everything else assumes you have. Implementation Playbooks (Level 2) is where you use what you learned. Each module is a complete build guide for a specific domain. Building Animations. The Ultimate Browser. Pick the one that matches your work. Finish with something real. Building Your Stack (Level 3) is where you build the tools. Custom UIs. Remote access. Infrastructure that wraps around your workflows. You're not adapting to someone else's setup anymore. You're assembling your own. They're abstraction layers. Each one builds on the last. How Lessons Work Now Every lesson follows the same structure. What you'll get, the content, resources, cross-links, and at the bottom: a discussion post with a poll. The polls are there for a reason. We want to know where you are. We want you talking to each other. When you finish a lesson, scroll down, vote, and drop a comment. If you're stuck, say so. If something clicked, share what it was. The community gets better when you use it. New Categories We reorganized the community posts. Here's where things live now: Announcements - Updates from us. New content drops. Changes to the course. General Discussion - Conversation that doesn't fit elsewhere. Questions, ideas, whatever's on your mind. Show Your Work - Post what you built. Animations, automations, folder setups, custom tools. This is where the community challenges live. Share your stuff.

Context (and a little more about me): I've been using Claude to vet and analyse the "shiny objects" that appear on my socials. If your algorithm is working as hard as mine, the deeper you go into the rabbit hole of Claude.ai, Claude Code, OpenClaw etc. and all it's wonderful capabilities the more you will naturally see all the cool tools and skills people post about on X, Instagram etc. (The main way I came across Jakes content!) Well... as someone with ADHD, I sometimes (most of the time lol) fail to let go of things and that question of "Is this something that is useful to me now or could be useful for my later goals and what I plan to build/create/do" constantly rings in my head. To combat the possibility of focusing on glittery sh*t, I've been sending reels, X posts and the like through transcript converters and then asking Claude to vet it thoroughly and confirm if it's something that is of use now (learn/study/having fun phase) or something that could help me in the future (end game/gigachad final boss/bigstonks) achieve what I'd like it to achieve. Claude has been great at doing that, and has actually pushed back and has been super helpful in outlining VERY clearly if I am simply adding jargon to the mix and saving the really useful ones that do fit in context. The problem: The issue is that on Free/Pro/Max (not sure about other plans) you're limited to 30 memories per account. When you hit this limit, Claude can no longer save anything new. Naturally, being the lazy, rather cheap and very broke person I am (I make bad decisions sometimes), I started wondering if there was a workaround that could include a file system. After about an hour of brainstorming, I managed to conclude a workaround that offers little friction. Here's what I found. You can get Claude to list all existing memories and output each one as text. From there, copy each one into a separate note or doc, 1 per memory and save them into a "Memory" folder in your Google Drive. This part is manual but takes minutes, not hours. Once saved, you can then head to Settings > Memory in Claude.ai and delete all existing memories (scary). Once that part is confirmed, you can create a new chat and ask it to save the first memory with something like "Every time I open a new chat, can you please remind me to connect you to my memory bank in Google Drive".