Launch trust

Security and Native API Boundaries

BuildAPlugin exposes powerful plugin and native bridge capabilities, so the launch site should be clear about what plugins can do, what needs user confirmation, and what is intentionally not silent.

Plugin execution model

BuildAPlugin plugins are local JavaScript files that run inside the app runtime. They can add UI, update requests, persist plugin data, call approved app actions, and request native bridge operations through structured action maps.

Install plugins you trust. Keep secrets in secure storage where possible, and review plugin source before using plugins from outside your team.

SMS, phone, mail, calendar, and contacts

composeEmail, composeSms, and phoneDial open the operating system handler with a draft or dialer screen. They do not silently send email, silently send SMS, or place calls. Calendar and contact operations generate portable .ics and .vcf files that the user can open/import.

Android and private data

androidSnapshot exposes non-sensitive metadata such as build information, app information, battery, display, sensors, system features, declared permissions, and intent-handler counts. SMS inbox, contacts, call logs, phone identity, precise location, and similar private data require explicit Android permissions and store-policy review before being exposed.

Files and desktop commands

File operations use user-selected files/folders or explicit paths. processRun is desktop-only and intended for diagnostics/developer tooling. Plugins should prefer narrow, visible operations over broad filesystem or shell access.