Digesto — Privacy Policy
Last Updated: July 2026
1. What Digesto does
Digesto is a standalone Windows desktop application (not a Revit add-in) that ingests regulatory PDFs and building codes, uses an AI provider to extract them into a structured rule set, and stores the result as git-versioned rule packs for use by compliance tools across the AvantLeap ecosystem. All processing is initiated explicitly by the user.
2. Data stored locally
Digesto stores the following data on the user's machine only:
| Location | Content | Retention |
|---|---|---|
%APPDATA%\AvantLeap\Digesto\settings.json |
App configuration: git identity, rule-packs repository URL, AI provider preference, and secrets (Anthropic key, OpenAI key, GitHub PAT) | Persists until changed or deleted by the user |
| Rule-packs git repository (user-selected local clone) | Extracted rule packs (.json / .md), derived from published standards |
Versioned in git; persists until deleted by the user |
| Source regulatory documents | The PDFs / code documents the user selects to ingest | Remain wherever the user stored them — Digesto does not copy or relocate them |
Secrets at rest: API keys and the GitHub Personal Access Token are DPAPI-encrypted (Windows CurrentUser scope) inside settings.json. They are never committed to a repository, never written to a log line, and never placed in a git remote URL. DPAPI ties the encryption to the current Windows user — copying settings.json to another user or machine yields empty secrets (fail-closed).
No data is transmitted to AvantLeap. AvantLeap does not operate any server that receives document text, rule packs, or secrets.
3. Data sent to third-party AI providers
When the user runs Ingest Document, Digesto sends the text extracted from the selected regulatory document to the chosen AI provider's API so it can be structured into rules:
Digesto supports three AI providers. The data sent externally depends entirely on which provider the user configures:
Cloud providers (data leaves the machine):
| Provider | API endpoint | Privacy policy |
|---|---|---|
| Anthropic (Claude) | https://api.anthropic.com/v1/messages |
https://www.anthropic.com/privacy |
| OpenAI (GPT) | https://api.openai.com/v1/chat/completions |
https://openai.com/policies/privacy-policy |
What is sent (cloud): The text content of the regulatory document the user chose to ingest, plus a versioned system prompt instructing the AI to extract rules. Source documents are published codes and standards with low personal-data (PII) exposure; no special-category data is processed.
API keys: The user's API key is entered in Settings, stored DPAPI-encrypted on disk, and sent only as the authorization header of requests to the chosen provider. AvantLeap never receives or stores the user's API key.
Local provider (no data leaves the machine):
| Provider | Endpoint | External data sent |
|---|---|---|
| Ollama (local) | http://localhost:11434 (user-configured) |
None |
When the user selects Ollama, the document text is sent only to a locally running Ollama process on the user's own machine. No data is transmitted to any external server, and no API key is required. Users who handle documents that must not leave their network should use this option.
The ingest step is the only action that sends data to any AI provider. Browse Rules, Compliance Graph, Settings, and Rule & Ecosystem Map operate entirely on locally stored or cached data (except the ecosystem map's status fetch, described in section 3a).
3a. Rule & Ecosystem Map status fetch
When the user opens the Rule & Ecosystem Map dialog, Digesto performs one read-only HTTPS GET request to:
https://raw.githubusercontent.com/Avant-Leap/AvantLeap.Tools.Docs/main/ecosystem-status.md
This fetches a plain-text Markdown file containing tool status and progress data. No user data, document content, or secrets are included in this request. If the request fails, a built-in offline snapshot is used instead. If the user has configured a GitHub token in Settings, that token is included as an Authorization header to support private repository access.
4. Data sent to GitHub
Rule packs are version-controlled in a GitHub repository the user configures. When the user saves an ingested rule pack or runs Browse Rules, Digesto performs git operations (commit / push / pull) against that repository, authenticated with the user's fine-grained Personal Access Token (least-privilege: only the rule-packs repository).
What is sent: The rule packs (public data, derived from published standards) and the user's git commit identity (name and email). No secrets and no source documents are pushed. See GitHub's privacy policy: https://docs.github.com/site-policy/privacy-policies/github-general-privacy-statement
5. Licensing / entitlement check
Digesto's licensing check is currently a local stub that returns "licensed" and performs no network call. When App Store distribution is added, this section will be updated to describe any entitlement verification introduced at that time.
6. Data the application does NOT collect
- Digesto does not collect telemetry, usage statistics, or crash reports.
- Digesto does not transmit secrets (API keys, PAT) to any server — they stay DPAPI-encrypted on the local machine.
- Digesto does not include full document content in production logs (only model / token / latency metadata).
- Digesto does not create accounts or user profiles.
7. Children's privacy
Digesto is a professional compliance tool intended for use by architecture, engineering, and construction professionals. It is not directed at children under 13.
8. Changes to this policy
AvantLeap may update this policy as Digesto evolves. Material changes will be noted in the product release notes. Continued use of Digesto after an update constitutes acceptance of the revised policy.
9. Contact
Questions about this policy: contact@avantleap.com | https://www.avantleap.com/