Roblox launches Device Trust API for Android security checks
Roblox launches the Device Trust API with Android-only support today. Measure your audience’s trust levels before restricting access or features.
Roblox has launched the Device Trust API, letting developers use device checks to control entry, trading or competitive matchmaking. The October 27, 2026 announcement specifies Android-only support today, with the upcoming Web client also part of the initial launch plan. Roblox plans to add iOS, consoles and Windows in the upcoming year.
Device trust is not player guilt
According to Roblox, the API uses hardware attestation and other signals to check device and app integrity. It returns 4 levels: Unknown for unsupported platforms or attestation errors; None for failed or missing attestation; Standard for passing devices whose data authenticity is not fully assured; and Full for passing, fully updated devices.
Roblox warns that legitimate players can receive None, particularly on older or low-end Android hardware. Some can resolve this through updates or configuration changes; others need another device. Unsupported platforms return Unknown, not evidence of cheating. Roblox also says this layer does not replace server-side validation of actions, currency or scores.
Measure before restricting access
Developers can receive results through IntegrityService.EvaluatePlayerDeviceTrust and optionally return an approval or rejection decision. For checks after joining, Player.DeviceTrustLevel provides the cached result. Roblox recommends server-side access: clients can alter locally reported values, and client availability varies with platform support and rollout.
Our recommendation is to review the new Creator Hub breakdown under Safety, then Anti-cheat, this week before enforcing restrictions. We'd start by recording server-side results without blocking players, then testing a narrow feature policy, such as trading access, against the affected audience. Use the implementation guide and keep existing server validation in place. Treat Unknown separately from None rather than making every unsupported platform fail your access policy.