Sacred Byte GmbH · Effective: 2 July 2026 · Version 1.4 (English convenience translation — the German version is authoritative, see § 17)
These General Terms and Conditions (“GTC”) form a single agreement between Sacred Byte GmbH (“Sacred Byte”) and the customer. The agreement consists of two parts. Part I (§§ 1–19) sets out the general provisions that apply to every engagement. Part II (§§ 20–21) sets out additional provisions that apply only to the specific engagement model designated in the offer or order confirmation — project engagements (§ 20) or managed services (§ 21). The offer or order confirmation, together with these GTC, forms the entire agreement between the parties.
PART I — GENERAL PROVISIONS
1.1 These GTC apply to all contracts between Sacred Byte and its customers concerning the provision of IT and security services, including endpoint management, security operations, compliance support, project work and managed IT services.
1.2 These GTC apply exclusively to entrepreneurs, legal entities under public law and special funds under public law within the meaning of § 310 (1) BGB (German Civil Code).
1.3 Conflicting or deviating terms of the customer are not accepted unless Sacred Byte has expressly agreed to their validity in writing. These GTC also apply if Sacred Byte provides services without reservation despite being aware of conflicting or deviating customer terms.
1.4 The contract between Sacred Byte and the customer is formed by either
(a) written or electronic (email) confirmation of an offer or order confirmation by the customer, or
(b) actual commencement of services by Sacred Byte with the customer’s knowledge and without immediate objection, provided that the scope of services has been mutually agreed in advance.
1.5 The written form requirement under these GTC is also satisfied by email, provided the message is sent by an authorised person.
2.1 The specific scope of services is set out in the respective offer or order confirmation. Sacred Byte renders the agreed services with the care of a diligent IT service provider.
2.2 Unless expressly agreed otherwise, Sacred Byte owes the professional performance of the service (service contract within the meaning of §§ 611 et seq. BGB) and does not owe a specific result.
2.3 Sacred Byte is entitled to engage qualified subcontractors for the performance of services. Sacred Byte will bind such subcontractors to corresponding confidentiality and data-protection obligations and remains responsible to the customer for their performance.
2.4 Sacred Byte undertakes to perform only reasonable and meaningful work, to work efficiently, and to keep costs for the customer as low as possible without compromising quality.
3.1 The customer shall provide Sacred Byte with all information, access and resources necessary for the performance of services in a timely and complete manner.
3.2 The customer shall designate a responsible contact person and a deputy.
3.3 The customer is responsible for the regular backup of its own data unless data backup has been expressly commissioned as a service. Where data backup has been expressly commissioned as a service, the customer remains co-responsible for periodically verifying the integrity and recoverability of the backups.
3.4 The customer warrants that the software and IT infrastructure it provides is properly licensed and meets the minimum requirements set out in the offer.
3.5 The customer shall report problems or concerns to Sacred Byte’s support team in a timely manner.
3.6 Delays or additional effort caused by late or incomplete customer cooperation shall not be borne by Sacred Byte. Specific consequences for customer-caused timeline overruns in project engagements are set out in § 20.8.
4.1 The response and resolution times set out below are Sacred Byte’s standard service levels and are included in the rates set out in the offer. They apply to every engagement unless the offer or order confirmation specifies different or enhanced service levels (for example faster response times, extended coverage hours, or 24/7 coverage), which may be agreed in the offer as an upgrade. The standard levels represent the minimum service expectation included in the standard rates; they do not include dedicated standby or on-call capacity, which requires an enhanced service level agreed and priced in the offer.
| Severity | Description | Response time | Resolution time* |
|---|---|---|---|
| Critical | Security incident or data breach immediately endangering customer data | within 24 hours | within one business day |
| Standard | Significant security gap or unauthorised access requiring containment | within 48 hours | within two business days |
| Low | General security questions or implementation requests without acute risk | within 72 hours | within five business days |
* Technical and security-related incidents may partly lie outside Sacred Byte’s control (e.g. third-party vulnerabilities). Sacred Byte supports with best effort and clear risk-mitigation guidance. For the purposes of this § 4, “resolution” means containment of the incident or provision of a workaround that restores safe operation; full system restoration, root-cause analysis and forensics are not covered by the resolution times and may take longer. Resolution times are target values, not guaranteed results. In break/fix situations in which Sacred Byte has limited information about, or limited control over, the affected systems, the times above apply to the response only.
4.2 Customers may report incidents via email at support@sacredbyte.com or by phone at +49-30-44 050 823.
4.3 Scheduled maintenance is generally performed outside business hours (typically after 7 pm local time). Emergency maintenance may also be required during business hours and will, where possible, be coordinated with the customer.
4.4 Systems outside Sacred Byte’s control. Where systems, services, applications or data are not under Sacred Byte’s technical control — in particular third-party cloud, SaaS or vendor-managed software — Sacred Byte cannot guarantee the availability, integrity or completeness of backups, nor the full or partial restoration of operations, and the service levels under § 4.1 do not apply to such systems. In these cases, and in any incident affecting them (including where a third-party account is compromised), Sacred Byte’s obligation is limited to best-effort mitigation and risk-mitigation guidance within the agreed scope of services. Specialist services that go beyond the agreed scope — in particular digital forensics, legal counsel, crisis or public-relations communications, and third-party data-recovery or cloud specialists — are not included and require separate commissioning.
5.1 The applicable rates are set out in the respective offer or order confirmation. All amounts are net plus statutory VAT.
5.2 Surcharges. Unless otherwise expressly stated in the offer:
5.3 Travel:
5.4 Scheduled maintenance. Scheduled maintenance windows performed outside core hours that form part of the agreed regular scope of services (in particular under a Managed Service) are not subject to the surcharges in § 5.2.
5.5 Business hours. Business hours are weekdays 10:00–18:00 unless otherwise agreed in the offer.
5.6 Additional effort. Effort beyond the scope agreed in the offer requires prior customer approval and is billed at the hourly rate specified in the offer.
6.1 The remuneration is set out in the respective offer or order confirmation. All prices are net plus statutory VAT.
6.2 Billing model. Invoicing is performed either
(a) on a monthly cadence (default for time-and-material and Managed Service engagements), or
(b) on milestone completion, where the offer defines specific milestones. In the milestone model, Sacred Byte issues an invoice upon completion of each milestone as specified in the offer; milestone acceptance is governed by § 20.4.
6.3 For time-based services, only actually rendered hours are invoiced. Estimates in the offer serve as guidance and as a cost ceiling per checkpoint. Effort that materially exceeds the estimates specified in the offer requires prior customer approval.
6.4 Invoices issued on a monthly cadence are issued, in general, by the 7th of the following month. Milestone invoices are issued upon completion of the relevant milestone. Payment is due within fourteen (14) days of the invoice date, without deduction.
6.5 Payments are made by bank transfer to the account specified in the invoice or by any other method agreed between the parties.
6.6 In the event of late payment, default interest at the statutory rate for commercial transactions of nine (9) percentage points above the base rate of the Deutsche Bundesbank (§ 288 (2) BGB) is charged, plus the statutory lump sum of € 40.00 (§ 288 (5) BGB). The right to claim further damages caused by default remains reserved. Suspension of services for prolonged non-payment is governed by § 7.
7.1 If the customer fails to pay an undisputed amount within thirty (30) calendar days of the due date, Sacred Byte is entitled, after a written reminder, to suspend
7.2 During a suspension:
7.3 Sacred Byte will lift the suspension within one (1) business day after receipt of all outstanding amounts including default interest and any reasonable reactivation fee.
7.4 If the default persists for more than sixty (60) calendar days from the start of the suspension, Sacred Byte may terminate the contract for good cause with immediate effect, without prejudice to further claims.
7.5 Statutory rights of retention, in particular pursuant to § 320 BGB, remain unaffected.
8.1 Both parties undertake to treat all confidential information and data of the other party that becomes known in the course of cooperation as confidential, to use it exclusively for the purpose of contract performance and to protect it against unauthorised third-party access.
8.2 This obligation does not apply to information that (a) is already publicly known, (b) was demonstrably already known to the receiving party, or (c) must be disclosed by legal or official order.
8.3 The confidentiality obligation survives termination of the contract for a period of three (3) years.
9.1 Sacred Byte processes personal data in accordance with the EU General Data Protection Regulation (GDPR) and the German Federal Data Protection Act (BDSG), confidentially and for the agreed purpose only.
9.2 Insofar as Sacred Byte processes personal data on behalf of the customer in the performance of services, the parties shall enter into a separate data-processing agreement under Art. 28 GDPR upon the customer’s request.
9.3 Sacred Byte is entitled to engage sub-processors for the performance of services. Such sub-processors will be bound to corresponding confidentiality and data-protection obligations.
9.4 Deletion of personal data at the end of the contract is governed by § 18.
10.1 All security policies, checklists, concepts and documentation created by Sacred Byte in the course of cooperation may be used exclusively internally by the customer.
10.2 Any disclosure to third parties (except professional advisors and auditors who are bound by statutory or contractual confidentiality obligations and do not compete with Sacred Byte, or authorities to whom disclosure is required by law) requires Sacred Byte’s prior written consent.
10.3 Existing intellectual property rights and know-how brought into the performance of services by Sacred Byte remain with Sacred Byte.
11.1 Notwithstanding the service-contract character of the engagement (§ 2.2), Sacred Byte will rectify defects in its deliverables within a reasonable time at no additional cost to the customer, provided the customer notifies Sacred Byte of the defect in writing without undue delay and grants Sacred Byte adequate access and information to perform the rectification.
11.2 To the extent that an engagement, in particular a milestone-based project engagement, is qualified as a work contract (Werkvertrag) within the meaning of §§ 631 et seq. BGB, Sacred Byte is entitled to two (2) rectification attempts before the customer may exercise further statutory remedies under §§ 634 et seq. BGB. The customer’s right to claim damages remains governed by § 12.
11.3 The rectification right under this § 11 does not apply to defects caused by (a) customer-supplied information, hardware or software not provided or maintained by Sacred Byte, (b) modifications to deliverables made by the customer or third parties without Sacred Byte’s consent, or (c) the customer’s failure to comply with operational instructions provided by Sacred Byte.
12.1 Sacred Byte is liable without limitation
12.2 In the case of a slightly negligent breach of a material contractual obligation (cardinal duty), Sacred Byte’s liability is limited to typical and foreseeable damages. Material contractual obligations are those whose performance enables the proper execution of the contract in the first place and on whose observance the customer regularly relies and may rely.
12.3 Liability under § 12.2 is limited in aggregate to the amount the customer has paid to Sacred Byte in the twelve (12) months prior to the damage-causing event.
12.4 Otherwise, Sacred Byte’s liability is excluded.
12.5 In particular, Sacred Byte is not liable for indirect damages, consequential damages, lost profits, data loss or replacement costs, except in the cases set out in § 12.1. If the customer has failed to perform regular data backups in breach of § 3.3, Sacred Byte’s liability for the loss or recovery of data is in any event limited to the notional cost that restoring the affected data from a proper backup would typically have required had the customer met its backup duty under § 3.3 — irrespective of whether such a backup in fact exists.
12.6 The above limitations of liability also apply to the personal liability of Sacred Byte’s legal representatives, employees and vicarious agents.
12.7 The above provisions do not entail any change in the burden of proof to the customer’s disadvantage.
13.1 The customer undertakes not to solicit or hire, directly, indirectly or through third parties, any employees or subcontractors of Sacred Byte who were involved in the performance of services for the customer, during the term of the contract and for a period of two (2) years after termination.
13.2 Before entering into contract negotiations with such an employee or subcontractor, the customer will inform Sacred Byte of the intended engagement by email to contracts@sacredbyte.com and await a written response from Sacred Byte.
13.3 If the customer breaches § 13.1, Sacred Byte is entitled to a placement fee of 40 % of the annual gross salary (including variable compensation components) of the relevant employee or subcontractor, but at least € 20,000, plus statutory VAT where applicable. The annual salary or annual compensation agreed at the time of the engagement is decisive.
13.4 The placement fee is due in the same month in which the employment or contractor relationship begins. The payment terms set out in § 6 of these GTC apply.
13.5 If the customer demonstrates that the engagement occurred without solicitation by the employee in question or by Sacred Byte and without use of contacts obtained through the cooperation (i.e. an independent application by the employee or subcontractor to a publicly advertised position of the customer, without any prior contact arising from the cooperation), the placement fee does not apply.
14.1 Neither party is liable for non-performance or delayed performance of its obligations to the extent caused by force majeure. Force majeure includes in particular natural disasters, war, terrorism, civil unrest, embargoes, acts of civil or military authorities, pandemics, epidemics, fire, floods, accidents, strikes, lockouts, transport delays, failures or delays of third-party infrastructure (e.g. cloud services, internet providers) and large-scale cyber attacks on third-party infrastructure or on general internet or cloud availability, in each case to the extent outside Sacred Byte’s reasonable control. Cyber attacks directed at the customer’s own environment that fall within the agreed scope of services do not constitute force majeure.
14.2 The affected party will inform the other party without undue delay of the occurrence and expected duration of the force majeure event and will use all reasonable efforts to minimise its impact.
14.3 If a force majeure event continues for more than 60 calendar days, either party is entitled to terminate the contract with 14 days’ written notice without any claim for damages arising therefrom.
15.1 Amendments, supplements or side agreements to this contract require written form to be effective. This also applies to the waiver of this written form requirement. § 1.5 (email satisfies written form) applies accordingly.
15.2 Sacred Byte is entitled to amend these GTC with effect for the future. Amendments will be communicated to the customer in text form at least sixty (60) days before the planned effective date. If the customer does not object to the amendment in text form within six (6) weeks of receipt of the amendment notice, the amended GTC are deemed accepted. Sacred Byte will draw the customer’s attention to the right to object and the consequences of silence separately in the amendment notice. Amendments under this § 15.2 may not alter the agreed remuneration or the core service obligations to the customer’s disadvantage; such changes require an express agreement between the parties.
15.3 In the event of a timely objection, the previous GTC continue to apply; Sacred Byte is in this case entitled to terminate the contract with three (3) months’ notice to the end of a month.
16.1 This contract and all disputes arising from it are governed exclusively by the law of the Federal Republic of Germany, excluding the UN Convention on Contracts for the International Sale of Goods (CISG) and the conflict-of-laws rules of German private international law.
16.2 The exclusive place of jurisdiction for all disputes arising from or in connection with this contract is Berlin.
16.3 Sacred Byte is entitled to also sue the customer at the customer’s general place of jurisdiction.
These GTC are provided in German and English. Only the German version is authoritative for interpretation and in case of dispute; the English version is provided for non-binding information only.
Upon termination or expiry of the contract for any reason, Sacred Byte will, within a reasonable time and at no additional cost, hand over to the customer:
Sacred Byte will, upon request, provide reasonable transition support to a successor provider or to the customer’s internal team at the hourly rate set out in the offer (or, if no rate is set out, at Sacred Byte’s then-current standard rate).
18.3.1 Sacred Byte will delete or irreversibly anonymise all personal data and operational data of the customer that Sacred Byte processed on behalf of the customer (“Customer Data”) within ninety (90) days after the effective date of termination, unless statutory retention obligations or § 18.3.2 require longer retention.
18.3.2 Sacred Byte may retain:
18.3.3 Upon the customer’s reasoned written request, Sacred Byte will confirm in writing that deletion has been completed.
18.4.1 Recommendation. Sacred Byte recommends that customers procure software licences and cloud subscriptions directly under their own commercial relationships wherever possible. Direct procurement avoids any dependency on Sacred Byte and lets the customer retain full control of its licensing in the event of a change of provider. Sacred Byte does not seek to lock customers in and will support direct procurement at any time during the engagement.
18.4.2 Transferable licences. Where a software licence or subscription procured by Sacred Byte on behalf of the customer can be transferred to the customer or to a successor provider, Sacred Byte will, at the customer’s request, support the transfer in a timely manner. Reasonable cooperation by Sacred Byte under this clause is provided at no additional cost.
18.4.3 Non-transferable licences. Where a software licence or subscription is not directly transferable, the customer may elect either
(a) to continue receiving the licence or subscription through Sacred Byte under a licence re-sale arrangement, in which case Sacred Byte will charge the customer at Sacred Byte’s documented procurement cost plus an administration surcharge of ten percent (10%); or
(b) to re-procure the licence or subscription directly from the vendor, in which case Sacred Byte will provide reasonable support for the migration.
18.4.4 Continuity. Sacred Byte will not terminate or interrupt the customer’s access to licences or subscriptions procured by Sacred Byte solely as a result of contract termination, provided the customer continues to pay the applicable licence fees. Such continuity is, however, limited to one (1) full billing cycle following the effective date of termination unless the parties agree on a longer transition or a re-sale arrangement under § 18.4.3 (a). Within that period, the customer is responsible for completing the licence transfer or for instructing Sacred Byte to maintain the re-sale arrangement.
18.4.5 Non-payment. § 7 (Suspension for Non-Payment) remains unaffected and applies in case of non-payment for re-sold licences under § 18.4.3 (a).
19.1 If any provision of this contract is or becomes invalid or unenforceable, the validity of the remaining provisions remains unaffected.
19.2 The parties undertake to replace the invalid or unenforceable provision with a valid and enforceable provision that comes closest to the economic purpose of the invalid or unenforceable provision. The same applies to any contract gaps.
PART II — ENGAGEMENT-SPECIFIC PROVISIONS
The following provisions form part of the same single agreement set out in Part I. They are not a separate contract. They apply additionally — and only — to the engagement model designated in the offer or order confirmation. Where the offer designates a project engagement, § 20 applies. Where the offer designates a Managed Service (whether as an hourly retainer or per-user model), § 21 applies. In the absence of a designation, the provisions in Part I apply on their own.
This § 20 applies where the offer or order confirmation designates the engagement as a project or ad-hoc time-and-material engagement.
The scope, deliverables and — where applicable — the milestones with their acceptance or completion criteria are defined in the offer.
Project engagements are billed either
(a) on a time-and-material basis with monthly invoicing, or
(b) on the basis of defined milestones, with an invoice issued upon completion of each milestone, as specified in the offer. The applicable model is set out in the offer.
20.4.1 Where the offer defines milestones, Sacred Byte will notify the customer in writing (email is sufficient) upon completion of each milestone, attaching or referencing the corresponding deliverables.
20.4.2 A milestone is deemed accepted ten (10) business days after such notification unless the customer has objected in writing within that period and specified material defects in reasonable detail.
20.4.3 Where the customer objects in time and the objection identifies material defects, Sacred Byte will rectify the defects in accordance with § 11. After successful rectification, the acceptance period restarts for the rectified items only.
20.4.4 Minor defects (i.e., defects that do not materially impair the use of the deliverable) do not justify rejection of the milestone. They will be rectified separately under § 11 without delaying acceptance or invoicing of the milestone.
Estimates contained in the offer serve as guidance and as a cost ceiling per checkpoint. Sacred Byte will not exceed the estimated effort for a checkpoint without the customer’s prior approval. Any additional hours beyond an estimated checkpoint require prior client approval.
The project engagement runs for the duration set out in the offer (typically defined by milestones, scope completion, or a fixed end date). There is no statutory minimum term beyond this; the term of the engagement is the term agreed in the offer.
20.7.1 The right of either party to terminate this engagement for convenience (ordentliche Kündigung) is excluded. Project engagements are concluded for the full duration set out in the offer.
20.7.2 The right of either party to terminate for good cause (außerordentliche Kündigung pursuant to § 626 BGB) and the right of both parties to terminate by mutual written consent remain unaffected.
20.7.3 If the customer terminates the engagement without good cause or otherwise causes Sacred Byte to discontinue the engagement without good cause attributable to Sacred Byte, the customer remains liable for (i) the agreed remuneration for all work performed up to the date of discontinuation, including any completed milestones, and (ii) in accordance with § 648 sentence 2 BGB, the agreed remuneration for the part of the services not yet performed, less the expenses saved as a result of the early termination and less what Sacred Byte acquires, or wilfully refrains from acquiring, through other use of its working capacity. Sacred Byte may instead claim, without specific proof, five percent (5%) of the agreed remuneration attributable to the part of the services not yet performed (§ 648 sentence 3 BGB).
20.8.1 Project plans, timelines and milestone dates set out in the offer are calculated on the assumption that the customer fulfils its cooperation obligations under § 3 in a timely manner. Sacred Byte’s resource planning depends on these assumptions.
20.8.2 Where the project timeline is exceeded by more than twenty-five percent (25%) of the originally planned duration and the overrun is attributable to delays, non-availability or non-cooperation on the customer’s side (for example: late provision of information or approvals, unavailability of contact persons, missed enrolment or working sessions, repeated rescheduling, or failure to procure prerequisites), Sacred Byte is entitled, in addition to its rights under §§ 642 and 643 BGB, to charge a continuation fee. The continuation fee covers the additional project management, communication and resource-retention effort required to keep the project active and is billed at the hourly rate set out in the offer on a monthly basis until project completion.
20.8.3 Where the project timeline is exceeded by more than fifty percent (50%) of the originally planned duration and the overrun is attributable to delays or non-cooperation on the customer’s side, Sacred Byte may, after providing the customer with a written notice and a remedy period of fifteen (15) business days, either
(a) terminate the engagement for good cause pursuant to § 626 BGB; in such case § 20.7.3 applies, together with any fees accrued under § 20.8.2; or
(b) propose, at Sacred Byte’s election, a renegotiated scope, timeline and pricing for the customer’s written acceptance.
20.8.4 Sacred Byte will, to the extent reasonably possible, give the customer early warning when significant timeline slippage attributable to customer cooperation is foreseeable, so that the customer has the opportunity to remedy the cause before § 20.8.2 or § 20.8.3 is invoked.
This § 21 applies where the offer or order confirmation designates the engagement as a Managed Service, whether structured as an hourly retainer (§ 21.3) or as a per-user model (§ 21.4).
21.2.1 Minimum term. The Managed Service agreement is concluded for an initial minimum term of twelve (12) months from the agreed start date.
21.2.2 Continuation and termination. After expiry of the minimum term, the agreement continues for an indefinite period and renews automatically until terminated by either party with three (3) months’ written notice to the end of a calendar month. Termination must be in writing; § 1.5 applies accordingly. The right to extraordinary termination for good cause remains unaffected.
21.2.3 Tier change. A change of service tier is possible with thirty (30) days’ notice to the end of a month.
21.2.4 Price changes. Sacred Byte may adjust the agreed prices to reflect inflation and changing market conditions, with at least three (3) months’ notice in text form. The customer may terminate the agreement with the same notice to the effective date of the price change. In the event of material changes to the framework conditions (e.g. significant relocation of the customer, significant increase in headcount), the agreement may be renegotiated.
21.2.5 Operating model. Sacred Byte performs Managed Services primarily during business hours as defined in § 5.5. Scheduled maintenance windows that form part of the agreed Managed Service scope and are performed outside business hours are not subject to surcharges (see § 5.4).
21.2.6 Out-of-hours work. Where circumstances require Sacred Byte to perform work outside business hours, on weekends or on public holidays — including in response to emergencies, escalations or specific customer requests — such work is subject to the surcharges set out in § 5.2, even where the underlying work falls within the Managed Service scope.
21.2.7 Out-of-scope work. Support beyond the scope of the Managed Service defined in the offer requires prior customer approval and is billed at the hourly rate specified in the offer, plus any applicable surcharges under § 5.
21.3.1 Sacred Byte commits to availability up to the hours range agreed in the offer (the “Retainer”).
21.3.2 Invoicing is performed monthly at the agreed Retainer fee for the agreed band of hours, irrespective of the hours actually utilised within that band.
21.3.3 Hours rendered beyond the upper end of the Retainer range in a billing month require prior customer approval and are billed at the hourly rate set out in the offer.
21.3.4 Unless otherwise agreed in the offer, unused Retainer hours within a billing month do not carry over into the following month.
21.3.5 The Retainer is a fixed monthly fee for the agreed availability. Sacred Byte is not obliged to provide itemised time records or to otherwise evidence the individual hours rendered within the agreed Retainer band, and the Retainer fee is payable in full irrespective of actual utilisation. This does not affect the customer’s right to approve and review any additional hours billed beyond the Retainer band under § 21.3.3.
21.4.1 Scope and pricing. Sacred Byte provides the Managed IT and security services defined in the offer. The selected service tier and the per-user price are set out in the offer; they determine the scope of services and the applicable service level.
21.4.2 Billable User definition. A natural person counts as a Billable User (“BU”) in a billing month as soon as at least one of the following criteria is met:
21.4.3 Freelancers, working students and consultants are counted from the time they receive a company account or use a managed or supported device.
21.4.4 Cut-off. The number of BUs is determined on the last calendar day of the month at 23:59 local time (Berlin).
21.4.5 Data source. The count is performed automatically based on reports from the identity or mobile device management system. The corresponding report is attached to each monthly invoice as evidence. Manually supported persons or devices are listed separately. Infrastructure (servers, central firewalls/gateways and the like) is billed separately by agreement.
21.4.6 Proration. If a person is onboarded or offboarded up to 15 days before month-end, half the regular monthly price is charged or credited. If the start or leaving date is more than 15 days before month-end, the full monthly price is charged or remains payable.
Sacred Byte GmbH
Friedrichstraße 155, 10117 Berlin, Germany
Managing Director: Ekkehard Endruweit
Commercial Register: Amtsgericht Berlin (Charlottenburg) HRB 263350
VAT ID: DE367553800
Effective: 2 July 2026 · Version 1.4 · English convenience translation
