Protect privacy and reduce risk

Map four things: what enters the system, what the provider may retain, who can access output, and what action follows. For this topic the operative rule is: do not include account details, private purchase history, or personally sensitive constraints unless they are necessary and safe to share. “No secrets” is too vague; name prohibited fields and approved substitutes.

Classify the work by consequence. Low-risk ideation with synthetic data may need ordinary review. Internal drafts based on approved material need access and retention controls. Public claims, student decisions, deployments, impersonation, sensitive targeting, or automated external actions require a stricter gate and sometimes should not use the tool at all.

The scenario is make a multi-constraint laptop recommendation auditable without requesting hidden reasoning. Ask:

• Do we have permission to process every input and license every asset?
• Could the output mislead someone about authorship, evidence, identity, or reality?
• Can untrusted text or media alter tool instructions?
• Is there a reversible draft stage before publication, sending, grading, or deployment?
• Can a person contest, correct, remove, or revoke the result?

Compare three laptops for college using price, measured battery life, weight, and required-software compatibility. First output a short comparison plan and evidence table. Then recommend one in under 150 words with three deciding facts. Finally list unknowns to verify on seller pages. Give concise rationale, not private hidden reasoning.

The prompt can state boundaries, but prompts are not access control, consent records, or legal clearance. Configure minimum permissions, retention, sharing, and deletion in the surrounding system. Keep an incident route for accidental exposure and a kill switch for repeated workflows.

For the expected result—A criteria table, explicit unknowns, a short recommendation tied to three inspectable facts, and a verification checklist—review privacy, security, bias, rights, and deception separately. Use provenance notes and disclosures where audiences could mistake synthetic media or generated claims for direct evidence. Preserve human ownership of consequential decisions.

Likely failures include equating longer rationale with truth; post-hoc justification; invented specifications; hidden weighting; arithmetic that cannot be reproduced. Ask for visible work products—plans, formulas, evidence tables, assumptions, and checks. A model's private reasoning is neither required nor a substitute for proof. When local law, organizational policy, a contract, or platform rule is stricter than this lesson, the stricter rule wins.

Try one hostile or ambiguous input without using real sensitive information. Observe whether the model invents, follows embedded instructions, exceeds the schema, or proposes an irreversible action. A safe run should fail closed: return “unknown,” route to review, or stop.