Agnoclast — legal

Privacy Policy

Effective 2026-11-12. Plain-language, and the plain meaning is the intended one. Change from the 2026-11-06 version: Section 11 now says when the full text of a reply is read from Gmail for an AI assistant you connected, and that it is not stored. Nothing that was already promised is taken away.
Changed 2026-11-06: Section 6 now says what happens when you connect an AI assistant such as Claude or ChatGPT, and Section 12 adds a support address. Nothing that was already promised is taken away.
Changed 2026-10-29: Sections 7 and 9 now describe deleting your account yourself, from Settings in the app or on the web, and exactly what that deletes and what it keeps. Nothing that was already promised is taken away.
Changed 2026-10-02: Section 5 describes a new rule for who can see captured activity. A record is visible to whoever can read the page it is filed under. Before, a scoped record stayed with its owner's management chain and teammates explicitly added to the same project, even when it was filed under a page the whole team could read. This widens what your teammates can see, so it is a material change. It applies from the outset to organizations created on or after 2026-10-02, and from 2026-10-16 to organizations created earlier — 14 days after their owner was notified — or sooner where the owner has agreed. Until then the earlier rule continues to apply in those organizations. Confidential records, records their owner has locked, and AI-session summaries captured before 2026-10-01 are not widened.
Changed 2026-09-23: Section 5 previously said scoped activity widens to teammates who "collaborate with you in the same work context." Measured against the system, that widening followed explicit project membership only — it was never inferred from sharing a repository, channel or folder, and no one is added to a project automatically. Section 5 was corrected to say so. That narrowed what we claimed was shared; nobody gained access they did not have.
Changed 2026-09-20: Section 5 now says tenant isolation is tested automatically on every merge to main, rather than on every code change. The test that runs against the production database runs once per merge; a pull request is checked against a separate copy of the database instead. Nothing about who may reach your data changed — this corrects how often we said we verify it.
Changed 2026-09-18: Sections 5 and 8 began describing operator access as it works today. People who operate the Service can reach Customer Content directly in the database, for the purposes listed there, and only part of that access is recorded and shown to your organization.
Changed 2026-09-17: Section 11 began describing what Agnoclast can do inside a connected Google account when you use its email and calendar features — mark, archive and label email, create reply drafts, send an email you approved, and add calendar events — and how a requested email is stored while it waits for your approval.
Changed 2026-09-10: Section 3 began stating when part of a session transcript reaches our servers, and Section 11 began stating how data received from Google (Gmail and Google Calendar) is accessed, used, stored, shared and deleted. Contact moved to Section 12.
Changed 2026-09-08: the controller is now named. It is Agnoclast LLC, a Utah limited liability company, which replaced Theron Peterson as operator of the Service on that date. No data practice described below changed.

1. Scope

Agnoclast is operated by Agnoclast LLC, a Utah limited liability company ("we," "us"). It is a business tool used by organizations. For content your organization puts into Agnoclast ("Customer Content" — work records, pages, summaries), your organization is the controller and we process it on the organization's behalf under our agreement with them. For the basic account data we need to run the Service (your name, email, login), we are the controller. Questions about what your employer captures should also go to your organization's admin — see the notice they provided at onboarding.

2. What we collect

3. What we deliberately do NOT collect

4. How we use information

Solely to provide and operate the Service: building your org's knowledge base, serving permission-scoped context, security, debugging, and (if you contact us) support. We do not sell personal information, do not use Customer Content for advertising, and do not use it to train AI models — and our AI subprocessor is contractually barred from training on it too.

5. Who can see what

Inside your organization, visibility is decided by pages. Every page has an owner, and the owner chooses who can read it: everyone in the organization (accessible); a part of the org chart relative to the owner — everyone below them, their direct reports, or their peers — together with the owner's managers; the owner and their managers only (scoped); or the owner alone (confidential).

Captured activity — commits, meetings, AI-session summaries and other records — is filed under pages, and a record is visible to whoever can read the page it is filed under. In an organization created before 2026-10-02 this takes effect on 2026-10-16, or earlier if the organization's owner agreed; until then a scoped record there is visible only to its owner's management chain and to teammates explicitly added to the same project. Three things stay narrower than their page:

Separately, and as before, a scoped record that belongs to a project is visible to teammates who have been explicitly added to that project, whatever page it is filed under. Project membership is never inferred from sharing a repository, channel, or folder, and no one is added to a project automatically. Email and iMessage records are visible only to the people on the message, and calendar events also to the people invited. Activity not yet filed under any page is visible only to the person it belongs to, or to the organization's owner and admins when it belongs to no one. You can lock or release any record of yours at any time. Across organizations, tenant isolation is enforced at the database layer and tested automatically on every merge to main. People who operate the Service can also reach Customer Content directly in the database, outside these controls. They do so only to run, maintain, secure and support the Service, when you ask them to, or when the law requires it, and for data received from Google the stricter limits in Section 11 apply. Some of that access is recorded and shown to your organization in the console's Data-access panel, and some is not yet. Full detail, including which is which: Data Access & Tenant Isolation.

6. Sharing

We share data only with the infrastructure subprocessors needed to run the Service (hosting, database, AI inference) — the current list, and what each one sees, is at /legal/subprocessors — and when required by law (we will notify your organization of legal demands unless legally barred). No sale, no ad networks, no data brokers.

AI assistants you connect. When you connect an AI assistant such as Claude or ChatGPT, it receives what you ask it to read from Agnoclast: your pages, obligations, calendar and records you can see, including email headers and message text from sources you connected. That provider handles it under its own terms. Some may use it to improve their models unless you turn that off (in ChatGPT: Settings → Data controls → Improve the model for everyone). You can disconnect an assistant at any time from Connect in Agnoclast or from the assistant's own settings.

7. Retention and deletion

8. Security

Postgres row-level security enforces tenant and tier isolation on every read; an automated security test suite runs against the production database on every code change; credentials are rotated; and operator access is purpose-limited and, where Section 5 says so, recorded and shown to your organization. No internet service can promise zero risk, and we don't — see the honest limits in Data Access & Tenant Isolation. If we learn of a breach affecting your data, we will notify your organization without undue delay.

9. Your rights

Depending on where you live you may have rights to access, correct, delete, or export your personal data. For Customer Content, direct requests to your organization's admin (they control the tenant); for account data, delete your account yourself from Settings (Section 7), or contact us directly and we'll respond within 30 days. We honor these rights regardless of jurisdiction where practicable.

10. Miscellany

11. Google user data (Gmail and Google Calendar)

This section applies when you connect a Google account. Where it differs from the rest of this policy, this section controls for data received from Google APIs.

12. Contact

Privacy questions or requests: theronpeterson654@gmail.com.

Help using Agnoclast: support@agnoclast.com, or agnoclast.com/support.