Lodestar
Lodestar Privacy Policy
Last updated November 11, 2026
Lodestar keeps a business's record of commitments inside Claude. It stores conclusions with pointers back to the original, plus files and messages a customer chooses to upload from their own computer. It never stores Claude conversations.
Who we are and what this covers
Aveteva LLC, a Virginia limited liability company doing business as Explorers ("Explorers," "we"), makes Lodestar. Explorers is based at P.O. Box 231, Middleburg, VA 20118, United States.
This policy covers three things:
- The Lodestar connector that a customer adds to Claude.
- The Lodestar desktop extension for Claude Desktop on macOS and Windows.
- The Lodestar control plane at control.lodestar.explorers.work, where account owners manage seats and settings.
A business that uses Lodestar is our customer. The customer decides which people get a seat and which sources Lodestar reads. We process the customer's business data on the customer's behalf. Our Explorers privacy policy covers visitors to this website.
What we collect
Lodestar reads nothing on its own. The customer's Claude reads the customer's connected apps and reports to Lodestar. The desktop extension reads only the threads and folders the user allowlists.
| Source | What Lodestar receives | What Lodestar stores |
|---|---|---|
| Account sign-in | Name and email from the identity provider, and the organization chosen at consent | A user id and seat. Name and email stay with our sign-in provider and in the encrypted personal-data vault |
| Email, chat, calendar, documents, CRM, accounting, and task tools, through the customer's Claude | Short quotes, snippets, record ids, links, and tracked fields such as owner, status, due date, and amount | Commitments, requests, deadlines, and deliveries, each with a quote and a pointer back to the original. Never whole email or chat bodies |
| Desktop extension: allowlisted messages and files | The full text of allowlisted messages and the bytes of allowlisted files, uploaded directly by the extension | The uploaded files, their extracted text, and the commitments found in them |
| Statements in Claude | Decisions, goals, priorities, and corrections a user asks Claude to record | Those statements, attributed to the user who made them |
| Connector list | The names of the connector tools the user's Claude can see, with hashes of their descriptions | A per-customer list of available tools, used to plan sweeps |
| Service logs | Request times, tool names, error codes, and ids | Operational and security logs. No message content and no request bodies |
One credential is the exception. The account owner gives Lodestar the address and token of a Claude routine, so Lodestar can wake that routine when a task is ready. We keep the token in Google Secret Manager and use it for nothing else. The owner can replace or remove it at any time.
What we do not collect
- Claude conversations. Lodestar sees only the tool calls Claude makes to it. It never reads Claude's chat history, memory, conversation summaries, or files uploaded to Claude.
- Credentials to other systems. Lodestar holds no passwords, API keys, or OAuth tokens for the customer's email, CRM, books, or other apps. The customer's Claude holds those connections.
- Anything outside the allowlist. The desktop extension enforces the allowlist on the user's computer when it reads. Nothing else leaves the computer.
- Advertising data. We use no advertising trackers, sell no data, and build no profiles for advertising.
How we use data
We use the customer's data only to run Lodestar for that customer:
- Keep a record of the company's commitments, with evidence and confidence.
- Show what is slipping, what serves each goal, and each person's task list.
- Plan the sweeps the customer's Claude runs, and check what Claude reports against the source.
- Secure the service, prevent abuse, and fix problems.
We do not use one customer's data to serve another customer. We do not train AI models on customer data. Lodestar sends nothing outside Claude: no email, no text messages, and no calls on the customer's behalf.
Where data is stored and how it is protected
All customer data is stored in Google Cloud in the us-east4 region (Northern Virginia, United States).
- Separation. Each paying customer runs in its own Google Cloud project. Free customers share one project, where the database enforces row-level separation by customer on every query.
- Encryption. Data is encrypted in transit with TLS and at rest with keys we manage in Cloud KMS. Names, email addresses, and other personal details sit in a separate vault, each person under their own key.
- Erasure by key. Destroying a person's key makes their personal details unreadable everywhere, including in backups.
- Access. Our staff reach production only through audited, least-privilege roles. Every administrative and data-access event is written to an audit log that cannot be edited or shortened.
Who we share data with
We share customer data only with the service providers below, only to run Lodestar, and under written terms that limit their use of it. We do not sell customer data.
| Provider | What it does for Lodestar | Data it handles |
|---|---|---|
| Google Cloud | Hosting, database, file storage, key management, logs | All data Lodestar stores |
| WorkOS | Sign-in for Lodestar accounts (AuthKit) | Name, email, organization membership |
| Anthropic | Reads text from uploaded files with Claude, only when the customer turns this on | Text from the uploaded files being read |
The customer's own use of Claude and of its connected apps is governed by the customer's agreements with Anthropic and those vendors.
We may disclose data when the law requires it, or to protect the security of the service. We tell the customer first unless the law forbids it. If Explorers is sold or merged, this policy continues to apply to the data we hold.
How long we keep data
| Data | Kept for |
|---|---|
| The commitment record: claims, quotes, pointers, and the owner's statements | The life of the customer's account |
| Personal details in the vault | The life of the account, or until erased on request |
| Uploaded files and their extracted text | While the file stays in the user's allowlist. Removing it from the allowlist deletes the file and its text |
| Everything above, after the account closes | Deleted within 30 days of closure |
| Database backups | Rolled off within 30 days |
| Audit logs (ids, times, and actions, no content) | 400 days, then deleted |
| Sign-in sessions | Expire after 30 days unused, and after 90 days in any case |
The commitment record never overwrites itself, so it can show what the company knew on any past date. Erasing a person destroys their key. Their name and details then read as removed everywhere the record mentions them.
Your choices and rights
- Stop a source. Disconnect an app from Claude, or remove a thread or folder from the extension's allowlist. Lodestar stops receiving it at once.
- See, correct, or export. Ask Claude to show what Lodestar holds about a topic, or record a correction, which outranks anything Lodestar inferred. The account owner can request a full export.
- Erase. Ask us to erase a person's personal details or to close the account. We confirm the request with the account owner, since the record belongs to the business.
- Your rights by law. Depending on where you live, you may have rights to access, correct, delete, or port your data, or to object to its use. A person whose details appear in a customer's record can contact us, and we will work with that customer to answer.
We answer requests within 30 days.
Children
Lodestar is for businesses. It is not directed at children under 16, and we do not knowingly collect their data.
Changes and contact
We will post any change to this policy here with a new date. For a material change, we tell account owners at least 30 days before it takes effect.
- Privacy questions and requests: privacy@explorers.work
- Product support: support@explorers.work
- Security reports: security@explorers.work
- Mail: Explorers, P.O. Box 231, Middleburg, VA 20118, United States