Skip to content

Your crew data, kept in India and kept apart

Where AeroLarke stores your data, how each operator is kept separate from every other, who can change what, and how it is backed up. Bring this page to your security review; we answer anything it does not.

Where your data goes
Your crew office and crewBrowser and crew app

Microsoft Azure, Central India (Pune)

  • ApplicationWeb app, crew app API, sign-in
  • DatabaseRow-level security per operator
  • Audit anchorsWrite-once, one a day
  • BackupsWrite-once for 35 days

Where your data lives

In India, encrypted, and copied three ways.

Data residency in India

The product runs on Microsoft Azure in its Central India region, in Pune. Indian operators’ data, and its backups, are stored there.

One region
The application, the database, uploaded files, the nightly backups and the server snapshots all stay in Azure Central India.
Enquiries too
Demo and sandbox requests from this website are stored by the AeroLarke API in the same region.
The exceptions
Push notifications to the crew app pass through Expo, Apple and Google, and email has its own provider. The privacy policy lists each one.

Encryption

Data is encrypted in transit and at rest.

In transit
Every AeroLarke address is served over HTTPS only, and browsers are told to keep using it. Backups travel to storage over HTTPS too.
At rest
Server disks and backup storage are encrypted at rest by Microsoft Azure.
Locked-down storage
Backup storage accepts no shared keys and no public access: only the server’s own identity and our administrators’ networks reach it.

Backups and recovery

Three layers of copies, all in Central India, and a scripted restore that checks what it brought back.

Every 10 minutes
Database changes are copied off the server continuously, for recovery to a point in time.
Every night
A full backup at 02:00 IST. Copies are held for 35 days under a write-once policy, so the server itself cannot change or delete them.
Every day
A snapshot of the whole server at 03:00 IST, kept for 30 days, 12 weeks and 12 months.

Who can see and change it

Your people, by role and designation. An inspector, read-only. Our support staff, only when you approve.

Each operator kept apart

Every operator has its own workspace. Every record carries the operator it belongs to, and the database itself refuses to return another operator’s rows.

Row-level security
PostgreSQL row-level security is switched on and forced on every operator table, so a query only ever sees the signed-in operator’s data.
Sandboxes stay separate
A sandbox or demo workspace is a workspace of its own, never a view of live data.
Support with your approval
AeroLarke staff reach your data only through a support session your administrator approves: time-limited, read-only by default, every request logged.

Who can do what

Named, personal accounts only. Roles grant rights per module and per screen, and the actions the CAR cares about need a designated officer.

Designated officers
Approving an override, verifying actual times, publishing a roster and approving a Scheme change need a designated-officer appointment in force that day.
Separation of duties
Whoever requests an override or a Scheme change cannot approve it, and whoever enters actual times cannot verify them.
Sign-in
Passwords of at least 12 characters, no reuse of the last five, and lock-out after repeated failures. Two-step sign-in with an authenticator app is supported.

DGCA inspector access

An inspector gets a login of their own, so nobody shares an account or exports data to show it.

Read-only and time-limited
A designated officer grants the access, for the period the inspection needs.
Every visit logged
Each request an inspector makes is recorded, including any that were refused.
The reasoning on screen
Every legality result shows the limit, the actual value, the margin and the CAR paragraph.

What is recorded

Every change, in a history that shows if anything was altered.

An audit trail that shows any change

Nothing is deleted or overwritten: corrections are amendments that keep the original. Every change is written to a hash-chained audit trail.

Chained entries
Each entry’s hash covers its contents and the entry before it, so altering or removing one breaks every link after it.
Daily anchors
Each day the chain head is written to write-once storage, kept apart from the database.
Verify integrity
Anyone authorised can recompute the chain over a period and compare it with the anchors.
See the integrity check on the Compliance page

The DPDP Act 2023

India’s Digital Personal Data Protection Act sets how personal data is handled. Here is how the roles fall.

Bring your security questions

Send us your security questionnaire, or ask in the demo. To report a security problem, email us and we will reply.