Apps and permissions

Before you install a game overlay or companion app

Check where the software comes from, what it can access and whether you need that access for the feature you want. A familiar name, an open-source repository or a working website is useful context, but none is a blanket safety or game-policy guarantee.

By GG Atlas · Reviewed Oct 26, 2026 · About 5 min read

First check whether a browser tab solves the problem

Name the feature you want: an occasional item lookup, repeated in-session price checks, progress tracking or a shared plan. If a website or the game's own settings answer the question, installing a desktop package may add work and access you do not need.

An overlay displays information over gameplay; a companion may run separately; a browser extension can change pages in your browser. One product can combine these formats. Assess the part you intend to use rather than assuming every feature in the package is necessary.

Follow the project's own download path

Find the project or developer's recognised site and follow its download instructions. Compare the destination, publisher information and version with those instructions. A similarly named download page, unsolicited attachment or repackaged installer needs a separate explanation, even when a familiar logo is present.

Read installation requirements before starting. Check the operating system, dependencies and whether another platform or launcher is involved. If an installer asks for something the project's documentation did not prepare you for, stop and investigate rather than accepting it to reach the next screen.

Translate each permission into something the app can do

Ask what the requested access enables. Does the tool read a screenshot, a local log or copied item text? Can it change browser pages, publish an account status or access a shared workspace? These are different capabilities and deserve different explanations.

For a browser extension, look at which sites it can access, not only its name or star rating. Chrome's own documentation describes controls for managing extension access to websites. Check the available controls in your browser and whether the extension still works with access limited to the sites it actually needs.

Which information does it read?
What can it change or publish?
Does it send data elsewhere, and is that explained?
Can the feature run without the optional account connection?
How do I revoke access or remove the software?

Treat game-policy questions separately from software security

A tool can be legitimate software and still be unsuitable for a particular game's rules. Read the publisher's current guidance for the behaviour involved, and distinguish showing reference information from taking actions in the game. Do not rely on a community directory or an old discussion as proof of permission.

If the project claims a feature is permitted, look for the publisher's own statement and check what it actually covers. Do not infer that permission for one tool, feature or game mode extends to every integration. GG Atlas cannot promise anti-cheat compliance or an account outcome.

Example: a price lookup does not require every available connection

Suppose you want occasional price reference. One option works in a browser. Another offers an overlay, an optional trade-account connection and collection syncing. Those extra features may be convenient for frequent use, but they are separate decisions.

Start with the feature that solves the task. Before connecting an account, identify what is added, what data is involved and how the connection can be revoked. Declining an optional feature is not a failure to finish setup. It can be the right choice when you have no use for it.

Put it into practice

Warframe: a browser price check or a relic-reward companion?

Choose based on how often you need the information, not on how many integrations a package offers.

Warframe · Warframe.market
For an occasional lookup, inspect the relevant buy and sell orders in a browser. That can answer a price-reference question without installing a reward overlay.
Warframe · WFInfo
If relic-reward lookups repeatedly interrupt play, read the companion's setup and disclosure first. Its project describes reading reward text from screenshots and presenting Platinum and Ducat information. Decide whether you want that workflow, and assess any optional market-status feature separately.

These are alternatives for different needs, not two required setup steps. The GG Atlas profiles lead to each project's source and recorded disclosures; neither a listing nor an old policy statement is a guarantee about current publisher rules.

Make the first session a small, reversible trial

Record the starting configuration and back up files you intend to edit. Install one new tool at a time, test the feature you chose and make sure you can disable it. This makes it easier to understand a conflict than changing several overlays, extensions and presets together.

Keep the parts that demonstrably reduce an interruption. Remove unused integrations through their normal controls and review any associated account permissions. A clean trial does not establish permanent safety; a changed release, permission request or publisher rule is a reason to review the setup again.