VognaryContact
Security

Where your data goes

Three things decide everything on this page: what this deployment can currently prove, the one path evidence travels, and the boundaries the system will not cross. Each is stated below, in that order.

Mailbox access
None. Google is sign-in only
Customer financial data
Blocked until the independent assessment and retest close
Model training on your invoices
Never
Ask a security questionReport a vulnerability

Deployment truth

Live status, measured rather than promised

These states are read from this deployment's configuration each time the page loads. Backup Proven requires a recorded restore of a stored encrypted dump, not only a storage setting. Anything unproven is labeled that way.

  • Signed session cookies

    Configured

    Session cookies are signed and expire; unsigned or expired cookies are rejected.

  • Encrypted token vault

    Configured

    The vault key passed an encrypt-decrypt round-trip; connector secrets and workspace snapshots are stored encrypted.

  • Encrypted backups and restore drill

    Configured

    Backup storage is configured, but the restore status has no valid restricted record hash.

  • Identity provider

    Configured

    Google sign-in is active; the provider's issuer and subject are verified on every callback.

  • Receipt forwarding configuration

    Configured

    Receiving configuration and operator evidence are present. The public entry still verifies required database migrations before offering forwarding.

  • Retention enforcement schedule

    Not yet proven

    No production retention schedule has been attested yet.

  • Renewal alert delivery

    Not yet proven

    Production renewal-alert delivery has not been attested yet.

  • Independent security assessment

    Not yet proven

    No dated independent assessment and remediation retest is recorded for this release. Real customer financial data remains blocked until that evidence exists.

  • Private-pilot collection

    Not yet proven

    Online collection for the private pilot is not configured on this deployment.

Data flow

The one path evidence travels

There is no second route in. Nothing is scanned, polled, or fetched on your behalf.

  1. You submit one document. A paste, an upload, or mail you send to a private receipt address. Vognary never reaches into a mailbox, a bank, or a card account to find it.
  2. Ingress is verified and bounded. Resend webhook requests are checked against the untouched request body, size-bounded, replay-fenced, and resolved through a secret alias before any content is retrieved.
  3. Accepted text is encrypted at the application layer. Raw source text is stored with authenticated encryption. Normalized facts keep a reference back to the evidence they came from.
  4. Every read rechecks who is asking. Protected routes revalidate the session and the workspace role, and queries are scoped to the signed-in workspace id.
  5. Retention is minimized, not promised away. Encrypted raw source text and terminal transport metadata are minimized after 30 days when retention runs. Provider-held email follows Resend's own schedule, and Vognary does not promise instant deletion from backups.

Operating boundaries

What the system does and does not hold

No passwords or PINs
Vognary never asks for bank passwords, card PINs, UPI PINs, or netbanking credentials.
No mailbox access
Vognary does not access or scan Gmail. Any mail sent to a private receipt address can reach the receiving provider, so the address must be kept confidential.
Signed receipt ingress
Resend webhook requests are verified against the untouched request body, bounded, replay-fenced, and resolved through a secret alias before content is retrieved.
Encrypted Recovery storage
Accepted raw source text uses authenticated application-layer encryption. Protected routes recheck the session and workspace role; normalized facts retain evidence references.
Separate retention boundaries
Vognary minimizes encrypted raw source text and terminal transport metadata under its retention policy. Provider-held email follows Resend’s separate retention and deletion controls.
Source before action
Each suggestion links to receipt evidence. Planning to cancel records your intent; Vognary does not cancel the service.

Detail on request

Questions the evidence policy must answer

Does Vognary read my Gmail?

No. Google is used for sign-in only.

Is Gmail connected through OAuth?

No. Direct mailbox OAuth is not offered.

Is global forwarding required?

No. You can paste or upload receipts. A private billing address is optional after the first result.

What do I provide?

Only evidence you explicitly submit or send to your private receipt address.

Why can I trust a number?

Every important claim exposes the receipt or observation behind it. Unsupported facts stay unpublished.

Is invoice content used for model training?

Vognary does not train models on your invoices or receipt text.

Does AI processing see invoice content?

Signed-in commitment reconstruction is deterministic. If an Anthropic API key is configured, the guest document-ingest assist can send document text to Anthropic; proposed line items are kept only when they reconcile to the document’s own total. Vognary does not control Anthropic’s retention.

What is retained?

Normalized facts and bounded excerpts remain until you delete the workspace or account. Encrypted raw source text is minimized after 30 days when retention runs. Provider-held email follows Resend’s own schedule. Vognary does not promise instant deletion from backups.

Are workspaces isolated?

Queries are scoped to the signed-in workspace id. That is application-level isolation, not a certified multi-tenant audit.

If your question is not answered above, ask it directly — contact Vognary. Security reports have their own channel in security.txt.