Privacy

Data TaskFlow processes

• - Account identity data such as name, email, role, and project membership.
• - Project records, tasks, documents, comments, requirements, activity, and builder-run metadata users create inside TaskFlow.
• - Connector access metadata such as OAuth grants, token usage, tool calls, and audit events needed to operate the MCP server safely.

Connector access

• - TaskFlow supports OAuth and bearer-token access for MCP clients.
• - Connector calls use the permissions attached to the signed-in user or project-scoped API key.
• - TaskFlow does not ask users to share Claude conversations as a data source for normal connector operation.

Model and data usage

• - TaskFlow does not use customer workspace data to train public foundation models.
• - Connector responses are generated from TaskFlow account data that the authenticated session is allowed to access.
• - Operational logs should contain TaskFlow domain events and request metadata, not full Claude conversation transcripts.

Contact

Privacy questions or account-data requests can be sent to support@emun.io. Include the workspace name and the email attached to your TaskFlow account so the request can be verified safely.