Terms of service

These terms govern the use of Regensbot. Regensbot is a product of Ibram & Dawwa GmbH. Regensbot is for businesses only, not for consumers. As of 28 October 2026 (version 2026-10-28).

This is a translation; the German AGB are binding.

§ 1 Scope and parties

(1) These general terms and conditions (AGB) apply to all contracts for the use of Regensbot. This covers the web application at app.regensbot.de, the application programming interface (API) and access through the Model Context Protocol (MCP).

(2) Your contracting party is:

Represented by

Ibrahim Anjro (managing director)

Register court

Amtsgericht Regensburg, HRB 21570

VAT ID

DE454844528

E-mail

info@ibramdawwa-gmbh.de

Phone

+49 1575 1702770

In these terms Ibram & Dawwa GmbH is called "we". The customer is the business (§ 14 BGB) for which an account or an organisation is created in Regensbot. Whoever registers or is invited to an organisation acts as a user on behalf of the customer. The customer is responsible for its users' actions. If the customer is a sole trader, it is itself the user.

(3) The customer's own terms do not apply, even if we do not expressly object to them.

§ 2 Businesses only

(1) Regensbot is open only to businesses (Unternehmer) within the meaning of § 14 BGB. These are natural or legal persons and partnerships with legal capacity that act in the exercise of their trade, business or profession when concluding the contract. Consumers (§ 13 BGB) may not use Regensbot. This also applies to the Free plan.

(2) At registration the customer expressly confirms that it acts as a business and not as a consumer. Whoever creates an account for a business warrants that they may represent it.

(3) For a paid plan the customer gives its VAT identification number when ordering, where our payment provider can check it for the customer's country. We may check the details about business status, also through our payment provider.

§ 3 Conclusion of the contract and proof

(1) The customer registers through a user with an e-mail address and password. In doing so it confirms that it acts as a business, accepts these terms and the AVV and confirms that it has read the privacy notice. An invited person does so when creating their account. If we created an account at the customer's request, this happens when the person sets their password; the account cannot be used before then.

(2) We store which version of these terms and of the privacy notice was accepted (for example "2026-10-28") and the time of acceptance. This serves as proof of the conclusion of the contract.

(3) The contract for the Free plan is concluded when the registration form is sent. API keys, connecting AI assistants and Google, teams and paid plans are available only once the customer has confirmed its e-mail address through the link sent to it. If it does not confirm it within 7 days, we delete the account; this ends the contract.

(4) The customer orders a paid plan in the application under "Billing". Payment runs through the checkout of our payment provider Stripe. There the customer enters its billing address, VAT identification number and payment method and accepts these terms. By completing the checkout the customer makes an offer. We accept it by activating the plan.

(5) The language of the contract is German.

(6) The obligations under § 312i(1) sentence 1 nos. 1 to 3 and sentence 2 BGB do not apply. These terms and the data processing agreement (AVV) are always available at app.regensbot.de/agb and app.regensbot.de/avv and can be saved and printed.

§ 4 Services

(1) Regensbot automatically checks websites against technical and content requirements. The benchmark is the requirements and recommendations for search published by Google. Regensbot shows findings, explains them and helps to fix them.

(2) Depending on the plan, the services include in particular:

• audits of single URLs,
• limited crawls of a website of the customer,
• rendered checks of pages, once this function is in operation,
• checklists, workflows and uploading evidence,
• analysis of server logs of the customer's website,
• access through API keys and through AI assistants connected via MCP.

(3) Some functions are optional. They run only if the customer switches them on. These include the connection with the customer's Google account (Search Console, Merchant Center, BigQuery) and the AI-assisted assessment of content. The AI-assisted assessment is switched off at present.

(4) The functions and limits of each plan are on the pricing page at regensbot.de/preise and in the application under "Billing". The state at the conclusion of the contract or at the last plan change applies.

(5) To connect AI assistants and Google services, the customer uses third-party offerings. Their providers' terms apply. We are not responsible for their availability and behaviour.

(6) We develop Regensbot further and in particular adapt checks when Google changes its requirements. Such changes are permitted if the essential services of the customer's plan are kept. Changes to the essential services of a paid plan apply only under § 18(3).

(7) For the term of the contract the customer receives a simple, non-transferable right to use Regensbot for its own business purposes. It may use the results freely, also for its own clients. The customer may not resell or rent out access to Regensbot or let third parties use it for their own purposes. Customers on the Agency plan may use Regensbot to serve their own clients. They too do not offer access to Regensbot as a product of their own.

§ 5 Free plan

(1) The Free plan costs nothing. It has tighter limits and keeps results for a shorter time than the paid plans.

(2) There is no entitlement to the Free plan beyond these terms. We may change its functions and limits or discontinue it. We announce this in text form at least four weeks in advance.

§ 6 Prices and payment

(1) The prices on the pricing page at the time of the order apply. All prices are net prices plus statutory VAT where it applies.

(2) Paid plans are available with monthly or yearly billing. The price for the whole billing period is due in advance.

(3) Stripe Payments Europe, Limited (Ireland) handles payment. The customer can use the payment methods offered at checkout. We issue invoices electronically through Stripe. The customer finds them in the customer portal.

(4) Only the owner of an organisation in Regensbot can take out, change or cancel its subscription.

(5) We announce a price change for future billing periods in text form at least six weeks before it is to take effect. It applies at the earliest from the first billing period that begins after that. A price increase applies only if the customer expressly agrees to it. After the announcement the customer may terminate the contract at any time with effect from the date the new price is to apply (special right of termination). If the customer does not agree to a price increase, either side may terminate the contract with effect from that date. We point this out in the announcement.

§ 7 Term and termination

(1) The contract for the Free plan runs for an indefinite period. The customer can end it at any time by deleting its account (see § 17). We can terminate it with four weeks' notice.

(2) A paid plan runs for the chosen billing period, one month or one year. It renews automatically for the same period unless cancelled before.

(3) The customer can cancel at any time with effect from the end of the paid billing period. This is done in the customer portal, which it reaches in the application under "Billing". If the customer portal cannot be reached, it can cancel in text form to info@ibramdawwa-gmbh.de. The plan remains usable until the end of the period. After that the organisation is on the Free plan.

(4) We can terminate a paid plan with four weeks' notice to the end of a billing period.

(5) Both sides' right to terminate for cause remains unaffected. Cause for us exists in particular if the customer materially breaches § 11 despite a warning or uses Regensbot to attack third parties.

(6) We do not refund fees already paid, not even pro rata for a partial period. The only exception is where the contract ends before the end of a paid period because either side terminates under § 18(4) or the customer terminates under § 8(3) AVV, or because the customer terminates for a cause for which we are responsible. We then refund the share paid in advance for the time after the end of the contract.

§ 8 Late payment

(1) If a payment fails, Stripe informs the customer and retries the payment.

(2) If a payment due is still outstanding 7 days after the first failure, the organisation is on the Free plan with its functions and limits. Until the first invoice of a subscription is paid, the Free plan applies as well. Stored results and evidence keep their original retention period; older results are only temporarily unavailable. If the outstanding invoice is paid while the subscription still exists, the paid plan applies again.

(3) If the customer is in default, it owes default interest of nine percentage points above the base rate (§ 288(2) BGB) and the lump sum of 40 euros (§ 288(5) BGB). Other statutory rights, in particular termination for cause, remain unaffected.

§ 9 Plan changes

(1) In the customer portal the customer can switch between the paid plans and between monthly and yearly billing. The new plan applies at once. Stripe charges or credits the difference for the current period pro rata.

(2) On a change to a smaller plan or to the Free plan, its limits apply. Results older than the new plan's retention period are no longer shown; we delete them when the period that applied when they were created ends. We delete evidence after the period that applied when it was uploaded. The customer should save results it still needs beforehand (§ 17(1)).

§ 10 Fair use and limits

(1) Every plan has limits, for example for audits per hour and month, concurrent audits, websites, pages per crawl, storage for evidence and team members. The limits are on the pricing page. Monthly quotas apply per calendar month (UTC); unused quotas expire at the end of their period.

(2) Technical limits apply as well. They protect Regensbot and the audited websites. One example is a cap on audits of the same domain across all customers. When a limit is reached, Regensbot temporarily refuses further requests.

(3) The customer may not get around limits. In particular, creating several accounts or organisations only for this purpose is not permitted.

(4) If a use endangers the operation or security of Regensbot or of third parties, we may restrict it at once or block access temporarily. We inform the customer and lift the block as soon as the reason no longer applies.

§ 11 Permitted websites and customer obligations

(1) The customer enters only addresses (URLs) of websites it owns or manages with the owner's permission. It may also have single, publicly accessible pages checked that it may lawfully have checked. It runs crawls, that is fetches of several pages, only for websites it owns or manages with the owner's permission.

(2) Crawls beyond the limit for unverified websites (one manual crawl of at most 25 pages a month), scheduled checks and the AI-assisted assessment require the customer to verify the website in Regensbot. The customer verifies only websites it owns or for which it has the owner's consent.

(3) The customer keeps passwords, API keys and access tokens secret. It does not pass them on to unauthorised persons. If it suspects that an unauthorised person knows them, it revokes them at once in the application and informs us. The customer is responsible for actions taken with its credentials if it is responsible for their misuse.

(4) The customer is responsible for the people it invites to its organisation and for the AI assistants and applications it gives access.

(5) The customer uses Regensbot only within the law. It uploads only content and sends only data that it may use. It is itself responsible for its content.

(6) If the customer has personal data processed, for example server logs with data of visitors to its website or evidence containing names, it needs its own legal basis for this. It ensures that it has one.

(7) In particular, it is not permitted:

• to attack, overload or disrupt Regensbot or third-party websites,
• to circumvent or test Regensbot's security measures without our prior consent,
• to use Regensbot in an automated way other than through the API and MCP provided for this,
• to upload malware or unlawful content.

(8) The customer indemnifies us against all third-party claims arising from it or its users entering addresses contrary to paragraph 1 or 2 or otherwise culpably breaching these obligations. This includes the reasonable costs of legal defence. We inform the customer of such claims without delay.

§ 12 The RegensbotBot crawler

(1) Regensbot fetches pages with the RegensbotBot crawler. It identifies itself with the user agent RegensbotBot/1.0 (+https://app.regensbot.de/bot). Some checks of single URLs repeat a request with the user agent of Googlebot, of Storebot-Google or of a browser. This makes it possible to compare what search engines and visitors are served. These requests come from Regensbot, not from Google.

(2) If a robots.txt excludes RegensbotBot (or its older name SEOAuditorBot) entirely with "Disallow: /", it fetches nothing more from that host except robots.txt, neither in crawls nor in audits of single URLs. Exception: if another address redirects RegensbotBot to that host, the target page is fetched once before the host's robots.txt can be read; Regensbot then does not evaluate it.

(3) In crawls RegensbotBot follows the rules a robots.txt sets for RegensbotBot. In crawls of websites the customer has not verified, it also follows the rules for all crawlers (User-agent: *) when there is no group of its own for RegensbotBot. We treat these rules as a machine-readable reservation of use under § 44b UrhG. Only on the hosts of a website the customer has verified do the rules for all crawlers not apply to RegensbotBot, because the owner itself checks how search engines see its website. If a host's robots.txt cannot be fetched (server error, status code 429 or no answer), RegensbotBot fetches nothing further from that host in crawls unless the host belongs to a website the customer has verified; if it is the host of the start address, the crawl stops.

(4) An audit of a single URL is one fetch the customer requests for that address. It includes the requests needed to check that page, for example robots.txt, sitemaps and the canonical address.

(5) RegensbotBot asks politely. In crawls it makes at most one request per second, for unverified websites at most one request every two seconds. If a website answers with 429 or 503, it stops and waits. Details are on the RegensbotBot page.

(6) Website operators can exclude RegensbotBot or have their domain blocked with us. If a website is excluded, blocked or unreachable, Regensbot cannot check it, or only in part. This is not a defect in our service.

§ 13 Availability and maintenance

(1) We promise no particular availability. There is no service level agreement (SLA) and there are no promised response times.

(2) Regensbot may be temporarily unavailable for maintenance, updates and security measures. Where possible we schedule planned maintenance at times of low use.

(3) We are not responsible for disruptions outside our control, in particular force majeure, disruptions of the internet outside our systems and failures of services the customer itself connects to Regensbot (for example its Google account or its AI assistant).

§ 14 Results and defects

(1) Regensbot's results are automated assessments against published guidance, above all Google's documentation. They are based on the state of this guidance at the time of the check and on the data the customer provides. They may be incomplete or turn out to be wrong.

(2) We owe no particular result. In particular, we promise no rankings, no indexing, no visibility in search engines or AI answers, no growth in visitors and no completeness or correctness of the results. Regensbot does not give legal advice.

(3) The customer decides itself whether and how it changes its websites and is responsible for these changes. It checks results for plausibility before acting on them.

(4) We give no guarantees in the legal sense.

(5) The customer reports defects without delay in text form to info@ibramdawwa-gmbh.de, describing as precisely as possible how the defect shows. We remedy defects within a reasonable time.

(6) Strict liability for defects that already existed when the contract was concluded (§ 536a(1) alt. 1 BGB) is excluded.

§ 15 Liability

(1) We are always liable without limitation

• for intent,
• for injury to life, body or health,
• under the Product Liability Act (Produkthaftungsgesetz),
• if we fraudulently concealed a defect,
• to the extent we expressly gave a guarantee (§ 14(4): we give none).

(2) On the Free plan we are, beyond this, liable only for gross negligence. On the Free plan we are not liable for slight negligence.

(3) On paid plans we are also liable without limitation for gross negligence. For slight negligence we are liable only if we breach an essential contractual obligation (cardinal duty). This is an obligation whose fulfilment makes the proper performance of the contract possible in the first place and on whose observance the customer may regularly rely. Liability is then

• limited to the damage that was typical and foreseeable when the contract was concluded, and
• limited per contract year to the fees the customer paid us in the 12 months before the damaging event.

For slight negligence we are not liable for lost profit, indirect damage or consequential damage.

(4) Otherwise our liability is excluded.

(5) For loss of data we are liable only for the effort that would have been needed to restore it from backups the customer could reasonably have made. The customer saves results it needs itself, for example through the API, through MCP or by downloading them. This does not apply to intent or gross negligence or in the cases of paragraph 1.

(6) These rules also apply to the personal liability of our officers, employees and vicarious agents.

§ 16 Data protection and processing on behalf

(1) How we process personal data as controller, for example account data, is set out in our privacy notice.

(2) The customer is the controller for the pages it has fetched and for the data it connects or uploads (for example data from its Google account, server logs and evidence). We process them as its processor. Our data processing agreement (AVV) under Art. 28 GDPR applies to this. It is part of this contract.

(3) The AVV names the sub-processors we use. We use some of them only when the related optional function is switched on.

§ 17 Account deletion and data at the end of the contract

(1) The customer keeps copies of the results it needs permanently itself. It can retrieve them through the API or MCP, download evidence one file at a time and export its account data as a file. Regensbot is not an archive.

(2) The customer can delete its account in the application at any time. The deletion ends the organisations of which the customer is the only member. A running subscription of these organisations ends at once; there is no pro-rata refund. If the customer is the only owner of an organisation with other members, it must hand the owner role to another member before deleting.

(3) After deletion we lock the account at once. After 30 days we delete it with the related data for good. Copies in backups are deleted within at most 14 more days.

(4) Data we must keep for legal reasons are deleted only when the periods end. We keep invoices and accounting records under commercial and tax law (up to ten years).

(5) If only a paid plan ends, the account continues on the Free plan. § 9(2) then applies.

§ 18 Changes to these terms

(1) We may change these terms and the AVV if there is a valid reason, such as new laws or case law, changed requirements from Google or new functions.

(2) We announce every change in text form at least six weeks before it takes effect, usually by e-mail to the owner of the organisation. The customer may object to the change in text form until then.

(3) Changes to the essential services, the prices or the balance between service and payment take effect only if the customer expressly agrees to them. Silence never counts as agreement to such changes. § 6(5) applies to prices.

(4) Other changes take effect if the customer does not object before they take effect. We point out this consequence, the right to object and the deadline expressly in the announcement. If the customer objects to a change, or does not agree to a change under paragraph 3, the contract first continues on the previous terms. Either side may then terminate it with effect from the date the change was to take effect.

§ 19 Final provisions

(1) The law of the Federal Republic of Germany applies. The UN Convention on Contracts for the International Sale of Goods (CISG) is excluded.

(2) If the customer is a merchant (Kaufmann), a legal person under public law or a special fund under public law, Regensburg is the exclusive place of jurisdiction for all disputes arising from this contract. We may also sue the customer at its general place of jurisdiction.

(3) These terms exist in German and in English. The German version is binding.

(4) If a provision of these terms is invalid, the remaining provisions stay valid. The statutory rules take the place of the invalid provision.