LEGAL · PRIVACY POLICY
Scopa Privacy Policy
Last updated: 3 October 2026
Scopa is an independent multiplayer card-game service operated by an individual developer using the project name Scopa Studio. Scopa Studio is a project name, not a claim that a separate company has been incorporated. For privacy questions or requests, contact [email protected].
This policy covers the Scopa game and its related websites and apps (the “Service”). It describes the information Scopa handles, why it is used, when it is shared, and the choices available to you. It is written for the Service as currently implemented and will be updated if its features or data practices change.
Information Scopa handles
- Account information. A random Scopa player ID, whether the account is a guest or linked account, and the display name used in the game.
- Google sign-in information. When you choose Google sign-in, Google returns a stable account identifier and may return your profile name. Scopa requests only the
openidandprofilesign-in scopes. It does not request your Google email address, Gmail, contacts, Drive files, or permission to post on your behalf. The authorization code and ID token are processed by the server to verify sign-in; Scopa does not retain Google access or refresh tokens. - Game information. Room membership and the actions needed to run a match. Completed match results, participant IDs, display names, scores, and timestamps may be saved so players can view match history and so the game can operate reliably.
- Room chat. Text, quick phrases, and emoji are visible to people in the room. The current chat service keeps up to 50 recent messages per room in server memory and removes messages older than 30 minutes. Chat history is not kept as a permanent account record by the current implementation; room shutdown or a server restart may remove it sooner.
- Voice messages. If you send a voice message, the audio is stored for delivery to room members. The current service sets voice media to expire after one hour and runs cleanup periodically; deletion may be delayed by service outages or backups. The service also keeps a small database record about the upload (such as room, sender, file size/type, and expiry) for delivery and cleanup. A metadata record may remain after the audio file is deleted. Signed upload/download links expire quickly.
- Security and technical information. The Service and its infrastructure providers may process IP address, request time, browser/device details, error data, and security events to deliver the Service, prevent abuse, and troubleshoot failures. Scopa does not intentionally collect precise location.
- Messages to support. If you email support, Scopa receives the sender address and any information you include.
Please do not put passwords, financial information, or other sensitive personal information into display names, room chat, or voice messages.
How information is used
Scopa uses this information to create and secure accounts, connect players, run games, show match results, deliver room chat and voice messages, investigate abuse or technical problems, respond to support requests, and meet legal obligations. Scopa does not sell personal information, use Google sign-in data for advertising, or use Google sign-in data to train generalized AI or machine-learning models.
Google user data
Google sign-in data is used only to authenticate your account, link it to a Scopa player ID, and display the profile name Google supplies when available. Scopa’s handling of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. You can revoke Scopa’s sign-in access in your Google Account. Revocation stops future Google sign-ins but does not itself delete your Scopa account or match records.
When information is shared
Scopa shares information only as needed:
- with room members, who can see your chosen display name, game actions, and the messages or voice messages you send in their room;
- with Google to complete the sign-in flow;
- with infrastructure providers that operate or protect the Service, such as Cloudflare and the providers used for application hosting, database, networking, and voice storage; and
- where disclosure is reasonably necessary to comply with law, respond to valid legal process, protect users, or protect the Service from abuse or security threats.
Scopa does not make private room content public by default. Third-party providers handle information under their own terms and privacy notices. The Service may be operated from infrastructure in a different country from yours, so information may be processed across borders.
Retention
Room chat is held in memory for up to 30 minutes (and up to 50 recent messages per room), unless removed sooner. Voice media is configured to expire after one hour; its file deletion may be delayed if systems are unavailable, and a metadata record may remain afterward. Account identifiers and completed match results are kept while needed to provide accounts, match history, and service integrity. Expired login transactions and sessions become unusable, but their database records may remain until they are removed through maintenance. Support correspondence is kept only as long as needed to resolve the request and maintain appropriate service records. Information may be retained longer where required by law or needed to address security incidents or disputes.
Your choices and privacy requests
You can choose not to use Google sign-in and can stop using the Service at any time. You may ask Scopa to access, correct, export, or delete personal information associated with your player ID by emailing [email protected]. Include your display name or player ID, but do not send passwords or Google sign-in codes. Scopa may ask for reasonable proof that you control the account before acting. Account deletion may remove or unlink account information; match records may be retained in a form that no longer identifies you where needed for service integrity or required by law. Scopa will respond within the period required by applicable law.
Rights depend on where you live. Nothing in this policy takes away rights that cannot be waived under applicable law. If you believe a child has used Scopa in a way that violates this policy, contact support so the issue can be reviewed.
Age
Scopa is intended for people aged 13 or older. If the minimum age to use online services or consent to data processing is higher where you live, that higher local age applies. Scopa does not currently ask for a date of birth or perform age verification. The Service is not directed to children under 13 and does not knowingly seek to collect their personal information. If Scopa learns that a child under 13 has provided personal information, a parent or guardian should contact support so the matter can be reviewed and the information removed where appropriate.
Cookies, device storage, and security
The web Service uses storage needed to maintain a login session and protect requests. The game may store local preferences. Scopa does not currently use advertising cookies. Scopa uses reasonable safeguards such as encrypted network connections, restricted service credentials, access controls, and short-lived media links. No internet service can guarantee absolute security.
Changes and contact
Scopa may update this policy when the Service or its data practices change. The “Last updated” date will change with a revised policy. For material changes, Scopa will provide notice in the Service or by another reasonable means where required.
Privacy contact: [email protected]. The service operator uses the project name Scopa Studio.