Security & Privacy

Your engineering data is yours alone.

Engineering documents contain some of the most commercially sensitive data in your organisation. We built aikaruvi's infrastructure around that fact — not as an afterthought.

AES-256 encryption Isolated per account Never used for AI training
Infrastructure

Built on enterprise-grade foundations.

Every component of the aikaruvi stack was chosen for security, not convenience.

Encryption at Rest & Transit

All documents are encrypted with AES-256 at rest inside Google Cloud Storage. All data in transit is protected by TLS 1.2+. No document ever travels over an unencrypted connection.

Account Isolation

Every account is provisioned with a dedicated, isolated Google Cloud Storage bucket. No data is ever co-mingled between accounts. IAM rules enforce strict access boundaries at the infrastructure level.

JWT Authentication

Every API request is authorised using short-lived JSON Web Tokens signed with a secure secret. Tokens are validated server-side on every call — there are no permanent API keys to leak or rotate.

Secret Management

All credentials — API keys, database passwords, service account tokens — are stored in Google Cloud Secret Manager with version control and access audit logging. No secrets live in environment files or source code.

No AI Training on Your Data

Your engineering documents are never used to train, fine-tune, or evaluate any AI model — ours or anyone else's. The OpenAI API calls we make are subject to OpenAI's zero-data-retention enterprise terms for API users.

Right to Delete

You can permanently delete any document or your entire account from the dashboard at any time. Deletion removes the file from storage and purges all associated extraction records. No soft-deletes, no recoverable backups retained.

Data Flow

Exactly where your document goes.

No black boxes. Here is the complete path your engineering PDF takes from upload to structured output.

1

Upload via HTTPS

Your browser sends the PDF over TLS-encrypted HTTPS directly to our Cloud Run backend. The file never touches any intermediate server.

2

Stored in your isolated bucket

The backend writes the file to your account's dedicated Google Cloud Storage bucket with AES-256 encryption applied automatically. IAM rules prevent any other account from reading it.

3

Sent to OpenAI API (pages only)

Individual page images are sent to the OpenAI Vision API over HTTPS for structured extraction. OpenAI's API terms for enterprise users apply zero-data-retention — content is not stored or used for training.

4

Structured output returned to you

The extraction result (JSON/CSV) is written to your account's Firestore document store and returned to your dashboard. Only your authenticated session can read it.

Nothing else has access

No aikaruvi employee, contractor, or internal service can read your documents without explicit IAM escalation — which is logged and auditable. Your data is accessible only to your authenticated account.

Vulnerability Disclosure

Found a security issue?

We take security reports seriously and will respond within 48 hours. Please do not publicly disclose findings before we've had a chance to fix them.

Report a Vulnerability

security@aikaruvi.com — PGP key available on request

Security questions before you sign up?

Our team is happy to walk through our security architecture in detail with your IT or InfoSec team.