Legal center

1. Terms and definitions

1.1.Service means the php2go software and hardware system available through https://p2g.dev and intended for analysis, diagnostics, compilation of PHP projects, and provision of build results to the user.

1.2.Administration means the person or entity operating php2go, hosting the service, ensuring its technical operation, support, development, payment acceptance, and communication with users.

1.3.User means an individual, individual entrepreneur, legal entity, organization representative, or other person using the service for personal, commercial, professional, testing, or other lawful purposes.

1.4.Account means the user's service account created to access the personal dashboard, projects, builds, plans, payments, operation history, and other functions.

1.5.Project means a set of files uploaded by the user, including PHP code, Composer dependencies, configuration files, templates, assets, documentation, and other materials intended for analysis or compilation through the service.

1.6.Source code means files and data uploaded by the user to the service, including program code, libraries, settings, internal project files, and other materials comprising the user's project.

1.7.Build means the process of service-side project processing, including diagnostics, preparation, transformation, compilation, packaging, log generation, artifact generation, and other technical operations.

1.8.Artifact means a build result, including an executable file, archive, report, log, diagnostic file, run instructions, checksums, and other files generated by the service.

1.9.Diagnostics means an automated project check for compatibility, structure, entry point availability, dependencies, potential errors, unsupported features, configuration issues, and other factors affecting build feasibility.

1.10.Plan means a set of service usage conditions, including available limits, number of projects, upload size, number of builds, artifact retention period, technical support, and paid features.

1.11.Paid functions mean service functions available after payment for a plan, subscription, one-time payment, or other provided payment method.

1.12.Personal dashboard means the restricted part of the website available to the user after authorization.

1.13.User materials mean projects, source code, files, settings, comments, support requests, payment data to the permitted extent, technical logs, and other information transmitted by the user to the service.

1.14.Documentation means reference materials, instructions, technical descriptions, command examples, limitations, ZIP archive requirements, artifact descriptions, and other materials published on the website.

2. General provisions

2.1.These Terms are binding on all users of php2go.

2.2.The Terms regulate relations between the user and the Administration arising from use of the website, personal dashboard, documentation, paid functions, upload tools, diagnostics, compilation, and receipt of artifacts.

2.3.The service is intended to help developers, companies, teams, and PHP project owners prepare, diagnose, and compile PHP applications into executable artifacts.

2.4.The service is not legal, financial, accounting, tax, or other professional advice.

2.5.The service does not guarantee that any PHP project of the user will be successfully compiled, launched, or operate without errors after the build.

2.6.The user is solely responsible for the legality, correctness, security, quality, licensing, and operability of uploaded projects.

2.7.Certain terms may be governed by additional documents published on the website, including:

• Privacy Policy;
• Cookie Policy;
• Payment and Refund Policy;
• Acceptable Use Policy;
• Security Policy;
• Data Deletion Policy;
• Intellectual Property Policy;
• documentation and technical limitations of the service.

2.8.If these Terms conflict with additional documents, the special document applies to the extent it regulates the relevant matter in more detail.

3. Acceptance of terms

3.1.The user is deemed to have accepted these Terms upon performing any of the following actions:

• visiting the website and continuing to use it;
• registering an account;
• logging into the personal dashboard;
• uploading a project;
• running diagnostics;
• running a build;
• downloading an artifact;
• paying for a plan or subscription;
• contacting support;
• using an API, if such functionality is provided;
• otherwise using service functionality.

3.2.Acceptance of the Terms means the user's consent to all provisions of the Terms.

3.3.If the user acts on behalf of an organization, the user confirms that they have authority to accept these Terms on behalf of that organization.

3.4.If the user lacks the required authority, responsibility for use of the service and the consequences of such use lies with the person actually using the service.

3.5.The user confirms that they have reached the age required to enter into an agreement under applicable law.

4. Subject matter of the Terms

4.1.The Administration provides the user with access to php2go under these Terms and the selected plan.

4.2.The service may provide the following capabilities:

• user registration and authorization;
• upload of ZIP archives and other project formats if supported by the service;
• storage of projects in the personal dashboard within plan limits;
• automated project diagnostics;
• generation of compatibility reports;
• launch of PHP project builds;
• generation of executable files and related artifacts;
• storage of build history;
• downloading build results;
• configuration of plans, payments, and subscriptions;
• build status notifications;
• technical support;
• access to documentation.

4.3.The Administration may change the composition of service functions, add new capabilities, change the interface, update documentation, change technical limits, and discontinue support for obsolete functions.

4.4.Some functions may be available only on paid plans.

4.5.The ability to compile a specific project depends on the project structure, PHP features used, dependencies, extensions, dynamic code, file structure, access rights, configuration, and other technical factors.

4.6.The service is not obliged to ensure compatibility with all PHP versions, all frameworks, all Composer packages, all extensions, and all ways of running PHP applications.

5. Registration and account

5.1.To access certain service functions, the user may be required to create an account.

5.2.During registration, the user undertakes to provide accurate and up-to-date data.

5.3.The user is solely responsible for maintaining confidentiality of credentials, including password, access tokens, verification codes, and access to the email used for the account.

5.4.All actions performed through the user's account are deemed to have been performed by the user unless the user proves otherwise.

5.5.The user must immediately notify the Administration if they become aware of unauthorized account access, password loss, email compromise, or other circumstances threatening account security.

5.6.The Administration may temporarily restrict access to an account if hacking, breach of the Terms, unlawful service use, fraud, payment discipline violation, or a security threat is suspected.

5.7.The user may not transfer the account to third parties, sell it, rent it out, use another person's account without permission, or create accounts to bypass restrictions.

5.8.The Administration may require additional verification of identity, email, phone number, payment data, or authority of an organization representative if necessary for security, payments, support, or legal compliance.

6. Requirements for projects and uploaded files

6.1.The user may upload to the service only projects, files, and materials for which the user has the required rights and permissions.

6.2.The user is solely responsible for preparing the project for upload, including:

• correct ZIP archive structure;
• availability of an entry point;
• correctness of Composer dependencies;
• absence of unnecessary, secret, or prohibited files;
• absence of malicious code;
• compliance with licenses of third-party libraries;
• availability of rights to all uploaded code.

6.3.The user must not upload data that is not required for building the project, including unnecessary personal data, payment data, passwords, private keys, database dumps, secret tokens, private certificates, and other sensitive information unless such data is strictly necessary.

6.4.If the user uploads secret keys, configuration files, database credentials, or other sensitive information, the user does so at their own risk.

6.5.The Administration may set limits on:

• archive size;
• number of files;
• total storage volume;
• number of projects;
• number of builds;
• build duration;
• commands used;
• file types;
• request frequency;
• artifact retention period.

6.6.The Administration may reject, block, or delete a project if it violates these Terms, contains prohibited materials, creates a security threat, overloads the infrastructure, or may harm the service, users, or third parties.

7. Diagnostics and compilation

7.1.The service may perform automated project diagnostics before or during a build.

7.2.Diagnostics may identify:

• missing entry point;
• project structure problems;
• unsupported PHP features;
• missing dependencies;
• Composer problems;
• autoload errors;
• unsupported extensions;
• file system problems;
• potentially dangerous or prohibited operations;
• plan limit exceedance;
• other factors affecting build feasibility.

7.3.Diagnostic results are informational and do not guarantee successful build or correct project operation.

7.4.Project compilation is performed automatically or semi-automatically within the capabilities of the service.

7.5.During the build, the service may create temporary files, logs, intermediate data, cache, diagnostic reports, and artifacts.

7.6.The service may finish a build with an error for technical reasons, including errors in the user's project, dependency incompatibility, limit exceedance, infrastructure failures, compiler errors, or external restrictions.

7.7.An unsuccessful build is not always a ground for a refund if diagnostics, processing, or a build attempt was actually provided, unless otherwise stated in the Payment and Refund Policy.

7.8.The user understands that the build result may require additional testing, environment configuration, target platform verification, configuration setup, access permissions, environment variables, network parameters, and other conditions.

8. Build artifacts

8.1.Artifacts are provided to the user in the form in which they are generated by the service.

8.2.Depending on the plan and build result, artifacts may include:

• executable file;
• ZIP archive;
• README or run instruction;
• diagnostic report;
• build log;
• checksums;
• runtime information;
• other files generated by the service.

8.3.The user must independently verify the artifact before using it in a production environment.

8.4.The Administration does not guarantee that the artifact will meet all user expectations, be compatible with all operating systems, be safe for the user's specific infrastructure, or work without errors.

8.5.The user is solely responsible for distribution, launch, storage, publication, and use of artifacts.

8.6.If an artifact contains user code, dependencies, data, or materials, the user is responsible for such materials.

8.7.The Administration may limit artifact retention periods. After the retention period expires, artifacts may be deleted without recovery.

8.8.The user must independently download and save required artifacts before the retention period expires.

9. User rights

9.1.The user may use the service in accordance with these Terms, the selected plan, and the documentation.

9.2.The user may:

• create an account;
• upload projects for which the user has rights;
• run diagnostics and builds;
• receive diagnostic results;
• download available artifacts;
• manage projects within available functionality;
• pay for plans;
• contact support;
• delete projects if such function is available;
• stop using the service.

9.3.The user may use build results for personal or commercial purposes if such use does not violate law, third-party rights, third-party component licenses, or these Terms.

9.4.The user retains rights to their source code and projects.

9.5.The user may request deletion of the account and data in accordance with the Data Deletion Policy and technical capabilities of the service.

10. User obligations

10.1.The user must comply with these Terms, documentation, plan limits, and applicable law.

10.2.The user must use the service in good faith and only for lawful purposes.

10.3.The user must independently ensure that they have rights to uploaded projects, source code, libraries, images, texts, databases, configurations, and other materials.

10.4.The user must not upload prohibited materials, malicious code, stolen code, third-party data without lawful basis, or materials violating third-party rights.

10.5.The user must not attempt to disrupt the service, bypass limits, access other users' projects, interfere with service infrastructure, or use the service in a way that creates excessive load.

10.6.The user must independently test build results before using them in a production environment.

10.7.The user must maintain backups of their projects and must not use the service as the only storage location for source code or artifacts.

10.8.The user must timely pay for paid functions if using a paid plan.

10.9.The user must keep contact data up to date and ensure access to the email specified in the account.

10.10.The user must compensate the Administration for losses, expenses, claims, fines, or other damages arising from the user's breach of these Terms, third-party rights, or applicable law, to the extent permitted by law.

11. Administration rights

11.1.The Administration may manage the service and change its functionality, interface, documentation, plans, limits, and technical requirements.

11.2.The Administration may:

• provide, restrict, or terminate access to the service;
• set technical limits;
• change project upload rules;
• change project and artifact retention periods;
• conduct technical maintenance;
• delete temporary files, cache, and obsolete artifacts;
• block dangerous, unlawful, or suspicious actions;
• request additional information from the user;
• refuse service in case of Terms violation;
• change plan pricing;
• engage contractors, payment providers, and infrastructure providers.

11.3.The Administration may temporarily restrict access to an account, project, build, or artifact if there are grounds to believe that they violate these Terms, third-party rights, security requirements, or law.

11.4.The Administration may delete projects, artifacts, and temporary data after the retention period expires, when limits are exceeded, upon breach of the Terms, or upon account termination.

11.5.The Administration may send the user service notifications related to the account, builds, payments, security, document changes, technical work, and support.

12. Prohibited use of the service

12.1.The user is prohibited from using the service for any unlawful, malicious, fraudulent, dangerous, or bad-faith purposes.

12.2.It is prohibited to upload, compile, distribute, or otherwise use through the service projects that:

• contain malicious software;
• contain viruses, trojans, ransomware, spyware, backdoors, botnet code, miners, or other dangerous components;
• are intended for unauthorized access to systems, accounts, networks, or data;
• are used for phishing, credential theft, fake login pages, or social engineering;
• are used for spam, unlawful mass mailing, or bypassing anti-spam systems;
• infringe copyrights, licenses, trademarks, trade secrets, or other third-party rights;
• contain stolen source code or unlawfully obtained data;
• are intended to bypass technical protection measures, DRM, licensing, or access control;
• are intended for DDoS attacks, vulnerability scanning without authorization, vulnerability exploitation, or automated hacking;
• violate applicable law;
• create a threat to the security of the service, users, or third parties.

12.3.The user is prohibited from:

• attempting to access other users' accounts, projects, artifacts, or internal service systems;
• probing, scanning, attacking, or testing the service infrastructure without written permission;
• interfering with service operation;
• bypassing limits, plan restrictions, payment mechanisms, or security mechanisms;
• using automated tools that create excessive load on the service;
• creating multiple accounts to bypass restrictions;
• reselling access to the service without the Administration's consent;
• removing, hiding, or altering technical notices, licenses, warnings, or service restrictions;
• using the service in a way that may damage the reputation of php2go.

12.4.In case of violation of this section, the Administration may immediately suspend access, delete the project, delete artifacts, cancel the build, block the account, refuse a refund, and transfer information to competent authorities if required by law or necessary to protect rights and security.

13. User intellectual property

13.1.The user retains all rights to uploaded source code, projects, files, and other materials if such rights belong to the user.

13.2.Uploading a project to the service does not transfer ownership of the project to the Administration.

13.3.The user grants the Administration a limited, non-exclusive, technically necessary right to use, copy, store, analyze, process, transform, and compile user materials solely for:

• providing service functions;
• performing diagnostics;
• performing builds;
• generating artifacts;
• storing build history;
• ensuring security;
• technical support upon user request;
• complying with these Terms and law.

13.4.This right applies during the period of service use, the retention period for projects and artifacts, and the technically necessary period for backups, logs, security, and legal obligations.

13.5.The user guarantees that they have all required rights, licenses, and permissions to upload and process the project through the service.

13.6.If the project contains third-party libraries or components, the user is solely responsible for compliance with their licenses.

13.7.The Administration is not obliged to verify the licensing purity of user projects.

14. Intellectual property of php2go

14.1.All rights to php2go, including service software code, interface, design, operation logic, documentation, texts, trade designations, databases, algorithms, runtime components, technical solutions, and other elements, belong to the Administration or its rights holders.

14.2.The user receives a limited right to use the service only in accordance with these Terms.

14.3.The user may not:

• copy the service;
• reproduce the interface or documentation without permission;
• create derivative products based on the service;
• decompile, disassemble, or attempt to extract the internal code of the service unless permitted by law;
• use the php2go brand without the Administration's consent;
• impersonate a service representative.

14.4.If an artifact contains php2go runtime components, their use may be governed by a separate license or technical terms published on the website or included in the artifact.

14.5.The user does not acquire rights to internal tools, compiler, runtime, cloud infrastructure, documentation, or other service elements except for the expressly granted right of use.

15. Confidentiality of projects

15.1.The Administration understands that user projects may contain trade secrets, internal code, configurations, and other valuable information.

15.2.The Administration undertakes to take reasonable organizational and technical measures to protect user projects from unauthorized access.

15.3.Access to user projects may be performed by automated service systems and by a limited circle of authorized persons when necessary for:

• technical support upon user request;
• diagnosing a technical problem;
• ensuring security;
• investigating a breach of the Terms;
• complying with legal requirements;
• preventing harm to the service, users, or third parties.

15.4.The user understands that data transmission over the Internet and cloud processing cannot be absolutely secure.

15.5.The user must independently remove from the project data that is not required for the build and that the user is not ready to transmit to a cloud service.

15.6.The Administration is not liable for disclosure of data if it occurred due to the user's actions, weak password, email compromise, uploading secrets to the project, transferring access to third parties, or the user's violation of security rules.

16. Personal data and privacy

16.1.Personal data processing is carried out in accordance with the Privacy Policy published on the website.

16.2.For service operation, account data, email, technical logs, IP addresses, browser information, payment statuses, support requests, project information, and other data necessary to provide the service may be processed.

16.3.The user must not upload unnecessary personal data of third parties into projects if such data is not required for the build.

16.4.If the user uploads personal data of third parties as part of a project, the user confirms that they have a lawful basis for such upload and processing.

16.5.The user understands that payment operations may be processed by third-party payment providers, banks, or aggregators under their own terms.

16.6.Detailed information about collection, storage, use, transfer, and deletion of data is set out in the Privacy Policy and Data Deletion Policy.

17. Plans, payments, and subscriptions

17.1.The service may provide free and paid plans.

17.2.The cost, limits, set of functions, and plan terms are indicated on the website.

17.3.The Administration may change plans, pricing, limits, function sets, trial periods, and payment terms.

17.4.Price changes do not apply to an already paid period unless otherwise required by law or stated in the terms of a specific plan.

17.5.Payment may be made through third-party payment providers, banks, payment aggregators, or other available methods.

17.6.The user must provide accurate payment data and must not use another person's payment instruments without permission.

17.7.When using a subscription, the user agrees to possible automatic charging for the next billing period if such possibility is provided by the selected payment method and clearly indicated at checkout.

17.8.The user may cancel a subscription in the personal dashboard or through support if the corresponding function is available.

17.9.Subscription cancellation stops subsequent renewal but does not always mean a refund for the already paid period.

17.10.Refunds, payment disputes, cancellations, partial refunds, and exceptions are governed by the Payment and Refund Policy.

17.11.In case of payment error, overdue payment, payment cancellation, chargeback, or suspected fraud, the Administration may restrict access to paid functions.

18. Limits and technical restrictions

18.1.The service may set limits depending on the plan, technical condition of infrastructure, security policy, and current load.

18.2.Limits may include:

• maximum project size;
• maximum number of files;
• maximum number of builds;
• build execution time;
• number of parallel builds;
• storage volume;
• project retention period;
• artifact retention period;
• number of users in an account or organization;
• API request frequency;
• available build platforms;
• available runtime components.

18.3.Exceeding limits may result in upload refusal, build termination, deletion of temporary files, need to switch to another plan, or temporary access restriction.

18.4.The Administration may change limits to protect service stability and security.

18.5.Documentation and the service interface may contain additional limitations that form part of these Terms.

19. Support

19.1.The Administration may provide technical support via email, feedback form, personal dashboard, ticket system, messengers, or other channels indicated on the website.

19.2.The scope of support depends on the plan and technical capabilities of the service.

19.3.Support may include help with:

• project upload;
• understanding diagnostics;
• build errors;
• payments;
• account access;
• documentation;
• general recommendations for project preparation.

19.4.Support is not obliged to perform project development, source code fixing, security audit, server setup, infrastructure migration, legal license review, or application optimization for the user unless provided by a separate agreement.

19.5.Support response time may depend on the plan, request complexity, team workload, weekends, and holidays.

20. Service availability and technical work

20.1.The Administration strives to ensure stable operation of the service but does not guarantee continuous and error-free availability.

20.2.The service may be temporarily unavailable due to:

• technical work;
• updates;
• accidents;
• hosting provider actions;
• network problems;
• attacks;
• software errors;
• actions of third parties;
• force majeure circumstances.

20.3.The Administration may conduct scheduled and unscheduled technical work without prior notice if necessary for security, stability, or service development.

20.4.The Administration is not liable for losses arising from temporary service unavailability unless expressly provided by a separate agreement.

20.5.If the service provides an SLA in the future, its terms will be published separately and apply only to users for whom such SLA is expressly provided.

21. Third-party services

21.1.php2go may use third-party services, including hosting providers, cloud infrastructure, payment providers, email services, analytics tools, authorization systems, monitoring systems, and other solutions.

21.2.The user understands that use of third-party services may be governed by their own terms and policies.

21.3.The Administration is not liable for failures, restrictions, commissions, blocks, or actions of third-party services if such circumstances are outside the Administration's reasonable control.

21.4.If the user logs in through a third-party provider, such as a social network or developer account, the user is responsible for the security of that account and compliance with the relevant provider's rules.

22. Disclaimer of warranties

22.1.The service is provided on an “as is” and “as available” basis.

22.2.The Administration does not guarantee that:

• the service will operate without errors and interruptions;
• any project will be successfully compiled;
• the build result will fully meet the user's expectations;
• the artifact will work on any system;
• the service will identify all project errors;
• diagnostics will be complete and exhaustive;
• the service will be compatible with all libraries, frameworks, and extensions;
• use of the service will lead to the user's commercial result;
• data will never be lost under circumstances outside the Administration's reasonable control.

22.3.The user uses the service at their own risk.

22.4.The user must independently test build results, verify artifact security, comply with licenses, and assess the suitability of the service for their tasks.

23. Limitation of liability

23.1.To the maximum extent permitted by applicable law, the Administration is not liable for indirect, incidental, special, punitive, or consequential damages.

23.2.The Administration is not liable for:

• loss of profit;
• loss of revenue;
• loss of clients;
• loss of data;
• business downtime;
• failures of the user's infrastructure;
• errors in the user's code;
• user's license violations;
• data leakage caused by the user;
• use of artifacts without testing;
• actions of third parties;
• blocks by payment providers;
• inability to compile a specific project.

23.3.If the Administration's liability cannot be completely excluded, it is limited to the amount actually paid by the user for using the service during the last 30 calendar days before the event giving rise to liability, unless otherwise established by mandatory law.

23.4.Nothing in these Terms limits liability that cannot be limited under applicable law.

24. User liability

24.1.The user is responsible for all actions performed through their account.

24.2.The user is responsible for uploaded code, files, dependencies, licenses, personal data, secrets, payment actions, and use of artifacts.

24.3.The user must compensate the Administration for losses, expenses, claims, fines, third-party demands, and other damages arising from:

• the user's breach of these Terms;
• upload of an unlawful or malicious project;
• violation of third-party rights;
• license violations;
• unlawful processing of personal data;
• use of another person's payment instruments;
• distribution of dangerous artifacts;
• other unlawful actions of the user.

24.4.The user independently resolves third-party claims related to the user's projects, code, artifacts, and service use.

25. Blocking, suspension, and termination of access

25.1.The Administration may temporarily or permanently restrict the user's access to the service, account, projects, builds, or artifacts in case of violation of these Terms.

25.2.Grounds for access restriction may include:

• violation of acceptable use rules;
• suspicion of malicious code;
• violation of third-party rights;
• fraud;
• violation of payment discipline;
• chargeback;
• attempt to bypass limits;
• attack on the service;
• unauthorized access;
• requirement of law or competent authority;
• security threat.

25.3.The Administration may delete prohibited projects and artifacts without prior notice.

25.4.In case of a material breach of the Terms, paid amounts may not be refunded if permitted by law and the Payment and Refund Policy.

25.5.The user may stop using the service and request account deletion.

25.6.After access termination, some data may be stored for a technically necessary period for backups, logs, security, financial accounting, legal compliance, and protection of the Administration's rights.

26. Data deletion

26.1.The user may delete individual projects, artifacts, or the account if such function is available in the interface.

26.2.If deletion through the interface is unavailable, the user may send a deletion request to the contact email.

26.3.Deletion may be restricted if data retention is necessary for:

• compliance with law;
• financial accounting;
• investigation of violations;
• fraud prevention;
• dispute resolution;
• security;
• recovery after technical failures.

26.4.Deleted data may remain in backups for a limited technical period until automatic overwrite or deletion.

26.5.Detailed data deletion terms are governed by the Data Deletion Policy.

27. Notices

27.1.The Administration may send notices to the user through:

• email;
• personal dashboard;
• website interface;
• system messages;
• payment notifications;
• other channels specified by the user or available in the service.

27.2.Notices are deemed received by the user after being sent to the email specified in the account or after publication in the personal dashboard.

27.3.The user must keep contact data up to date.

27.4.The user may not opt out of service notices related to security, payments, account, legal documents, and service operation.

28. Changes to the Terms

28.1.The Administration may change these Terms at any time.

28.2.A new version of the Terms is published on the website.

28.3.If changes are material, the Administration may additionally notify the user by email, personal dashboard, or website interface.

28.4.Continued use of the service after changes enter into force means the user's acceptance of the new version.

28.5.If the user does not agree with the changes, the user must stop using the service.

29. Governing law and dispute resolution

29.1.These Terms are governed by the law of the Republic of Kazakhstan unless otherwise expressly required by mandatory provisions of applicable law.

29.2.The parties shall seek to resolve all disputes and disagreements through negotiations and written claims.

29.3.A claim is sent to the Administration's contact email or another address indicated on the website.

29.4.The claim review period is up to 30 calendar days unless another period is established by law or agreed by the parties.

29.5.If the dispute is not resolved through negotiations, it shall be considered by a competent court in accordance with applicable law.

29.6.A consumer user may have additional rights provided by mandatory consumer protection laws. These Terms do not limit such rights to the extent they cannot be limited by agreement.

30. Force majeure

30.1.The parties are released from liability for full or partial non-performance of obligations if such non-performance is caused by force majeure circumstances.

30.2.Such circumstances may include:

• natural disasters;
• military actions;
• civil unrest;
• actions of state authorities;
• power supply interruptions;
• communication network failures;
• data center accidents;
• attacks on infrastructure;
• epidemics;
• sanctions;
• payment system failures;
• other circumstances outside the reasonable control of a party.

30.3.The party affected by such circumstances must take reasonable measures to mitigate the consequences.

31. Invalidity of individual provisions

31.1.If any provision of these Terms is held invalid, unlawful, or unenforceable, this does not affect the validity of the remaining provisions.

31.2.The invalid provision is replaced by a provision as close as possible in meaning and economic purpose, to the extent permitted by law.

32. Assignment of rights and obligations

32.1.The user may not assign rights and obligations under these Terms to third parties without the written consent of the Administration.

32.2.The Administration may assign rights and obligations under these Terms to a successor, affiliate, new service owner, or other person in connection with reorganization, business sale, project transfer, or change in service management structure.

33. Contact information

33.1.For questions related to these Terms, the user may contact:

Email: admin@p2g.dev Website: https://p2g.dev Administration: IE php2go Company details: published on the “About company” page or provided upon lawful request.

33.2.For legally significant requests, the user must specify:

• full name or organization name;
• account email;
• description of the issue;
• documents confirming authority if the request is submitted on behalf of an organization;
• information about the project, build, or payment if the request relates to a specific operation.

34. Appendix 1. Short rules for the user

For user convenience, a short summary of the main rules is provided below. If this summary conflicts with the full text of the Terms, the full text applies.

34.1.Upload only projects for which you have rights.

34.2.Do not upload viruses, phishing, miners, malicious code, or illegal materials.

34.3.Do not use the service for hacking, spam, bypassing protection, or violating third-party rights.

34.4.Do not store unnecessary secrets, passwords, private keys, or personal data in the project.

34.5.Check the build result before running it in production.

34.6.Keep your own backups of your projects.

34.7.Pay for plans on time if you use paid functions.

34.8.In case of build errors, first review diagnostics and documentation, then contact support.

34.9.The service does not guarantee successful compilation of every PHP project.

34.10.Your source code remains yours, but you allow the service to technically process it for diagnostics and builds.

35. Appendix 2. Recommended footer links

For proper legal presentation of the website, it is recommended to place the following links in the footer:

• Terms of Service;
• Privacy Policy;
• Cookie Policy;
• Payment and Refund Policy;
• Acceptable Use Policy;
• Security Policy;
• Data Deletion Policy;
• Intellectual Property Policy;
• Contacts;
• About company.

36. Final provision

These Terms are the basic document regulating use of php2go. All special terms related to personal data, cookies, payments, refunds, security, data deletion, and acceptable use must be published as separate documents and apply together with these Terms.

37. Document language and priority of versions

37.1.These Terms may be published in Russian, English, Ukrainian, Kazakh, and other languages.

37.2.Translations are provided for user convenience and must correspond to the Russian version in structure, meaning, sections, and numbering.

37.3.In case of any inconsistency between translations and the Russian version, the Russian version shall prevail, unless mandatory applicable law requires otherwise.

37.4.The user may contact support if they find any inconsistency between language versions of the document.