Security & Subprocessors
Effective November 5, 2026
How AeroCoreHC protects your airline’s data, written for IT and security reviewers. If your questionnaire asks something this page doesn’t answer, contact us below.
Hosting and where data lives
- Servers are in data centers in the United States (Hostinger). Customer data, including backups, stays in the United States.
- Each airline has its own site address and its own database. A signed-in session only works on the airline’s own site, so it can’t be used on another airline’s.
- Uploaded photos are stored outside the website’s public folders and served only to signed-in users of the same airline, or through a Pick-Up Sheet photo link (next).
- Pick-Up Sheet photos can be shared with the maintenance vendor’s Leads, who have no sign-in, through a link in the Excel download. Each link holds a 256-bit random key, and only a hash of it is stored. It shows one aircraft’s walk-item photos, read-only, and is kept out of search engines. It stops working 7 days after the aircraft returns to service (180 days at the most), a rep can stop it at once from the sheet, and every opening is recorded in the Audit Trail.
Encryption
- All traffic uses HTTPS (TLS) with HSTS, so browsers refuse unencrypted connections.
- Off-site backups are encrypted with AES-256 before they leave our server, and checked to decrypt correctly before they’re sent.
- Passwords are stored only as salted one-way hashes (bcrypt).
Signing in and access
- Your airline’s administrators create accounts and choose which apps each person can open. New accounts get a one-time temporary password that must be changed at first sign-in. Passwords must be at least 10 characters.
- Two-step sign-in for everyone. After the email and password, a 6-digit code is emailed to the person. It works once, for 10 minutes, and allows 5 tries. Only a one-way hash of it is stored. A stolen password alone isn’t enough to get in.
- Sign-ins last 12 hours, never longer. After that, the person signs in again with their password and a new code. Signing out, a password change or a deactivated account ends it straight away, on every device.
- Repeated failed sign-ins are blocked, whether the password or the code is wrong (per account and per network address).
- “Forgot password?” emails a one-time link that works for 30 minutes. It answers the same way, in the same time, whether or not the address has an account, and requests are limited per address and per network. Setting a new password, or any password change, signs the person out on every other device, and they’re emailed that it changed.
- Session cookies are Secure, HttpOnly and SameSite. The cookie that keeps a device signed in is a random one-time code, stored only as a hash, replaced each time it’s used, and expiring at the end of the 12 hours.
- Every form is protected against cross-site request forgery. Pages can’t be framed by other sites, and the app loads no third-party scripts, fonts or trackers. Every page also tells the browser to load and send nothing to any other site (a Content Security Policy), and turns off device features the app doesn’t use.
- Our own access to an airline’s site is only through a clearly labeled “AeroCoreHC Support” account that the airline can see, and its actions are recorded in the Audit Trail.
- Not yet available: codes by text message, and single sign-on (SAML / OIDC). Both are planned. Single sign-on can be set up for an Enterprise customer with its IT team.
Audit Trail
Every action in the app is recorded with who, when, which app and what: sign-ins (including failed attempts), account and access changes, data changes, deletions and downloads. Entries can’t be edited or deleted from the app. The text of notes and chats isn’t recorded.
Backups and recovery
- A full backup of each customer’s database runs every night. It’s kept about a week on the server, and an encrypted copy, including uploaded photos, is kept off-site for 14 days, at a separate US location.
- Backups are checked automatically, and failures alert us.
Monitoring and maintenance
- An automated health check runs every 15 minutes. It checks backups, that each site answers, certificates, disk space and database consistency, and alerts us to any server error a user hits.
- The operating system and software are kept up to date with security patches. The code is kept in a private repository, and automated tests run on every change.
Incidents
If we confirm a security incident that affects your airline’s data, we’ll notify your airline’s contact without undue delay, and within 72 hours. We’ll tell you what happened and what data was involved, and keep you updated as we learn more. See the Data Processing Agreement.
Certifications
AeroCoreHC doesn’t currently hold a SOC 2 or ISO 27001 certification, and no outside penetration test has been done yet. We’re happy to answer your security questionnaire and to support a test arranged by your airline.
Subprocessors
These companies handle data for us. We’ll tell customers’ administrators at least 30 days before adding or replacing one.
| Company | What it does | Data it handles | Location |
|---|---|---|---|
| Hostinger International Ltd. | Hosts the servers and databases, and the encrypted off-site backups | All customer data (backups are encrypted before they leave our server) | United States |
| Brevo (Sendinblue SAS) | Delivers the app’s emails: sign-in codes, password-reset links and “your password was changed” notices to users, and sales requests and server alerts to our staff | The recipient’s name and work email, and the email’s contents (a sign-in code, a one-time link, or what a sales request or alert says) | European Union |
| Stripe, Inc. | Card payments for online purchases | Billing contact and payment details (we never see card numbers) | United States |
Our DNS provider (Cloudflare) only answers address lookups for our domain names. App traffic and data don’t pass through it.
Contact
UlfApp Software LLC, an Indiana limited liability company
Greenwood, Indiana
support@aerocorehc.com
