Privacy
PRIVACY POLICY
Last updated: 29 August 2026
This policy explains how Pyenix, operated through Pyenix, handles information used to run the creator gallery and community.
INFORMATION RECEIVED FROM GOOGLE
When you sign in with Google, Pyenix receives the unique Google account identifier, verified email address, display name and basic profile information Google supplies for the approved scopes. Pyenix does not receive your Google password. The unique Google identifier is used to link future sign-ins to the correct local account.
INFORMATION YOU PROVIDE
The service stores profile details, projects, posts, comments, messages, collections, collaboration applications, reports, contact enquiries, preferences and moderation history that you choose or need to provide.
TECHNICAL AND ACTIVITY DATA
Pyenix may record login times, security events, IP-derived rate-limit data, browser information, project views, launch clicks, outbound clicks, saves, reactions, searches and similar operational analytics. The platform distinguishes a page view or launch click from proof that an external video, song or game was fully consumed.
WHY INFORMATION IS USED
Information is used to authenticate accounts, display creator profiles and content, operate community features, prevent abuse, process reports and contact enquiries, maintain security, diagnose errors, provide creator analytics and improve the service.
EXTERNAL SERVICES
Google handles authentication under Google's own privacy terms. Projects may embed or link to YouTube, Spotify, SoundCloud, game hosts and other external services. Embedded providers may receive technical information such as your IP address and browser details as soon as a project page loads their content.
DISCLOSURE
Personal information is not sold. Information may be disclosed when reasonably necessary to operate hosting or authentication, investigate abuse, protect users, comply with law or respond to a valid legal request. Public profile and published project information is visible to visitors according to the visibility settings selected.
RETENTION AND DELETION
Content and account data is retained while needed to operate the service. Deleted items may remain temporarily in backups, logs, audit records, reports or moderation evidence. You may request account deletion or correction through the logged-in contact form.
SECURITY
Reasonable technical measures are used, including prepared database queries, CSRF protection, secure sessions, restricted uploads, permissions and sandboxed embeds. No internet service can promise absolute security, so users should not submit information that is unnecessary or highly sensitive.
CONTACT
Privacy, access, correction and deletion enquiries can be submitted through the public Contact page or the contact address shown there. Account-specific requests may require identity verification.
Last updated: 29 August 2026
This policy explains how Pyenix, operated through Pyenix, handles information used to run the creator gallery and community.
INFORMATION RECEIVED FROM GOOGLE
When you sign in with Google, Pyenix receives the unique Google account identifier, verified email address, display name and basic profile information Google supplies for the approved scopes. Pyenix does not receive your Google password. The unique Google identifier is used to link future sign-ins to the correct local account.
INFORMATION YOU PROVIDE
The service stores profile details, projects, posts, comments, messages, collections, collaboration applications, reports, contact enquiries, preferences and moderation history that you choose or need to provide.
TECHNICAL AND ACTIVITY DATA
Pyenix may record login times, security events, IP-derived rate-limit data, browser information, project views, launch clicks, outbound clicks, saves, reactions, searches and similar operational analytics. The platform distinguishes a page view or launch click from proof that an external video, song or game was fully consumed.
WHY INFORMATION IS USED
Information is used to authenticate accounts, display creator profiles and content, operate community features, prevent abuse, process reports and contact enquiries, maintain security, diagnose errors, provide creator analytics and improve the service.
EXTERNAL SERVICES
Google handles authentication under Google's own privacy terms. Projects may embed or link to YouTube, Spotify, SoundCloud, game hosts and other external services. Embedded providers may receive technical information such as your IP address and browser details as soon as a project page loads their content.
DISCLOSURE
Personal information is not sold. Information may be disclosed when reasonably necessary to operate hosting or authentication, investigate abuse, protect users, comply with law or respond to a valid legal request. Public profile and published project information is visible to visitors according to the visibility settings selected.
RETENTION AND DELETION
Content and account data is retained while needed to operate the service. Deleted items may remain temporarily in backups, logs, audit records, reports or moderation evidence. You may request account deletion or correction through the logged-in contact form.
SECURITY
Reasonable technical measures are used, including prepared database queries, CSRF protection, secure sessions, restricted uploads, permissions and sandboxed embeds. No internet service can promise absolute security, so users should not submit information that is unnecessary or highly sensitive.
CONTACT
Privacy, access, correction and deletion enquiries can be submitted through the public Contact page or the contact address shown there. Account-specific requests may require identity verification.