Privacy and Google data use

What you choose to connect

Google access starts when you choose Sign in with Google, select an account, and grant permissions on Google’s consent screen. The built-in integration requests read-only access to Gmail, Calendar, Drive file metadata, Docs, Sheets, and Tasks.

These permissions support the actions you request: viewing unread mail metadata and snippets, upcoming events, recent file metadata, task lists and tasks, a document by its identifier, or a spreadsheet range. The built-in actions do not send mail or edit your Google files, calendar, or tasks.

Where information goes

The local Arnés server exchanges authorization codes and tokens directly with Google and sends API requests directly to Google. Results are displayed in your local workspace. The built-in Google integration does not send your Google content to an Atomic 22 Industries server, advertising service, or AI model provider.

Other dashboards, services, and plugins you choose to use have their own data practices. Third-party plugins execute with the access of your local Arnés process; install only code you trust. This policy does not describe those independent services.

Storage and retention

Account access and refresh tokens are stored on the computer running Arnés, outside its source repository. Windows installations protect saved credentials using Windows DPAPI for the signed-in operating-system user. On other supported systems, the credential store uses local files with owner-only permissions; the installation owner is responsible for protecting that computer and account.

The built-in integration displays Google API results without maintaining a separate content archive. Activity records contain action names, times, and outcomes; they exclude message bodies, file contents, commands, and credentials. Local activity files rotate. Browser-local navigation settings are stored separately in your browser.

Your controls

Disconnect Google account removes the saved account tokens and attempts to revoke the Google grant. If Google cannot be reached, Arnés reports the revocation failure so you can remove its access through your Google account. Installation client settings remain available for a later sign-in. Disabling the plugin stops access inside Arnés but retains its saved connection.

You can also revoke access in your Google account’s connections settings. The installation owner controls local files and backups. Clearing browser storage alone does not remove the local server’s credential store.

Use of Google API data

Google API data is used to provide the connected features you request. The built-in integration does not sell it, use it for advertising, or use it to train generalized AI models. Arnés’ use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

Website and support

This static website is hosted by GitHub Pages. Requests to it are subject to GitHub’s privacy statement. Visiting the website does not connect a Google account to Arnés.

For questions or data-use concerns, contact the maintainer through the project issue tracker. Do not post tokens, credentials, private mail, or document contents in a public issue.

Terms of use

Arnés is provided under its MIT software license, including that license’s warranty and liability provisions. You control your local installation and the services and plugins you connect. Google services remain subject to Google’s terms and account policies.