AGLedger Sub-processor List

Version: 1.8 Effective Date: June 9, 2026 Last Updated: September 15, 2026

This page lists the third-party sub-processors that AGLedger LLC engages in connection with its services. It is published pursuant to Section 6 of the AGLedger Data Processing Agreement ("DPA").

1. Scope

A "sub-processor" is a third party engaged by AGLedger to process Customer Personal Data on AGLedger's behalf, as defined in the DPA.

This page does not list:

2. Sub-processors Engaged for Customer Personal Data

As of the effective date of this page:

AGLedger engages zero (0) sub-processors for Customer Personal Data.

All AGLedger personnel access to Customer systems for support or professional services is performed directly by AGLedger employees under the security controls set out in DPA §5. AGLedger operates no hosted or managed federation service and receives no Customer data through Federation.

3. Website Vendors

Third parties that process website data are listed in the AGLedger Privacy Policy §5. None of them processes Customer Personal Data from licensed deployments, and none is a sub-processor under the DPA.

4. Changes to This List

If AGLedger engages a sub-processor for Customer Personal Data, AGLedger will update this page and provide Licensees reasonable advance notice; the objection right in DPA §6.2 then applies. Material changes are posted here with an updated "Last Updated" date.

5. Contact

AGLedger LLC Privacy: privacy@agledger.ai Web: https://agledger.ai/subprocessors

6. Change Log

DateChange
2026-04-16Initial list published. Zero sub-processors for Customer Personal Data.
2026-05-25Replaced Google Analytics 4 (Google LLC) with cookieless Cloudflare Web Analytics in the informational §3 list (website analytics changed 2026-05-04). Removed retired "managed federation services" references (no hosted federation service exists; Federation is peer-to-peer between self-hosted Servers). Customer Personal Data sub-processor count remains zero. v1.1 → v1.2.
2026-06-03Clarified that the optional telemetry endpoint is opt-in / off by default (operator must set AGLEDGER_TELEMETRY=true); the telemetry-endpoint relationship exists only when an operator explicitly opts in. Customer Personal Data sub-processor count remains zero. v1.2 → v1.3.
2026-06-09Telemetry/phone-home removed product-wide. AGLedger operates no telemetry or phone-home endpoint and collects no usage data from any deployment. Removed the Hostinger "telemetry endpoint" relationship (now website hosting only) and the §3 opt-in telemetry framing. Customer Personal Data sub-processor count remains zero. v1.3 → v1.4.
2026-06-09Lean trim. Collapsed the §4 30-day-notice + email-subscription machinery and the §5 15-day objection window (which duplicated the DPA's former fixed notice and objection windows) into a single lean §4 "Changes to This List"; the objection right now points to the trimmed DPA §6.2. Renumbered Contact §6→§5, Change Log §7→§6. Customer Personal Data sub-processor count remains zero. v1.4 → v1.5.
2026-09-10Added Cal.com, Inc. (booking-page scheduler) and Google LLC (YouTube embedded videos) to the informational §3 list. Both are click-to-load: nothing is sent to either provider until the visitor activates the embed (agledger-legal#22). Customer Personal Data sub-processor count remains zero. Hostinger's row now names the Developer Edition registration records it stores. v1.5 → v1.6.
2026-09-15Version 1.8: the informational §3 vendor table replaced by a pointer to Privacy Policy §5, where those vendors are already listed (the table duplicated it row for row and contradicted §1's own exclusion); §2 no longer describes the Federation transport; §4 no longer restates the zero count.
2026-09-15Removed Cal.com, Inc. from the informational §3 list: the website booking page and its scheduler were retired on 2026-08-21, so no website data reaches Cal.com. Customer Personal Data sub-processor count remains zero. The 2026-06-09 change-log entry was reworded to describe that change neutrally. v1.6 → v1.7.