Security & trust

Trust is the foundation of stewardship

Tara Financial is built for boards, auditors, and finance leaders who carry real fiduciary responsibility. Security and privacy are not features — they are the product's foundation.

Tenant isolation

Every organization's data is partitioned by org_id. No query, view, or export can cross organization boundaries.

Role-based access

Seven org-scoped roles — from platform admin to auditor — govern exactly what each person can see and do.

Audit logs

Sensitive actions are recorded with actor, timestamp, and context, available for review and export.

Encryption

Data is encrypted in transit and at rest using industry-standard ciphers.

Secure payment tokenization

When giving goes live, payment instruments are tokenized by certified providers — Tara stores references, never raw data.

No raw card or bank data stored

Tara never stores card numbers, CVV, account numbers, routing numbers, or raw EFT/PAD details. Ever.

Privacy by design

Data minimization, retention controls, and least-privilege access are built into the architecture from day one.

Human review before real data

Real customer financial data is only used after explicit human review and authorization — never silently.

Payment data boundary
Tara never stores raw card or bank account details. Payment data is tokenized through secure payment providers. Tara retains only provider-issued references — customer IDs, payment method tokens, payment intent IDs, mandate IDs, and settlement IDs.
Phase 1 scope
Today, Tara Financial demonstrates the full product vision using deterministic demo data. Giving, accounting sync, and payment rails are visual prototypes — no real payment processing, banking, or accounting integration occurs in this phase.