Jon Croft sub-processors
Last updated: 13 November 2026
Ascendant Media Strategies - FZCO uses the third-party service providers below to help run Jon Croft. They may process customer personal data on our behalf, only as needed to provide the Service.
| Sub-processor | Purpose | Data potentially processed |
|---|---|---|
| Railway | Application hosting | All data processed by the Service, including account data, workspace content, and request logs |
| Neon | Database hosting and backups | Account data, workspace content, connection tokens (encrypted), billing and usage records |
| Cloudflare | File storage, DNS, and website delivery | Uploaded and generated files; website visitor IP addresses and request data |
| OpenRouter | Routing requests to AI model providers | Prompts, conversation context, files and excerpts, tool results, and AI outputs |
| AI model providers | AI model processing (see below) | Prompts, conversation context, files and excerpts, tool results, and AI outputs |
| Stripe | Payments, subscriptions, invoicing, and tax | Name, email, billing address, tax ID, payment details, and transaction data |
| Resend | Transactional email | Name, email address, and email content |
| ImprovMX | Forwarding email sent to our @joncroft.si addresses | Sender name and address, email content, and attachments |
| Slack | Messaging, if enabled by the customer | Messages and files in channels and direct messages where Jon Croft is present; Slack user IDs |
| Meta | Ads management, if enabled by the customer | Ad account data and ad content |
| Composio | Connecting the third-party apps a customer chooses to link, if enabled by the customer | Connection credentials (OAuth tokens and API keys) and data passing through the integrations the customer enables |
AI model providers
Jon Croft uses large language models and other AI models from leading providers, such as Anthropic, OpenAI, Google, DeepSeek, Mistral, and Perplexity, accessed through OpenRouter and, for some models, through cloud platforms such as Microsoft Azure, Amazon Bedrock, and Google Cloud. The provider used for a request depends on the task.
Where data is located
Product and workspace data is hosted primarily in the United States. Email sent to our @joncroft.si support addresses is relayed through infrastructure in the EU (France) before delivery.
How we manage sub-processors
- We only use a sub-processor where it is needed to run the Service, and we share only the data it needs for its job.
- Before we start using one, we review its security and data protection practices, and we rely on written terms with it that require it to protect the data, use it only to provide its services to us, and keep it confidential.
- We remain responsible to you for our sub-processors' handling of customer data.
- Services that a customer chooses to connect, such as Slack or Meta Ads, are also governed by the customer's own agreement with that provider.
Change notifications
We update this page at least 30 days before a new sub-processor starts processing customer personal data. If you object to a new sub-processor, email security@joncroft.si within that period.