Terms and conditions

Last updated: 23 October 2026

§ 1 Scope

1. These terms and conditions (the "terms") apply to all contracts on the use of the online application Blog Automation (the "service") between Internet am Dornbusch, owner Sajjad Hanifa, Eschersheimer Landstraße 297, 60320 Frankfurt am Main, Germany (the "provider") and its customers.
2. The service is aimed exclusively at businesses within the meaning of § 14 of the German Civil Code (BGB), legal entities under public law and special funds under public law. Consumers within the meaning of § 13 BGB are excluded from use; a consumer right of withdrawal therefore does not exist. By signing up, the customer confirms that it is acting as a business.
3. Deviating or additional terms of the customer only apply if the provider expressly agrees to them in text form.

§ 2 Services of the provider

1. The service helps companies create and edit blog posts and featured images with artificial intelligence (AI), plan topics, review and approve posts in a team and publish them on the customer's WordPress websites: immediately, at a scheduled time or through automations.
2. The scope of each plan follows from the service description and the price list valid at the time of booking, in particular the number of tokens, websites and users.
3. The service supports WordPress only. To connect a website, the customer needs a WordPress website from version 5.6 with HTTPS, a WordPress user with the role Editor (recommended) or Administrator, and an application password. No WordPress plugin is needed.
4. The provider may develop and change the service as long as the agreed scope of services is not significantly reduced and the change is reasonable for the customer.
5. The provider uses service providers to deliver the service, in particular for hosting and for the AI features. § 13 applies to personal data.

§ 3 Sign-up, conclusion of contract and demo

1. The presentation of the service on the website is not a binding offer.
2. To sign up, the customer enters name, company, business e-mail address and a password in the app and accepts these terms and the privacy notice. A contract on the Free plan is concluded when the sign-up is completed; the account can be used at once. The provider sends the customer a link to confirm the e-mail address. Only after this confirmation can the customer invite further team members.
3. The customer books paid plans in the app through the checkout of the payment service provider Stripe (§ 6). The contract on the paid plan is concluded when the checkout is completed successfully.
4. The customer provides true and complete information when signing up and keeps it up to date.
5. The demo can be used without signing up. It works with sample data; the demo AI returns sample texts and uses no tokens. There is no right to the provision of the demo.

§ 4 Plans and prices

1. Prices are in US dollars per month plus statutory VAT. The price list valid at the time of booking applies.
2. The provider may change prices with effect for a future billing period. It announces price changes in text form at least six weeks before they take effect. Running subscriptions keep their price until the change takes effect. The customer may cancel the plan until the change takes effect; the provider points this out in the announcement.

§ 5 Tokens

1. AI actions in the service use tokens. The number of tokens an action costs follows from the price list and is shown before each action. For example, an AI post costs a flat 65 tokens regardless of its length, an AI image 15 tokens and a post with image 80 tokens.
2. If an AI action fails, no tokens are charged for it.
3. In the Free plan, the customer receives 200 tokens every calendar month. Unused tokens of the Free plan expire at the end of the respective calendar month.
4. In the Starter and Pro plans, the customer receives the tokens of the plan per billing period. These tokens are valid for 12 months from being credited. They are credited with every paid invoice for the plan.
5. In every plan, the customer can buy more tokens at any time: 1,000 tokens for $10 plus VAT. Bought tokens are valid for 12 months from being credited.
6. The service always uses the tokens that expire first.
7. After a plan change and after cancelling a paid plan, tokens already credited remain usable until they expire, as long as the contract on the Free plan continues. Tokens have no cash value: they are not paid out, not refunded and cannot be transferred to other accounts. When the contract ends altogether, unused tokens lapse. For plan tokens when the money-back guarantee is used, § 7 (6) applies.
8. If the customer uses its own AI keys in the Pro plan (§ 10), actions run through them use no tokens.

§ 6 Payment and invoices

1. Fees for paid plans are due monthly at the start of each billing period; bought tokens are due on purchase. The amounts are collected in advance from the stored payment method.
2. Payment is processed by the payment service provider Stripe Payments Europe, Limited, Dublin, Ireland ("Stripe"). The payment methods shown in the checkout are available, for example card payment and SEPA direct debit. Stripe's terms apply in addition.
3. The customer receives invoices by e-mail and can download them in Stripe's customer portal, which it opens from the app.
4. If the customer is in default of payment, the provider may block access to the paid features after prior notice in text form and expiry of a reasonable deadline. The obligation to pay remains.

§ 7 Term, plan change and cancellation

1. The contract on the Free plan runs for an indefinite period. Either party may terminate it at any time.
2. Paid plans run for one month each and renew automatically for another month unless cancelled before the end of the current billing period.
3. The customer can book, change or cancel a plan in the app at any time. It can also cancel in text form, for example by e-mail to info@blog-automation.com. A cancellation takes effect at the end of the current billing period; until then, the booked plan remains usable, after that the account is switched to the Free plan. Data is kept.
4. A change to a higher plan (upgrade) takes effect at once. The price difference for the rest of the current billing period is charged pro rata, and the customer receives the additional tokens of the higher plan at once. A change to a lower plan (downgrade) takes effect at the end of the current billing period. If the customer leaves the Pro plan, its own AI keys (§ 10) are paused; they stay stored in encrypted form.
5. Fees already paid are not refunded pro rata on cancellation or downgrade, except in the case of a justified termination for good cause by the customer and in the case of the money-back guarantee under paragraph 6.
6. Money-back guarantee: if the customer books a paid plan (Starter or Pro) for the first time, it may cancel within 30 days of the first payment for that plan without giving reasons by e-mail to info@blog-automation.com and request a refund. The date the e-mail is received is decisive. The provider then refunds the fees the customer paid for the plan during this period, including any upgrade charge, in full to the original payment method. With the refund the paid plan ends at once; the account is switched to the Free plan and the customer's data is kept. Plan tokens credited with the refunded payments lapse with the refund. The guarantee applies once per customer. Bought tokens (§ 5 (5)) are excluded from the guarantee. The money-back guarantee creates a contractual right to a refund; it is not a guarantee of particular properties or results of the service.
7. The right of either party to terminate for good cause remains unaffected.
8. On request, the provider provides the customer with an export of its data, also within 30 days after the end of the contract. The provider deletes the customer's data 30 days after the end of the contract, unless statutory retention obligations apply.

§ 8 AI results and responsibility for published content

1. Texts, images and suggestions of the service are generated automatically by AI models. They may be factually wrong, incomplete, outdated or similar to texts of third parties. The provider gives no guarantee that the results are correct or legally permissible and does not owe any particular search engine ranking or visitor numbers.
2. The customer checks all AI results before publication, including title, description, tags and image alt texts. For this, the service offers an approval workflow and a setting that always sends AI posts to review first (recommended).
3. The customer decides on publication and is responsible for the published content. This includes checking whether labelling obligations apply to the content, for example under Art. 50 of the AI Act (Regulation (EU) 2024/1689), and whether it infringes copyright, trademark, personality or competition law.
4. If the customer sets up automations or chooses the WordPress status "publish" for new posts, the service publishes posts according to these settings. The customer is responsible for the settings.

§ 9 Obligations of the customer

1. The customer keeps its login details secret. It gives team members only the rights they need and is responsible for actions in its account.
2. The customer only connects WordPress websites it is entitled to connect. It uses a WordPress user with the necessary rights (recommended: Editor) and can revoke the application password in WordPress at any time. The customer itself is responsible for backups of its WordPress website.
3. The customer does not enter or publish content that violates applicable law or the rights of third parties. It only enters personal data of third parties where it is entitled to do so.
4. The customer refrains from anything that impairs the function or security of the service, in particular circumventing technical limits, introducing malicious code and automated mass requests outside the intended functions.
5. If the customer breaches these obligations, the provider may block the content concerned or temporarily restrict access. It takes the customer's legitimate interests into account and informs the customer without delay.
6. The customer indemnifies the provider against third-party claims based on a culpable breach of these obligations, including reasonable costs of legal defence.

§ 10 Own AI keys (Pro plan)

1. In the Pro plan, the customer can store its own API keys from OpenAI, Anthropic (Claude), Google (Gemini) or OpenAI-compatible providers (for example Mistral or OpenRouter). The service stores the keys encrypted.
2. Actions run through an own key are carried out by the respective AI provider under the contract the customer has concluded with it. The customer is responsible for that contract, its costs and terms, and any data processing agreement it requires.
3. With keys from Anthropic (Claude) and OpenAI-compatible providers, the service does not create images.

§ 11 Rights to content and to the service

1. Content the customer brings into the service remains the customer's content. The customer grants the provider the non-exclusive right to store and process it, to transmit it to the AI providers used and to publish it on the customer's WordPress websites, to the extent necessary to provide the service.
2. The provider claims no rights to AI results. Where the provider holds rights to results, it grants the customer a non-exclusive right of use, unlimited in time and place. The provider does not warrant that AI results are protected by copyright or free of third-party rights.
3. For the term of the contract, the customer receives the non-exclusive, non-transferable right to use the service within the scope of its plan.

§ 12 Availability

1. The provider aims for the service to be available with as few interruptions as possible. It only owes a specific availability if this has been expressly agreed.
2. The provider carries out maintenance work at times of low usage where possible.
3. The service depends on services of third parties, in particular the AI providers and the hosting of the customer's WordPress website. The provider is not responsible for disruptions outside its control, for example when a security plugin or the customer's server blocks the connection to WordPress.

§ 13 Data protection and data processing on behalf

1. For personal data the customer processes in the service, the customer is the controller within the meaning of the GDPR; the provider processes it as a processor. In every plan, the data processing agreement under Art. 28 GDPR applies. It is part of this contract and is deemed concluded on sign-up; no signature is needed. On request, the customer receives a copy for its records via support; the request can also be made in the app under Settings, Privacy.
2. The sub-processors used are listed on the page sub-processors.
3. Otherwise, the privacy policy applies.

§ 14 Liability

1. The provider is liable without limitation for intent and gross negligence, for injury to life, body or health, under the German Product Liability Act and to the extent of any guarantee given.
2. In the case of slight negligence, the provider is only liable for the breach of essential contractual obligations, i.e. obligations whose fulfilment makes the proper performance of the contract possible in the first place and on whose observance the customer may regularly rely. In this case, liability is limited to the foreseeable damage typical for the contract at the time it was concluded.
3. Strict liability for defects that already existed when the contract was concluded (§ 536a (1) alt. 1 BGB) is excluded.
4. For loss of data, the provider is only liable to the extent that the damage would also have occurred if the customer had backed up its data properly.
5. In the Free plan and the demo, the provider is only liable for intent and gross negligence, except in the cases of paragraph 1.
6. These limitations also apply to the provider's legal representatives, employees and vicarious agents.

§ 15 Changes to these terms

1. The provider may change these terms with effect for the future if there is a valid reason, such as a change in the law or the further development of the service, and the balance between performance and consideration is not shifted significantly to the customer's disadvantage.
2. The provider announces changes in text form at least six weeks before they take effect. If the customer does not object before they take effect, the changes are deemed accepted. The provider points out the right to object and the consequences of silence in the announcement. If the customer objects, either party may terminate the contract as of the date the changes take effect.

§ 16 Final provisions

1. The law of the Federal Republic of Germany applies, excluding the UN Convention on Contracts for the International Sale of Goods.
2. If the customer is a merchant, a legal entity under public law or a special fund under public law, the exclusive place of jurisdiction for all disputes arising from this contract is Frankfurt am Main. The provider may also sue the customer at its general place of jurisdiction.
3. Changes and additions to the contract require text form.
4. If a provision of these terms is invalid, the remaining provisions remain valid. The statutory provision replaces the invalid provision.
5. The German version of these terms is authoritative. The English version is for information only.