{% extends "base.html" %} {% block title %}Privacy Policy — Timmy Time{% endblock %} {% block content %}

# // PRIVACY POLICY

Effective Date: March 2026 · Last Updated: March 2026

// PLAIN LANGUAGE SUMMARY

Timmy Time runs primarily on your local machine. Most data never leaves your device. We collect minimal operational data. AI inference happens locally via Ollama. Lightning payment data is stored locally in a SQLite database. You can delete your data at any time.

// 1. DATA WE COLLECT

#### 1.1 Data You Provide

- Chat messages — conversations with the AI assistant, stored locally
- Tasks and work orders — task descriptions, priorities, and status
- Voice input — audio processed locally via browser Web Speech API or local Piper TTS; not transmitted to cloud services
- Configuration settings — preferences and integration tokens (stored in local config files)

#### 1.2 Automatically Collected Data

- System health metrics — CPU, memory, service status; stored locally
- Request logs — HTTP request paths and status codes for debugging; retained locally
- WebSocket session data — connection state; held in memory only, not persisted

#### 1.3 Data We Do NOT Collect

- We do not collect personal identifying information beyond what you explicitly configure
- We do not use tracking cookies or analytics beacons
- We do not sell or share your data with advertisers
- AI inference is local-first — your queries go to Ollama running on your own hardware, not to cloud AI providers (unless you explicitly configure an external API key)

// 2. HOW WE PROCESS YOUR DATA

Data processing purposes:

- Service operation — delivering AI responses, managing tasks, executing automations
- System integrity — health monitoring, error detection, rate limiting
- Agent memory — contextual memory stored locally to improve AI continuity across sessions
- Notifications — push notifications via configured integrations (Telegram, Discord) when you opt in

Legal basis for processing: legitimate interest in operating the Service and fulfilling your requests. You control all data by controlling the self-hosted service.

// 3. DATA RETENTION

Data Type | Retention Period | Location
--- | --- | ---
Chat messages | Until manually deleted | Local SQLite database
Task records | Until manually deleted | Local SQLite database
Lightning payment records | Until manually deleted | Local SQLite database
Request logs | Rotating 7-day window | Local log files
WebSocket session state | Duration of session only | In-memory, never persisted
Agent memory / semantic index | Until manually cleared | Local vector store

You can delete all local data by removing the application data directory. Since the service is self-hosted, you have full control.

// 4. YOUR RIGHTS

As the operator of a self-hosted service, you have complete rights over your data:

- Access — all data is stored locally in SQLite; you can inspect it directly
- Deletion — delete records via the dashboard UI or directly from the database
- Export — data is in standard SQLite format; export tools are available via the DB Explorer
- Correction — edit any stored record directly
- Portability — your data is local; move it with you by copying the database files

If you use cloud-connected features (external API keys, Telegram/Discord bots), those third-party services have their own privacy policies which apply separately.

// 5. LIGHTNING NETWORK DATA
⚡ LIGHTNING PRIVACY CONSIDERATIONS
Bitcoin Lightning Network transactions have limited on-chain privacy. Payment hashes, channel identifiers, and routing information may be visible to channel peers and routing nodes.

Lightning-specific data handling:

- Payment records — invoices, payment hashes, and amounts stored locally in SQLite
- Node identity — your Lightning node public key is visible to channel peers by design
- Channel data — channel opens and closes are recorded on the Bitcoin blockchain (public)
- Routing information — intermediate routing nodes can see payment amounts and timing (not destination)

We do not share your Lightning payment data with third parties. Local storage only.

// 6. THIRD-PARTY SERVICES

When you configure optional integrations, data flows to those services under their own privacy policies:

- Telegram — messages sent via Telegram bot are processed by Telegram's servers
- Discord — messages sent via Discord bot are processed by Discord's servers
- Nostr — Nostr events are broadcast to public relays and are publicly visible by design
- Ollama — when using a remote Ollama instance, your prompts are sent to that server
- Anthropic Claude API — if configured as LLM fallback, prompts are subject to Anthropic's privacy policy

All third-party integrations are opt-in and require explicit configuration. None are enabled by default.

// 7. SECURITY

Security measures in place:

- CSRF protection on all state-changing requests
- Rate limiting on API endpoints
- Security headers (X-Frame-Options, X-Content-Type-Options, CSP)
- No hardcoded secrets — all credentials via environment variables
- XSS prevention — DOMPurify on all rendered user content

As a self-hosted service, network security (TLS, firewall) is your responsibility. We strongly recommend running behind a reverse proxy with TLS if the service is accessible beyond localhost.

// 8. CONTACT

Privacy questions or data deletion requests: file an issue in the project repository or contact the service operator directly. Since this is self-hosted software, the operator is typically you.

{% endblock %}