LoginSign-Up

Project PS Unified Privacy Policy

Language precedence: This English version is provided for convenience. In case of any discrepancy between the Korean and English versions, the Korean version (/privacy) shall prevail.

1. Scope

This Privacy Policy applies to the following Project PS services (one unified account across all):

  • project-ps.com: problem solving and contest participation
  • papyrus.project-ps.com: problem creation and management
  • edu.project-ps.com: online lectures (curriculum content)
  • Public board: Q&A / information sharing (public posts and comments)

2. Purposes of processing

We process personal data to:

  1. manage accounts (registration, login, authentication, deletion)
  2. provide problem solving/contest features (submissions, judging, results, records)
  3. provide problem authoring and publishing features
  4. provide online lecture (curriculum) content
  5. operate the public board (display posts/comments, handle reports/disputes)
  6. ensure security and service stability (fraud prevention, incident response)
  7. respond to inquiries and resolve disputes
  8. (Optional) provide GitHub integration for authoring
  9. (If applicable) provide advertising and analytics (e.g., Google AdSense / Google Analytics)

3. Data we collect

3.1 Required for account registration

  • Email, Username, Nickname, Password
  • Passwords are stored using a non-reversible method (e.g., one-way hashing).

3.2 Automatically collected during use

  • IP address, access time, User-Agent (browser/device), cookie/session identifiers, request URL/referrer (depending on settings), security/error logs (depending on settings)

3.3 Service-generated data (submissions/records)

  • Source code submissions, judging results, timestamps, language, runtime/memory metrics, contest participation/results/rankings
  • Note: Combined with account data, these records may be considered personal data.

3.4 Public board data (public posts/comments)

  • Post title/body (may include Markdown), timestamps
  • Comment body (may include Markdown), timestamps
  • No file upload/attachment feature on the board.
  • Note: The board is public. Do not include personal data or secrets (tokens/keys/passwords) in posts/comments.

3.5 Optional GitHub integration

  • GitHub Apps access token, minimal GitHub identifiers required for integration
  • Used for: authoring features that require GitHub integration
  • The token is deleted when it expires or when you disconnect it in Settings.

3.6 Payment data

  • No payment features are provided and no payment data is collected.

4. Public display / visibility

4.1 Public account identifier

  • The only account identifier shown to other users is your Nickname.
  • Your Username and Email are not publicly displayed.

4.2 Records that may be visible

  • Submission records (time/result), rankings/contest results, board posts/comments, and author labels for content may be visible in the service, with the author shown as Nickname.

4.3 Source code visibility

Depending on service functionality/policy, submitted source code may be viewable by:

  • the author of the problem, and
  • other users who solved the same problem (e.g., met the “solved/accepted” condition defined by the service)

5. Retention

  • Account data: until account deletion
  • GitHub token: until expiry or disconnect, then deleted
  • Access logs: up to 3 months (for security/stability)
  • Submissions and contest/judging records: after account deletion, we may keep them with identifiers removed (e.g., showing “Deleted User”) for continuity and integrity of service records
  • Public board posts/comments:
    • You can delete your own posts/comments using the in-service deletion UI.
    • If content remains after account deletion, the author label may be replaced with “Deleted User”.
    • We may remove or restrict content if required by law or policy (e.g., privacy violations, rights infringements).

6. Deletion

We delete personal data when the purpose is achieved or retention expires, using reasonable technical measures.

7. Sharing with third parties

We do not sell personal data. However, data may be transferred/processed by service providers used to operate the service (see “Processors and international transfers”), and we may disclose data if required by law.

8. Processors and international transfers

We use:

  • AWS RDS (Seoul region, South Korea) for database hosting/storage
  • Cloudflare for CDN/security
  • Google services (Analytics, Search Console, AdSense) for analytics/search performance and advertising

Due to the global operations of Cloudflare/Google, data may be processed or accessed outside South Korea.

9. Cookies, analytics, and ads (AdSense)

We use cookies or similar technologies for session/login, security, analytics, and advertising.

Google AdSense summary

  • Third-party vendors, including Google, may use cookies to serve ads based on prior visits.
  • Google’s advertising cookies may enable Google and its partners to serve personalized ads.
  • You can manage/opt out of personalized ads and some third-party vendors via:

(Optional) Google Analytics opt-out: https://tools.google.com/dlpage/gaoptout?hl=en

10. Your rights and contact

For requests (access, correction, deletion, etc.), contact:
[email protected]

11. Security

We apply reasonable security measures such as HTTPS, access controls, and password hashing.

12. Changes

We may update this Policy and will post notice within the service.