The Service is operated by Aditya Agarwal as an independent project under the name Cardopoly. We act as the data controller for personal information processed through our own servers and databases in connection with the Service.

Authentication and related identity processing are provided by Clerk(Clerk, Inc.), which acts as a processor under our instructions for sign-in, session management, and user-profile data tied to your account. Clerk's privacy policy also applies to how Clerk handles data on its systems: clerk.com/legal/privacy.

2.1 Account and profile (via Clerk + our database)

When you create or use an account, we process:

• Email address and username (required for a full profile in our app).
• A Clerk user identifier that links your Clerk account to our records.
• An internal stable player ID (UUID) we assign for gameplay and stats consistency.
• Password material: if you use email/password sign-in, Clerk stores credentials according to Clerk's practices. Our backend may store a legacy password hash for accounts imported from prior systems; new accounts typically authenticate through Clerk.
• If you choose Sign in with Google, Google receives your interaction with Google's login flow and shares limited profile data with Clerk according to your consent and Google's policies.

2.2 Gameplay and multiplayer

To run matches, we process:

• Lobby and room data, including room identifiers, player display names in the room, readiness state, and related session metadata stored while a room exists.
• Real-time game messages sent over WebSockets between your client and our servers (and through our channel infrastructure) while you are connected to a game.
• After games end, we store game history: room id, duration, player count, winner (if any), and per-player statistics such as win/loss/abandon, cards played, rent and economy-related counters, and counts of specific card types used (e.g. action cards). These statistics power leaderboards and player profiles.

2.3 Social features (friends)

If you use friends features, we store friend relationships and friend requests (who invited whom, status, timestamps) between user accounts.

2.4 Feedback and ratings

When you submit in-app feedback or a rating, we collect:

• Your message, category, optional star rating, and optional written rating comment.
• An optional screenshot you attach (stored on our servers for staff review).
• Technical context: the page URL you were on, browser user-agent string, and viewport size, to help reproduce issues.

We may send an internal email notification when new feedback arrives if server-side email is configured; that email may include details of the submission.

2.5 Clerk webhooks

We receive signed webhooks from Clerk for events such as user created, updated, and deleted. We use these to keep our user database in sync (for example linking email and username). When Clerk deletes a user, we currently deactivate the linked local account and clear the Clerk identifier; historical gameplay or stats rows may still exist until you contact us for a broader deletion request.

2.6 Device storage (your browser)

The app stores small amounts of data in your browser's local storage, including: your theme preference (light/dark), a short-lived rejoin game hint (room id and expiry), and an optional local game log for the current session. This data stays on your device unless our code sends other information to the server as part of normal gameplay or API calls.

2.7 What we do not do (based on the current codebase)

We do not embed third-party advertising or analytics SDKs in the repository for tracking across sites. If that changes, we will update this policy.

• To provide authentication, profiles, and secure access to the Service.
• To create and manage game rooms, run live games, and persist results and statistics.
• To show public-facing profiles and leaderboards (for example username and aggregated stats visible to other players).
• To operate friends, invites, and related social features.
• To receive and triage bug reports and product feedback, and to compute aggregate satisfaction metrics.
• To protect the Service, enforce rules, and troubleshoot technical issues.
• To comply with law when required.

Where GDPR-style laws apply, we rely on: contract (providing the Service you asked for); legitimate interests (securing the Service, improving features, fraud/abuse prevention, and limited internal analytics derived from server logs); and, where required, consent (for example OAuth or optional feedback with a screenshot). You may withdraw consent where processing is consent-based, without affecting prior lawful processing.

We share data with service providers that make the Service possible:

• Clerk — authentication, session, and hosted auth UI assets (which may be served from Clerk-controlled hostnames, including custom domains such as clerk.cardopoly.io and accounts.cardopoly.io when configured).
• Google— only if you choose Google sign-in, subject to Google's terms and privacy policy.
• Vercel — hosting and delivery of the web frontend.
• Railway (or equivalent) — hosting of our API, databases, WebSocket infrastructure, and uploaded feedback files.
• Redis (or compatible) — real-time messaging layers for multiplayer channels.

We do not sell your personal information. We may disclose information if required by law, court order, or to protect rights, safety, and integrity of users and the Service.

We retain account and gameplay data while your account is active and as needed to operate the Service. Game history and statistics may be kept to preserve leaderboard integrity and your profile history unless you ask for deletion. Feedback submissions may be retained for product improvement and audit trails. Server logs are rotated on a typical operational schedule. If you delete your account (via Clerk and/or our deletion flow where available), we will delete or anonymize associated personal data within a reasonable time, except where law requires retention.

We use industry-standard measures appropriate to the nature of the Service (encryption in transit for HTTPS/WSS, access controls on servers, signed webhooks). No method of transmission or storage is 100% secure; we cannot guarantee absolute security.

We and our subprocessors may process data in the United States and other countries where they operate. Where required, we rely on appropriate safeguards (such as Standard Contractual Clauses) or other lawful transfer mechanisms.

Depending on your location, you may have rights to access, correct, delete, export, or restrict certain processing, and to object to processing based on legitimate interests. You may also lodge a complaint with a supervisory authority.

To exercise rights against data we control directly, email aditya130805@gmail.com. For data held primarily by Clerk (such as core auth account settings), you can also use Clerk's account tools and privacy channels.

California residents: we do not "sell" personal information as defined by the CCPA/CPRA in the manner described in those laws. You may still contact us for access and deletion requests regarding personal information we hold.

The Service is not directed at children under 13 (or the age required by your jurisdiction). We do not knowingly collect personal information from children. If you believe we have, contact us and we will delete it.

We may update this policy from time to time. We will post the new version on this page and update the "Last updated" date. Continued use after changes means you accept the revised policy, except where law requires explicit consent.