PHP2GO DATA DELETION POLICY
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 Data Deletion Policy describes how user data may be deleted, deactivated, anonymized, restricted, retained, or otherwise handled within php2go.
This Policy applies to accounts, PHP projects, source code, build artifacts, diagnostic reports, logs, support requests, payment-related information, and other data connected with use of the Service.
1. General provisions
1.1.This section governs: data deletion terms and relation to other legal documents.
1.2.Such data may be deleted manually, automatically based on retention periods, or upon the User request where deletion is technically possible and not contrary to law.
1.3.The Administration may temporarily retain or restrict deletion of such data if needed for security, accounting, violation investigation, contract performance, refunds, chargebacks, or protection of rights.
1.4.The User must preserve necessary copies in advance and understand that after deletion access, restoration, or repeated download may become impossible.
2. Data categories
2.1.This section governs: account, email, settings, projects, source code, artifacts, logs, payment details, and support requests.
2.2.Such data may be deleted manually, automatically based on retention periods, or upon the User request where deletion is technically possible and not contrary to law.
2.3.The Administration may temporarily retain or restrict deletion of such data if needed for security, accounting, violation investigation, contract performance, refunds, chargebacks, or protection of rights.
2.4.The User must preserve necessary copies in advance and understand that after deletion access, restoration, or repeated download may become impossible.
3. Account deletion
3.1.This section governs: dashboard, profile, settings, operation history, subscriptions, and project access.
3.2.Such data may be deleted manually, automatically based on retention periods, or upon the User request where deletion is technically possible and not contrary to law.
3.3.The Administration may temporarily retain or restrict deletion of such data if needed for security, accounting, violation investigation, contract performance, refunds, chargebacks, or protection of rights.
3.4.The User must preserve necessary copies in advance and understand that after deletion access, restoration, or repeated download may become impossible.
4. Deletion of projects and source code
4.1.This section governs: uploaded ZIP archives, PHP code, Composer dependencies, configurations, templates, and resources.
4.2.Such data may be deleted manually, automatically based on retention periods, or upon the User request where deletion is technically possible and not contrary to law.
4.3.The Administration may temporarily retain or restrict deletion of such data if needed for security, accounting, violation investigation, contract performance, refunds, chargebacks, or protection of rights.
4.4.The User must preserve necessary copies in advance and understand that after deletion access, restoration, or repeated download may become impossible.
5. Deletion of build artifacts
5.1.This section governs: executables, archives, README files, diagnostic reports, build logs, and checksums.
5.2.Such data may be deleted manually, automatically based on retention periods, or upon the User request where deletion is technically possible and not contrary to law.
5.3.The Administration may temporarily retain or restrict deletion of such data if needed for security, accounting, violation investigation, contract performance, refunds, chargebacks, or protection of rights.
5.4.The User must preserve necessary copies in advance and understand that after deletion access, restoration, or repeated download may become impossible.
6. Temporary files and cache
6.1.This section governs: temporary directories, dependency cache, intermediate files, task queues, and service records.
6.2.Such data may be deleted manually, automatically based on retention periods, or upon the User request where deletion is technically possible and not contrary to law.
6.3.The Administration may temporarily retain or restrict deletion of such data if needed for security, accounting, violation investigation, contract performance, refunds, chargebacks, or protection of rights.
6.4.The User must preserve necessary copies in advance and understand that after deletion access, restoration, or repeated download may become impossible.
7. Logs and diagnostics
7.1.This section governs: technical logs, errors, build statuses, IP addresses, user-agent, and diagnostic messages.
7.2.Such data may be deleted manually, automatically based on retention periods, or upon the User request where deletion is technically possible and not contrary to law.
7.3.The Administration may temporarily retain or restrict deletion of such data if needed for security, accounting, violation investigation, contract performance, refunds, chargebacks, or protection of rights.
7.4.The User must preserve necessary copies in advance and understand that after deletion access, restoration, or repeated download may become impossible.
8. Payment and accounting data
8.1.This section governs: plans, payments, refunds, invoices, receipts, subscriptions, chargebacks, and accounting records.
8.2.Such data may be deleted manually, automatically based on retention periods, or upon the User request where deletion is technically possible and not contrary to law.
8.3.The Administration may temporarily retain or restrict deletion of such data if needed for security, accounting, violation investigation, contract performance, refunds, chargebacks, or protection of rights.
8.4.The User must preserve necessary copies in advance and understand that after deletion access, restoration, or repeated download may become impossible.
9. Support requests
9.1.This section governs: correspondence, attachments, screenshots, code fragments, logs, and problem descriptions.
9.2.Such data may be deleted manually, automatically based on retention periods, or upon the User request where deletion is technically possible and not contrary to law.
9.3.The Administration may temporarily retain or restrict deletion of such data if needed for security, accounting, violation investigation, contract performance, refunds, chargebacks, or protection of rights.
9.4.The User must preserve necessary copies in advance and understand that after deletion access, restoration, or repeated download may become impossible.
10. Cookies and sessions
10.1.This section governs: cookies, local browser data, server sessions, authorization tokens, and security settings.
10.2.Such data may be deleted manually, automatically based on retention periods, or upon the User request where deletion is technically possible and not contrary to law.
10.3.The Administration may temporarily retain or restrict deletion of such data if needed for security, accounting, violation investigation, contract performance, refunds, chargebacks, or protection of rights.
10.4.The User must preserve necessary copies in advance and understand that after deletion access, restoration, or repeated download may become impossible.
11. Automatic deletion
11.1.This section governs: outdated artifacts, temporary files, old logs, inactive projects, and incomplete uploads.
11.2.Such data may be deleted manually, automatically based on retention periods, or upon the User request where deletion is technically possible and not contrary to law.
11.3.The Administration may temporarily retain or restrict deletion of such data if needed for security, accounting, violation investigation, contract performance, refunds, chargebacks, or protection of rights.
11.4.The User must preserve necessary copies in advance and understand that after deletion access, restoration, or repeated download may become impossible.
12. Backups
12.1.This section governs: backups, archival systems, rotation, failure recovery, and reapplication of deletion requests.
12.2.Such data may be deleted manually, automatically based on retention periods, or upon the User request where deletion is technically possible and not contrary to law.
12.3.The Administration may temporarily retain or restrict deletion of such data if needed for security, accounting, violation investigation, contract performance, refunds, chargebacks, or protection of rights.
12.4.The User must preserve necessary copies in advance and understand that after deletion access, restoration, or repeated download may become impossible.
13. Request procedure
13.1.This section governs: request through the dashboard or email to admin@p2g.dev with account, project, build, or payment details.
13.2.Such data may be deleted manually, automatically based on retention periods, or upon the User request where deletion is technically possible and not contrary to law.
13.3.The Administration may temporarily retain or restrict deletion of such data if needed for security, accounting, violation investigation, contract performance, refunds, chargebacks, or protection of rights.
13.4.The User must preserve necessary copies in advance and understand that after deletion access, restoration, or repeated download may become impossible.
14. Identity verification
14.1.This section governs: email access confirmation, authorization, project or payment information, or authority documents.
14.2.Such data may be deleted manually, automatically based on retention periods, or upon the User request where deletion is technically possible and not contrary to law.
14.3.The Administration may temporarily retain or restrict deletion of such data if needed for security, accounting, violation investigation, contract performance, refunds, chargebacks, or protection of rights.
14.4.The User must preserve necessary copies in advance and understand that after deletion access, restoration, or repeated download may become impossible.
15. Fulfillment timelines
15.1.This section governs: review timelines, data volume, infrastructure complexity, involvement of payment providers and third-party services.
15.2.Such data may be deleted manually, automatically based on retention periods, or upon the User request where deletion is technically possible and not contrary to law.
15.3.The Administration may temporarily retain or restrict deletion of such data if needed for security, accounting, violation investigation, contract performance, refunds, chargebacks, or protection of rights.
15.4.The User must preserve necessary copies in advance and understand that after deletion access, restoration, or repeated download may become impossible.
16. Grounds for refusal or restriction
16.1.This section governs: law, contract, accounting, tax reporting, security, fraud prevention, disputes, and authority requests.
16.2.Such data may be deleted manually, automatically based on retention periods, or upon the User request where deletion is technically possible and not contrary to law.
16.3.The Administration may temporarily retain or restrict deletion of such data if needed for security, accounting, violation investigation, contract performance, refunds, chargebacks, or protection of rights.
16.4.The User must preserve necessary copies in advance and understand that after deletion access, restoration, or repeated download may become impossible.
17. Third-party services
17.1.This section governs: hosting, cloud infrastructure, payment providers, email services, monitoring, analytics, OAuth, and support.
17.2.Such data may be deleted manually, automatically based on retention periods, or upon the User request where deletion is technically possible and not contrary to law.
17.3.The Administration may temporarily retain or restrict deletion of such data if needed for security, accounting, violation investigation, contract performance, refunds, chargebacks, or protection of rights.
17.4.The User must preserve necessary copies in advance and understand that after deletion access, restoration, or repeated download may become impossible.
18. Consequences of deletion
18.1.This section governs: possible inability to restore a project, build, artifact, report, operation history, settings, or account.
18.2.Such data may be deleted manually, automatically based on retention periods, or upon the User request where deletion is technically possible and not contrary to law.
18.3.The Administration may temporarily retain or restrict deletion of such data if needed for security, accounting, violation investigation, contract performance, refunds, chargebacks, or protection of rights.
18.4.The User must preserve necessary copies in advance and understand that after deletion access, restoration, or repeated download may become impossible.
19. Users from other countries
19.1.This section governs: mandatory user rights under the laws of their country, if such rights apply and cannot be excluded by agreement.
19.2.Such data may be deleted manually, automatically based on retention periods, or upon the User request where deletion is technically possible and not contrary to law.
19.3.The Administration may temporarily retain or restrict deletion of such data if needed for security, accounting, violation investigation, contract performance, refunds, chargebacks, or protection of rights.
19.4.The User must preserve necessary copies in advance and understand that after deletion access, restoration, or repeated download may become impossible.
20. Priority of Russian version
20.1.This section governs: priority of the Russian version in case of inconsistencies, unless mandatory law requires otherwise.
20.2.Such data may be deleted manually, automatically based on retention periods, or upon the User request where deletion is technically possible and not contrary to law.
20.3.The Administration may temporarily retain or restrict deletion of such data if needed for security, accounting, violation investigation, contract performance, refunds, chargebacks, or protection of rights.
20.4.The User must preserve necessary copies in advance and understand that after deletion access, restoration, or repeated download may become impossible.
21. Contacts
21.1.This section governs: data deletion questions to admin@p2g.dev and additional instructions on the website.
21.2.Such data may be deleted manually, automatically based on retention periods, or upon the User request where deletion is technically possible and not contrary to law.
21.3.The Administration may temporarily retain or restrict deletion of such data if needed for security, accounting, violation investigation, contract performance, refunds, chargebacks, or protection of rights.
21.4.The User must preserve necessary copies in advance and understand that after deletion access, restoration, or repeated download may become impossible.
If you need a copy of terms, a data request, a copyright complaint, or a payment question, contact support.
mailContact support