TL;DR
Treat AI tools as third parties that may retain prompts. Minimize PII, prefer business accounts with training opt-out, separate personal/company use, ban secrets and reckless customer exports, and document AI use honestly. Privacy is weekly hygiene, not a binder for later.
Introduction
Founders paste faster than they think. That is the productiveness — and the risk. Use this as an operational baseline, not a replacement for legal advice.
Concepts Without Fog
PII/personal data: identifies people — names, emails, ticket bodies, account IDs tied to humans.
Training vs processing: improving models vs serving your request.
Retention: how long prompts, files, embeddings, and logs live.
Subprocessors: vendors inside vendors.
Safe Defaults
- Enable training opt-out / business protections
- Company emails for company AI seats
- Unique credentials via password manager
- Redact when the task allows
- Never paste keys or DB dumps
- Maintain an approved-tools list
- Revoke seats on offboarding day-one
Classification Cheatsheet
Public marketing → generally OK. Internal roadmaps → business accounts. Customer confidential → minimize + approved vendors. Secrets → never. Special-category regulated data → get advice before tooling experiments.
Consumer vs Business Plans
If customer content flows regularly, budget business tiers or stop the flow. Consumer defaults are not designed for your customers' expectations.
When Your Product Uses AI
Disclose. Contract with model providers. Minimize fields. Consider regions. Log for debug, not hoarding. Honor deletion/opt-out promises. Your brand wears the trust, not the model vendor's.
Prompts Are Records
Do not put secrets, sensitive HR notes, or unreleased deal terms into casual chats. Clean shared workspaces when contractors leave. Embeddings stores are data stores — include them in deletion.
Quarterly Hygiene
Delete stale projects, review connectors, read vendor policy emails, rotate keys, confirm who still has seats.
One-Page Acceptable Use
Approved tools, banned data, required settings, contractor rules, how to request new tools, escalation contact. Share at onboarding.
Privacy Policy Honesty
If AI reads tickets or user content, say so at a sensible level. Coordinate with counsel for GDPR/CCPA-style duties that apply to you.
Incident Pattern
Stop → delete where possible → assess notification with counsel → fix process → teach the story in onboarding.
Regional High Level
US sector and state rules vary. UK/EU emphasize lawful basis, minimization, processor terms, transfers. Minimization and honesty travel well everywhere — still verify locally.
Week-One Setup
Inventory tools → flip privacy settings → write acceptable use → anonymized prompt templates → privacy policy notes if product AI → train + revoke unused seats.
Shadow IT
Ask monthly: what AI tools did people try with company data? Bring them into the approved list or shut them down. Punishment-free reporting beats secret risk.
Field Notes From Operators
The difference between AI tourism and AI leverage is usually process. Operators who win write the decision criteria down, keep prompts in a shared library, and schedule a weekly review of what the tools got wrong. They treat model output like an intern draft: useful, sometimes impressive, never automatically trusted with customers, cash, or compliance.
When something works, they turn it into a checklist. When something fails, they add a ban rule. Over a quarter, that creates a private playbook no generic Twitter thread can replace. Your advantage is not access to the same models everyone else has — it is the taste and constraints you encode around them.
Use the rest of this guide as a living document. Revisit after each quarter's tooling changes. Delete advice that no longer matches how you work. Add examples from your own tickets, deploys, and sales calls so the next hire inherits judgment, not just subscriptions.
If you only remember one practice, make it this: every AI-assisted external action needs a named human owner. Ownership is what converts speed into responsibility. Without it, you get probabilistic chaos with a friendly chatbot UI.
Practical Exercises
Exercise A — Constraint writing. Take a vague prompt you used last week. Rewrite it with stakes, options, criteria, and a required disconfirming paragraph. Compare outputs. Keep the better template in your library.
Exercise B — Data minimization. Redo a support or research prompt with redaction. Note whether quality dropped. If not, make redaction the default.
Exercise C — Cost model. Pick one AI SaaS tool. Estimate monthly cost at 10x usage. Decide in writing whether that curve is acceptable.
Exercise D — Stop list. Add three company-specific "do not use AI for X" rules based on your product risk. Share them with anyone who has a seat.
Exercise E — Postmortem. Find one bad AI output that reached a customer or commit. Document cause, blast radius, and the process change that prevents repeats.
These exercises take a few hours total and prevent months of quiet drift.
Worked Walkthrough
Imagine a solo founder considering an AI support add-on at $400/month. They run a 21-day pilot on 60 tickets, measure edit distance and CSAT, discover the bot mishandles plan-change requests, and keep draft-only mode while rewriting three KB articles. They revisit autonomy next quarter. That sequence — hypothesis, timebox, metric, decision — is the entire craft. Apply it to vendors, content systems, coding agents, and prompting for strategy. The tools change; the discipline does not.
Another walkthrough: a founder wants "thought leadership" via AI. They brief one distinctive thesis from a real customer failure, draft with AI, rewrite the opening by hand, add a checklist artifact, publish, and pitch a single niche newsletter. One earned mention follows. That beats twenty interchangeable posts with zero distribution. Systems create that behavior on purpose.
Extended Playbook
Operators who get durable value from AI treat it like infrastructure with runbooks. They keep a shared prompt library, a stop list, and a weekly 30-minute review of failures. They measure outcomes (tickets resolved well, features shipped safely, pages that earn citations) instead of chat volume. They assign a human owner to every customer-facing automation. They budget for business-tier privacy settings the moment real customer data appears. They refuse multi-year vendor contracts before a pilot proves fit on their own messy inputs.
They also write. Short specs before coding agents. Decision memos before strategy chats. Briefs before content drafts. The writing is the control surface; the model is the accelerator. Without writing, you get confident entropy.
Another durable habit: version your rules. When a bad output ships, add a ban. When a good pattern repeats, add a template. After a quarter you have a private operating system that competitors cannot copy by buying the same subscriptions. That is the real stack advantage — taste encoded as process.
Finally, schedule deletion. Old chats, unused seats, stale connectors, and zombie pilots accumulate risk and cost. A monthly cleanup is as important as a new tool trial. Speed without subtraction is how startups drown in dashboards.
Scenarios and Responses
Scenario: investor asks for AI strategy. Answer with jobs-to-be-done, current tools, data boundaries, and what you will not automate. Do not perform science fiction.
Scenario: customer asks if a human will help. Promise a human path and keep it. Autonomy theater destroys NPS.
Scenario: contractor pastes a client list into a consumer model. Revoke access, delete where possible, review legal duties, update acceptable use training immediately.
Scenario: coding agent "fixes" auth broadly. Revert, re-spec, implement in a thin slice, add a regression checklist.
Scenario: content calendar demands five AI posts/week. Cut to one deep piece with distribution. Volume without voice trains readers to ignore you.
Scenario: vendor demo looks perfect. Demand a pilot on your samples with kill criteria and 10x pricing before you celebrate.
Checklists You Can Run Tomorrow
- Approved AI tools list exists and is shared
- Training opt-out enabled on business accounts
- One-page acceptable use for data
- Prompt library with at least five templates
- Stop list with at least five bans
- Pilot template for any new AI vendor
- Content brief template with voice kit link
- Support escalation matrix if AI drafts exist
- Weekly failure review on the calendar
- Monthly seat and connector cleanup
If fewer than six boxes are checked, fix basics before buying another tool.
Extended Playbook
Operators who get durable value from AI treat it like infrastructure with runbooks. They keep a shared prompt library, a stop list, and a weekly 30-minute review of failures. They measure outcomes (tickets resolved well, features shipped safely, pages that earn citations) instead of chat volume. They assign a human owner to every customer-facing automation. They budget for business-tier privacy settings the moment real customer data appears. They refuse multi-year vendor contracts before a pilot proves fit on their own messy inputs.
They also write. Short specs before coding agents. Decision memos before strategy chats. Briefs before content drafts. The writing is the control surface; the model is the accelerator. Without writing, you get confident entropy.
Another durable habit: version your rules. When a bad output ships, add a ban. When a good pattern repeats, add a template. After a quarter you have a private operating system that competitors cannot copy by buying the same subscriptions. That is the real stack advantage — taste encoded as process.
Finally, schedule deletion. Old chats, unused seats, stale connectors, and zombie pilots accumulate risk and cost. A monthly cleanup is as important as a new tool trial. Speed without subtraction is how startups drown in dashboards.
Scenarios and Responses
Scenario: investor asks for AI strategy. Answer with jobs-to-be-done, current tools, data boundaries, and what you will not automate. Do not perform science fiction.
Scenario: customer asks if a human will help. Promise a human path and keep it. Autonomy theater destroys NPS.
Scenario: contractor pastes a client list into a consumer model. Revoke access, delete where possible, review legal duties, update acceptable use training immediately.
Scenario: coding agent "fixes" auth broadly. Revert, re-spec, implement in a thin slice, add a regression checklist.
Scenario: content calendar demands five AI posts/week. Cut to one deep piece with distribution. Volume without voice trains readers to ignore you.
Scenario: vendor demo looks perfect. Demand a pilot on your samples with kill criteria and 10x pricing before you celebrate.
Key Takeaways
- Minimize PII; prefer business plans with training opt-out.
- Classify data; ban secrets and careless exports.
- Document approved tools; revoke seats quickly.
- Product AI needs disclosure and contracts.
- Hygiene is continuous: retention, settings, honesty.
FAQ
Customer data in ChatGPT?
Avoid sensitive PII in consumer tools; minimize and use business protections.
Training vs processing?
Processing serves you; training may improve their models.
DPA?
Often yes when vendors process personal data for you — confirm with counsel.
Usage rules?
One-page acceptable use plus approved tools.
Can vendors see prompts?
Possibly — read policies.
Tell customers?
Accurate disclosures about AI involvement.