Skip to content
AptiroAptirodocs
Menu: Security overview

Security

Security overview

On this page

This page is for a procurement or security team reviewing Aptiro. It describes how the shipped product handles hosting, tenancy, encryption, secrets, the audit log, backups and access control, as implemented in this codebase and its Terraform. It is not a certificate, a penetration-test report or a contractual commitment.

A named sub-processor list is available on request under NDA. A longer supplier security questionnaire is also available on request. Terms, privacy policy and data-processing agreement wording are to confirm with Aptiro.

Related pages: sub-processors, data flows.

Hosting

The application runs on our cloud hosting provider, in the EU. Infrastructure is defined in Terraform under infra/ in the product repository. In outline:

  • The API runs as serverless functions behind an HTTPS API gateway.
  • The database is managed PostgreSQL in private subnets, reachable only from the application (and staff) functions.
  • The web app is static files on object storage, delivered through a CDN with HTTPS redirect and TLS 1.2 minimum on the viewer policy checked in Terraform.
  • Sign-in uses a managed identity service (email and password, and Google sign-in where enabled).
  • Browser telemetry and backend metrics go to collectors self-hosted on Aptiro's own infrastructure. Operational traces from the API and the AI assistant connector are also sent to a hosted observability provider in the EU (see sub-processors).

Region wording in a contract is to confirm with Aptiro; this page describes where the product is built to run, not a contractual hosting-region promise.

Tenancy (keeping organisations apart)

Customer data belongs to one organisation. Each signed-in member's queries are scoped to their organisation, and role-based visibility further narrows what they may read or change inside it. Scans, reports and settings changes use the caller's organisation and do not reach another tenant's accounts.

Customer credentials (integration secrets) live in a secret store keyed by organisation. A reference that does not belong to the caller's organisation is refused. See Secrets below.

Encryption

In transit. Customer browsers and APIs use HTTPS. The CDN and API custom domains are configured for HTTPS; viewer policy redirects HTTP to HTTPS. Database connections from the application use SSL required mode.

At rest. The database has storage encryption enabled. Attachment and export object stores use server-side encryption on the bucket configuration in Terraform. Customer credentials in production are held in the cloud provider's secrets service (see below), not in the application database.

Exact key policies and cipher suites are operational detail and are not listed here.

Secret store

Customer credentials (for example webhook signing secrets, messaging tokens, SMTP passwords, calendar OAuth client secrets, people-data provider keys) are stored through the per-organisation secret store. In production that is the cloud provider's secrets service under a configured prefix; every stored secret is tied to its organisation. The database keeps a reference, not the secret value.

The API never sends a credential back to the browser, whatever the role. Responses carry a write-only flag (for example that a secret is set). Form fields stay empty until someone types a new value.

Platform secrets that Aptiro itself uses (billing, model providers, and so on) are separate from the per-organisation store and are not readable through customer APIs.

Audit log

On plans that include it, Aptiro records signed-in API requests at the HTTP edge: who, which route pattern, target id where applicable, status, and for changes the names of fields sent, never bodies, query strings or secret values. Rows are kept for 400 days; older rows are swept by housekeeping.

Who can view it: members with audit permission (owners, admins and the Audit built-in role). The page is Audit log in the app menu. Nothing is recorded for an organisation until the plan includes the entitlement.

Backups

Database backup retention in Terraform is 7 days, with a defined backup window. Production enables Multi-AZ and deletion protection. Restore testing and recovery objectives for a buyer's contract are to confirm with Aptiro; they are not asserted here.

Access control and roles

Each organisation member has a role. Built-in roles (Admin, Full access, Team manager, Standard, Read only, Audit, and related) and custom roles on Scale are defined in shared permissions code and enforced on authenticated routes. Field groups a role hides are stripped in the scoped database client, not reimplemented per endpoint.

Owners manage billing and ownership transfer. Members can be required to use an authenticator app (TOTP) for email-and-password sign-in; see set up an authenticator. Google sign-in follows Google's second step and is exempt from Aptiro's TOTP requirement, as the Settings copy states.

Aptiro staff use a separate admin application, identity pool and database login. Staff powers follow an explicit staff role list, not merely being on a sign-in list. Staff credit changes that affect a customer organisation are visible on that organisation's audit log as Aptiro support, without the staff member's email.

Does the platform use PHP?

No. The backend is Node.js (Express, TypeScript, Prisma). The customer app is React (TypeScript, Vite). There is no PHP application runtime in this repository. A separate marketing website, if any, is outside this repo: to confirm with Aptiro if a buyer needs that stack in writing.

Last updated 2026-10-31

Search the documentation