Terms & Conditions

1. Service Structures: One-Time & Subscription Models

The Provider offers services under two distinct pricing mechanics:
a) One-Time Payments: Fees applied for standalone deployments, migration architectures (e.g., Shopify-Independence converters), or specific setup structures. These services are considered fully executed upon successful pipeline initiation.
b) Monthly Tiers (Subscriptions): Recurring charges for continuous infrastructure provision, automated logistics tracking (e.g., MATU sync), or hosted services. Monthly tiers are billed strictly in advance at the start of each operational interval.

2. Provision of Services (Lieferung und Leistung)

Since the services provided are purely digital, cloud-native, and serverless infrastructure components, traditional physical shipping does not apply. Delivery is defined as providing access to the compiled environment or establishing active API synchronization hooks within the target project dashboard.

3. Payment Gateways & Processing Window

Payments are handled via third-party providers (e.g., Revolut Pay). Upon completing the transaction, the target system initiates verification.
Important Deployment Note: While verification often triggers instantaneously, final infrastructure compilation, routing tables update, and secure deployment status activation can take **up to 12 hours** to fully propagate across edge networks.

4. Payment Failure & Instant Suspension

For subscription models (Monthly Tiers), timely compensation is an absolute dependency for live-traffic infrastructure maintenance. If a recurring charge is declined, cancelled, or charged back by the payment gateway, the Provider reserves the right to **instantly suspend all active API routes, compilation webhooks, and dashboard access**. The infrastructure will remain frozen until all outstanding balances are fully cleared. The Provider is not liable for any revenue losses or operational downtime resulting from a suspension triggered by payment failure.

5. Client Dependencies & API Third-Party Rates

The proper functionality of our automated engines depends heavily on external factors, including third-party API availability (such as external e-commerce engines or supply chain tools). The Provider cannot be held responsible for operational delays or structural errors resulting from faulty client configurations or third-party rate limiting.

6. Limitation of Liability

The services are provided on an "as-is" and "as-available" architecture. To the maximum extent permitted under applicable law, the Provider’s total liability for any service interruptions, compilation failures, data synchronicity gaps, or financial losses is strictly capped at the total net fee paid by the Client for the specific billing interval.

7. Governing Law & Corporate Contact

These Terms are governed by the applicable commercial laws of the Provider's registered legal entity jurisdiction. For architecture reviews or urgent technical legal inquiries, reach out directly via info@iceeweb.online.

5. Cancellations, Refunds & Right of Withdrawal

a) B2B Exclusion: If the Client acts as a business entity or corporate contractor, all sales and subscription charges are final. The statutory right of withdrawal (Widerrufsrecht) does not apply to commercial B2B contracts.

b) Digital Execution & Waiver: For individual consumers, the Client explicitly agrees and requests that the Provider begins the execution of the digital service (e.g., system compilation, migration deployment, or infrastructure routing) immediately upon payment. The Client acknowledges that by giving this immediate execution request, **the right of withdrawal expires automatically** once the digital deployment pipeline has been initiated.

c) Subscription Cancellation: Monthly Tiers (Subscriptions) can be cancelled at any time directly via the client dashboard. The cancellation will take effect at the end of the current billing cycle. No partial refunds will be issued for remaining days within an already paid interval.

6. Database Integrity, API Credentials & Backups

a) Data Storage & Hosting: All operational data, including client configurations, synchronized e-commerce payloads, and system state logs, are stored securely using MongoDB architectures. The Provider implements industry-standard encryption and security measures.

b) Backup Responsibility: While the Provider executes regular automated database snapshots to ensure platform stability, these backups are primarily for disaster recovery of the overall infrastructure. The Provider does not guarantee permanent availability of individual historical transaction logs and is not liable for data loss resulting from faulty client-side API behavior or unexpected database sync drops.

c) Storage of Third-Party Credentials: If the Client stores API keys, access tokens, or webhooks within the platform database (e.g., for store migrations or logistics sync), these credentials are encrypted at rest. The Client remains solely responsible for the access permissions and any operations triggered by these keys.

6.1 Database Architecture Options: Shared vs. Native Database (BYODB)

The Provider allows two distinct infrastructure methods for data operations:

a) Shared Infrastructure Mode: Data is executed and stored within the Provider's centralized, EU-located MongoDB environment according to our standard policies.

b) Native Database / Bring-Your-Own-Database (BYODB) Mode: The Client has the operational option to connect their own native MongoDB cluster by providing their private connection parameters (URI/Strings) within the setup dashboard. In this mode, all e-commerce transactions, SKU layers, and personal payloads are written directly into the Client’s own data infrastructure. The Client assumes 100% legal, technical, and compliance responsibility for their database security, data integrity, regular snapshot backups, and statutory regulatory requirements. The Provider acts strictly as an un-cached logic processing layer and is entirely exempt from any liability regarding connection drops, data leaks, or corruption inside the Client’s database.