Public Beta Terms
Effective date: 6 July 2026
Version: 1.0
1. What the Comers public beta is
The Comers public beta is a testing stage of a product under development before its full commercial launch.
Comers is an independent technology startup currently being built and developed by its founder. The project is in the stage of development, testing, and collecting feedback from real users.
The public beta allows selected participants to test Comers, try its features in practice, and provide feedback that may help with further product development.
2. The beta is not a finished commercial product
Comers in beta may:
- contain bugs,
- work unstably,
- have availability interruptions,
- include incomplete features,
- change without prior notice,
- have technical, functional, or organisational limitations,
- lose or change certain features during testing.
By participating in the public beta, you accept that the product is being tested and developed, and is not provided as a finished, stable commercial service.
3. Who may apply
Any adult interested in Comers may apply to the public beta.
Comers is intended primarily for professional and B2B use, in particular for people and organisations operating in e-commerce, marketplaces, online sales, operations, logistics, order handling, customer support, or related areas.
An application may be submitted by an individual or by a person acting on behalf of a company or organisation.
We do not accept applications from minors.
4. Applying does not guarantee access
Submitting the application form does not mean automatic acceptance into the public beta.
Access to Comers in the beta is granted by invitation only. Comers may select participants manually, in stages, and at its own discretion.
When selecting participants, we may consider, among other things:
- fit with the features currently being tested,
- type of business activity,
- sales channels,
- scale of sales or operations,
- country or market,
- readiness to provide feedback,
- diversity of the test group,
- technical or organisational risk related to accepting a given participant.
Comers is not required to justify a decision to accept, reject, or move an application to a later testing wave.
5. Beta waves and the waiting list
The public beta may be run in waves. This means some candidates may receive an invitation later, even if they were not accepted in the first round.
If a candidate confirms that they want to remain on the waiting list, we may contact them about future beta waves, availability, invitations to testing, or other organisational information about the program.
6. Participant and team access
An invitation to the public beta is granted to a specific person.
If a participant wants their co-workers, employees, or team members to receive access as well, they should request this from Comers. Comers may accept or reject adding additional people at its own discretion.
The participant is responsible for ensuring that people who receive access at their request use Comers in accordance with these Terms and any additional rules accepted during access activation.
7. Free beta
The public beta is free of charge, unless we expressly agree otherwise with a specific participant.
Free participation in the beta does not create any right to use Comers for free after the beta ends, any right to a specific discount, or any right to specific commercial terms in the future.
Comers may grant selected participants discounts, preferential terms, or other benefits, in particular for active and valuable cooperation during the beta. Such benefits are discretionary and require separate confirmation.
8. Limits and infrastructure protection
Comers may apply usage limits, including technical, functional, quantitative, time-based, or organisational limits.
Limits may apply, for example, to:
- number of users,
- number of organisations,
- number of integrations,
- number of orders, products, messages, or other objects,
- frequency of API requests,
- infrastructure resource usage,
- type of available features.
Comers may limit, suspend, or terminate a participant’s access if their use excessively burdens the infrastructure, creates a security risk, negatively affects other users, or goes beyond the purpose of the public beta.
9. What we expect from participants
A participant should use Comers reasonably, lawfully, and in line with the purpose of the public beta.
We expect the participant to:
- test the product in good faith,
- report significant bugs, issues, and comments,
- respond to reasonable feedback requests,
- not abuse access,
- not take actions that threaten the security of Comers,
- not share access with unauthorised persons.
If a participant does not cooperate with testing, ignores important feedback requests, or uses Comers in a way that is inconsistent with the purpose of the program, Comers may limit or terminate their participation in the public beta.
10. Feedback, ideas, and suggestions
A participant may provide Comers with feedback, suggestions, ideas, comments, problem descriptions, feature needs, proposed changes, and other information about the product.
By providing feedback, the participant agrees that Comers may freely use such information to develop, change, improve, promote, and commercialise the product, without any obligation to pay compensation, obtain additional consent, or transfer rights to the participant.
Providing an idea, suggestion, or need does not mean that Comers is required to implement it. If Comers implements a feature, change, or solution, it remains part of Comers and does not give the participant any ownership rights to the product, code, feature, concept, or business model.
11. Data entered into Comers
During the public beta, a participant may be able to process in Comers real data of their company, organisation, customers, orders, products, messages, shipments, marketplace accounts, online stores, carriers, or other integrations.
The participant decides which accounts, systems, and data they connect to Comers. If the participant enters real data into Comers, they do so at their own responsibility and should make sure they have the appropriate legal bases and authorisations.
Before access to features enabling such data processing is activated, Comers may require the acceptance of additional terms, including a data processing agreement or another document concerning data entered into the application.
Submitting a public beta application does not itself create a data processing agreement and does not grant access to the Comers environment.
12. Integrations with external services
Comers may allow integration with external accounts, platforms, stores, marketplaces, carriers, payment systems, email systems, AI tools, or other services.
The participant decides which integrations they enable and what data they transmit through them. The participant is responsible for using such integrations in compliance with the terms, conditions, and settings of external providers.
Comers may add, change, limit, or remove integrations during the beta.
13. Confidentiality, security, and public disclosure
The public beta does not mean that all information about Comers, its operation, bugs, limitations, vulnerabilities, or non-public features may be freely disclosed.
The participant should not publicly disclose information that could harm the security, integrity, reputation, or development of Comers, in particular:
- details of discovered security issues,
- vulnerabilities, weaknesses, or ways to bypass protections,
- technical details of non-public features,
- screenshots of features made available only within the beta, if they may disclose non-public information,
- data of other users or customers,
- information that may be misleading as to the operation, availability, or development stage of Comers.
Bugs, vulnerabilities, security issues, and important comments should be reported directly to Comers.
Comers may withdraw access from a participant if their actions or public communication violate security, the good name of the project, the integrity of the beta program, or Comers’ legitimate interests.
14. What is not allowed
The participant must not:
- bypass Comers security measures,
- attempt unauthorised access,
- conduct penetration testing without prior consent,
- perform reverse engineering, decompilation, or attempts to reconstruct system operation beyond what is permitted by law,
- automatically overload the API or infrastructure,
- use Comers for unlawful activities,
- enter data for which they do not have appropriate rights or authorisations,
- share access with unauthorised persons,
- take actions that may disrupt the operation of the product or infrastructure.
15. Technical support
During the public beta, Comers may provide technical, organisational, or product support.
Support during the beta is provided on a best-effort basis. We do not guarantee a specific response time, support availability, SLA, issue resolution time, or continuity of product operation.
16. Ending participation by the participant
A participant may resign from the public beta at any time by contacting Comers or using available resignation mechanisms, if provided.
Resignation may result in removal or deactivation of access to Comers. Details concerning data entered into the application may be set out in additional terms, including a data processing agreement, if one has been concluded.
17. Ending or limiting access by Comers
Comers may at any time limit, suspend, or terminate a participant’s access to the public beta, in particular where:
- the participant breaches these Terms,
- the participant does not cooperate with testing,
- the way Comers is used creates technical, legal, or security risk,
- use of Comers excessively burdens the infrastructure,
- the participant acts to the detriment of Comers, other participants, or third parties,
- further participation is not aligned with the purpose of the beta program.
Comers may also end the entire public beta, a specific testing wave, or the availability of selected features at any time.
18. No guarantees
Comers in beta is provided “as is” and “as available”.
We do not guarantee that:
- Comers will operate without errors,
- access will be uninterrupted,
- all data will be preserved in every situation,
- all features will be available in the future,
- Comers will fit every participant’s business scenario,
- external integrations will operate without interruption,
- the beta will result in a commercial product launch by a specific date.
19. Liability
To the fullest extent permitted by law, Comers is not liable for damages resulting from the use of the beta version, in particular for data loss, lost profits, business interruptions, integration errors, business decisions made based on beta operation, or product unavailability.
This does not limit liability that cannot be excluded or limited under mandatory provisions of law.
20. Privacy
Information about processing data of public beta candidates and participants is available in the “Public Beta Privacy Notice”.
General information about data processing on comers.app is available in the “Privacy Policy”.
21. Changes to the Terms
Comers may update these Terms if the operation of the public beta, product features, access model, or technical, organisational, or legal requirements change.
The current version of the Terms will be available on comers.app or provided to participants in another reasonable way.
22. Governing law and disputes
These Terms are governed by Polish law.
Any disputes related to the Comers public beta should first be resolved amicably. If they cannot be resolved amicably, they will be resolved by the competent court in Poland, subject to mandatory provisions of law that cannot be excluded.
23. Contact
For matters related to the public beta, you can contact Comers at:
For privacy and data protection matters: