Trust Center

Architecture

LifeHub runs as a single-node app with a private PostgreSQL database on the family's own server, with foreign keys, migration discipline, verified backup sets, and restore drills. Uploaded files and calendar OAuth tokens are encrypted by the application. Other database contents are protected by server and database access controls.

Security Controls

• Protected actions require authentication, CSRF checks, current-password or explicit step-up confirmation, rate limiting, authorization checks, and audit logging.
• Sensitive emails are sent through Resend when configured, and local development degrades cleanly when Resend credentials are unset.
• Security notifications avoid secrets, invite tokens, session cookies, reset tokens, and recovery codes.

Backup Retention Policy

Backup sets should be retained according to the configured BACKUP_RETENTION_DAYS value, verified with backup:verify before off-server trust, and tested through monthly restore drills. Missing or stale backups can fail /api/health when HEALTH_REQUIRE_RECENT_BACKUP is enabled.

Providers And Subprocessors

• Resend: transactional email for verification, password reset, invites, and security notifications.
• Google Calendar: optional calendar connection and sync when configured.
• Web Push: optional browser push notifications when VAPID credentials are configured.
• AI assistant (OpenAI or Google Gemini): optional AI assistance only when AI_PROVIDER is set to openai or gemini and the model/API key are configured.
• Infrastructure and storage: Mahan Fathi operates the VPS, volumes, backup storage, and reverse proxy in Cyprus.

Incident Readiness

Production deployments need structured logs, health checks, provider checks, uptime monitoring, backup freshness checks, and incident runbooks before public launch.