Trust & Security

Last updated 2026-08-07 · Artifinance is operated by Anthrotech · contact hello@artifinance.io

This page describes how artifinance.io and the ARIA sandbox at app.artifinance.io are actually built today — not an aspirational architecture diagram. Where something isn't true yet, we say so directly, on the same page as everything else, because a due-diligence reviewer finds the gap either way and a page that only lists strengths reads as less credible, not more.

Architecture, today's shape

• The hosted product runs as a single active Cloud Run service, deliberately capped at one active instance (--max-instances 1) so that every tenant's SQLite-backed ledger writes stay consistent. That cap means we do not yet horizontally scale — a real, current limitation we hold ourselves to rather than risk split writes across instances.
• Each tenant's book is written to local disk and synced to Google Cloud Storage on a fixed loop (today, every 45 seconds), plus a best-effort flush when an instance is asked to shut down for a redeploy. Worst case: writes made in the last moments before an unexpected instance recycle, inside that sync window, can be lost. That is a real, bounded, and shrinking gap, not a hypothetical one — we would rather state the window than claim a durability guarantee we don't have.
• TLS is terminated by Cloud Run and Firebase Hosting; requests are upgraded to HTTPS and HTTP Strict Transport Security is enforced with preload.

Encryption & credentials

• Sensitive personal fields (for example HR identifiers) are encrypted at the application layer with AES-256-GCM before they reach storage — not just relying on disk-level encryption for that data.
• The underlying disks and object storage are encrypted at rest by our cloud provider, Google Cloud, for everything else.
• API keys and service credentials are held in Google Secret Manager and attached at deploy time — never committed to source and never carried as plaintext config in the running container image.

Access & audit

• Access inside a workspace is role-based and scoped to that workspace's own tenant — one customer's data is not reachable from another's session.
• Every ledger write is appended to a hash-chained audit trail, so a book's history can be verified and reconstructed rather than just trusted on faith.
• AI-drafted actions sit behind a maker-checker approval step — nothing posts to your books without a human approving it first.

Subprocessors

The same short list named in our Privacy Notice, kept in sync with it:

• Google Cloud (Cloud Run, Cloud Storage) — hosts the application and your workspace's stored data.
• Firebase — hosts this marketing site and handles sign-in for the hosted app where configured.
• Anthropic, OpenAI, and Google's model APIs — process the specific request text you send ARIA to generate a response, draft an entry, or answer a question. Requests are not used by us to train models.

Data protection rights

DPDP 2023 (India) and GDPR (EU/EEA/UK) rights — access, correction, export, deletion, and withdrawal of consent — are covered in full in our Privacy Notice, along with how to exercise them.

What we haven't certified yet, honestly

• No SOC 2 or ISO 27001 certification exists today.
• No independent third-party penetration test has been completed yet.
• No formal uptime SLA is offered yet — see the architecture note above for why.

These are open items, not hidden ones. If your procurement process needs to track them, ask us for status — we'll tell you where each one stands.

Report a security issue

Found a vulnerability or something that looks like one? Email hello@artifinance.io with what you found and how to reproduce it, and we'll treat it as a priority.