VIRULE Privacy Policy

Effective date: October 1, 2026

VIRULE is a Windows application for game developers and publishers that provides tools for managing games, outreach campaigns, contacts, Steam keys, builds, and related workflows.

This Privacy Policy explains how VIRULE handles information when you use the application, including information accessed through Google APIs.

Local Application Data

VIRULE is designed as a local-first application. Application records and configuration are stored on the user's computer rather than in a VIRULE-hosted cloud account.

Depending on how you use VIRULE, locally stored information may include:

• Publisher, developer, and game records
• Contacts and outreach lists
• Campaign information
• Steam keys and related campaign records
• Email and reply-tracking information
• Application settings and build configuration

Users are responsible for maintaining appropriate backups of locally stored VIRULE data.

Press Access and Press Activity

Some games distributed with VIRULE offer Press Access: earlier access for people who received a press Steam key from the game's developer or publisher. Using Press Access requires verifying that Steam key with VIRULE.

When someone uses Press Access, VIRULE may record limited Press Activity:

• Successful verification of the press Steam key with VIRULE (key use)
• When the game is opened
• When the game is closed
• Related technical identifiers required to provide Press Access and associate the activity with the developer or publisher that issued the key

The developer or publisher that issued the press key can see that Press Activity.

Press Activity does not include your name or email address, gameplay behavior, inputs, screenshots, files, or the contents of your computer. Key verification is performed by VIRULE and is separate from redeeming a key on Steam; VIRULE does not receive information from Steam about whether a key was redeemed there.

Press Activity recording is limited to the period before the game's public release and ends at public release. VIRULE does not collect Press Activity from the general public after a game's release. The separate usage information described under “Usage Information” below applies to every session of a game that includes VIRULE.

QA Access and QA Activity

Developers and publishers can invite testers to a game through VIRULE QA Access. Accepting an invitation verifies the tester's computer with VIRULE.

When QA Access is used, VIRULE may record limited QA Activity:

• That an invitation was issued and that it was accepted
• When a tester opens and closes the game
• The result of the automatic check VIRULE runs after a test session and, when that check finds a problem, one short technical description of it
• Whether a tester's access was revoked or restored
• Related technical identifiers required to provide QA Access and associate the activity with the developer or publisher that issued the invitation

To show an invited tester what they are accepting, VIRULE stores the name of the inviting organization and the title of the game with the invitation. The developer or publisher that issued the invitation can see that QA Activity.

QA Activity does not include the tester's name or email address, gameplay behavior, inputs, screenshots, files, or the contents of the tester's computer.

Usage Information

VIRULE records limited information about how its software is used, so that it can understand how the product is used and keep it working. This information is sent to VIRULE's own service. VIRULE does not use a third-party analytics service for it.

Usage information is made of identifiers, short event names, version numbers, times, and counts. The identifiers are random values created by VIRULE. They are not your name, email address, Windows user name, or any hardware serial number.

The VIRULE application

When VIRULE is installed, it checks with VIRULE for updates when it starts and a few times a day while it is running. That check includes:

• Identifiers for the VIRULE installation on that computer
• If the installation's identifier has changed, the identifier it used before, so that VIRULE can recognize it as the same installation
• The installed VIRULE versions

VIRULE's service records when the installation was first and most recently seen.

When you use VIRULE to manage games, VIRULE also records which kinds of actions were taken, for example that a game was created or edited, that a tool was turned on or off, that a build was made or failed, that a campaign was created, changed, or sent and how many messages it sent, or that a setting was changed. Each record carries an identifier for your VIRULE workspace and for the session in which the action was taken, and refers to games, builds, campaigns, testers, and organizations by identifier rather than by name. These records are stored on your computer first and sent with a later update check.

These records do not include the names or titles of your games, campaigns, or organizations, your contacts or their email addresses, the content of your email, Steam keys, file names or folder locations, or the files on your computer.

Games that include VIRULE

A game distributed with VIRULE contacts VIRULE when a play session starts and when it ends normally. It does not send information while the game is being played. For each session VIRULE records:

• An identifier for the VIRULE installation on that computer, created the first time it is needed
• Identifiers for the game and the build
• When the session started and ended, and whether it ended normally
• Which VIRULE features that build includes
• Counts of how the VIRULE overlay was used: how many times and for how long it was open, and how many times its leaderboard, feedback, review, troubleshooting, promotional, and link controls were used

If a session cannot be reported, for example because the computer is offline, the record stays on that computer and is sent the next time the game starts.

These records do not include your name or email address, your Steam account, gameplay behavior, inputs, screenshots, which links were opened, files, or the contents of your computer.

Network addresses

Like any internet service, VIRULE's service receives the network (IP) address of a computer that contacts it. VIRULE uses it to limit how often requests can be made and does not store it in the records described above.

Google Account Access

Connecting a Google account is optional and is initiated by the user.

VIRULE requests only the Google permissions needed for its Gmail-based outreach features.

Sending Email

VIRULE requests Gmail permission to send email on the user's behalf.

This permission is used to send outreach and campaign emails created and initiated by the user through VIRULE.

VIRULE does not use this permission to send unrelated advertising or email independently of the user's outreach activity.

Reading Email

VIRULE requests read-only Gmail access so it can identify replies to outreach messages and associate those replies with the appropriate contacts and campaigns inside VIRULE.

Read-only access does not allow VIRULE to modify or delete Gmail messages.

Use of Google User Data

Google user data accessed by VIRULE is used only to provide the user-facing Gmail and outreach functionality requested by the user.

VIRULE does not use Google user data for advertising.

VIRULE does not sell Google user data.

VIRULE does not use Google user data to build advertising profiles.

VIRULE does not transfer Google user data to third parties except where necessary to provide functionality requested by the user, comply with applicable law, protect against security threats or abuse, or where the user has provided explicit consent.

VIRULE's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Storage of Gmail-Related Data

VIRULE's Gmail integration is designed to operate locally on the user's computer. Gmail-derived campaign and reply information used by VIRULE is stored as part of the application's local data rather than in a VIRULE-hosted mailbox service.

VIRULE does not operate a remote email inbox on behalf of users.

Google itself processes Gmail and OAuth activity according to Google's own terms and privacy policies.

OAuth Credentials

VIRULE uses Google's OAuth authorization system so users can grant Gmail permissions without giving VIRULE their Google password.

Authorization credentials are used only to maintain the Gmail connection and provide the functionality authorized by the user.

Data Retention and Deletion

Locally stored VIRULE data remains on the user's computer until the user removes it, removes the VIRULE data files, or uses deletion functionality provided by the application.

Press Activity, QA Activity, and usage information are kept by VIRULE's service. Usage records that have not yet been sent are kept on the computer that created them and are removed from it once VIRULE's service confirms it received them. To ask about or request deletion of information held by VIRULE's service, use the contact address below.

Disconnecting a Google account prevents VIRULE from continuing to use that connection.

Users may also revoke VIRULE's Google access through their Google Account security settings.

Sharing of Information

VIRULE does not sell personal information.

VIRULE does not operate a centralized service that publishes a user's contacts, campaigns, email content, Steam keys, or other locally stored business records.

The Press Activity, QA Activity, and usage information described in this policy are stored by VIRULE's own service, which runs on infrastructure provided by Cloudflare. VIRULE does not sell that information and does not use it for advertising. Press Activity and QA Activity are shown to the developer or publisher that issued the key or invitation, as described above.

If future VIRULE features introduce optional online synchronization, peer-to-peer sharing, or other new forms of data transfer, this Privacy Policy will be updated before those features are made generally available.

Security

VIRULE is designed to limit access to user information to the functionality required by the application. No software or storage system can guarantee absolute security, and users should maintain appropriate security and backups for their computers and business data.

Third-Party Services

VIRULE may interact with third-party services selected by the user, including Google Gmail, Steam, websites, and other external services.

Those services operate under their own terms and privacy policies.

Changes to This Policy

This Privacy Policy may be updated as VIRULE develops or its functionality changes.

Material changes affecting how user information or Google user data is accessed, used, stored, or shared will be reflected in an updated version of this policy.

Contact

Questions about this Privacy Policy or VIRULE's handling of user data may be sent to:

nrwentertainment@gmail.com