Trust and safety
Read-only first. Approval before action.
PlainOps should lower operational risk, not create it. The validation scanner is designed around low-friction evidence and explicit customer approval.
What not to send
Passwords, API keys, recovery codes, or admin credentials.
Card numbers, bank details, or customer payment card data.
Personal data unnecessary for subscription or billing analysis.
What is acceptable
Tool/vendor lists with spend bands and owners; CSV exports without secrets; renewal dates, invoice totals, licence counts, and usage screenshots; authorised Stripe/Paddle summaries for revenue leakage scans.
Operating boundaries
No automatic cancellations
PlainOps identifies candidate actions; the customer approves before any cancellation, downgrade, vendor contact, or workflow change.
No invented savings claims
Synthetic demo numbers are labelled. Real savings claims require real customer evidence and permission.
No write-access dependency
Validation starts with exports and screenshots. Integrations can come later only if they improve trust and repeatability.