FARO — Privacy Policy
Last Updated: June 2026
2. Data stored locally
FARO stores its data on the user's machine only, under %AppData%\AvantLeap\FARO\:
| Location | Content | Retention |
|---|---|---|
settings.json |
App configuration: user identity, Anthropic API key, GitHub token, paths | Persists until changed or deleted by the user |
data\requests.json |
Client requests (status, priority, plan) | Persists until deleted by the user |
data\clients.json |
Client records | Persists until deleted by the user |
docs\ |
Local clone of the AvantLeap docs repository (knowledge base) | Refreshed on pull; persists until deleted |
faro-repo\ |
Local clone of the FARO data repository | Refreshed on sync; persists until deleted |
logs\faro-*.log |
Application logs (Serilog) | Persists until deleted by the user |
Secrets: the Anthropic API key and GitHub token are stored in settings.json and are not committed to any repository.
No data is transmitted to a FARO server. AvantLeap does not operate a backend that receives FARO's chat content, client data, or requests; sync happens directly between the app and GitHub.
3. Data sent to Anthropic (Claude)
FARO's chat and strategic-analysis features send content to the Anthropic API:
| Provider | API endpoint | Privacy policy |
|---|---|---|
| Anthropic (Claude) | https://api.anthropic.com/v1/messages |
https://www.anthropic.com/privacy |
What is sent: The user's chat messages, the request or client context being analyzed, and a system prompt assembled from the local docs knowledge base. This may include internal business information and client-request details. The user should treat the chat as sending internal data to a third-party AI provider and avoid pasting credentials or special-category personal data.
API key: stored in settings.json and sent only as the authorization header to Anthropic. AvantLeap operates no intermediary server.
4. Data sent to GitHub
FARO uses LibGit2Sharp to pull the docs knowledge base and push FARO data (requests, clients) to GitHub, authenticated with the user's Personal Access Token.
What is sent: The contents of requests.json / clients.json (which may include client names and request details) and the user's git commit identity. The GitHub token itself is never pushed. See GitHub's privacy policy: https://docs.github.com/site-policy/privacy-policies/github-general-privacy-statement
Because client data is pushed to a GitHub repository, ensure that repository is private and access-restricted to authorized AvantLeap staff.
5. Presentations
The Build Presentation feature generates .pptx files locally using DocumentFormat.OpenXml. Generated presentations are written to disk on the user's machine; FARO does not upload them anywhere.
6. Data the application does NOT collect
- FARO does not send telemetry or usage analytics to AvantLeap.
- FARO does not transmit its API key or GitHub token to any server other than the respective provider (Anthropic / GitHub).
- FARO does not create end-user accounts — it is a single-user internal desktop tool.
7. Audience
FARO is an internal tool for named AvantLeap staff only. It is not distributed publicly and is not directed at children under 13.
8. Changes to this policy
AvantLeap may update this policy as FARO evolves. Material changes will be noted in the internal release notes.
9. Contact
Questions about this policy: contact@avantleap.com | https://www.avantleap.com/