Privacy Policy

Your data stays with you

This is the most important thing to understand about Cronable, so we will say it plainly. Cronable is self-hosted software. It installs and runs on your own computer or server, and everything you do with it is stored there.

Left to itself, the software sends us almost nothing: a periodic licence check (which confirms your subscription and reports only simple counts — how many jobs and users your install has) and a check for new releases. Neither carries the content of your work or a secret value. That is a deliberate design choice: what we never hold, we cannot lose. Some features change this, each only when you use it, and each is described under “What we collect, and why” below: the hosted Cronable Assistant, inbound webhooks, remote control, remote MCP, one-click Google sign-in, and bug reports. Remote control is the one to understand before you use it: your browser reaches your server through our relay, so while it is in transit your dashboard traffic passes through our infrastructure — job definitions, run logs, and a secret value at the moment you type one into the remote dashboard. We do not store that traffic; our edge servers keep only a short access log of each request, described below. Run the dashboard on the same machine as the engine and none of it applies.

The hosted AI option deserves the same attention, because it hands your content to another company: if you run the built-in Assistant on the hosted Cronable Assistant (rather than your own AI key or your machine's local Claude CLI), what it needs in order to work — your messages and the job details behind them — is sent through us to a third-party AI model provider to generate the replies. We describe exactly what is and isn't sent, and what we keep, in the sections below.

The rest of this policy is about the limited personal data we handle to run our website, your subscription, and these hosted features — not what happens inside your Cronable install, which does not reach us otherwise.

Who is responsible for your data

Jefe Digital Pte. Ltd. is responsible for the personal data described in this policy. We are registered in Singapore with UEN 201601734E, at 2 Havelock Road, #06-01, Havelock II, Singapore 059763. You can reach us about privacy at privacy@cronable.ai.

What we collect, and why

We keep what we collect deliberately small. Here is the full list.

• Account data — your name, email address, a hashed (scrambled) version of your password, your plan, and your subscription or licence status. To keep your licence active and enforce your plan's limits, your running install also periodically reports simple counts — how many jobs and users it has, never the jobs themselves. We use this to create and secure your account and administer your licence. It is held by our own licence server.
• Billing data — we use Stripe to take payment. Stripe handles your card details; we see your subscription status and billing records, but not your full card number. We use this to manage your subscription and meet our accounting and tax obligations.
• Contact and support messages — if you contact us, we receive your name, email, company and team size (if you give them) and your message, delivered to us by email through Resend. We use this to reply and to help you.
• Waitlist — before Cronable opens to sign-ups, you can join our waitlist with your email (and your name, if you like). We use it only to email you when Cronable launches. We store it in a spreadsheet hosted by Google, and delete it after launch or sooner if you ask.
• Website analytics — we measure how our website is used with privacy-friendly, cookieless analytics (Vercel Analytics and Plausible). These produce aggregate figures, with one exception: when you start the AI demo on our homepage, the first 200 characters of your question are recorded with that analytics event, so we can see what people ask. There is no cross-site tracking and there are no advertising profiles.
• Website AI demo (only if you try it) — when you use the AI demo (on our homepage or use-cases page) or the idea generator on our use-cases page, what you type is sent through our website to OpenRouter, an AI model gateway, and on to a company that hosts the AI model, to write the reply (see “Who we share it with”). We do not store your conversation — apart from the first 200 characters of the question you start it with on our homepage, which our website analytics records (see above) — and nothing you build in the demo is saved. We use your IP address to apply the daily limits on the demo and the idea generator. For that purpose we keep only a scrambled form of it — a keyed hash that cannot be traced back to your address without our secret key — with a count of that day's requests, in a database run for us by Upstash, which deletes it automatically after two days, and any backup copy of it within three days after that; the web server that handles your request may also hold that scrambled form, with the times of your requests, in its temporary memory.
• AI Assistant content (hosted option only) — if you use the hosted Cronable Assistant, rather than your own AI key or your machine's local CLI, what the Assistant works on passes through our assistant service to OpenRouter, an AI model gateway, which sends it on to a company that hosts the AI model to generate the replies (see “Who we share it with”). That is your messages to the Assistant — or, for an Assistant job, the instructions you wrote for it — and the details it needs to help you: your jobs' configuration and non-secret variable values, the names — never the values — of your secrets, and, when you ask the Assistant to look at a run (for example “why did this fail?”), that run's history and its log output. Run logs are secret-masked before they are ever stored, so the values of your secrets are not in them; they can, however, contain whatever your own job printed, and file paths from your server. We record only a per-day count of your messages, to enforce your plan's allowance; we do not store the messages or their content. We never send your secret or credential values on your behalf — though, because a job's fields are filled in before it runs, a secret you deliberately reference in an AI job's own instructions becomes part of what that job sends. AI steps you give tools do not use this option: they always run on the provider key you chose for that step.
• Inbound webhooks (only if you use them) — when another service sends a webhook to your Cronable address on our relay, we receive the whole request: its body, headers and query string, which include details of the sending service, its IP address and any secret token it puts in the headers. The relay writes the event to disk and holds it until your machine collects it, then deletes it; if your machine does not collect it within 24 hours, it is discarded.
• Remote control and remote MCP (only when you use them) — when you use the dashboard from outside your machine, or an AI app you have authorised reaches your Cronable over remote MCP (Business plan and above), that traffic passes through our relay to your machine and back. It includes job definitions, run history and logs, variable values, the names of your secrets, and anything you type into the remote dashboard — a secret value included. We do not store this traffic. For remote MCP we also keep a record of each AI app you authorise and hashed tokens that let it reconnect.
• One-click Google sign-in (only when you connect a Google account this way) — so you can connect a Google account without setting up your own Google app, Google returns your approval to our sign-in service, which exchanges it for that account's access tokens and an ID token carrying the account's email address. We hold those tokens, encrypted, only until your machine collects them — normally within seconds — and erase them once collected; tokens that are never collected can no longer be released after 10 minutes, and are deleted within a few minutes after that. Afterwards, whenever the connection's access needs renewing, your machine sends its refresh token through the same service to Google and gets a fresh access token back; we do not keep either. Connect with your own Google app instead (choose “Advanced — use my own OAuth app” when connecting) and none of this passes through us.
• Bug reports (only when you send one) — if you report a bug from inside Cronable, we receive what you write; the diagnostic details shown in the form (app version, page, browser, language, window size, theme and mode — switch them off and only the app version and language are sent); your install's Cronable version, operating system, runtime version and machine identifier; and the IP address it connects from. A screenshot of the Cronable window is included only if you attach one: you see it before sending, and it can show whatever was on screen, including job details. Bug reports are held by our own licence server, linked to your licence.
• Technical and security logs — our systems and our host (Vercel) keep short-lived logs that can include your IP address, browser type, and a record of the messages you send us. The edge servers of our relay log each request they handle — the IP address, the time, the full address requested (minus our own tokens), and the request and response headers, minus the ones that carry Cronable credentials or the webhook secrets our built-in triggers use — but never its body. We use these to keep the service secure, diagnose problems, and prevent abuse.

Why we are allowed to use it

Under Singapore's Personal Data Protection Act, we handle your data with your consent and for the reasonable purposes described here. For customers in the EU or UK, the equivalent legal bases under the GDPR are:

• Contract — to provide your account, subscription and support, and the hosted features you choose to use.
• Legitimate interests — to run, secure and improve our website (including cookieless analytics, which we do not use to identify you as an individual), and to communicate with you.
• Legal obligations — such as meeting our tax and accounting duties.
• Consent — for example, to add you to our pre-launch waitlist and email you when Cronable opens. You can withdraw it at any time.

Who we share it with

We do not sell your personal data, and we never will.

We may disclose personal data if the law genuinely requires it, or to establish or defend our legal rights — always kept to the minimum necessary.

Otherwise, we share the limited data above only with the service providers that help us run Cronable — our sub-processors — and only so they can do their job for us. You can see them, and what each one does, on our Sub-processors page. In short:

• Stripe — to process subscription payments.
• Resend — to deliver our transactional and contact or support emails.
• Vercel — to host our website and provide cookieless website analytics.
• Plausible Analytics — to provide cookieless website analytics.
• Upstash — to hold the scrambled (keyed-hash) forms of IP addresses, and the daily request counts, that enforce the limits on our website's AI demo and idea generator; each record is deleted automatically after two days, and any backup copy of it within three days after that. Upstash does not receive the IP addresses themselves; until 25 September 2026 it did, and those records are deleted on the same schedule.
• Google — a spreadsheet where we hold pre-launch waitlist sign-ups until Cronable launches; and Google Cloud, which hosts our licence server, hosted Assistant, Google sign-in service and relay on servers in Singapore.
• OpenRouter, an AI model gateway based in the United States — only if you use the hosted Cronable Assistant, or try the AI demo or idea generator on our website. It passes each request to one of the companies that host the AI model, and that company generates the reply. 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. What they receive is what the Assistant sends — your messages and the job details behind them — or what you type into the website demo or idea generator. OpenRouter and the model host handle it under their own terms and data policies. If you use your own AI key or your machine's local CLI instead, nothing goes through us or to our OpenRouter account.

Sending data outside Singapore

Our own servers — the licence server, the relay and the hosted Assistant service — run in Google Cloud's Singapore region. Some of our service providers are based in, or process data in, countries outside Singapore, including the United States and the European Union. When your data is transferred abroad, we rely on appropriate contractual safeguards — such as the standard data protection clauses these providers offer — so that it stays protected to a comparable standard. One exception to know about: if you use the hosted Cronable Assistant or our website's AI demo, OpenRouter may send your request to a model host in another country, including China, and we do not choose which.

How long we keep it

We keep account data for as long as your subscription is active. We keep billing and transaction records for at least 5 years after the end of the financial year they relate to, because Singapore tax and company law requires it, after which we delete or anonymise them. We keep contact and support messages for up to 24 months after your query is resolved, unless we need them longer to handle a dispute. Technical and security logs are short-lived. Our relay's edge access logs are deleted after at most 7 days. An inbound webhook waits on our relay only until your machine collects it, and never more than 24 hours. Tokens from a one-click Google sign-in are erased as soon as your machine collects them; tokens it never collects cannot be released after 10 minutes and are deleted within a few minutes after that. Remote-control and remote-MCP traffic is not stored; the record of an AI app you authorise for remote MCP is kept while your account exists. We keep bug reports, including any screenshot, so we can follow a problem through to a fix; we do not delete them automatically, but we will delete yours whenever you ask. What you send the hosted AI option or the website's AI demo — your messages — is not stored by us, apart from the start of an opening homepage demo question kept in our website analytics; for the hosted option we keep only a per-day count to enforce your plan's allowance. Our rate-limit database, run for us by Upstash, deletes the scrambled form of the IP address we use for the daily limits on the website's AI demo and idea generator automatically after two days, and any backup copy of it within three days after that; a copy held in a web server's temporary memory lasts only as long as that server keeps running. We keep waitlist sign-ups only until Cronable launches, or until you ask us to remove you, then delete them. Our cookieless analytics are not tied to you as an individual. When we delete something from our database, it leaves our backups within 14 days.

How we protect it

We use sensible technical and organisational measures to protect the data we hold. Passwords are stored hashed, not in plain text. Access to account and billing systems is limited to the people who need it. Payment card details are handled by Stripe, not by us.

And the most sensitive material of all — your secret values and your credentials — is protected by the fact that it is stored on your machine, not ours. It can still pass through our systems, for example: a value you type into the remote dashboard crosses our relay in transit; a one-click Google sign-in's tokens are held, encrypted, until your machine collects them, and later renewals pass through the same service; a secret you deliberately reference in an AI job's own instructions, or type into a chat with the hosted Assistant, travels with that request to our AI provider; and a secret another service puts in the headers of a webhook it sends you — such as GitLab's or Telegram's webhook token, or Asana's signing secret — is held with that webhook for up to 24 hours. Our relay's access log leaves out the headers our built-in triggers take these secrets from; any other header is recorded there, so a secret you have a sender put in a header of your own choosing is kept until that log is deleted, after at most 7 days.

Your rights

You have rights over the personal data we hold about you. Depending on where you live — for example under Singapore's PDPA, the GDPR in the EU or UK, or the CCPA in California — these include the right to:

• Access — ask for a copy of the personal data we hold about you.
• Correct — ask us to fix data that is wrong or out of date.
• Delete — ask us to erase your data, where we are not required to keep it.
• Port — ask for your data in a portable form, or that we send it to another provider.
• Withdraw consent — change your mind about a use you previously agreed to.
• Object or restrict — ask us to stop or limit certain uses, including any marketing.

How to exercise your rights

To make any of these requests, email us at privacy@cronable.ai. We will respond within 30 days; if a request is complex and we need more time, we will tell you within that period and explain why — and in every case within the maximum the applicable law sets (for example, one month under the GDPR, extendable for complex requests, and 45 days under the CCPA). We will not charge you or treat you differently for exercising your rights, and we may need to confirm your identity first, to keep your data safe.

If you are in California, we do not sell or share your personal information, and we will not discriminate against you for exercising your rights. If you are in the EU or UK, you also have the right to complain to your local data protection authority; if you are in Singapore, you may contact the Personal Data Protection Commission (PDPC) — though we hope you will come to us first.

Children

Cronable is a business and developer tool, and it is not directed at children. We do not knowingly collect personal data from anyone under 13. If you believe a child has given us personal data, contact us at sales@cronable.ai and we will delete it.

Changes to this policy

We may update this policy as Cronable grows or the law changes. If we make a significant change, we will update the date at the top and, where appropriate, let you know by email or a notice on the website.

How to reach us

For any privacy question or request, email privacy@cronable.ai, or write to Jefe Digital Pte. Ltd., 2 Havelock Road, #06-01, Havelock II, Singapore 059763. We are the company responsible for your data, and we are happy to help.