MonaddleApplications

UPDATED SEPTEMBER 15, 2026

Privacy notice

This notice describes Google account information used by Monaddle’s Warden and SIEM applications, operated by Daniel Porter.

Google sign-in

Google provides an identity token containing your account identifier, email address, verification status and, for managed accounts, organization domain. Basic profile information may also be included by Google. The applications verify this token, apply account access rules and establish a signed-in session.

Sign-in information is used for authentication, authorization and session security. It is not used for advertising or sold. Signing in alone does not authorize access to Google Docs, Drive, Gmail or other Google account content.

Shared demo workspace

Warden demo users share the same chats, sandbox files and connected data sources. Admitted employees can select documents from the owner’s connected Google account and grant chats temporary access. Only the owner can connect or reconnect that Google account; employee sign-in does not connect an employee’s Google Docs account. Chat messages and document content supplied to chats can be seen by other admitted demo users. Use only material suitable for this shared audience.

Sessions and storage

The applications use session cookies to keep you signed in. Session records associate your Google account identifier and email address with your application role. Signing out ends the application session. Application data, such as chats or security events, is separate from your Google sign-in information and may remain after sign-out.

Warden’s separate document connection

Warden also has a separately authorized Google document integration. Connecting it is a different action from signing in. Where enabled, it requests Google Docs access and Drive file metadata to let a user select documents for an agent. Document permissions can include reading and editing document contents and creating documents, depending on the consent granted and the approved operation.

The integration stores its connection credentials on the host service. Agents receive access through approved, time-limited document grants, rather than receiving Google credentials. Content from a document you approve can be processed by the AI provider selected for that Warden chat. Do not connect an account or approve document access unless you are authorized to share that content.

Service providers and disclosure

Google processes authentication. Application hosting providers process the data needed to run the services. Warden’s selected AI provider processes chat inputs and any content supplied to its agents. Google sign-in tokens are used by the authentication service and are not supplied as agent credentials.

Your choices

You can sign out of either application and manage connected-app permissions in your Google Account. Revoking Google permissions does not automatically delete previously saved application data. Contact the operator to request information about retained data or deletion, or to report an access concern.

Contact

Daniel Porter
danielbporter@gmail.com