Data Handling.

Core philosophy

Decent Ops follows a minimal-data and least-access approach. The goal is simple: collect only what is reasonably needed, request only the access needed for the project, and keep clients in control of their important systems whenever practical.

Information Decent Ops may handle

• Client name and contact information.
• Business name, website, brand materials, and project notes.
• Intake form submissions, emails, and project communications.
• Documents, copy, images, spreadsheets, or operational files provided for the work.
• Website or platform access needed to complete agreed work.
• Payment or billing records through third-party payment providers.

Least-access work

Whenever possible, Decent Ops prefers temporary, revocable, project-specific access instead of permanent shared credentials. Collaborator access, limited user roles, screen-share walkthroughs, and client-owned accounts are preferred where practical.

Credentials

Clients should not send passwords through standard contact forms. When a project is complete, clients are encouraged to revoke temporary access, remove unused collaborators, rotate shared passwords, and review platform users and permissions.

Files and project materials

Client files may be used to complete agreed work. Decent Ops does not want unnecessary sensitive information. If information is not needed for the project, do not send it.

Security limits

This is not a promise of perfect security. No responsible operator should promise that. It is a plain-language explanation of how Decent Ops intends to work: carefully, minimally, and with respect for client-owned systems.

AI-assisted workflows

When AI-assisted tools are used, Decent Ops aims to use only the amount of context needed to complete the work. Sensitive details should be removed, reduced, summarized, or anonymized whenever practical.