Sub-processors
A sub-processor is a company we use to help run our business that may handle a small amount of personal data on our behalf. Because Cronable is self-hosted and your secret and credential values are stored on your own machine, this list is deliberately short. Two entries matter most for what you do in Cronable: OpenRouter, which the hosted AI option uses, and Google Cloud, which runs our relay and our Google sign-in service — both described below.
Last updated September 25, 2026
These are all the sub-processors we use today. Each one handles only what it needs to do its job.
Stripe
What it does: processes our subscription payments. When you subscribe, Stripe securely handles your card details and charges — we do not store your full card number. You can learn more from Stripe's own privacy documentation on their website.
Resend
What it does: delivers our email. This covers transactional email, such as account and billing messages, and the contact or support messages you send us. You can learn more from Resend's privacy documentation on their website.
Vercel
What it does: hosts the cronable.ai website and provides cookieless website analytics — aggregate usage figures with no cross-site tracking, plus the first 200 characters of your question when you start the AI demo on our homepage. You can learn more from Vercel's privacy documentation on their website.
Plausible Analytics
What it does: provides cookieless, privacy-friendly website analytics — again, aggregate figures plus the start of your question when you begin the homepage AI demo, with no cookies and no personal profiles. You can learn more from Plausible's privacy documentation on their website.
Google (pre-launch waitlist only)
What it does: while Cronable is pre-launch, waitlist sign-ups (your email, and name if given) are stored in a Google Sheet through Google Apps Script, so we can email you when we open up. Provided by Google LLC in the United States. This applies only to the pre-launch waitlist — it is not part of the product — and we delete the sheet after launch.
Upstash
What it does: runs the small database our website uses to enforce the daily limits on the AI demo and idea generator. For each visitor who uses them, it holds a scrambled form of their IP address — a keyed hash, not the address itself — and a count of that day's requests, and deletes both automatically after two days, and any backup copy of them within three days after that. Until 25 September 2026 it received the IP address itself; those records are deleted on the same schedule. We use it through our website host, Vercel. You can learn more from Upstash's privacy documentation on their website.
OpenRouter (hosted AI option and website demo)
What it does: OpenRouter is an AI model gateway based in the United States. It powers the hosted Cronable Assistant (the built-in Assistant, including Assistant jobs you schedule) and the AI demo and idea generator on our website. If you choose the hosted option — rather than your own AI key or your machine's local Claude CLI — what the Assistant needs is routed, through our own assistant service, to OpenRouter, which passes each request to one of the companies that host the AI model to generate the reply. For the Assistant that is your messages and the job details needed to answer them; for the website it is what you type into the demo or idea generator. Those hosts include companies in the United States and in China, among other countries; OpenRouter picks the host for each request (and may retry it on another), and we do not currently restrict which. We do not store any of it — apart from the start of an opening homepage demo question, kept in our website analytics — and for the Assistant we keep only a per-day message count. OpenRouter and the model host handle it under their own terms and data policies. If you use your own key or the local CLI, our OpenRouter account is not involved.
Google Cloud Platform
What it does: hosts our licence server and its database, the hosted Assistant service, our Google sign-in service, and the relay that carries inbound webhooks, remote control and remote MCP. Our servers run in Google Cloud's Singapore region. It holds the account and licence data described in our Privacy Policy, along with the bug reports you send us. When you use them, some of these services also carry your Cronable data: the relay holds each inbound webhook until your machine collects it, for up to 24 hours, and passes remote-control and remote-MCP traffic through without storing it — including a secret value at the moment you type one into the remote dashboard; the sign-in service holds a new Google connection's tokens, encrypted, only until your machine collects them, and relays later renewals; and the hosted Assistant passes what it is sent on to OpenRouter, keeping only a per-day message count. The relay's edge servers keep access logs — IP addresses, request addresses and headers, never bodies — for up to 7 days.
Our own licence server
Your account and licence details — your name, email, hashed password, plan and subscription status — are held on our own licence server. This is our first-party system, not a third-party sub-processor, but we mention it here so you have the full picture of where your account data lives.
Where these providers operate
Our own servers run in Singapore. Some of these providers process data outside Singapore, including in the United States and the European Union. When that happens, appropriate contractual safeguards are in place so your data stays protected to a comparable standard. One exception: the model host that OpenRouter chooses for a hosted-AI or website-demo request can be in China or another country, and we do not choose it. Our Privacy Policy explains this in more detail.
How we tell you about changes
If we add or change a sub-processor, we will update this page and change the date at the top. Where a change is significant, we will also give reasonable notice — for example by email or a notice on the website — so you always know who helps us run Cronable. Questions? Email sales@cronable.ai.