OutcomeCraft
Product guide · Español (México)
Effective / Vigente: 23 August 2026

Subprocessors and integrations

Providers currently used to operate OutcomeCraft or connected at customer direction.

Service providers

ProviderPurposeData involved
Fly.ioApplication hosting and network deliveryApplication requests, runtime data and operational logs
NeonManaged PostgreSQL databaseAccount, tenant, editorial, knowledge, usage, audit and waitlist records
OpenAIModel inference for generation, critique and calibrationSelected editorial profile, approved examples/knowledge, recent content context and requested output; credentials are not included in prompts
GoogleOptional identity login and operational email deliveryIdentity claims or transactional email metadata/content, depending on the feature used
InfisicalDeployment secret managementOperational credentials and configuration required to deploy the service

Customer-directed integrations

ProviderDirection
XReads authorized/public account content and metrics and, only when enabled, publishes an approved original post using the connected account.
NotionReads only pages made available through the customer's authorization and selected for synchronization.
Claude or ChatGPT through MCPThe customer's assistant may send only explicitly approved profile drafts, examples and knowledge capsules to OutcomeCraft. The assistant provider remains governed by the customer's relationship with that provider.

International processing and changes

Providers may process data in multiple countries under their applicable data-protection terms. This register identifies functional roles, not guaranteed storage regions. Tecnicora will update the effective date when the provider set materially changes. Contact hola@tecnicora.com for relevant provider safeguards or to raise an objection where applicable.