Terms of Use

Critical Web Ops is operated by Bc. Michal Poluch in the Czech Republic, business ID 75702592, VAT/tax ID CZ7901204608. Business correspondence starts by email. A postal contact and invoice details are provided before acceptance of paid work and on verified business, legal, or data-protection request.

This website is for business service inquiries and general information. It does not create an emergency support, consulting, employment, partnership, agency, or fiduciary relationship by itself.

You may not misuse the website, attempt unauthorized access, interfere with availability, scrape at abusive volume, or submit unlawful, confidential third-party, credential, or payment-card data through general forms.

Submitting a form, email, payment request, or calendar request does not mean that Critical Web Ops accepts the work. An engagement starts only after written confirmation of scope, price, timing, access requirements, payment terms, and any required data-processing terms.

Critical Web Ops may decline or pause work where the request creates unreasonable security, legal, payment, platform, conflict, or operational risk.

Emergency, after-hours, priority, or guaranteed response commitments apply only if they are expressly agreed in the accepted order.

• Emergency Triage: narrow diagnosis for one visible issue that blocks sales, leads, updates, or a revenue path.
• Reliability Audit: fixed-scope diagnosis of checkout, forms, analytics, consent, updates, rollback paths, hosting, and operational risk.
• Repair Sprint: implementation work after evidence supports a safe fix sequence.
• Ops Care: planned office-hours support after a known technical baseline exists.

• Provide accurate information about the website, ownership, business impact, recent changes, known incidents, and third-party dependencies.
• Confirm that you have authority to request the work, grant access, and approve changes to the relevant systems.
• Maintain backups unless the accepted order expressly includes backup creation or verification.
• Provide licenses, hosting access, payment-provider access, analytics access, plugin/theme access, legal approvals, and stakeholder decisions needed for the agreed work.
• Review deliverables and raise issues within the agreed acceptance window.

Access should be temporary, least-privilege, and removed after the engagement. Prefer temporary accounts, role-based access, password-manager sharing, and client-controlled access logs.

Do not send passwords, recovery codes, API keys, SSH keys, payment-card data, or customer exports through plain email or the public inquiry form. If a secure sharing method is unavailable, work may be delayed.

Critical Web Ops may require a verified backup, staging environment, maintenance window, rollback plan, or written risk acceptance before production changes.

Public prices are B2B starting points or ranges. They may exclude VAT, sales tax, withholding, currency conversion, bank charges, payment processing fees, third-party licenses, hosting costs, and after-hours premiums.

Payment may be requested by invoice, bank transfer, Wise, Stripe Payment Links, Stripe Checkout, or another agreed processor. Payment processor terms also apply. Do not send card details directly to Critical Web Ops.

The default payment model is full upfront payment for Emergency Triage, a deposit or full upfront payment for audits and sprints, and monthly invoicing or subscription billing for care plans.

Late payment may pause delivery, support, access to future work, or handover of non-essential deliverables. Cancellation and refund treatment depends on the accepted order, work already performed, non-recoverable third-party costs, and mandatory law.

Deliverables may include diagnostic notes, audit reports, issue memos, configuration notes, fix summaries, code/configuration changes, access-removal reminders, and follow-up recommendations.

Unless the order says otherwise, change requests outside the accepted scope require separate approval and may change price or timing.

Client-side delays, missing access, third-party outages, hosting restrictions, plugin/vendor behavior, or payment-provider review can change delivery dates.

For Critical Web Ops inquiries, orders, billing, and support records, Critical Web Ops normally acts as an independent controller.

When Critical Web Ops accesses a client website, logs, checkout data, customer records, analytics, or hosting environment only to deliver the agreed service, Critical Web Ops may act as a processor under the client's instructions. A separate data processing agreement must be agreed before GDPR-covered processor work starts.

Clients must avoid sharing unnecessary personal data and must confirm that they have a lawful basis to provide any customer, employee, contractor, or visitor data needed for the work.

Client-specific reports, memos, configuration notes, and agreed fixes are delivered for the relevant engagement after payment according to the order.

Pre-existing tools, templates, checklists, methods, scripts, know-how, diagnostic approaches, and reusable materials remain the property of their original owner. The client receives only the rights expressly stated in the order.

Both parties should protect non-public business, technical, access, customer, payment, and security information received during an engagement.

Confidentiality does not prevent disclosure required by law, court order, tax obligations, professional advisers under confidentiality duties, or security incident handling.

Critical Web Ops can diagnose, stabilize, document, and implement agreed technical work. It does not guarantee revenue, conversion rate, ad performance, search ranking, uptime, uninterrupted availability, security outcome, or third-party platform behavior unless a specific written service level says otherwise.

Any liability limit must respect applicable law. Unless an accepted order says otherwise, the intended B2B liability cap is the fees paid for the affected order, with indirect loss, lost profit, lost revenue, data loss caused by unavailable backups, and third-party platform issues excluded where the law allows.

Unless an accepted order says otherwise, Czech law and Czech courts are the intended default for B2B engagements operated from the Czech Republic.

The public offer is intended for business customers. If consumer-law obligations apply to a specific customer, the order and legal text must be adjusted before acceptance.

Service: hello@criticalwebops.com. Billing: hello@criticalwebops.com. Security: hello@criticalwebops.com. Privacy: hello@criticalwebops.com.