Privacy Policy

We are very pleased about your interest in our company. Data protection has a particularly high priority for the management of cronjob.de. Use of the cronjob.de website is generally possible without providing any personal data. However, if a data subject wants to use special services of our company via our website, processing of personal data may be necessary. If the processing of personal data is necessary and there is no legal basis for such processing, we generally obtain the consent of the data subject.

The processing of personal data, such as the name, address, email address, or telephone number of a data subject, is always carried out in accordance with the General Data Protection Regulation (GDPR) and in compliance with the country-specific data protection regulations applicable to cronjob.de. By means of this privacy policy, our company wishes to inform the public about the type, scope, and purpose of the personal data we collect, use, and process. Furthermore, data subjects are informed of their rights by means of this privacy policy.

As the controller, cronjob.de has implemented numerous technical and organizational measures to ensure the most complete protection possible for personal data processed through this website. Nevertheless, Internet-based data transmissions can generally have security vulnerabilities, so absolute protection cannot be guaranteed. For this reason, every data subject is free to transmit personal data to us by alternative means, for example by telephone.

1. Definitions

The privacy policy of cronjob.de is based on the terminology used by the European legislator when adopting the General Data Protection Regulation (GDPR). Our privacy policy should be easy to read and understand for the general public as well as for our customers and business partners. To ensure this, we would like to explain the terminology used in advance.

In this privacy policy, we use the following terms, among others:

2. Name and address of the controller

The controller within the meaning of the General Data Protection Regulation, other data protection laws applicable in the Member States of the European Union and other provisions of a data protection nature is:

cronjob.de

Prager Str. 5

60437 Frankfurt am Main

Germany

Email: joscha@schultze.cc

Website: www.cronjob.de

3. Cookies and similar technologies

We only use cookies that are technically necessary to operate this website. Under Section 25 (2) no. 2 of the German TDDDG, no consent is required for these. The related processing is based on Art. 6 (1) (b) GDPR (customer area and contract) and Art. 6 (1) (f) GDPR (secure operation). We do not use cookies for statistics, advertising or tracking.

You can delete or block cookies in your browser at any time. Without the session cookie, however, you cannot sign in to the customer area.

4. Collection of general data and information

The cronjob.de website collects a series of general data and information with each access to the website by a data subject or automated system. This general data and information is stored in the server log files. The following may be collected: (1) browser types and versions used, (2) the operating system used by the accessing system, (3) the website from which an accessing system reaches our website (so-called referrers), (4) the sub-websites that are accessed via an accessing system on our website, (5) the date and time of access to the website, (6) an Internet Protocol address (IP address), (7) the Internet service provider of the accessing system and (8) other similar data and information used for security purposes in the event of attacks on our information technology systems.

When using this general data and information, cronjob.de does not draw any conclusions about the data subject. Rather, this information is needed to (1) deliver the contents of our website correctly, (2) optimize the content of our website, (3) ensure the long-term functionality of our information technology systems and the technology of our website, and (4) provide law enforcement authorities with the information necessary for prosecution in the event of a cyber attack. Therefore, cronjob.de analyzes anonymously collected data and information on one hand statistically and on the other hand with the aim of increasing data protection and data security in our company to ultimately ensure an optimal level of protection for the personal data we process. The anonymous data of the server log files are stored separately from any personal data provided by a data subject.

5. Registration on our website

The data subject has the possibility to register on the website of the controller by providing personal data. Which personal data are transmitted to the controller is determined by the respective input mask used for the registration. The personal data entered by the data subject are collected and stored exclusively for internal use by the controller and for his own purposes. The controller may arrange for the transfer to one or more processors, for example a parcel service provider, who also uses the personal data exclusively for an internal use attributable to the controller.

By registering on the website of the controller, the IP address assigned by the Internet service provider (ISP) of the data subject, the date and time of registration are also stored. The storage of this data takes place against the background that only in this way can the misuse of our services be prevented and, if necessary, this data makes it possible to clarify committed crimes. In this respect, the storage of this data is necessary for the protection of the controller. As a matter of principle, this data is not passed on to third parties unless there is a legal obligation to pass it on or the passing on serves criminal prosecution.

The registration of the data subject with voluntary provision of personal data serves the controller to offer the data subject content or services which, due to the nature of the matter, can only be offered to registered users. Registered persons are free to modify the personal data provided during registration at any time or to have it completely deleted from the database of the controller.

The controller shall provide any data subject at any time upon request with information about which personal data about the data subject are stored. Furthermore, the controller shall correct or delete personal data at the request or notice of the data subject, insofar as this does not conflict with any statutory retention obligations. A data protection officer named in this privacy policy and the entirety of the controllers employees are available to the data subject as contact persons in this context.

6. Contact possibility via the website

Due to legal regulations, the cronjob.de website contains information that enables quick electronic contact with our company and direct communication with us, which also includes a general address for so-called electronic mail (email address). If a data subject contacts the controller by email or via a contact form, the personal data transmitted by the data subject are automatically stored. Such personal data transmitted on a voluntary basis by a data subject to the controller are stored for the purpose of processing or contacting the data subject. This personal data is not passed on to third parties.

7. Routine deletion and blocking of personal data

The controller processes and stores personal data of the data subject only for the period necessary to achieve the storage purpose or insofar as this is provided for by the European Directive and Regulation maker or another legislator in laws or regulations to which the controller is subject.

If the storage purpose ceases to apply or if a storage period prescribed by the European Directive and Regulation maker or another competent legislator expires, the personal data is routinely blocked or deleted in accordance with the statutory provisions.

Specifically at Cronjob.de: free accounts in which for three years nobody has signed in and nothing has been paid, and in which no cronjob, heartbeat or server monitor is active any more, are deleted together with their cronjobs, folders and history. Registrations that were never confirmed are deleted after 30 days. Invoices and payment records are kept until the end of the statutory retention period (currently eight years after the end of the calendar year) and deleted afterwards.

8. Rights of the data subject

9. Legal basis for processing

Article 6(1)(a) GDPR serves as the legal basis for our company for processing operations where we obtain consent for a specific processing purpose. If the processing of personal data is necessary for the performance of a contract to which the data subject is party, as is the case, for example, when processing operations are necessary for the supply of goods or to provide any other service, the processing is based on Article 6(1)(b) GDPR. The same applies to such processing operations which are necessary for carrying out pre-contractual measures, for example in the case of inquiries concerning our products or services. If our company is subject to a legal obligation by which processing of personal data is required, such as for the fulfillment of tax obligations, the processing is based on Article 6(1)(c) GDPR. In rare cases, the processing of personal data may be necessary to protect the vital interests of the data subject or of another natural person. This would be the case, for example, if a visitor were injured in our company and his name, age, health insurance data or other vital information would have to be passed on to a doctor, hospital or other third party. Then the processing would be based on Article 6(1)(d) GDPR. Finally, processing operations could be based on Article 6(1)(f) GDPR. This legal basis is used for processing operations which are not covered by any of the above-mentioned legal grounds, if processing is necessary for the purposes of the legitimate interests pursued by our company or by a third party, except where such interests are overridden by the interests or fundamental rights and freedoms of the data subject. Such processing operations are particularly permissible because they have been specifically mentioned by the European legislator. He considered that a legitimate interest could be assumed if the data subject is a client of the controller (Recital 47 Sentence 2 GDPR).

10. The legitimate interests pursued by the controller or by a third party

Where the processing of personal data is based on Article 6(1)(f) GDPR our legitimate interest is to carry out our business activities in favor of the well-being of all our employees and shareholders.

11. Period for which the personal data will be stored

The criteria used to determine the period of storage of personal data is the respective statutory retention period. After expiration of that period, the corresponding data is routinely deleted, as long as it is no longer necessary for the fulfillment of the contract or the initiation of a contract.

12. Provision of personal data as statutory or contractual requirement; Requirement necessary to enter into a contract; Obligation of the data subject to provide the personal data; possible consequences of failure to provide such data

We clarify that the provision of personal data is partly required by law (e.g. tax regulations) or can also result from contractual provisions (e.g. information on the contractual partner). Sometimes it may be necessary to conclude a contract that the data subject provides us with personal data, which must subsequently be processed by us. The data subject is, for example, obliged to provide us with personal data when our company enters into a contract with him or her. The non-provision of the personal data would have the consequence that the contract with the data subject could not be concluded. Before personal data is provided by the data subject, the data subject must contact our data protection officer. Our data protection officer clarifies to the data subject whether the provision of the personal data is required by law or contract or is necessary for the conclusion of the contract, whether there is an obligation to provide the personal data and the consequences of non-provision of the personal data.

13. AI assistance for scheduling

On the crontab generator page and when creating a cronjob in the customer area, you can describe the schedule you want in your own words instead of assembling it yourself. If you use this option, we transmit only the sentence you entered to the service OpenRouter, Inc., which has a language model translate it into a crontab expression. This processing also takes place on servers outside the European Union.

We do not transmit your name, email address, account number, the address your cronjob calls, or any other details from your account. The sentence is cached by us for 30 days so that the same input does not have to be transmitted again; this cache contains no reference to you or your account. To limit abusive use we additionally store, for at most three days, an irreversible numeric value derived from your IP address together with the number of requests.

Use of this feature is voluntary. You can always assemble the schedule by clicking instead, or type it as a crontab expression; in that case no information leaves our servers. The legal basis for the processing is Art. 6(1)(f) GDPR, our legitimate interest in comprehensible operation, and for signed-in users Art. 6(1)(b) GDPR for the performance of the usage contract.

The execution of your cronjobs themselves is not affected. It continues to take place exclusively on our servers within the European Union.

14. Existence of automated decision-making

As a responsible company, we do not use automatic decision-making or profiling.

15. Service providers and recipients

We use the following service providers to operate our service. Where they act on our behalf, a data processing agreement under Art. 28 GDPR is in place.

16. Heartbeat check-ins (runcheck.de)

With a heartbeat we monitor cron jobs and other tasks that run on your own systems. Your server reports each run to its own address at runcheck.de; if an expected check-in does not arrive or reports a failure, we notify you. A cron job that we call can also report the end of its run through such an address (end signal). This processing serves the performance of the contract for the use of Cronjob.de; the legal basis is Art. 6 (1) (b) GDPR.

We process the time of each check-in and the IP address of the reporting server. If, at your choice, your server sends output via POST, we store up to 10 KB of it. If it also reports the start of a run (/start), we calculate the runtime from it. The output is meant for status messages of your script – please do not include any personal data in it.

Check-ins, including any output sent along, reach us like every request to our website via Cloudflare, Inc., which provides the network connection for us as a processor (section 15). In the process, Cloudflare processes the IP address of the reporting server and the technical data of the request, possibly also outside the EU, on the basis described there.

We store check-ins like the call log of your cron jobs: the last 20 check-ins per heartbeat with time, IP address and output. Each new check-in replaces the oldest one; for older check-ins the output is shortened to 500 characters. For the history of recent weeks we additionally keep the number of check-ins, error periods and runtimes per day, without IP address and without output: 30 days on the Plus plan, 90 days on the Unlimited plan and during the trial. On the Unlimited plan and during the trial we also keep time, duration and size of the last 200 check-ins for the runtime statistics. When you delete a heartbeat or your account, this data is deleted as well.

End-signal check-ins are kept at most 20 times per cron job and for at most one month, with IP address and up to 400 characters of output. Like every request to our website, a check-in is also recorded in the web server log files (section 4).

17. Status pages (status.cronjob.de)

At status.cronjob.de we show the status of our own service. Customers on the Unlimited plan can also publish their own status pages there, showing the availability of their websites, cron jobs and heartbeats. The customer alone decides which entries, names, logo and link appear and is responsible for this content. We only show states, shares and points in time, no addresses and no error texts.

Status pages set no cookies and load no third-party content. When you open one, we process your IP address and the technical data of the request in the web server log files, as with every visit to our website (section 4); the pages run through Cloudflare, Inc. (section 15). Legal basis is Art. 6(1)(f) GDPR (secure operation).

An uploaded logo is stored in reduced size on our servers until the customer replaces it or deletes the status page or the account. A deleted status page is no longer reachable immediately; we keep its address reserved for the account for 90 days.

This privacy policy was generated by the privacy policy generator of DGD Deutsche Gesellschaft für Datenschutz GmbH, which operates as External Data Protection Officer Duisburg, in cooperation with the Cologne IT and data protection lawyer Christian Solmecke.