Privacy Policy

How ICPC Assiut handles platform data, visibility, providers, and privacy requests.

Last updated: 2026-05-26

1. Who we are

This website is independently operated for the ICPC Assiut community.

The platform is mainly intended to support competitive programming training and community activity for students, coaches, organizers, alumni, and public visitors interested in the community.

The platform is primarily focused on users in Egypt. It is not currently designed to specifically target users outside Egypt, although people from other countries may be able to access or use it.

2. Information we collect

We collect information needed to operate the platform and provide its features.

This may include:

  • Account information, such as your name, display name, email address, profile image, and Google sign-in information.
  • Profile information you choose to add, such as bio, organization, profile links, and Telegram handle.
  • Programming platform handles, such as Codeforces and VJudge handles.
  • Codeforces-related public information, such as rating, rank, profile photo, standings, gym data, and solve-related data where relevant.
  • VJudge-related information used for training features, such as handles, contest metadata, problem metadata, and progress information where the platform has permission to access it.
  • Guild and Trial information, such as Guild membership, roles, invitations, join requests, spectator grants, access settings, Trial lists, progress dashboard settings, and member dashboard visibility settings.
  • Training and activity information, such as solved-problem counts, progress dashboard rows, gym participation, reviews, ratings, tags, reports, contribution records, and leaderboard-related activity.
  • Notification and announcement information, such as notification status, announcement recipients, and delivery status.
  • User identifiers or account details entered for Guild membership operations, such as member management, join-request handling, and batch member additions.
  • Email delivery information, such as whether a platform email was sent, delivered, bounced, complained about, delayed, rejected, or failed to render.
  • Moderation, security, audit, and abuse-prevention records, such as admin actions, account status changes, report handling, contribution records, and operational logs.
  • Authentication and session information needed to keep you signed in and protect accounts.

Information we do not currently collect

We do not currently collect payment information.

We do not currently collect national ID numbers, phone numbers, physical addresses, dates of birth, gender, religion, health information, official grades, attendance records, university IDs, course enrollment records, or admission/application data as regular platform features.

3. Information that may be public

Some information may be visible publicly or to other users, depending on the feature.

Public profile pages may show information such as:

  • display name or account name
  • verified Codeforces handle
  • verified VJudge handle
  • Codeforces rating, rank, and public profile photo
  • organization, if you add it
  • bio, if you add it
  • public profile links, if you add them
  • joined date
  • contribution points
  • pending contribution count
  • activity counts, such as gym, review, import, tag, and solve counts

Public gym information

Public gym pages may show information such as:

  • gym reviews and reviewer names
  • ratings
  • problem tags
  • contributor names, handles, and points
  • public problem and gym information

Guild and Trial information

Guilds may be public, unlisted, invite-only, or private depending on their settings.

Public Guilds may appear in Guild discovery. Unlisted Guilds may be viewable by direct link. Invite-only and private Guilds are intended for invited users, members, authorized Guild roles, or administrators.

Spectator-safe Guild pages may show overview information and Trial metadata, such as Trial titles, providers, problem counts, and imported contest links. Progress dashboards, member rosters, settings, and management pages are intended for authorized users only.

Private information

Solved counts may be shown publicly, but exact solved-problem lists are not currently shown publicly on user profiles.

Guild progress dashboards and member rosters may show member handles and solved counts to authorized Guild members, Guild roles, or administrators depending on Guild settings and permissions.

Your email address, Google OAuth identifiers, OAuth tokens, admin status reasons, detailed reports, private notifications, provider credentials, and internal account metadata are not intended to be public.

Do not add sensitive personal information to your profile, bio, organization field, reviews, reports, tags, announcements, or any other public or community-facing area.

4. How we use information

We use information to:

  • let users sign in and manage accounts
  • provide profiles, handles, gyms, Guilds, Trials, tags, reviews, ratings, and contribution features
  • show training progress and community activity according to visibility and permission settings
  • import or update Codeforces and VJudge training data where authorized administrators configure or trigger those features
  • support announcements, notifications, and platform emails
  • manage moderation, reports, and contribution integrity
  • protect the platform from abuse, spam, unauthorized access, and misuse
  • debug issues, maintain reliability, and improve the platform
  • enforce platform rules and handle support requests
  • comply with legal obligations where required

Data sale

We do not sell personal data.

5. Google sign-in, sessions, and cookies

The platform uses Google sign-in. When you sign in with Google, we may receive and store account information needed for authentication, such as your name, email address, profile image, Google account identifier, and related authentication records.

The platform uses essential authentication/session cookies or similar technologies to keep users signed in and protect sessions.

The application code currently does not include advertising cookies, retargeting pixels, or marketing cookies. However, infrastructure providers may process technical request data such as IP addresses, request metadata, security events, or logs as part of hosting, routing, security, and reliability.

6. Emails and communications

We may send platform emails related to:

  • account or status updates
  • administrative announcements
  • training or community updates
  • important platform changes
  • operational or security-related notices

Email delivery

Platform emails may include basic personalization, such as your display name or verified handle, where appropriate.

We use email delivery services to send emails and process delivery events, such as sends, deliveries, bounces, complaints, delays, rejects, and rendering failures. Email open and click tracking are currently not enabled.

Organizers or administrators may use limited user information to manage community activities, training groups, access lists, sheets, or related educational/community workflows. For example, accepted trainees may be added to an external group or granted access to a shared resource when needed for a training activity.

We aim to limit such use to information reasonably needed for the relevant activity.

7. Third-party services

We use third-party services to operate the platform. These may include:

  • Google and Google OAuth for sign-in.
  • Google Cloud for hosting, database infrastructure, deployment, logs, scheduling, and related infrastructure.
  • Cloudflare for DNS, routing, CDN/proxy services, email routing, and related infrastructure services.
  • Amazon SES/SNS for sending platform emails and processing email delivery events.
  • Codeforces for public competitive-programming data, handles, ratings, standings, gyms, imports, and solve-related data.
  • VJudge for handles, contest and problem metadata, imported Trials, and progress-related data where authorized administrators configure access.

Provider practices

These providers may process information according to their own terms, privacy notices, and infrastructure practices.

8. Codeforces and VJudge

The platform may use Codeforces data to support training, profiles, gyms, standings, handles, ratings, and solve-related features.

Some Codeforces information is public on Codeforces and may also be shown on this platform, such as handles, ratings, ranks, profile photos, standings, and public contest/gym-related data.

The platform may store VJudge handles if users add them and may use active VJudge handles for Guild Trial progress.

Administrators may provide provider credentials for VJudge operations. Stored credential values are not intended to be displayed back to users or ordinary admins.

Users may report VJudge handle conflicts for administrator review. Conflict reports and review details are intended for authorized administrators.

9. User content and moderation

Users may contribute content or activity such as profile information, tags, reports, reviews, ratings, and other community or training-related information.

You are responsible for the content you submit. Do not submit sensitive personal information, private information about others, spam, abusive content, malicious reports, false information, or content that violates platform rules.

We may moderate, hide, correct, remove, or retain content where needed to protect users, preserve contribution integrity, prevent abuse, fix errors, or operate the platform.

Reports and detailed moderation information are generally available only to authorized administrators or helpers.

10. Admin and helper access

Authorized administrators, organizers, coaches, or helpers may access information when needed to operate, secure, moderate, support, or improve the platform.

Access depends on role and permissions. Not every helper has access to every type of data.

Administrative actions may be logged for security, moderation, audit, abuse-prevention, and platform-integrity purposes.

11. Data retention

We keep information for as long as reasonably needed to operate the platform, preserve training and contribution history, prevent abuse, maintain security, support moderation, and handle operational or legal needs.

In general:

  • Account and profile data may be kept while the account exists.
  • Contribution, tag, report, review, solve, and gym activity records may be retained to preserve platform integrity and history.
  • Audit, moderation, security, and abuse-prevention records may be retained as needed.
  • Email delivery, bounce, complaint, suppression, and related records may be retained for deliverability, abuse prevention, troubleshooting, and platform reliability.
  • Disabled or suspended account records may be retained to prevent abuse and preserve platform integrity.

Retention periods

We do not currently promise fixed retention periods for all categories of data.

12. Account deletion and user requests

You may contact us to ask about your data, request correction, request removal of profile information, or request account deletion.

We review requests case by case.

Where possible, we may disable an account, remove or anonymize profile information, or take other reasonable steps. Some records may be retained where needed for security, abuse prevention, audit, contribution integrity, legal reasons, or platform operation.

The platform does not currently provide a self-service account deletion or data export feature.

13. Minors and student users

The platform is mainly intended for competitive programming students, coaches, and community members. Expected users are generally older students, and the platform is not directed at young children.

If you are under the age required by your local law to use online services independently, you should use the platform with permission from a parent, guardian, school, university, coach, or other responsible authority where required.

We do not intentionally collect unnecessary personal information from minors. Users should avoid adding sensitive personal information to profiles, organization fields, reports, reviews, tags, or other public/community areas.

If a parent, guardian, school, university, coach, or responsible authority has a concern about a minor's information, they may contact us and we will review the request case by case.

14. Security

We use reasonable technical and organizational measures to protect platform data.

Access to personal data is limited to people who need it to operate, secure, moderate, or support the platform.

No online service can guarantee perfect security. If notifications are legally required, we will make them where required.

Do not send passwords, secret tokens, or unnecessary sensitive information through support requests, reports, reviews, or public platform areas.

15. International processing

Because we use third-party service providers, information may be processed in countries other than where you live.

This may include processing by infrastructure, authentication, email, routing, security, or external competitive-programming services.

16. What we do not currently do

The platform does not currently:

  • collect payment information
  • include advertising or marketing cookies in the application code
  • use retargeting pixels in the application code
  • provide user-facing AI features
  • send user data to AI providers as a platform feature
  • support user file uploads
  • provide private messaging or forums

Current feature statements

These statements describe the platform's current features and may change if new features are added.

17. Updates to this policy

The platform may change over time.

If we add features or materially change how information is collected, used, or shared, we may update this policy. The Last updated date will show when this page was last changed.