Effective Date: April 24, 2026

Introduction

Tridigm is a private, local-first life OS designed with your privacy as a core principle, not an afterthought.

Your data lives on your device. Cloud sync is automatic and end-to-end encrypted—we cannot read your content, and we don't want to.

This policy explains what data you create, how it's stored, and what we explicitly do NOT collect.

Data You Create

When you use Tridigm, you create:

• Tasks, schedules, templates, and todos
• Notes, reminders, and custom lists
• Your organization structure and preferences

All of this data is stored locally on your device in an encrypted database. When you sign in, it is also encrypted on your device and copied to our servers so it can reach your other devices — as ciphertext we hold but cannot read. See Encrypted Cloud Sync below.

You own your data. Tridigm is the tool; you are the owner.

What We Do NOT Collect

Tridigm explicitly does NOT collect, transmit, or have access to:

• Your usage patterns, analytics, or telemetry
• Your location, contacts, photos, camera, or calendar
• Your email address, phone number, or identity (beyond authentication for sync)
• Your browsing history or app usage
• Any data for advertising or third-party sharing

Two things deserve a plainer answer than a bullet point:

• Microphone. Libba's voice entry uses your device's own speech recognition to turn speech into text. Tridigm never receives, stores, or transmits the recording — only the text you dictated, which is then yours like anything else you type.
• Health and fitness. The Health tool holds what you record: workouts, macros, body metrics. It is encrypted on your device and synced as ciphertext, exactly like every other tool. We hold it; we cannot read it.

We do not use analytics SDKs, tracking pixels, or third-party data brokers.

We do not sell, rent, or share your data with anyone.

We do not serve ads or monetize your information.

Encrypted Cloud Sync

When you sign in, Tridigm automatically encrypts and syncs your data to a secure cloud backend so it's available across all your devices and survives app reinstall.

Key points about sync:

• Your local database is the single source of truth—not the cloud.
• All data is encrypted end-to-end (AES-256-GCM) on your device before transmission.
• The server stores only encrypted ciphertext plus minimal routing metadata (timestamps, entity IDs).
• Neither Tridigm nor our infrastructure provider can decrypt your content.
• Your encryption key never leaves your device in readable form. A copy wrapped under a secret only you hold is escrowed, so you can recover on a new device — we cannot unwrap it.

Cloud sync is transport and backup only. Tridigm works fully offline — all features function without a network connection.

If you delete data locally, the encrypted copy is also removed from the cloud.

Backups

Backups are distinct from sync:

Backups differ by platform, because the platforms differ:

• On iOS, Tridigm data may be included in your iCloud or iTunes device backups. That backup's encryption is controlled by Apple and by you, not by Tridigm.
• On Android, Google Drive Auto Backup is deliberately disabled for Tridigm, because it would place app data somewhere we cannot encrypt. Tridigm's own encrypted cloud sync is your backup instead.

On both, sync transports encrypted operations between devices as you use them, and the encrypted cloud copy is what restores you on a new device.

Permissions

• Notifications: To deliver reminders and scheduled alerts
• Network: To sync encrypted data and process Cloud AI queries

Denying permissions does not prevent core functionality—Tridigm works offline without sync or notifications.

Tridigm requests only the permissions a feature needs, at the moment it needs one:

• Notifications — reminders you scheduled yourself.
• Microphone — only for Libba's voice entry, and only while you use it.
• Biometrics (Face ID, Touch ID, fingerprint or face unlock) — optional app lock.
• Exact alarms (Android) — to fire a reminder at the exact minute you set.

You control all of them in your device's system settings for Tridigm.

AI Assistant (Libba)

Libba, Tridigm's built-in AI assistant, processes your queries using a tiered intelligence system:

• Tier 1 (Deterministic): Pattern matching runs entirely on-device. No data leaves your device.
• Tier 3 (Cloud AI): When you enable Cloud AI, your messages and relevant tool data are processed by Anthropic (Claude) via Tridigm's secure proxy.

Tridigm does not store, log, or have access to the content of your AI conversations. Data is transmitted over HTTPS and processed by Anthropic under their API data policy, which does not use API inputs for model training.

Rate limits apply to the managed service: 20 queries per day during your free trial, 100 queries per day with an active subscription.

Key facts about AI data handling:

• Only data from tools you have granted Libba access to (via Data Access settings) is included.
• You control the maximum context window size sent per request.
• You can disable Cloud AI at any time in Libba Settings — when disabled, all inference runs on-device.
• Tier 2 (On-Device ML): inference runs locally on your device — CoreML on Apple platforms, on-device frameworks on Android. No data leaves your device.

Bank Connections (Plaid)

Tridigm's Finance tool offers optional bank account connections powered by Plaid.

When you connect a bank account:

• Plaid securely accesses your account balances and transaction history.
• Your bank credentials are handled entirely by Plaid and never touch Tridigm's servers.
• Financial data is encrypted on your device with your personal key. Like every other tool it syncs as ciphertext we cannot read, and Tridigm's proxy never stores it.
• Tridigm's server acts as a stateless proxy — it forwards requests to Plaid and returns results without storing, logging, or retaining any financial data.

You can disconnect any linked bank account at any time from the account's settings. Disconnecting revokes Plaid's access and removes all associated data from your device.

Plaid's own data practices are governed by their End User Privacy Policy at plaid.com/legal.

Apple Card & FinanceKit

On iOS 17.4+, Tridigm can read Apple Card, Apple Cash, and Apple Savings data using Apple's FinanceKit framework.

• All data stays entirely on your device — no third-party servers are involved.
• Authorization is managed by iOS. You can revoke access at any time in iOS Settings.
• Tridigm does not store tokens or credentials for FinanceKit — Apple handles authorization natively.

FinanceKit is the most private way to connect financial accounts — zero network calls, zero third parties.

Authentication

Sign-in is handled by Firebase Authentication on both platforms — Apple Sign-In, Google Sign-In or Email on iOS; Google Sign-In or Email on Android.

• Firebase receives your authentication credentials (email or identity token).
• No other data is shared with Firebase or any third party beyond what is required to maintain your session.
• Your session is stored in the iOS Keychain, or on Android in EncryptedSharedPreferences backed by the Android Keystore.

Crash Reporting

• Stack trace (where the crash occurred in code)
• Device model and OS version

Crash reports cannot be linked to your identity or your content.

Crash handling differs by platform:

• On iOS, Firebase Crashlytics may collect anonymous crash reports to help us fix bugs.
• On Android, crash diagnostics are written to a local on-device journal. Nothing is uploaded automatically — you choose whether to attach it when you contact support.

Neither contains personal data: only a stack trace, app version, device model and OS version. Crash reports cannot be linked to your identity or your content.

Security

Tridigm uses industry-standard security practices:

• End-to-end encryption (AES-256-GCM) for all synced data
• No plaintext user content ever sent to cloud services

Security limitations:

• Tridigm assumes the device user is trusted. If an attacker gains physical access to your unlocked device, your data is accessible.
• Encryption keys are held in the iOS Keychain or the Android Keystore (hardware-backed where the device supports it), with cross-device recovery via encrypted key escrow.
• The local database is protected by iOS File Protection or Android file-based encryption.
• A biometric app lock is optional on both platforms.

Your Control

You have full control over your Tridigm data:

• Export data: Contact support@tridigm.com for data export requests.

Tridigm cannot prevent you from managing your data. All controls are on-device and immediate.

• Delete data: remove individual items or whole documents via Trash.
• Delete account: removes your authentication record, all local data and all synced cloud data, and disconnects any linked bank accounts. See tridigm.com/delete-account for step-by-step instructions.
• View sync status: check encryption and sync details in the app's sync settings.
• Manage permissions: control notifications and biometrics in your device's system settings.

Children's Privacy

Tridigm is not directed at children under the age of 13.

We do not knowingly collect personal information from children under 13.

If you believe a child under 13 has used Tridigm and created data, please contact us so we can provide guidance on data deletion.

Policy Updates

We may update this Privacy Policy to reflect changes in Tridigm's features or legal requirements.

When we make updates:

• The "Last Updated" date at the top of this policy will change.
• Material changes will be communicated via in-app notification or update notes.
• Continued use of Tridigm after updates implies acceptance of the revised policy.

We will never retroactively change our privacy practices in ways that weaken your privacy.

Contact

If you have questions about this Privacy Policy or Tridigm's privacy practices:

• Contact us through the channels listed in the Support screen.

We respond to privacy inquiries as promptly as possible.

• Review the Support screen inside the app for diagnostic information.