unpromptedDocumentation
← Back to Unprompted

Unprompted privacy policy

Last updated: November 3, 2026

Unprompted is an independent open-source project developed by Xinghan Pan. This policy describes the Unprompted website and the locally run Unprompted application, including its use of Google user data.

What Unprompted does

Unprompted helps you find and organize work from sources you connect, gather supporting context, and prepare replies, documents and other actions. It runs on your device. You choose which accounts and model to connect and which external actions to authorize. The current application has no project-hosted application backend or analytics endpoint.

Google data we access and why

Connecting Google is optional. After you grant Google permissions, Unprompted accesses the following data according to the features and permissions you select:

You may choose additional Google OAuth scopes for other authorized Google API actions; what can be accessed depends on those scopes and the action you authorize. Google shows its permissions when you connect or change access. Unprompted uses data to provide its visible work-assistance features and to carry out actions you authorize.

Storage, security and retention

Google content, identifiers, derived task records, evidence, drafts, history and memories may be stored in the local workspace. OAuth credentials and model settings may be stored in the local configuration. Local records can remain until you clear or delete them. The application binds its server to localhost without built-in authentication. Data, saved tokens and model keys are not encrypted at rest by the application; operating-system permissions and device-level encryption can help protect them. See the storage documentation for locations and configuration.

Sharing and model processing

Unprompted contacts Google to read or perform authorized actions. When you configure a model, selected task context, which may include Google messages, documents or derived data, can be sent to that model endpoint to perform the task. If the endpoint is remote, its provider receives that data; a compatible local model can avoid that remote transfer. Authorized actions can also send data to the destination you choose, such as a message recipient or connected service. Providers have their own retention and processing terms; check them before connecting a model or service.

The Unprompted project does not sell Google user data or use it for advertising. The project does not use Google user data to train generalized AI models. Before selecting a remote model, check that its data handling, including retention and training, is compatible with the permissions and policies that apply to your Google data. The project cannot control a separately configured provider's practices.

Google data is subject to the Google API Services User Data Policy and, where applicable, the Google Workspace API User Data and Developer Policy, including its Limited Use requirements. These policies restrict uses and transfers of Google user data.

Disconnect, revoke and delete

You can pause observation or disconnect a source in Unprompted. Disconnecting stops new reads but may retain local copies. Use Disconnect and clear when available to remove the source's local data and derived records, or use Forget for selected records. Review cleanup results: active operations, database files, migration backups and independent copies can limit removal. After stopping the application, you can also remove its workspace and configuration files; see the storage documentation and privacy controls.

To revoke Google's authorization, remove Unprompted in your Google Account connections. If you supplied credentials through environment variables or files, remove those separately. Clearing local data or revoking access does not delete the original Google messages or files, data already sent to a model or other provider, or independent backups. Contact the relevant provider about its copies.

Other connected services

Reading another cloud source contacts that provider, and the local workspace may contain its content and related task records. External actions depend on your selected permissions and authorizations. Connected services, your organization and model providers may have their own privacy and security requirements.

This website

GitHub Pages hosts this website and receives connection information, including IP addresses, to deliver and secure it. See GitHub's Privacy Statement for its processing and retention. The site has no project-operated analytics, advertising trackers, account registration or personal-data collection forms. Its assets are served with the site; the install-command button writes to your clipboard when pressed. Language and animation preferences are kept in memory for the current page.

Questions and privacy requests

For privacy questions or requests, email xinghan090611@gmail.com. You may also use the issue tracker to request a private channel. Issues and pull requests are public; do not post credentials, workspace files or private content. For vulnerabilities, follow the security reporting instructions.

Depending on your location and who controls processing, you may have rights to access, correct, delete or obtain a copy of personal data, object to or restrict processing, or complain to a data protection authority. Contact GitHub, your organization or a connected provider about data they control; the maintainer cannot directly erase their copies.

Changes

The date above identifies this notice. Repository history records revisions. Changes to Google data use require notice and consent as required by Google's policies before the new use.