We only use data you explicitly approve for this project and purpose.

We minimize sensitive details and keep them out of public chat tools.

When possible, we configure zero-retention or private deployments so prompts and outputs aren't stored or used for model training.

We don't scrape or ingest third-party content you don't own or license.

For demos and testing, we use de-identified or synthetic data whenever feasible.

We vet tools for privacy controls, encryption, enterprise terms, and retention settings.

If your company bans a tool, we propose alternative approaches.

When feasible, we build inside your accounts or with your API keys so you remain in control.

We prefer vendors with independent security attestations (SOC 2, ISO) and clear documentation about training-data sources and opt-outs.

For IP-sensitive use cases, we avoid generative tools whose training sources are unclear or likely to include unlicensed material.

Least-privilege access only. we request the minimum permissions required.

Devices are encrypted. Secrets and passwords live in a password manager, never in plain text.

Files live in approved folders with encryption at rest and in transit.

If email is unavoidable, attachments are encrypted and keys are shared via a separate channel.

We agree up front on what we receive, where it lives, who can access it, and for how long.

We maintain a simple data inventory for the project.

On project close, we delete local copies and temporary artifacts within the agreed timeframe and confirm in writing.

Backups and logs follow the same timelines unless your policy requires different handling.

Every workflow ships with a plain-English one-pager: inputs, steps, tools used, privacy notes.

Any external integrations, automations, or data connections require written approval.

We align with your legal and IT policies and adjust after your review.

A current list of tools and sub-processors used on your project is available on request.

AI outputs are drafts until a human approves them. Nothing auto-sends to customers without your sign-off.

We test for prompt risks, hallucinations, and data leakage before recommending production use.

Where relevant, we add guardrails and allow-lists.

We monitor outputs in pilots and adjust prompts, data, or workflows when necessary.

We avoid ingesting third-party content you don't own or license.

Deliverables, custom helpers, prompts, and workflow documents created for your business are yours as defined in our agreement.

We don't reuse your proprietary datasets or workflows in other client work.

We won't cross-pollinate competitive strategies between clients without explicit permission.

We don't use your name, logo, or results in marketing without written permission.

Testimonials and case studies are drafted for your approval before publication and can be anonymized.

If we detect a data exposure or security issue, we notify your point of contact promptly with facts, scope, and next steps.

We pause affected workflows until risks are addressed, then document the fix.

We keep a simple incident log for transparency.

We are not a law firm. We flag issues early and follow your counsel's guidance.

If needed, we can add a short data-processing addendum naming approved tools, sub-processors, and regions.

For regulated data (PHI, PCI, or government identifiers), we either put additional controls and agreements in place or avoid using it altogether.

If your policies require specific data residency, we configure regional controls where vendors support them.

You can require zero-retention modes where supported and available.

You choose data-residency preferences when tools support region selection.

You can opt out of any nonessential analytics or logging for copilots we build.

You approve the data sources a workflow may read and the channels it may write to.