Draft for review. This page is a draft. It is not in effect until Glen has reviewed it and set an effective date. Text in brackets is still to be confirmed.
Privacy Policy
Effective date: [to be set]
Glen is a service that runs teams of background agents for an organization, with the tools and data the organization gives them. This policy says what Glen holds, where it is kept, who else handles it and how to have it removed.
Glen is operated by [company legal name], [company address] ("Glen", "we"). This policy covers this site, meetglen.ai, and the service at app.meetglen.ai and its API.
In short
- Glen holds what it needs to run an organization's agents: who its members are, the agents it defines, the work it sends them, the record of each session and the knowledge base written from those sessions.
- Glen runs on Amazon Web Services in the United States (us-west-2, Oregon).
- The text an agent works with goes to a model provider to produce the agent's next step. Today that provider is Anthropic.
- Glen does not sell data, show advertising or train AI models.
- One organization's agents never read another organization's sessions, knowledge bases or secrets.
Whose data it is
An organization that uses Glen decides which tools, credentials and data its agents get. For that content Glen acts on the organization's instructions, as its processor. For account details and for correspondence with us, Glen decides how the data is used, as a controller. [lawyer to confirm the controller and processor roles]
An organization's admins control its members, its tools and its credentials. If your organization gave you access to Glen, ask its admins first about what its agents can reach.
What Glen holds
Account details
Sign-in runs through WorkOS. When you sign in, Glen receives your name, your email address, whether the address is verified, and the organization you signed in to with your role in it. Glen never receives your password.
What an organization puts in Glen
- Agent definitions: instructions, model, tools, triggers and the knowledge base each agent reads, with every earlier version.
- Work sent to agents: messages from the console, the API, schedules, feeds and webhooks.
- The journal of each session: the messages, the model's requests and responses, tool calls and their results, feedback and corrections from people, and the files in the session's workspace.
- Knowledge bases: pages a curator writes from the organization's own sessions, and pages its people edit, with every revision.
- Usage records: model tokens and run time for each session.
This content can include personal data about other people when an organization's tools or messages contain it. The organization is responsible for having the right to give that data to its agents.
Credentials
Secrets an organization gives Glen, such as a model provider key or a tool's API key, are stored in AWS Secrets Manager under that organization's name. Sign-ins to tools through OAuth are held in the token vault of Amazon Bedrock AgentCore Identity. Glen's database holds no secret. It holds hashes of API tokens.
Cookies
The console at app.meetglen.ai sets a session cookie that keeps you signed in, and a short-lived cookie during sign-in. Both are needed for the console to work. Glen sets no advertising or analytics cookies.
This site, meetglen.ai, sets no cookies and runs no analytics. It loads its fonts from Google Fonts, so your browser sends Google your IP address and browser details when you open a page.
Logs
Glen's servers log requests, errors and timestamps to keep the service working. The network names an agent's sandbox looks up are logged too.
Correspondence
If you email support@meetglen.ai, we keep the thread so we can answer. Glen's mail is hosted by Google Workspace.
How Glen uses it
- To run the organization's agents and show its people what they did.
- To write the organization's knowledge bases. A curator reads a synopsis of each finished session and writes what was learned into the knowledge base that session's agent reads.
- To meter usage against the organization's budgets.
- To keep the service secure and to fix problems.
Glen does not sell or rent data, does not share it with advertisers, and does not use an organization's content to train AI models. [Cliff to confirm these as commitments]
Glen's staff look at an organization's content only to fix a problem the organization reported, to keep the service secure, or when the law requires it. [Cliff to confirm]
Model providers
Agents and the curator work by sending text to a large language model. That text can include the agent's instructions, the messages in the session, knowledge base pages and the results of tool calls.
- Anthropic. Model calls go to Anthropic's API through Glen's proxy, with the organization's own Anthropic key or with Glen's. With its own key, the organization's agreement with Anthropic governs how Anthropic handles that text. With Glen's key, Glen's agreement with Anthropic does. [confirm Anthropic's retention and training terms for Glen's key before stating them here]
- OpenAI. Planned. No organization's data goes to OpenAI today, and this page will list OpenAI as in use before any does.
Glen stores no files or other content at a model provider.
Who else handles data for Glen
| Service | What it does for Glen | Where |
|---|---|---|
| Amazon Web Services | Hosting, the database, file storage, logs, secrets (AWS Secrets Manager) and the sandboxes agents run in (Amazon Bedrock AgentCore) | United States (us-west-2, Oregon) |
| Anthropic | Model provider | United States [confirm] |
| WorkOS | Sign-in, organization membership, and invitation and sign-in email | United States [confirm] |
| Email you send to Glen (Google Workspace), and the fonts on this site | United States [confirm] | |
| OpenAI | Model provider. Planned, not in use. | United States [confirm] |
The tools an organization connects to its agents, such as a code host, a chat workspace or a ticket tracker, are the organization's own choices and are not on this list. An agent reaches a tool with the credentials the organization gave it, and what the tool does with a request is governed by the organization's agreement with that tool.
Where data is kept and how it is protected
- Everything Glen stores is in AWS in the United States (us-west-2).
- Connections to Glen use TLS. The database and file storage are encrypted at rest.
- Each session runs in its own microVM. A sandbox gets only the secrets its agent's definition names.
- Glen reads and writes an organization's files and secrets under an AWS role limited to that organization.
How long Glen keeps it
Glen keeps an organization's content while the organization has an account. An organization's admins can delete agents and knowledge bases in the console. The console has no control that deletes a whole organization. Glen does that on request.
- Server logs are kept for 30 days.
- When a stored file is overwritten or deleted, its earlier version is kept for 30 days.
- Daily backups of file storage are kept for 35 days, and database backups for 7 days.
When an organization asks us to delete its data, we delete it from the live service within [30 days, to confirm], and the backups above expire on their own schedule after that. [Cliff and a lawyer to confirm the deletion commitment]
Your rights
You can ask to see, correct, export or delete the personal data Glen holds about you by emailing support@meetglen.ai. We check that the request comes from you before we act on it. If the data is in an organization's content, we pass the request to that organization, which decides. [lawyer to confirm for GDPR, UK GDPR and CCPA]
If you are in the European Union or the United Kingdom: your data is processed in the United States. [lawyer to confirm the transfer mechanism and whether Glen offers a data processing agreement]
Legal requests
We disclose data only when a valid legal process requires it. Unless the law forbids it, we tell the organization first so that it can object. [Cliff to confirm]
Changes to this policy
When this policy changes in a way that matters, we tell each organization's admins by email or in the console before the change takes effect. [Cliff to confirm]
Contact
support@meetglen.ai [confirm the contact address]
[company legal name], [company address]
Adapted from the Basecamp open-source policies, used under CC BY 4.0.