Empyralis

What we store

We may store account identifiers, workspace settings, chat messages, uploaded files, generated replies, memory summaries, connected app metadata, channel user identifiers, and operational events such as approvals, tool calls, quota events, runtime status, and audit records.

Google and connected app data

Empyralis uses Google user data only after you give consent through Google OAuth. Google data is used only to provide user-requested assistant actions, account connection, and product features you authorize.

If you connect Gmail, Empyralis may use authorized Gmail data to read, organize, draft, send, archive, or label email when you ask Sage to do so. If you connect Google Calendar, Empyralis may use authorized Calendar data to view availability, read events, create events, or update events when you ask Sage to do so. If you enable Google Drive access, Empyralis may use authorized Drive data only for the file actions you request.

Empyralis does not sell Google user data, does not use Google user data for advertising, and does not use Google user data to train third-party AI models.

OAuth tokens and credentials

Access tokens, refresh tokens, API keys, and other credentials are used to maintain the connections you configure. They are stored separately from normal workspace content where supported and are used only for the connected service actions you initiate or authorize.

Why we store it

This data is used to deliver the service, authenticate users, operate connected agents, enforce usage and safety controls, support configured memory, provide transparency and audit logs, troubleshoot issues, and protect the platform from abuse.

Deletion requests

You can request deletion of saved conversation data from a supported external channel by sending /delete to the deployed agent. You can also disconnect connected accounts inside Empyralis where connection controls are available. Disconnecting a Google account stops Empyralis from making new Google API requests for that connection.

Retention and scope

Deletion actions are scoped to the relevant user, workspace, deployed agent, external channel user, or connected account. Some operational records may be retained when needed for security, compliance, abuse prevention, billing, or audit integrity.

Contact

Questions or privacy requests can be sent to [email protected].