That data will be sent to Modulate’s secure servers for deeper contextual analysis, after which it is shared through a secure web console or API for your moderators to examine and respond to. Our servers are secured with industry best practices in an isolated AWS environment, and can be linked through VPC Peering with your existing AWS environment to further minimize any security risks related to the sending or receiving of data. If absolutely necessary, we are also able to deploy ToxMod on-premise within your own environment, though this may result in increased costs and alterations to support responsiveness.

To start, we don’t collect any PII about your users; just the relevant voice chat information and an anonymized user id. ToxMod only stores data to aid your moderators in making their decision. Moderators will be able to see saved audio, transcriptions, and other conversational context (for harmful conversations only, of course!) for a set number of days before that data is deleted. And of course, all data is stored and transferred using industry-standard encryption. Modulate also conducts regular penetration and security tests and is certified with full ISO 27001 compliance.

Modulate never shares your player data with any third parties. Some studios authorize Modulate to use portions of their data (after additional anonymization is done) to improve ToxMod’s core services, but by default, each customer’s data is used only within their own ToxMod ecosystem.

The data is associated only with a User ID (or other identifier specified by the client) and all data is automatically deleted after thirty days. Of course, we also support data subject requests (as defined in e.g. GDPR), and can delete data for users immediately upon request - though we require that request to be validated by you first, since we don’t have any data on our side to tie any Modulate user ID to a specific real person. For more, please see the Privacy and Data section of our website.

We can’t answer that for you, but we can show you that our commitment to ethics is more than just words. Modulate exists to make online communities better, and we’re not afraid to pump the brakes on features or ideas that could cause more harm than good or put your security at risk.

ToxMod is designed to scale to many millions of simultaneous chats without issue. This is made possible by our revolutionary triaging technology, which uses multiple algorithmic “gates” to quickly identify non-toxic chats which don’t require moderation.

When you integrate with our SDK, we strongly recommend you send us individual audio streams for each user rather than a mixed stream.. If this is impossible, ToxMod can still function while processing the mixed audio, but its performance and accuracy will be decreased compared to the single-stream-per-speaker approach.

We actively train our models to incorporate commonly used slang and gaming terminology. Additionally we collaborate with our customers to ensure any vocabulary that is specific to their game is included in our models.

ToxMod has currently been trained only for the English language, but our model architecture supports any language straightforwardly. Multiple languages including Korean, German, Spanish, Mandarin, and French are currently planned on our roadmap in the near future, and we are happy to work with customers on any additional language support needs.

Platforms: Window 7+, MacOS, Android (including Oculus), iOS, PS4, PS5, Xbox One

ToxMod can be integrated with any game engine and VoIP solution fairly seamlessly; but we additionally offer example plugins to expedite integration for some of the most common setups.

The exact values vary a bit depending on your platform, but typically between 8-16 MB memory, and about ~0.5% CPU usage.

Yes. By default, ToxMod data is visible on your ToxMod Web Console, but this data is supplied through a straightforward HTTP API. If you already have a moderation platform you wish to continue using, we’re happy to work with you to connect our API to that system.

Absolutely! ToxMod automatically learns based on your moderator’s behavior what should and shouldn’t count as disruptive, but if you’d like to do more, we give you additional levers related to different types of offenses (such as racial offenses vs religious hostility.) You can set your tolerance for each category individually, so if your game has substantial violence built in, you might only moderate the most severe violent dialogue, compared to a game which was catering to a younger audience. These settings can be adjusted live from your ToxMod Web Console at any time.

ToxMod is designed with a core SDK which can integrate smoothly into any game regardless of your specific game engine, VoIP solution, or platform, as well as some convenience wrappers to speed up the integration further for certain common setups (such as Unreal Engine + Epic Voice Chat + PC.)

If you’re looking for an engineer on your team to integrate one of these convenience “plugins”, you’ll need someone who meets the following criteria:

• They are a game developer who knows how to use a game engine (Unity / Unreal), and they know how to install a plugin for that game engine
• They have integrated (or are integrating) voice chat into your game (presumably through a plugin)
• They do NOT have to know audio programming or the ins and outs of how voice chat works. 
• They SHOULD know where in your code a player joins and leaves a voice chat room, and how you communicate that to your voice chat framework
• They are comfortable with the primary programming language for the game engine you are using
• They don’t need to know how to work with DLLs or shared libraries, but it can sometimes aid debugging if your game already utilizes similar dependencies to those our plugin will include (particularly libopus)
  

If you’ll instead be using the C++ Core SDK directly, you’ll want someone with the above expertise as well as a few other points of knowledge. The specific expertise you need will depend on whether you’ll be implementing our Server-Side SDK (Enterprise customers only) or our Client-Side SDK.

Client-Side SDK prerequisites

• They’re capable of managing state, creating/destroying resources “responsibly”, working w/ structs & pointers & C arrays
• If your game (or more precisely, voice chat framework interface with your game) is in another language, they are comfortable writing a wrapper for that language around our C interface
• They know audio programming - they know not to allocate memory in the audio thread, they know how to do format conversation (e.g. shorts to floats), etc.
• They know how your voice chat framework works - they know where the callback to get raw audio is, they know where the information on player and session identities lives, etc.
• They know how to deal with incorporating and maintaining shared libraries on your platform

Server-Side SDK prerequisites

• All Client-Side SDK prerequisites, plus…
• They know how to interact with raw opus packets from your voice chat stream on the server-side
• They are comfortable with multithreading (voice chat servers may receive many packets on distinct threads at once)