Data handling

The initial workflow audit should describe the process, tools, bottlenecks, and desired outcome. Do not send production credentials, private datasets, or sensitive documents through Calendar, WhatsApp, or ordinary email.

Required systems, data categories, permissions, third-party services, model providers, retention needs, and approval points are documented in the project scope before access is requested.

Where the selected tools support it, the delivery approach uses client-controlled accounts and the narrowest practical permissions. Exact controls depend on the tools and written project agreement.

Workflows are designed around explicit actions and ownership. High-impact writes or external communications can be placed behind human approval gates when included in scope.

Logging, fallback behavior, and recovery steps are defined for the implemented workflow rather than assumed from a generic policy.

The agreed handoff identifies configuration, ownership boundaries, operating instructions, and next steps. Access that is no longer required should be revoked at handoff or project end.

Hosting location, subprocessors, model data use, retention, deletion, incident response, backups, and intellectual-property terms vary by architecture. They must be stated in the written proposal or service agreement; this page does not claim certifications or controls that have not been contractually established.

Contact neurosformer@gmail.com before sharing sensitive information or to request deletion of project data that Neurosformer is not required to retain.