Trust

Security

Last updated 16 August 2026

The design decision behind all of this

Adease is a desktop application, not a hosted dashboard. Your ad account data travels from the advertising platform to your machine and stays there. There is no central warehouse of customer campaign data, which means there is no central warehouse to breach.

Credentials

Access tokens are written to the operating system's own credential store and are never placed in a plain file, a log or a database we control. Adease asks each advertising platform for the narrowest set of permissions it needs. Revoking access from the platform's own settings cuts Adease off immediately.

Nothing is applied without a person

The agent cannot write to a live ad account on its own. Every change it proposes is queued as a diff and applied only after someone approves it. Each applied action records who approved it and what the platform returned, so there is always an audit trail to work from.

The application itself

Our own systems

The systems we do run hold account details and billing records only. Access is limited to staff who need it, protected by multi-factor authentication, and removed when someone leaves.

Before publishing, confirm what you can evidence. If you hold a certification such as SOC 2 or ISO 27001, or you are in an active audit, say exactly which and link the report. If you do not, leave it out — claiming a compliance posture you cannot evidence is a real liability.

Reporting a vulnerability

If you believe you have found a security issue, email support@adease.io with the subject line "Security". Please include enough detail to reproduce it.

We will acknowledge your report, keep you updated while we investigate, and credit you when a fix ships if you would like us to. Please give us a reasonable opportunity to resolve the issue before disclosing it publicly, and avoid accessing or modifying data that is not yours while testing.

Contact

Security questions and due-diligence requests go to support@adease.io.