EL AGENTE

Privacy policy

Effective September 23, 2026

This policy describes how the El Agente scientific workspace handles information when you sign in, use its agents, or save your work. Contact luis@mail.elagente.ca with privacy questions or requests.

Account information

Google sign-in provides your name, verified email address, and Google account identifier. GitHub sign-in provides your profile and verified email addresses. We store your provider identifier, name, and selected email to recognize your account, keep your work associated with it, and enforce account permissions. Administrator access requires a separately authorized, verified email address.

We do not receive your Google or GitHub password. Google sign-in requests only basic identity information, not access to Gmail, Drive, contacts, or other Google files. Provider access tokens are used to complete sign-in and are not saved as ongoing access credentials in the application database.

If you register with email and password, we verify your address with a short-lived confirmation code and store a salted password hash, not your password. Verification and password-reset requests use limited attempts and delivery records to prevent misuse. Pending email content is encrypted in the delivery queue and removed after submission, invalidation, or expiry; old verification challenges are removed after one day. Resend delivers these account emails and processes the recipient address, email content, and delivery records.

Conversations, calculations, and saved work

We store messages, agent responses, molecular structures, selected atoms, calculation inputs and outputs, reports, and related usage records so you can continue your work. We also store account credentials in hashed form, credit balances, transaction references, and operational records needed to authenticate requests, account for usage, and investigate errors.

Services that process information

Agent requests send the relevant conversation and tool context to configured AI model providers through our model gateway. Scientific jobs send the inputs needed for the calculation to our compute services. Railway hosts the application, database, and stored artifacts; Modal runs isolated scientific compute. Google and GitHub handle their respective sign-in steps. Their services may process information in countries other than yours and apply their own data-handling terms.

Our pages use Google Fonts, which receives the ordinary network information needed to deliver fonts. Support emails sent to the contact address are forwarded through Cloudflare to the operator's inbox. If payment is enabled, Stripe processes checkout and receives the transaction information needed for payment; the application does not collect card numbers.

Google account information is used for authentication and account management. El Agente does not sell that information or use it for advertising. Our use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

Access and storage

Saved workspace content is restricted to its owning account through the application. Authorized operators may access stored information when needed to run the service, investigate an issue, or respond to a support request. Account data and saved work remain stored so the workspace can be resumed. Backups and operational records may retain copies after changes to the active workspace.

Cookies and your choices

We use cookies for sign-in, authorization state, and access to password-protected workspaces. You can sign out, revoke your platform API keys, and remove El Agente's authorization in your Google or GitHub account. Revoking provider authorization does not itself delete saved workspace data.

To request access, correction, or deletion of account data, email luis@mail.elagente.ca. We may need to verify account ownership. We will explain any records that must be retained for security, accounting, or legal obligations and any applicable backup limitations when handling the request.

Updates

We will update this page when the service's data practices change and show the effective date above.