Subprocessors & Infrastructure Providers

Last updated: September 14, 2026 · LifeOS v1.0.0

Overview

This page lists third-party services and infrastructure providers referenced by the LifeOS codebase and production deployment at lifeos.vision. It is intended to match actual implementation behavior. It does not claim legal compliance in any jurisdiction and is not a Data Processing Agreement.

Status meanings:

Active: Used in the current production deployment or required for core service operation.
Conditional: Integrated in code and used only when explicitly enabled and configured by the operator.
Dormant: Present in code or policy references but not active in the current production deployment.
Not present: No integration found in the LifeOS application codebase.

Active — Hosting & Core Infrastructure

Railway (hosting platform) — Runs the LifeOS web application and related production services. Evidence: railway.toml, Railway volume mount hooks in application startup.
PostgreSQL (Railway-managed database) — Primary application database for accounts, planner data, billing records, consents, and privacy requests. Evidence: production /ready database check; Alembic migrations.
Railway durable volume (/data) — Stores user media such as memory attachments, profile photos, and voice library files via LIFEOS_DATA_ROOT. Evidence: volume mount configuration and media path handling in the application.
Resend (transactional email) — Sends account email such as verification, password reset, and billing receipts when configured. Production boot requires RESEND_API_KEY and MAIL_FROM. Evidence: email_service.py, lifeos_email/providers/resend.py.

Conditional — Payments

Razorpay — Web checkout for plans and support donations when LIFEOS_PAYMENTS_ENABLED and Razorpay credentials are configured. LifeOS receives payment confirmation metadata; card/UPI credentials are handled by Razorpay. Checkout JavaScript loads only at payment time. Evidence: lifeos_payments/razorpay_*, checkout.razorpay.com in CSP.
Stripe — Alternate web payment integration present in code when payments are enabled and Stripe keys are configured. Evidence: lifeos_payments/stripe_*, payment webhook routes.
Google Play — Mobile in-app purchase verification when Google Play billing environment variables and credentials are configured. Evidence: lifeos_billing/providers/google_play.py.
Apple App Store — Mobile in-app purchase verification when Apple App Store Server API credentials are configured. Evidence: lifeos_billing/providers/apple.py.

Conditional — AI Providers

External AI is used only when the operator configures API keys and the signed-in user has not disabled external AI in Settings → Privacy. When enabled, LifeOS may send question text and, if memory context is also enabled, short non-vault memory snippets and recent voice conversation context. Vault content, raw productivity rows, and raw voice audio are not sent.

DeepSeek — Primary configured external AI provider in the current router. Evidence: lifeos_ai/router.py, DEEPSEEK_API_KEY.
Google Gemini — Fallback/configured external AI provider. Evidence: lifeos_ai/providers.py, GEMINI_API_KEY.

Conditional — Monitoring

Sentry (or compatible error monitoring) — Optional error reporting when SENTRY_DSN or LIFEOS_SENTRY_DSN is set. May receive stack traces and limited request context; not used for advertising. Evidence: observability.py.

Dormant — Integrated but Not Active in Current Production

Redis — Optional cache, rate-limit backend, and job coordination when REDIS_URL is configured. Current production readiness reports redis: skipped. Evidence: redis_support.py, /ready probe.
Cloudflare R2 — Optional object storage and sync transport when R2 credentials and flags are configured. Current production readiness reports r2: skipped. Evidence: object_storage.py (not modified by this policy page).
OpenAI API (legacy path) — Legacy configuration and code paths remain in the repository, but the primary Ask LifeOS external-AI runtime routes through DeepSeek/Gemini. Evidence: _call_lifeos_ai_conversation() documentation in app.py.
Mixkit CDN (assets.mixkit.co) — Referenced in the Cookie Policy and allowed in Content-Security-Policy for optional functional media. The current alarm sound catalog serves first-party files from /static/alarm/. Evidence: lifeos-alarm-catalog.js, templates/launch/cookie.html.
SMTP email provider — Stub provider exists (smtp_not_implemented); production uses Resend.

Not Present — Advertising / Analytics Trackers

LifeOS does not integrate Google Analytics, Google Tag Manager, Meta Pixel, Hotjar, Microsoft Clarity, PostHog, Mixpanel, Amplitude, Segment, or similar advertising/analytics trackers in application templates or CSP. Evidence: G7 cookie compliance tests and restricted CSP configuration.

Data Categories Potentially Shared

Only when a listed service is active or conditionally invoked:

Account identifiers, email address, and service metadata (hosting, email, support).
Productivity content you store in LifeOS (database and media volume).
Payment metadata and order references (payment processors).
Question text and optional non-vault memory snippets (external AI, when enabled).
Error reports and limited request context (optional monitoring).

LifeOS does not authorize these providers to use your productivity content for their own advertising.