Shipvise Terms and Conditions

Version: 1.0
Effective: upon publication of this version
Last updated: 21 August 2026
Stable URL: https://shipvise.com/en/legal/terms/

Translation notice: This English version is a machine-assisted translation provided for convenience. The original Czech version is the authoritative version. Where mandatory law requires otherwise, rights granted by mandatory law remain unaffected.

These general terms and conditions (the "Terms") govern the use of the Shipvise service and the contractual relationship between the Customer and the Provider.

1. Provider

The Shipvise service is provided by:

David Hošek
Company ID (IČO): 03956890
VAT ID (DIČ): CZ9503230539 (VAT-identified person, not a VAT payer)
Registered office: U Potoka 247, 440 01 Peruc – Telce, Czech Republic
Registered in the Czech Trade Register since 2 April 2015
Trade name: Shipvise by Progity

Phone: +420 602 352 762

Customer contact: support@shipvise.com
Personal-data contact: privacy@shipvise.com
Reporting abuse and illegal content: abuse@shipvise.com

Hereinafter the "Provider". The Provider operates the Shipvise service (the "Service").

2. What Shipvise is

Shipvise is a PaaS/SaaS platform that may, depending on the selected plan and configuration, provide in particular Workspace and Project management, source-code management, builds, artifact registries, Preview/staging, production operation of applications, controlled deployment, rollback, runtime configuration, managed resources, logs, control mechanisms, Senior Review, Starter Creation and Assisted Fix/Support.

Shipvise is not merely a code-review service. Review is one of the possible control steps before production operation.

The specific features, limits, prices and availability are governed by the current plan or by the individual order displayed to the Customer before the relevant order is concluded.

3. Definitions

• Account — the user account of a specific natural person.
• Workspace — the Customer's organisational space in which one or more users may act.
• Project — the Customer's system boundary within Shipvise, which may contain one or more Applications.
• Application — a separately deployable component of a Project, for example a website, API, worker or background process.
• Preview — a test/staging environment; it is not the Customer's production service.
• Production — the production environment of the Customer's Application.
• Release — a specific deployed version, which may reference an exact immutable artifact and an exact configuration revision.
• Credit — a non-transferable Shipvise service unit; it is not money and not stored monetary value.
• Consumer — a natural person acting outside the scope of their business activity or independent exercise of their profession.
• B2B Customer — a Customer who does not enter into the contract as a Consumer, in particular an entrepreneur, a company or other legal entity, an association, a society, an institution or another organisation, or a person acting when concluding the contract within the scope of a business, professional or other institutional activity.

4. Eligibility to enter into the contract

An Account may be created and the contract may be concluded only by a person who has reached the age of 18 and has the legal capacity to perform the relevant legal act.

On registration, the Customer states truthfully whether they act as a Consumer or as a B2B Customer. A B2B Customer provides the required company, institutional and tax details.

A person creating a Workspace on behalf of a legal entity or another entrepreneur confirms that they are authorised to bind it.

5. Countries of availability

The standard consumer self-service offering is intended for Customers in the EU/EEA. The Provider may refuse a B2C registration or purchase from another country and allow only a request for future availability.

The B2B service outside the EU/EEA may be provided after individual approval, in particular with regard to legal, tax, sanctions, payment and technical conditions. There is no automatic entitlement to being granted such access.

6. Conclusion of the contract and legal documents

The contract for the use of the Service is concluded by completing registration and accepting these Terms, unless stated otherwise for a specific offer. The Provider retains in particular the version of the Terms accepted, the moment of acceptance, and the relevant Account and Workspace.

When a Project is created for the first time, the Customer is, before the Project is created, presented with the data processing agreement (DPA) where the use of the hosting features involves processing of the Customer's personal data on the Customer's behalf. Creation of the first Project is conditional upon acceptance of the current DPA.

The Privacy Policy is an information document and its display does not in itself constitute "consent" to processing.

7. Account, Workspace and permissions

The Customer is responsible for the accuracy of the details provided, for protecting login credentials, for managing Workspace members and for the appropriate assignment of permissions.

Each Account is personal. Sharing a password or an access session among several persons is not permitted.

The Provider may use roles and granular permissions within the Service. The availability of specific roles and administrator functions may change over time.

The Customer must notify any suspected compromise of an account or access credentials without undue delay.

8. Ways of creating the source

Subject to the available features, the Customer may:

1. upload a source project;
2. connect a supported external Git repository;
3. create an empty managed project;
4. order Starter Creation.

Where an external repository is used, the external repository remains the source of truth to the extent resulting from the configuration. The Customer is responsible for the validity of the authorisations to that repository and to third-party accounts.

The Provider may refuse or stop an import that exceeds technical limits, contains manifestly dangerous content or breaches the Acceptable Use Policy.

9. Rights to the code and Customer Content

The Customer retains the rights to their source code, database data, files, configuration and other content they have created or placed into Shipvise.

The Customer grants Shipvise, for the period necessary to perform the contract, a non-exclusive authorisation to store, copy, build, analyse, review, test, back up, deploy, host, export and delete that content to the extent necessary.

The Customer warrants that they hold the necessary rights and authorisations to the content placed into the Service and to its processing.

The Shipvise platform, its source code, orchestration, internal tooling, generic templates, documentation and know-how remain the property of the Provider or of the relevant third parties.

10. Starter Creation and Assisted Fix

Under Starter Creation or Assisted Fix, a senior developer may create or modify the Customer's source code on the basis of the requirements submitted.

The Customer obtains the authorisations necessary to use, modify, export and operate the individual output, including outside Shipvise. Pre-existing generic components, reusable libraries, templates and know-how of the Provider remain the Provider's and may be licensed to the Customer as part of the output. Open-source and other third-party components are governed by their own licences.

The Provider may re-use generic know-how and non-identifying practices gained during the work, but not the Customer's proprietary source code as a template for another Customer.

11. External generative AI and Customer data

In the MVP, Shipvise does not use external generative AI providers as a subprocessor of Customer source code, secrets or hosted personal data.

Ordinary hosting and Senior Review do not automatically send Customer source code or Customer data to the services of external generative AI providers.

If Shipvise wishes to introduce such processing in the future, it must, before activating it, update the contractual and privacy documentation and the subprocessor list accordingly, and where applicable obtain consent or satisfy another relevant legal requirement.

AI-generated outputs, if ever used within the Service, may be inaccurate, incomplete or non-unique. The use of AI does not change the Customer's responsibility for their own application logic and statutory obligations.

12. Build, Preview and Production

Depending on the plan, the Provider may enable through the Service a standalone build or the preparation of a Preview comprising a build and deployment to a staging environment.

Builds may be subject to limits on CPU, memory, storage, time, the number of concurrent runs, cooldown or monthly consumption. The limits are stated in the plan, the documentation or the order.

The Provider may queue a build, terminate a runaway process, restrict an abusive workload or refuse a workload that endangers the platform or third parties.

Preview is a test environment and may be unavailable, incomplete, contain demo data or be subject to limits different from Production. The Customer must not use Preview to process real sensitive data unless this is expressly intended and permitted.

13. Runtime configuration and secrets

The Provider may reserve system keys and variables within the Service, including information about the environment. The Customer must not intentionally overwrite reserved system keys in a way that circumvents the security or operational logic of the platform.

Runtime configuration may be versioned and a Release may reference a specific configuration revision. Secret values are not to be stored in source code, in a build artifact or in logs.

The ordinary Customer-facing API is not to return plaintext secret values. For a complete exit/export, the Provider may offer a separate, strongly authenticated mechanism for a secure one-time export of secret values entered by the Customer.

The Customer is responsible for rotating compromised secrets and for the secure configuration of third-party services they connect to the Application.

14. Managed databases and Customer data

Where a managed database is part of the plan, the Provider seeks to separate staging and production database permissions and data. Production data is not automatically copied into staging without an explicit feature or Customer instruction.

The Customer is responsible for the data model, the lawfulness of the data stored, application migrations and their consequences. The Provider is not liable for a destructive migration triggered by Customer code, unless the damage arose from a breach of the Provider's own obligation.

Backup and restore are described in the security and data documents. The standard service does not provide a contractually guaranteed RPO/RTO unless an individual contract expressly provides otherwise.

15. Senior Review

Senior Review is an expert assessment of a Customer release, change or other agreed scope by an independent senior developer.

Before it begins, the Customer receives an estimate or range of Credits and approves the maximum consumption. The Provider may temporarily reserve the approved maximum. If the maximum needs to be exceeded, work beyond that limit will not be carried out without the Customer's further approval.

Once completed, the actual consumption within the approved limit is deducted and the unused reservation is released.

To the extent necessary to carry out the ordered Review, the reviewer may obtain access to the changes, to the relevant parts of the source code, to the related build/runtime logs and to the configuration, and, where necessary given the nature or context of the Review, also to the entire relevant repository. Access is purpose-limited to the ordered Review, minimised, and the reviewer is bound by confidentiality.

Approval within a review means only that the agreed review/policy scope has been satisfied. It is not a guarantee of freedom from defects, of security, availability, legal compliance, or of the application's fitness for a particular purpose.

16. Timing of human services

Unless an SLA is expressly agreed in a specific order, the Provider performs Senior Review, Starter Creation and Assisted Fix without undue delay, having regard to the complexity of the assignment, the cooperation required and current capacity.

Any date stated as "usual", "estimated" or "target" is not a guaranteed deadline where it is expressly designated as an estimate.

17. Prohibited and regulated use

The Customer must comply with the Acceptable Use Policy, which forms part of the contractual framework.

The standard self-service offering is not intended for workloads containing special categories of personal data, biometric identification data, data on criminal convictions, healthcare/clinical systems or other regulated and high-risk workloads requiring specific assurances, unless the Provider approves them in advance in writing.

Breach of this condition may lead to refusal of deployment, restriction or termination of the Service.

18. Customer obligations

The Customer is responsible in particular for:

• the lawfulness of their Application and its content;
• the rights to the uploaded source and data;
• their own terms, privacy information and legal bases towards the end users of their Application;
• securing their own application logic;
• testing application behaviour and database migrations;
• reviewing AI-generated or automatically created changes;
• protecting their own secrets and third-party accounts;
• complying with the sectoral and regulatory rules applicable to their activity;
• providing truthful B2B/B2C and tax details.

This does not transfer to the Customer obligations for which the Provider is responsible under the contract or by law.

19. Availability, maintenance and third parties

Standard plans do not provide a guaranteed availability percentage or a contractual RPO/RTO unless the offer expressly provides otherwise.

The Provider operates the Service with reasonable professional care and may carry out both planned and extraordinary maintenance. Parts such as build, registry, Preview or Production may be briefly unavailable.

The Service may depend on third-party infrastructure, networks, DNS, payment services or services connected by the Customer. The Provider is not liable for an event beyond its reasonable control; this is without prejudice to rights that cannot be excluded.

An individual Enterprise contract may contain a special SLA only to the extent expressly stated in it.

20. Payments, plans and Credits

The details are governed by the Billing, Subscription and Credit Terms, which form part of these Terms.

Plans may be monthly or annual and may renew automatically. Annual invoicing does not in itself mean that all plan Credits for the year are credited at once; as a standard they are released over monthly credit periods.

The Provider may offer promotional prices and discounts. The specific conditions of a promotion are displayed before the order and do not change general statutory rights.

21. Price changes

An increase in the price of an existing renewing subscription will be announced at least 30 days in advance and will apply only prospectively, typically from the next renewal period. The Customer may cancel the next renewal before the new price takes effect.

A period already paid for, or Credits already purchased separately, are not repriced retroactively.

22. Cancellation, termination and suspension

The Customer may switch off automatic renewal in the Portal or by another available means. As a standard, they retain access until the end of the paid period.

The Provider may proportionately restrict or suspend the Service in particular in the event of:

• an unpaid payment;
• breach of the Acceptable Use Policy;
• reasonable suspicion of compromise, phishing, malware or another serious threat;
• overloading or endangering the infrastructure;
• a legal obligation or an order of a competent authority.

Where there is an acute risk, the restriction may be applied without prior notice. As soon as reasonably possible, the Provider informs the Customer of the reason, unless such disclosure is prohibited by law or would jeopardise an investigation or security.

23. Export, switching and deletion

The Provider supports departure from the Service and portability to the extent described in the Data export and switching rules.

The switching fee is CZK 0. A switching request is initiated without undue delay after reasonable verification.

The standard transitional period will not exceed 30 calendar days unless it is technically impossible to complete the switching. After it ends, at least a 30-day retrieval period is available in accordance with the Data Act rules. The Customer has the right to extend the transitional period once, to the extent provided by applicable law.

After the retrieval period ends, exportable data and digital assets are removed from active systems and backup copies age out in accordance with the limited rotating backup cycle stated in the portability rules and the Privacy Policy.

24. Personal data protection

The Provider is the controller of personal data processed for its own purposes, for example accounts, billing, security, support and marketing. Details are set out in the Privacy Policy.

Where the Provider hosts, through the Service, personal data for which the Customer determines the purposes and means of processing, the Customer is typically the controller and the Provider the processor. Such processing is governed by the DPA accepted in the Portal.

25. Third-party intellectual property

The Customer must not use third-party content or software through the Service without authorisation. The Provider may respond to a credible notice of infringement in accordance with the AUP and the abuse process.

Open-source software remains subject to the applicable licences. The Provider does not warrant that AI-generated or Customer code is free from third-party claims.

26. Liability — B2B Customers

This article applies to a B2B Customer, i.e. to any Customer who does not enter into the contract as a Consumer.

To the maximum extent permitted by law, the Provider's aggregate liability for ordinary damage arising from the subscription concerned is limited to one monthly price of that subscription; for an annually paid plan, to 1/12 of its annual price. For a separate one-off service, the limit of ordinary liability is at most the price of that specific service.

To the extent permitted by law, the Provider is not liable for indirect or consequential losses, lost profit, loss of business opportunity, or for damage caused by the Customer's application logic, unlawful data, the Customer's own integrations or a destructive migration performed by the Customer.

The limits do not apply where the law does not permit their application, in particular to liability that cannot validly be limited or excluded in advance.

27. Consumers

In relation to a Consumer, these provisions are interpreted so as not to limit their mandatory rights, in particular rights relating to digital content/services, defective performance, late provision, changes to the service and withdrawal from the contract.

Detailed information on the 14-day regime and the model form are available on the withdrawal page.

If the Customer expressly requests that the provision of the service begin before the statutory period expires, their request and the wording of the information provided will be recorded. The effects of such a request on a possible withdrawal are assessed according to the nature of the specific service and mandatory law.

Alternative dispute resolution

In the event of a dispute, a Consumer may use alternative resolution of a consumer dispute before the Czech Trade Inspection Authority (ČOI), Štěpánská 567/15, 120 00 Prague 2, Czech Republic, where the dispute falls within its competence.

The EU online dispute resolution (ODR) platform has been discontinued and the Provider does not refer to it.

28. Force majeure and extraordinary events

The Provider is not liable for delay in, or impossibility of, performance caused by an extraordinary, unforeseeable and insurmountable obstacle beyond its reasonable control, for example a large-scale network outage, a third-party attack, a natural event, a state of war or a binding measure of a public authority. The Provider makes reasonable efforts to limit the impact.

29. Changes to the Service and to the Terms

The Provider may develop the Service and add, change or discontinue features. Changes that materially degrade a service already paid for or that alter the Customer's contractual rights will be announced a reasonable time in advance, unless an urgent security or legal change requires faster action.

Material changes to these Terms will be announced in a manner corresponding to the significance of the change, for example in the Portal or by e-mail. In relation to a Consumer, changes apply only to the extent permitted by the mandatory rules on digital services.

30. Governing law and courts

The contract is governed by the law of the Czech Republic.

In relation to a Consumer, this is without prejudice to the mandatory rights afforded to them by the law of the country of their habitual residence, where those rules apply under the relevant conflict-of-law rules. The mandatory consumer rules on jurisdiction of courts are likewise unaffected.

For B2B disputes, unless mandatory law provides otherwise, the courts of the Czech Republic determined by the Provider's registered office have jurisdiction.

31. Language versions

The Czech wording is the original and canonical one. Translations may be produced by machine and will be marked as such.

In the event of a conflict, the Czech wording prevails only to the extent permitted by applicable law. This rule may not be used to limit the mandatory rights of a Consumer or to justify a misleading translation.

32. Contact

General and contractual enquiries: support@shipvise.com
Personal data protection: privacy@shipvise.com
Abuse and illegal content: abuse@shipvise.com
Phone: +420 602 352 762

Further legal and DSA contacts are available at /en/legal/contact/.