Local processing
Screen recognition and assistant logic run locally on the user's Windows PC.
Safety & Privacy
Built around local screen recognition.
Peraphite is designed as a local Windows assistant. This page explains what it does, what it does not do, and what data may be involved during licensing and support.
No game-file modification
Peraphite interacts through screen recognition and standard Android input via LDPlayer. It does not patch, inject into, or modify game files.
No game password required
Peraphite does not require the user's game password.
Official release signing
Peraphite release builds are digitally signed using Microsoft Artifact Signing. Windows can verify the publisher and detect modified files.
Human-paced input
Peraphite does not spam the same screen coordinate with instant repeated clicks. Actions use deliberate pauses and small timing variations, closer to normal touch interaction with the game interface. This also gives menus and animations time to respond before the next action.
Controlled runtime
The interface exposes START/STOP state, runtime status, and logs. Stop requests are handled carefully, but no software can promise perfect behavior in every game state.
License privacy
License validation uses only the minimum data required for activation, device validation, and subscription status. Payment-provider details are not described until integration is finalized.
Data handling
What stays local and what may be sent.
Stays local
Screen processing, UI recognition, local settings, and runtime state are handled on the user's Windows PC.
May be sent
License key, device validation data, subscription status checks, support emails, and diagnostics voluntarily shared with support may be processed externally.
Not a detection claim
This page is about software trust and privacy. It is not a claim that account restrictions are impossible or that use carries no risk.