Privacy Policy
Last updated: April 26, 2026
Telemetry & Version Update Checks
Recallium Community edition includes a built-in version update check. When your Recallium instance is running, it periodically contacts our version-manifest API to determine whether a newer release is available. This check is a core feature of the Community edition and is how upgrade notifications are delivered.
Data we receive on each version check
| Field | Example | Purpose |
|---|---|---|
| IP address | 74.96.104.28 | Approximate geolocation; abuse detection |
| Approximate location | Country, region, city, coarse lat/long (e.g., US / MD / Gaithersburg) | Aggregate geographic distribution; infrastructure planning |
| User agent | Python/3.13 aiohttp/3.13.5 | Runtime compatibility tracking |
| Recallium version | 0.8.380 | Determine whether an upgrade is available |
| LLM model identifier | google/gemini-2.5-flash-lite | Prioritize compatibility for models our users actually run |
| Embedding model identifier | Snowflake/snowflake-arctic-embed-l-v2.0 | Same as above |
| Timestamp | 2026-04-06 23:03:22 -0400 | Rate analysis |
About the model identifiers
Recallium Community supports only publicly available models from major providers (OpenAI, Anthropic, Google, etc.), models routed through OpenRouter, and models hosted locally via Ollama. The model identifiers we receive are therefore drawn from a known public namespace — we do not receive proprietary or internal model names. No prompts, completions, embeddings, or vector data are transmitted; only the model identifier string itself.
What we do NOT collect
- Memory contents, prompts, completions, or embeddings
- Any data stored in your Recallium database
- API keys, credentials, or secrets
- Names, emails, or identifiers of your end-users
- Query payloads or business data
Legal basis (GDPR Art. 6(1)(f))
Legitimate interest in delivering software updates and security notifications to active installations and in maintaining compatibility with the model ecosystem our users rely on.
Retention
Raw telemetry records are retained for 90 days. After 90 days, IP addresses are truncated to /24 (IPv4) or /48 (IPv6) and only aggregate counts are kept indefinitely.
Sharing
Telemetry is processed by Vercel (our hosting provider, which performs the IP geolocation at the edge). It is not sold, shared with third parties for marketing, or used for advertising.
No opt-out in Community edition
The version update check is a built-in feature of the Community edition and cannot be disabled. By using Recallium Community, you accept that this telemetry is sent. If you require a deployment without external telemetry, the Recallium Enterprise edition supports self-hosted upgrade-check endpoints and air-gapped operation.
Your rights
EU/UK/California residents have rights to access, correction, deletion, and (for EU/UK) objection. Because we identify telemetry only by IP and not by account, fulfilling these requests requires you to contact us with the IP range(s) of your installation. Contact: privacy@recallium.ai.