Security and privacy
OSM does not interfere with running games. It is built that way and checked automatically at every build. The overview below shows which mechanisms OSM uses and which limits apply.
Passive behavior toward the game
OSM analyzes, calculates and recommends; the actual action in the game is always taken by the member.
| What OSM does (core and plugins) | What OSM never does |
|---|---|
| A screenshot through the normal Windows interface, only on a key press. | No reading, writing or altering of the game's memory or process. |
| Local text recognition, offline, on exactly that picture; the raw data is discarded afterwards. | No injecting of code, no intercepting of graphics. |
| Read-only access to the game's log file, only when the member turns it on. | No keys or mouse clicks sent to the game, no macros, no bots. |
| Read-only access to game data of its own installation, only on the leadership's click. | No altering of game files, no bypassing or influencing of Easy Anti-Cheat. |
| A copy of the keyboard through Raw Input, and of the mouse when a side button is bound: The app receives every key but reacts only to the bound ones, and each reaches the game unchanged. | No swallowing, altering, logging or storing of keys; no keyboard hook. |
| Its own visible app windows; brief hiding only for the duration of a screenshot. | No hiding or disguising of windows beyond that. |
Every system call stands in a list, with its reason. If one is missing, the build's check fails.
Even a passive companion is not expressly approved by Cloud Imperium Games. We do not claim OSM is “allowed”; we build it so that it does nothing the terms of use forbid.
End-to-end encryption
Confidential content is encrypted locally on the member's device, per area and clearance level, and decrypted only at the authorized recipient. Relays transport only encrypted data packets: They see connection data (IP addresses, times, amounts of data and which addresses use the same channel), but never the content. An organization's own service never sees file contents either; its modules read only what their task needs, such as the office's configuration and the list of badges. The organization's cryptographic root stays with the leadership.
Clearances and redaction
Clearance rules what someone may read; rank rules what they may do. Information above your clearance never arrives as plain text, only as bars whose length is rounded and capped and shows the extent only roughly.
Network communication and endpoints
OSM connects only to these destinations, with no telemetry and no crash service:
- The organization's relays: public or self-run relays that transport only encrypted data.
- The organization's own service: if there is one, the relay; the way of the office's packages is built, but not yet tried against a real service, voice is to follow.
- Update point: not yet in operation. The app asks for a new version and downloads it in the background, checked against checksum and signature; it installs only on a click.
- Discord: the sign-in in the browser at the first joining (Discord gives the account's ID and name and, if the office has named its Discord server, the roles there), and the sharing a member clicks themselves, redacted to their level.
- Sources of a plugin: for Star Citizen UEX for prices, with the member's token, and the Star Citizen Wiki, from which the app fetches game data once a day as long as none from its own installation or an office package is there. The office's data does not go there.
No data stored by ASMOD
There is no user account with ASMOD. This website does without tracking, cookies and outside resources. The update point will deliver only packages with checksums and signatures. Planned is, at an organization's wish, an entry in a list of servers, and nothing else. Details in the privacy statement.