{"found":true,"collection":"patterns","library_url":"https://www.grokbotdb.com/library/pat.legacy-privacy-mode-blocks","generated":"2026-09-06T05:32:11Z","citation":["Quote the record id and its source_url (or provenance if there is no URL).","Include last_verified or observed_at when present. Do not present an old date as current.","If tier is community and confidence is low, say so. Do not launder it into a fact.","If the database does not hold the answer, say that. Do not invent Grok Bot product claims.","Contradictions are data: when conflicts_with is present, report both records rather than picking a favourite.","Deprecated and removed records stay visible. They are history, not current guidance."],"record":{"id":"pat.legacy-privacy-mode-blocks","name":"Clear Legacy Privacy Mode before rollout","category":"onboarding","problem":"An account or team on Legacy Privacy Mode sees a sign-in error, and the product is unusable until it moves.","technique":"Change the Cursor account data setting to one that permits cloud data storage, or have the admin do it, before planning anything else.","why_it_works":"Grok Bot requires cloud data storage; there is no local-only or partial private mode, so this is a hard block rather than a degraded experience.","when_to_use":"Before any team rollout.","manual_ref":"2.1","evidence":"documented","related":["pat.beta-do-not-connect-list"],"confidence":"high","first_seen":"2026-09-03","last_verified":"2026-09-03"}}