Loading
Preparing the MinuteWork public site.
Preparing the MinuteWork public site.
Security
MinuteWork helps operators turn work history into AI workforces and customer-facing businesses. That only works if operator data, customer records, AI traces, and business relationships stay protected by design.
We are infrastructure for operator-owned businesses, not a data brokerage or ad network.
Security posture
MinuteWork is built around tenant isolation and operator ownership. Your customers, customer records, files, and generated business data are not a growth channel for us.
Prompts, outputs, files, drafts, and workflow decisions can reveal how an operator thinks. We treat that material as business-confidential, not generic product analytics.
MinuteWork helps AI workers prepare the work. Operators decide which actions require approval, when to escalate, and what should never move without human review.
Published operator businesses need reviewable workflows, explicit customer plans, metered usage, and clear ownership. We do not treat public customer delivery as a prompt playground.
Credentials, API keys, provider secrets, and payment secrets belong in controlled secret handling paths, not in generated content, published pages, or operator-facing copy.
Operators should know how runtime costs, usage, customer pricing, and earnings share work. Surprise infrastructure economics are a security risk for the business.
What we won't do
Security is not only encryption and access control. It is also refusing business models that would make your data less safe.
Not your resumes. Not your customer transcripts. Not your files. Not your AI traces. We document this in our Privacy Policy and require compatible behavior from subprocessors.
Operators are not inventory. Customers are not ad targets. Your business surface should serve the customer you brought, not a second hidden customer.
Customer lists, contact history, files, and workflow data belong to the operator business. We do not package them as benchmarks, leads, or enrichment products.
If MinuteWork builds in an operator's category, the operator becomes the partner or we do not ship it. That line protects data, trust, and incentives at the same time.
Useful details
These are the public trust surfaces we maintain today. As the platform matures, this page should become the index for deeper security documentation.
No-training policy, subprocessors, controller/processor split, cookies, and retention.
Operator responsibilities, platform rights, and commercial relationship.
Use this for security questions until a dedicated security intake is published.
Customer tenant floor, usage, build estimates, and operator earnings share.
Upload your resume or describe what you do. MinuteWork turns it into an AI workforce that runs under your name, with your customer relationship intact.
Find my business ->