Privacy Policy

1. Who this policy covers

This policy concerns Operative Anyone accounts, the Director and Operative portals, private operations, fictional cover experiences and optional messaging. The identity and contact details of the final legal operator are not yet published; these must be completed before general release. The service is intended only for people aged 18 and older.

2. Information supplied by you

• Account data: email address, authentication identifiers and any profile information supplied through an approved sign-in provider.
• Eligibility and game data: adult-eligibility and safe-play acknowledgments, codenames, invitations, operation titles and settings, memberships, game status, secret assignments, elimination claims, confirmations, disputes and associated activity records.
• Messages and reports: content you choose to provide in dispute descriptions, support inquiries or reports. Avoid providing home addresses, medical details or other unnecessary sensitive information.
• Optional SMS data: your mobile number, consent and verification timestamps, opt-out status, outbound message and session metadata, delivery/provider identifiers, incoming message text (including Y, N, HELP or STOP) and associated processing outcomes.

Some fields may be populated by the application as you participate, rather than entered directly. Different features may be unavailable until the associated pilot configuration is enabled.

3. Automatically processed technical data

Browsers, hosting and authentication services may process IP addresses, approximate network location derived from IP, device/browser attributes, timestamps, request identifiers, authentication cookies or session tokens, diagnostic and security logs. This may be necessary for service delivery, sign-in, abuse prevention and troubleshooting. Operative Anyone is not designed to continuously monitor players' GPS locations, and players should not add live locations to codenames or reports.

4. Why we use information

We process data to provide account access; authenticate and authorize Directors and Operatives; create and manage invitations and private operations; deliver an authorized target assignment; process claims, disputes and status changes; protect the Service from misuse; investigate credible safety or security issues; communicate about essential service changes; and, only when separately opted into, send game-related SMS verification and confirmation messages.

We do not make SMS consent a requirement for browser-based participation. We do not use SMS opt-in to authorize advertisements or other unrelated campaigns.

5. Who may receive or access data

Authorized players may see their own permitted game information. Directors may see and manage the operation information made available by their role, but being a Director does not automatically authorize access to every private target assignment. Authorized operators and service providers may process information as needed for hosting, authentication, messaging, security or support. Participants can also see information others intentionally disclose within gameplay; please use discretion.

The pilot application uses Supabase for database/authentication functions, Vercel for application hosting and Twilio for optional verification and SMS, when configured. A sign-in provider such as Google may separately process information under its own policies if you select that method. Telecom carriers and delivery partners may handle message routing. Their processing may occur in the United States or other permitted service locations.

Mobile information protection: We do not sell, rent, or share mobile numbers, SMS opt-in records or messaging consent with third parties or affiliates for their own marketing or promotional purposes. SMS consent is not transferred to other marketing programs. We share data with messaging vendors only as necessary to provide the requested messaging, comply with law or protect the service.

6. SMS processing and frequency

SMS enrollment requires a signed-in account, an optional affirmative checkbox, a telephone number and successful verification of that number. If enabled, the system records your verified number, consent timestamp and preferences. Operative Anyone may send verification codes and gameplay messages about elimination confirmation or dispute. Message frequency varies with the number of pending claims in operations where you participate; no fixed monthly message cap is currently implemented. Message and data rates may apply.

During the pilot, Operative Anyone accepts Y or N as replies to a current active request without requiring website login, using the verified originating number and a limited response window. The system processes only one active prompt per verified number at a time, across operations. Replies and provider message identifiers may be retained to prevent duplicate processing, record disputes and honor opt-outs. Reply STOP to unsubscribe; reply HELP for assistance or use the account SMS-disable control. STOP may also trigger provider-level message blocking. See SMS Notifications & Consent.

7. Cookies and session technologies

Authentication and hosting services may use cookies, tokens or similar technologies needed to maintain sessions, verify authorization and protect the Service. Specific cookie names and any optional analytics products must be verified against the deployed configuration before this draft is approved. Do not assume that blocking necessary authentication storage will leave sign-in functioning.

8. Retention and deletion

Accounts, game records, SMS sessions, security events and consent or opt-out records may remain after an operation ends to support game integrity, safety investigations, abuse prevention, legal duties or evidence of preferences. Some information may be preserved in provider logs or backups for limited periods controlled by those providers. There is not yet a verified universal retention schedule or self-service deletion workflow for every data category. Retention periods, backups and deletion procedures are mandatory items for review before general release. We will not promise immediate or total deletion where lawful exceptions or operational constraints apply.

9. Your choices and privacy requests

You may choose not to enroll in SMS, disable SMS after enrollment, request withdrawal from a game through available controls, and avoid including unnecessary information in game content. Depending on applicable law, you may have rights to request access to, correction of, or deletion of personal information, or to appeal an applicable privacy decision. Identity verification and legal exceptions may apply. A dedicated privacy contact and reliable intake procedure must be established before general release. Until then, private testers should use the confidential operator contact provided in their testing instructions, rather than sending sensitive information to a Director by default.

10. Security

We use application authentication, role-based access policies and restricted service functions to limit access. No Internet service or communications provider can guarantee absolute security. Protect your account, use unique sign-in credentials where applicable, and promptly report suspected unauthorized access through the designated testing support channel. SMS itself is not an encrypted end-to-end communications channel and may be visible to people with access to your phone or carrier account.

11. Minors and location-based requirements

Operative Anyone is for adults 18 and older and is not directed at children. If we learn that a minor registered, we may restrict the account and take steps appropriate to remove information where required. State or federal privacy rights and notice obligations depend on the user's residence, processing activities and applicable statutory thresholds. This policy does not assume that Rhode Island or Massachusetts law is the only relevant law.

12. Changes and contact

We may update this policy when the product, vendors, security practices or applicable law change. Material changes should be communicated in an appropriate way, with a revised effective date, and any legally required choices offered. The operator's legal identity, support email or other privacy request contact, and confirmed retention details remain open approval items. For general guidance see Help & FAQ; for private-testing privacy concerns use the contact provided with your invitation.

Account profile and choices

Your account stores a unique operative name, optional full name and phone, and separate game and news preferences by email and SMS. Contact details and full name are private to your account and trusted service processing. Phone ownership is checked through authentication; SMS preferences require a verified matching number. STOP suppresses both SMS channels, including later attempts to re-enable them. Consent changes record a private audit entry with the policy version. A phone suppression record remains to honor opt-out requests. Global leaderboard participation is off by default; opting in permits publication of your operative name and game results, never contact details. Existing memberships retain historical names when you edit your profile. News preferences do not themselves send messages.