Skip to content
cronpad

cronpad / terms

terms of service

Last updated

Thank you for using cronpad! We built it so scheduled jobs run on time, every time. Since cronpad Cloud sends requests to the internet on your behalf and we don’t know every customer personally, we need some terms to keep things running smoothly.

When we say “cronpad”, “we”, “our” or “us” in this document, we mean the people who build and operate cronpad.

When we say “Services”, we mean cronpad Cloud, the hosted service at app.cronpad.com, including its dashboard, API, MCP server and anything else we run for you there.

When we say “you” or “your”, we mean the people or organisations that have an account or workspace on the Services.

These terms do not cover cronpad’s source code. If you self-host cronpad, the software is governed by its license, not by these terms.

We may update these terms in the future. The date at the top shows the last change; usually changes clarify a term or link to a related policy. When we make a significant change, we will email active customers before it takes effect.

When you use the Services, now or in the future, you agree to the latest terms. That’s true for all features we add over time. If we don’t exercise or enforce a right or provision of these terms, we have not waived it. These terms contain a limitation of our liability.

If you break these terms, we may close your account. That’s a broad statement, and it means you need to place a lot of trust in us. We try to earn that trust by building cronpad in the open, publishing how it works, and keeping an open door to your feedback.

Account terms

  1. You are responsible for keeping your account secure, including your GitHub or Google account and any API keys you create. We cannot and will not be liable for any loss or damage from your failure to do so.
  2. You may not use the Services for any of the restricted uses below.
  3. You are responsible for all activity in your workspaces, including activity by members you invite and by anyone using your API keys.
  4. You must be a human. Accounts registered by bots or other automated methods are not permitted. Once you have an account, you’re welcome to automate it through the API, CLI and MCP server.
  5. You must be at least 16 years old, or the minimum age required to consent to data processing where you live.

Your jobs and the requests we send

  1. Your workspace content — jobs, schedules, requests, secrets and run history — belongs to you. You give us permission to store and process it only to provide the Services to you.
  2. When your jobs run, we send the requests you configured to the endpoints you configured. You are responsible for having permission to call those endpoints at the rate you schedule them, and for what those requests do.
  3. You are responsible for the data you put in requests, headers and secrets, and for having the right to send it.
  4. To protect the Services and the wider internet, we block requests to private and internal network addresses, and we may limit request rates, response sizes and timeouts. Current limits are on the limits page.

Payment, refunds and plan changes

  1. If you use the Free plan, it really is free: we don’t ask for a card, and — just as for paying customers — we don’t sell your data. Free workspaces have the limits listed on our editions page.
  2. Paid plans are billed in advance each month. Usage beyond what your plan includes, such as extra runs, is billed in arrears at the published rate. You can set a spend cap to limit those charges.
  3. If you upgrade from Free to a paid plan, we charge you immediately and your billing cycle starts that day. For other plan changes, the new price applies from the next billing cycle.
  4. If a payment fails, we’ll email you and retry. If it still fails, your workspace moves to the Free plan’s limits until you pay. A billing problem never deletes your jobs.
  5. All fees are exclusive of taxes, levies and duties. Where required, we collect them on behalf of the taxing authority. Otherwise, you are responsible for them.
  6. If you think we charged you by mistake, email contact@cronpad.com within 30 days of the charge and we’ll make it right.

Cancellation and termination

  1. You are responsible for cancelling your plan or deleting your account. You can downgrade to Free or delete your workspace from its settings at any time, no questions asked. An email asking us to cancel does not by itself cancel your plan, but we’re happy to help.
  2. If you cancel a paid plan before the end of the current billing cycle, it stays active until the end of that cycle and you won’t be charged again.
  3. When you delete your account or a workspace, its jobs stop and its content is no longer accessible. Within 30 days it is permanently deleted from our active systems, and from backups within a further 30 days. We cannot recover it once it is deleted.
  4. We may suspend or terminate your account and refuse current or future use of the Services at any time, for any reason. Suspension means you and your workspace members cannot use the account and its jobs do not run. Termination also means your account and its content are deleted. We have this clause because, statistically, someone will try to use the Services for something harmful, and this is how we stop them. For details, see restricted uses.
  5. Verbal, physical, written or other abuse (including threats of abuse or retribution) of anyone working on cronpad will result in immediate termination.

Modifications to the Services and prices

  1. We may change or discontinue, temporarily or permanently, any part of the Services, for example when a feature becomes impossible to maintain or we find a better design. If we remove something you rely on, we’ll email you first.
  2. We may change our prices. When we do, we usually keep existing customers on their current price. If we change the price for existing customers, we’ll give at least 30 days’ notice by email and may also post it on our website or in the dashboard.

Uptime, security and privacy

  1. Your use of the Services is at your own risk. We provide them “as is” and “as available”. The Pro plan has a published on-time objective, but no service credits; see delivery guarantees. We take reliability seriously: measuring whether jobs run on time is the point of cronpad.

  2. We may temporarily limit or disable a workspace whose usage significantly exceeds that of other customers on the same plan. We’ll contact the workspace owner first, except in the rare cases where the usage is hurting the Services for other customers.

  3. We protect your data with encryption, backups and access controls. Traffic to the Services is always encrypted. Requests your jobs send are encrypted when the target URL uses https://; plain http:// targets are sent unencrypted because you chose them.

  4. When you use the Services, you trust us with your data, and we take that seriously. You agree that cronpad may process your data as described in our privacy policy, and for no other purpose. People at cronpad may access your data only:

    • To help you with a support request — we’ll ask for your consent before looking inside your workspace.
    • When an error stops an automated process partway through — we get alerts for these. If we can fix the issue without looking at personal data, we do. In rare cases, we need to look at a minimum of it. We then work on the root cause so it doesn’t happen again.
    • To keep cronpad safe — we look at logs and metadata to keep the Services and your data secure, and may access an account while investigating an abuse report.
    • When the law requires it — see our privacy policy.

  5. We use third-party vendors and hosting partners for the hardware, software, networking, storage and related technology needed to run the Services. See the list of subprocessors that handle personal data.

  6. Under the California Consumer Privacy Act (“CCPA”), cronpad is a “service provider”, not a “business” or “third party”, with respect to your use of the Services. We process the data you share with us only for the purpose you signed up for, as described in these terms and our privacy policy. We do not retain, use, disclose or sell it for any other commercial purpose without your explicit permission. In turn, you agree to meet your own obligations under the CCPA and not to use the Services in a way that violates it.

Limitation of liability

To the maximum extent the law allows, cronpad will not be liable for any indirect, incidental, special, consequential or punitive damages, or any loss of profits, revenue, data or goodwill, arising from your use of, or inability to use, the Services — including missed, late or duplicate runs. Our total liability for any claim relating to the Services is limited to the amount you paid us in the 12 months before the claim.

Restricted uses

We’re proud to offer a service that helps people run their work on time. We also know that, however good the maker’s intentions, technology can amplify the ability to cause harm. A scheduler that sends requests on a timer is easy to point at someone else. So if you have an account, you may not use it for any of the purposes below. If we find out you are, we’ll get in touch to understand what’s happening. If we’re not satisfied, we’ll stop your jobs and close your account.

  • Attacking or overloading systems — No denial-of-service attacks, flooding, or sending requests at a rate or volume meant to degrade a service, whether it’s yours or someone else’s.
  • Unauthorised access or scanning — Don’t use cronpad to probe, scan, brute-force or exploit systems you don’t own or have explicit permission to test.
  • Abusing other services — No scraping or automated requests that break the target’s terms, rate limits or access controls, and no fake sign-ups, votes, clicks or reviews.
  • Spam — No sending unsolicited messages, through any channel, via jobs or alerts. If it doesn’t pass muster with CAN-SPAM or any other anti-spam law, it’s not allowed.
  • Malware or spyware — Code for good, not evil. You may not use cronpad to control, distribute or communicate with malware, spyware or botnets, including remote surveillance of people.
  • Evading our limits — No creating multiple accounts or workspaces to get around plan limits, or trying to bypass our network protections, such as the block on private addresses.
  • Violence, or threats of it — If an activity counts as a violent crime where you live, you may not use cronpad to plan, carry out or threaten it.
  • Child exploitation, sexualisation or abuse — We don’t tolerate any activity that creates, distributes or otherwise causes child abuse.
  • Hate speech — You may not use cronpad to advocate for the extermination, domination or oppression of people.
  • Harassment and doxing — No intimidating or targeting people through repeated communication, and no sharing other people’s private information to harass them.
  • Phishing or fraud — It is not okay to lie about who you are or who you’re affiliated with in order to steal from, extort or otherwise harm others.
  • Infringing intellectual property — You may not use cronpad to make or distribute work that uses others’ intellectual property beyond the bounds of fair use.

These restrictions are broad, but they can’t be exhaustive: an offence may defy categorisation or be something we haven’t thought of yet. We hope the spirit is clear — cronpad is not to be used for harm, whether mental, physical, personal or civic.

How to report abuse

If you think a cronpad job is sending requests to your systems that you didn’t ask for, or you suspect any other restricted use, email contact@cronpad.com. If you’re not sure whether something counts, report it anyway.

Share as much as you’re comfortable with: the requests you saw (times, URLs, headers such as User-Agent, and source IP addresses) and how they affect you. We will not disclose your identity to anyone associated with the reported account. We’ll reply within two business days to tell you we’ve started investigating, and we’ll let you know the outcome (unless you ask us not to, or the law doesn’t allow it).

If you have a question about any of these terms, please contact us.