DMCA / COPYRIGHT POLICY
If you believe code uploaded or distributed through the service violates your rights, send a notice to support.
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 Copyright Complaint Policy sets out the procedure for submitting, reviewing, and processing notices of alleged copyright and related-rights infringement in connection with the use of the php2go service.
This Policy applies to materials that a user uploads, processes, compiles, stores, publishes, transmits, or otherwise uses through the service, including source code, project archives, dependencies, documents, images, texts, databases, build artifacts, and other materials.
php2go respects the rights of authors, copyright holders, software developers, and owners of open-source and commercial licenses. Users of the service must upload and process only materials for which they have the necessary rights, licenses, and permissions.
This Policy is not legal advice. Rights holders and users should consult a qualified lawyer if there is a dispute regarding rights, licenses, or permitted use of materials.
1. Purpose of this Policy
1.1.This Policy is intended to protect copyright and related rights when php2go is used.
1.2.This Policy establishes the procedure for submitting complaints, counter-notices, temporary restrictions on access to materials, and restoration of access where grounds exist.
1.3.This Policy applies together with the Terms of Service, Acceptable Use Policy, Intellectual Property Policy, Security Policy, and other service documents.
1.4.If this Policy conflicts with a specific law, mandatory provisions of the relevant law apply to the extent they are binding on the parties.
2. Scope of Application
2.1.This Policy applies to materials posted, uploaded, stored, processed, or generated through the php2go service.
2.2.Such materials include source code, Composer packages, libraries, configuration files, databases, images, texts, templates, documents, archives, executable files, and build artifacts.
2.3.This Policy applies to publicly available materials as well as private projects if the Administration receives a substantiated complaint from a rights holder or detects signs of infringement.
2.4.This Policy does not govern disputes unrelated to copyright, such as contract, payment, work-quality, domain-name, trademark, or trade-secret disputes, unless such disputes include an element of copyright infringement.
3. Terms and Definitions
3.1.“Rights holder” means a person who owns copyright or related rights or is authorized to act on behalf of such person.
3.2.“Infringement notice” means a request by a rights holder or its representative to restrict access to material that allegedly infringes copyright or related rights.
3.3.“Counter-notice” means a request by a user whose material has been restricted, objecting to the complaint and requesting restoration of access where lawful grounds exist.
3.4.“Material” means any file, code, text, image, document, library, archive, artifact, link, log, or other object connected with the use of the service.
4. User Obligation to Respect Third-Party Rights
4.1.The user must upload, compile, and use through the service only materials for which the user has the necessary rights, licenses, and permissions.
4.2.The user is solely responsible for compliance with copyright, open-source licenses, commercial licenses, Composer package terms, and rights in images, texts, databases, and other materials.
4.3.The user may not use the service to process stolen code, pirated software copies, materials with violated licenses, or files obtained unlawfully.
4.4.Uploading material to the service constitutes the user’s confirmation that the user has the right to upload, store, process, compile, generate artifacts from, and further use the resulting output.
5. Where to Send Complaints
5.1.Complaints regarding alleged copyright or related-rights infringement should be sent to: admin@p2g.dev.
5.2.The email subject should preferably state: “Copyright Complaint”, “DMCA Notice”, or “Copyright Infringement Complaint”.
5.3.The Administration may publish a separate address or form for such complaints. If such a channel is published, the rights holder should use the current channel specified on the website.
5.4.Complaints submitted incompletely, without identification of the material, or without confirmation of the complainant’s authority may not be reviewed until the missing information is provided.
6. Contents of an Infringement Notice
6.1.The notice must include the details of the rights holder or its representative: full name or organization name, contact email, telephone number if available, and postal address where necessary.
6.2.The notice must include a description of the protected work or object whose rights are allegedly infringed, including its title, link to an official source, registration details, or other evidence of rights.
6.3.The notice must precisely identify the disputed material in php2go: a link, project or build identifier, file name, artifact description, code fragment, or other information sufficient to locate the material.
6.4.The notice must include a statement of the complainant’s good-faith belief that the use of the material is not authorized by the rights holder, its representative, or law, and a confirmation of the accuracy of the information and the complainant’s authority.
7. DMCA-Compatible Procedure
7.1.Where United States law applies or where the complainant submits a notice in DMCA format, the Administration may process such notice with reference to the principles of Section 512 of the U.S. Copyright Act.
7.2.Use of a DMCA-compatible procedure does not mean that php2go accepts the application of U.S. law to all users, materials, or disputes.
7.3.To improve transparency, the Administration may use a DMCA-like notice, access-restriction, and counter-notice mechanism even where the law of another country formally applies.
7.4.If the service is required or decides in the future to register a designated agent in the relevant U.S. directory, current information about such agent will be published on the website.
8. Preliminary Review of a Complaint
8.1.After receiving a complaint, the Administration performs a preliminary review of whether the information is complete and whether the disputed material can be identified.
8.2.The Administration is not required to conduct a full legal analysis of copyright ownership, licenses, fair use, or contractual relations between the parties.
8.3.If the complaint does not contain sufficient information, the Administration may request clarification or leave the complaint without further review until such information is provided.
8.4.If the complaint appears clearly unfounded, automated, bulk, inaccurate, or abusive, the Administration may refuse to take action.
9. Temporary Measures Following a Complaint
9.1.Where sufficient grounds exist, the Administration may temporarily restrict access to the disputed material, stop a build, block artifact downloads, or hide a public link.
9.2.Access restriction may apply to a specific file as well as to a project, build, artifact, account, or service function if necessary to prevent further infringement.
9.3.Temporary measures do not constitute an admission of the user’s fault or a final determination that infringement has occurred.
9.4.The Administration may consider the nature of the material, urgency of the complaint, risk of further distribution, repeat infringement history, consequences for the user, and the legal substantiation of the request.
10. Notification to the User
10.1.If access to material is restricted based on a complaint, the Administration will, where possible, notify the user by email, account dashboard, or another available channel.
10.2.The notification may include information about the disputed material, a brief description of the complaint, the date of access restriction, and the procedure for submitting a counter-notice.
10.3.The Administration may withhold certain information from the complaint where necessary for security, personal-data protection, trade-secret protection, legal compliance, or prevention of abuse.
10.4.Failure of the user to receive the notification due to an outdated email address, mail settings, blocking, technical errors, or the user’s inaction does not cancel the measures taken.
11. User Counter-Notice
11.1.The user may submit a counter-notice if the user believes that the material was restricted by mistake, due to misidentification, because a license or permission exists, because a copyright exception applies, or because another lawful ground exists.
11.2.The counter-notice must include the user’s details, identification of the restricted material, an explanation of the reasons for objection, and confirmation of the good faith of the information provided.
11.3.The user should attach documents or information confirming the right to use the material: a license, contract, link to an open-source license, rights-holder permission, evidence of authorship, or other confirmation.
11.4.Submitting a counter-notice does not guarantee automatic restoration of access and may result in information being shared with the complainant or competent authorities where required by law or necessary to resolve the dispute.
12. Restoration of Access
12.1.The Administration may restore access to material if the complaint is withdrawn, the complainant fails to confirm infringement, the user provides persuasive evidence of lawful use, or the statutory period for further action by the complainant has expired.
12.2.The Administration may refuse to restore access if there are signs of infringement, risks to the service, repeat complaints, litigation, a requirement of a competent authority, or other lawful grounds.
12.3.Restoration of access does not mean that the Administration confirms the lawfulness of the material’s use or assumes responsibility for the dispute between the parties.
12.4.If the dispute requires legal assessment, the parties must resolve it independently, including through negotiations, claims, court proceedings, or competent authorities.
13. Repeat Infringement
13.1.A user who repeatedly infringes copyright or related rights may be treated as a repeat infringer.
13.2.Repeat infringement may include confirmed complaints, re-uploading previously removed material, circumventing restrictions, using multiple accounts, or systematically violating licenses.
13.3.With respect to repeat infringers, the Administration may restrict certain functions, remove materials, stop builds, block the account, or refuse further service.
13.4.The Administration may consider the severity of the infringement, number of complaints, user good faith, existence of counter-notices, and measures taken by the user to stop the infringement.
14. False and Abusive Complaints
14.1.The complainant is responsible for the accuracy of the information stated in the complaint and for having authority to submit it.
14.2.False, misleading, automated, bulk, competitive, extortionate, or otherwise abusive complaints are prohibited.
14.3.If the Administration detects signs of abuse, it may refuse to take action, request additional evidence, restrict further submissions by the complainant, or take other reasonable measures.
14.4.A person who submits a false complaint may be liable to the user, the Administration, and third parties under applicable law.
15. Open Source and License Disputes
15.1.Disputes regarding compliance with open-source licenses, including MIT, Apache, GPL, LGPL, BSD, and other licenses, are considered under this Policy only to the extent they relate to alleged copyright infringement.
15.2.The Administration is not required to independently determine license compatibility, attribution accuracy, source-code disclosure obligations, or other complex licensing issues.
15.3.If the dispute concerns license terms, the complainant should specify in as much detail as possible which license is violated, which terms are not complied with, and where the disputed material is located.
15.4.The user must independently review dependency licenses and understand how compilation, static linking, packaging, or distribution of artifacts affects the user’s license obligations.
16. Private Projects and Confidentiality
16.1.Even if a user’s project is private, it may be subject to a complaint if the rights holder provides sufficient information about alleged infringement.
16.2.The Administration seeks not to disclose the user’s source code or confidential materials to the complainant without necessity or lawful grounds.
16.3.To review a complaint, the Administration may use metadata, file names, checksums, fragments provided by the parties, build logs, and other technical information.
16.4.If disclosure of certain data is required by law, by a competent authority, or to protect rights, the Administration may disclose only the minimum necessary amount of information.
17. Trademarks, Brands, and Other Rights
17.1.Complaints about trademarks, trade names, domain names, business reputation, trade secrets, or other rights are not DMCA complaints in the strict sense.
17.2.Nevertheless, the Administration may review such requests under the general rules on security, acceptable use, and protection of third-party rights.
17.3.The complainant should clearly identify which right is infringed, where the disputed material is located, and why the use is unlawful or unfair.
17.4.The Administration may refer the complainant to another review procedure, request a court order, a requirement from a competent authority, or additional evidence.
18. Cooperation with Authorities and Legal Compliance
18.1.The Administration may preserve, restrict, remove, or disclose information about disputed materials if required by applicable law, a court order, a competent authority request, or if necessary to protect rights and security.
18.2.The Administration may retain technical logs, information about complaints, user actions, and measures taken for the period necessary to resolve the dispute, maintain security, keep records, and comply with law.
18.3.If the dispute proceeds to a court or administrative process, the Administration may continue restricting access until a decision, party agreement, or other sufficient basis is received.
18.4.The Administration is not an arbitrator between the rights holder and the user and is not required to represent either party’s interests.
19. Changes to this Policy
19.1.The Administration may modify this Policy at any time to reflect development of the service, changes in law, payment requirements, hosting-provider requirements, and complaint-handling practice.
19.2.A new version of the Policy is published on the website and takes effect from the publication date or another date specified in the document.
19.3.Continued use of the service after changes take effect means that the user agrees to the updated version, unless otherwise required by law.
19.4.If the user does not agree with the changes, the user must stop using the service and, where necessary, remove the user’s materials in accordance with the service documents.
20. Contact Information
20.1.For matters related to this Policy, rights holders and users may contact: admin@p2g.dev.
20.2.The request should preferably include the full name or organization name, contact email, description of the matter, links or identifiers of materials, and documents confirming authority.
20.3.To speed up review, complaints should not be submitted as general statements without specific links, identifiers, file names, or other data that allow the disputed material to be located.
20.4.Legally significant notices may require additional identification of the complainant, confirmation of authority, and submission of documents in a readable format.
21. Priority of the Russian Version
21.1.This Policy may be published in several languages for user convenience.
21.2.The Russian version is the primary version of the document unless expressly stated otherwise on the website or unless mandatory provisions of applicable law require otherwise.
21.3.In case of any inconsistency between the Russian version and translations, the Russian version shall prevail unless mandatory provisions of applicable law require otherwise.
21.4.Translations are provided to inform users and should be interpreted in accordance with the primary Russian version and the general meaning of php2go documents.
If you need a copy of terms, a data request, a copyright complaint, or a payment question, contact support.
mailContact support