PHP2GO ACCEPTABLE USE POLICY
This policy keeps the service from being used for malicious, unlawful, or dangerous code.
This is working public product text. Before real international payments and advertising, review it with counsel for your jurisdiction, company, payment providers, and tax rules.
This Acceptable Use Policy (AUP) sets out mandatory requirements for using the php2go service available at https://p2g.dev.
This Policy applies to the website, user account area, PHP project uploads, diagnostics, compilation, build artifact generation, API if provided, technical support, payment features, and any other service functionality.
By using php2go, the user confirms that they will use the service lawfully, responsibly, safely, and only in accordance with this Policy, the Terms of Service, and other documents published on the website.
1. Status and purpose of this Policy
1.1.This Policy forms an integral part of the php2go Terms of Service.
1.2.The purpose of this Policy is to protect the service, users, infrastructure, payment providers, rights holders, and third parties from malicious, unlawful, fraudulent, dangerous, or excessively resource-intensive use.
1.3.This Policy applies to all users, including individuals, individual entrepreneurs, legal entities, organization employees, contractors, account administrators, and any persons who actually use the service.
1.4.If a specific rule in this document conflicts with a general provision of the Terms of Service, the stricter rule required for security, legality, and service protection shall apply.
2. General acceptable use principle
2.1.The user may use php2go only for lawful processing, diagnostics, and compilation of PHP projects for which the user has rights or lawful authorization.
2.2.The user must use the service in a manner that does not harm the Administration, other users, third parties, infrastructure, networks, devices, data, reputation, or business relationships of the service.
2.3.The user must not use the service in a way that creates legal risk, security risk, excessive load, infringement of third-party rights, circumvention of technical restrictions, or degradation of service quality for other users.
2.4.If the user is unsure whether a particular use of the service is permitted, the user must contact support in advance and obtain written confirmation.
3. Permitted use cases
3.1.The user may upload and compile their own PHP projects, internal corporate applications, educational projects, test applications, and commercial projects if the user has the necessary rights.
3.2.The user may compile projects with Composer dependencies, frameworks, templates, configurations, and assets if such use does not violate licenses or third-party rights.
3.3.The user may run compatibility diagnostics, analyze build errors, test artifacts, and use build results for personal, work, or commercial purposes while complying with this Policy.
3.4.The user may process projects of clients or employers only if the user has authority, a contract, assignment, consent, or another lawful basis.
4. Responsibility for user projects and materials
4.1.The user is fully responsible for all projects, source code, files, dependencies, configurations, data, secrets, and materials uploaded to the service.
4.2.The user warrants that upload, storage, diagnostics, compilation, download, distribution, and use of artifacts do not violate law, third-party rights, licenses, contracts, trade secret obligations, or information security requirements.
4.3.The Administration is not required to pre-screen the legality, licensing status, security, quality, purpose, or contents of user projects.
4.4.The user must independently remove from the project any data not needed for the build, including passwords, private keys, tokens, database dumps, personal data, and other sensitive information.
5. Malware and dangerous code
5.1.The user must not upload, compile, store, test, distribute, or obtain through the service any malware or code intended to cause technical, financial, reputational, or other harm.
5.2.Prohibited malicious code includes, without limitation, viruses, trojans, ransomware, spyware, stealers, backdoors, botnet components, droppers, worms, keyloggers, cryptocurrency miners without the system owner’s consent, malicious loaders, and covert remote access tools.
5.3.The user must not use the service to package, obfuscate, disguise, deliver, test antivirus evasion, harden, or distribute malicious code.
5.4.The user must not compile projects whose primary purpose is unauthorized data collection, credential theft, payment interception, covert surveillance, file damage, system locking, or bypassing security controls.
6. Unauthorized access, attacks, and vulnerability exploitation
6.1.The user must not use the service for hacking, unauthorized access, vulnerability exploitation, privilege escalation, authentication bypass, password spraying, credential stuffing, rate limit bypass, or attacks against systems, networks, and accounts.
6.2.The user must not compile tools intended for DDoS attacks, botnets, unauthorized mass scanning, automated credential guessing, or exploitation of known or unknown vulnerabilities without permission from the system owner.
6.3.The user must not use php2go to attack the service itself, its infrastructure, providers, payment systems, mail services, domains, users, or contractors.
6.4.Security testing is permitted only with respect to the user’s own systems or systems for which the user has explicit written authorization to test.
7. Phishing, fraud, and social engineering
7.1.The user must not use the service to create, compile, store, or distribute phishing pages, fake login forms, fake payment pages, brand impersonation, or imitations of banks, marketplaces, government services, social networks, or other services.
7.2.The user must not create artifacts intended to deceive users or steal logins, passwords, verification codes, payment data, session cookies, access tokens, or other confidential information.
7.3.The user must not use the service for fraudulent schemes, buyer deception, financial fraud, investment fraud, unlawful giveaways, fake support, fake notifications, or impersonation of another person or organization.
7.4.The user must not use the name, interface, domain, brand, or artifacts of php2go to imply that the Administration approves a fraudulent user project.
8. Spam, bulk messaging, and communication abuse
8.1.The user must not use the service to create or compile projects intended for spam, unlawful bulk messaging, anti-spam filter evasion, distribution of malicious links, or automated unsolicited messages.
8.2.The user must not use service artifacts for unlawful email, SMS, push notification, messenger message, comment, contact form, or other communications campaigns.
8.3.The user must comply with applicable laws on advertising, electronic communications, recipient consent, unsubscribe mechanisms, and personal data protection.
8.4.The Administration may restrict an account if the user’s project causes complaints, reputational risk, blocks by mail or network providers, or risk of inclusion of infrastructure in abuse lists.
9. Infringement of intellectual property rights and licenses
9.1.The user must not upload or compile source code, libraries, templates, images, databases, keys, documentation, or other materials unless the user has the right to use them.
9.2.The user must not use the service to distribute stolen code, pirated software, license bypass tools, protection removal tools, DRM violations, trademark infringement, or trade secret violations.
9.3.If a project contains open-source components, the user is solely responsible for complying with licenses, attribution notices, distribution terms, source disclosure requirements, and other obligations.
9.4.Upon receiving a substantiated complaint from a rights holder, the Administration may restrict access to a project, remove artifacts, request explanations from the user, and take other protective measures.
10. Personal data, secrets, and confidential information
10.1.The user must not upload personal data, payment data, medical data, government identifiers, private keys, tokens, passwords, database dumps, or other sensitive information unless it is required for the project build.
10.2.If the user uploads such data, the user confirms that they have a lawful basis for processing it and accepts responsibility for the consequences of such upload.
10.3.The user must not use the service for unlawful collection, processing, aggregation, sale, transfer, disclosure, or extraction of personal data of third parties.
10.4.The user must comply with the Privacy Policy, applicable personal data laws, and the internal rules of the user’s organization.
11. Resource and infrastructure abuse
11.1.The user must not use the service in a way that creates excessive or abnormal load on CPUs, memory, disks, network, build queues, storage, databases, API, payment systems, or support.
11.2.The user must not bypass tariff limits, quotas, file size limits, build count limits, parallel task limits, execution time limits, or other technical measures.
11.3.The user must not create multiple accounts, use false data, automate registration, split one project across accounts, or use other persons’ accounts to bypass restrictions.
11.4.The Administration may rate-limit requests, stop builds, delete temporary files, move tasks to a queue, reduce priority, require a different tariff, or suspend access if service stability is at risk.
12. Automation, API, and integrations
12.1.Automated access to the service is permitted only through official functions, interfaces, or APIs if provided by the Administration.
12.2.The user must not use parsers, bots, scripts, headless browsers, or other automation tools to bypass restrictions, perform bulk uploads, collect data, attack, overload the service, or gain unauthorized access.
12.3.The user must keep API keys, tokens, and credentials secure and must not transfer them to third parties.
12.4.The Administration may revoke tokens, restrict API access, change limits, introduce additional verification, or disable an integration if it violates this Policy or creates risk.
13. Payment abuse and fraud
13.1.The user must not use third-party payment instruments, false payment data, compromised cards, stolen accounts, nominee data, or other unlawful payment methods.
13.2.The user must not abuse trial periods, promo codes, bonuses, referral programs, refunds, chargeback procedures, or internal service credit.
13.3.If payment fraud, unlawful chargeback, money laundering, sanctions circumvention, or violation of payment provider rules is suspected, the Administration may restrict access, request verification, and cancel transactions to the extent permitted by law.
13.4.The user is responsible for all payments made through their account unless the user proves unauthorized access and promptly reported it to the Administration.
14. Prohibited and high-risk content
14.1.The user must not use the service for projects related to unlawful trafficking of weapons, narcotic substances, forged documents, stolen data, access trading, exploitation of minors, extremist activity, terrorist activity, or any other activity prohibited by law.
14.2.The user must not use the service for projects intended to bypass sanctions, export controls, financial monitoring, blocking measures, identification requirements, or other mandatory legal restrictions.
14.3.The user must not upload materials containing direct instructions for committing crimes, causing harm, unlawful access, manufacture of prohibited items, or concealment of unlawful activity.
14.4.The Administration may refuse to service projects that create increased legal, reputational, technical, financial, or security risk even if such project is not expressly listed in this Policy.
15. Permitted security research
15.1.Good-faith security research is permitted only if it does not violate law, does not attack php2go, does not affect third-party systems, and is performed with respect to assets the user is authorized to test.
15.2.The user must not use the service to publish, deliver, or exploit working exploits, zero-day exploits, malicious payloads, protection bypass tools, or instructions intended for immediate harmful use.
15.3.Educational, demonstration, and research projects are permitted only when presented safely, without malicious functionality enabled by default, without real credentials, and without risk to third parties.
15.4.Vulnerabilities discovered in php2go must be reported to the Administration via the contact email without public disclosure until remediation, unless a separate vulnerability disclosure program is published.
16. Monitoring, review, and protective measures
16.1.The Administration may use automated and manual abuse detection measures, including analysis of project metadata, logs, account behavior, payment indicators, complaints, network events, and diagnostic results.
16.2.The Administration is not required to disclose all internal abuse detection methods to the user in order not to reduce the effectiveness of service protection.
16.3.If a violation is suspected, the Administration may temporarily stop a build, block artifact download, isolate a project, restrict an account, request explanations, or conduct additional review.
16.4.Review of a project does not mean that the Administration confirms the legality, security, license compliance, or suitability of the user’s project.
17. Consequences of violating this Policy
17.1.If this Policy is violated, the Administration may apply one or more measures: warning, project deletion, artifact deletion, build cancellation, function restriction, limit reduction, temporary account suspension, permanent account suspension, or refusal of future service.
17.2.In cases of serious violations, including malware, phishing, hacking, fraud, infringement of third-party rights, or threats to infrastructure, measures may be applied immediately and without prior notice.
17.3.Violation of this Policy may result in refusal of a refund if permitted by law and the Payment and Refund Policy.
17.4.If a violation requires legal response or is necessary to protect rights and safety, the Administration may preserve evidence and provide information to a payment provider, hosting provider, rights holder, affected party, or competent authority.
18. Complaints, abuse reports, and appeals
18.1.Violations of this Policy may be reported to admin@p2g.dev.
18.2.A complaint should, where possible, include a description of the violation, link to the project or account, date and time of the event, evidence, complainant contact details, and information about the complainant’s rights if the complaint relates to intellectual property or personal data.
18.3.A user whose access has been restricted may submit a reasoned appeal explaining the situation and providing documents confirming lawful use of the service.
18.4.The Administration reviews requests within a reasonable time but is not required to restore access if the risk of violation, harm, or repeated abuse remains.
19. Relationship with other documents
19.1.This Policy applies together with the Terms of Service, Privacy Policy, Cookie Policy, Payment and Refund Policy, Security Policy, Data Deletion Policy, and Intellectual Property Policy.
19.2.Payment and refund matters are governed by the Payment and Refund Policy, but violation of this Policy may be considered when deciding on a refund.
19.3.Personal data processing matters are governed by the Privacy Policy, but the user must not upload excessive or unlawfully obtained personal data into projects.
19.4.Code ownership, licenses, and rights holder complaints are governed by the Terms of Service and the Intellectual Property Policy.
20. Changes to this Policy, governing law, and language
20.1.The Administration may amend this Policy to reflect new service features, new threats, payment provider requirements, hosting provider requirements, changes in law, and abuse practices.
20.2.The new version of this Policy is published on the website and applies from the publication date or another date specified in the document.
20.3.This Policy is governed by the law of the Republic of Kazakhstan, unless mandatory applicable law directly requires otherwise.
20.4.In case of any inconsistency between translations and the Russian version of this Policy, the Russian version shall prevail, unless mandatory applicable law requires otherwise.
21. Contact information and short summary
21.1.Questions regarding acceptable use of the service may be sent to admin@p2g.dev.
21.2.Short summary: upload only lawful projects for which you have rights; do not use the service for malware, phishing, spam, hacking, fraud, copyright infringement, unlawful personal data processing, or circumvention of technical and payment restrictions.
21.3.If a project may affect the security of third parties, requires special permissions, or may be perceived as malicious, the user must verify the legality of such use in advance and, where necessary, coordinate it with the Administration.
21.4.This Policy is intended to protect php2go, users, and third parties; therefore, violations may result in immediate blocking of a project, artifact, or account.
If you need a copy of terms, a data request, a copyright complaint, or a payment question, contact support.
mailContact support