Data Processing Agreement
Effective November 5, 2026
This Data Processing Agreement (“DPA”) is part of the agreement between UlfApp Software LLC, an Indiana limited liability company (“UlfApp”, the “Processor”) and the airline or company subscribing to AeroCoreHC (the “Customer”) under the Terms of Service or a signed agreement (the “Agreement”). It applies whenever we process personal information on the Customer’s behalf. It takes effect with the Agreement. A Customer that wants a signed copy can print this page (or save it as a PDF), sign it, and send it to us, and we’ll countersign.
1. Roles
The Customer is the controller (or “business”) for the personal information in its AeroCoreHC site (“Customer Personal Data”). UlfApp is its processor (or “service provider”). The details of the processing are in Annex 1.
2. Instructions
We process Customer Personal Data only to provide, secure and support AeroCoreHC under the Agreement, and on the Customer’s other documented instructions. The Customer’s administrators’ use of the app’s settings counts as an instruction. If we believe an instruction breaks the law, we’ll say so. If the law requires us to process data differently, we’ll tell the Customer first, unless the law forbids it.
3. What we won’t do
We won’t sell or share Customer Personal Data, use it for advertising, use it for any purpose other than the Agreement, keep or disclose it outside the Agreement, or combine it with data from other customers or sources, except as the law allows a service provider to do. We understand and will follow these restrictions.
4. Our people
Only people who need access to provide the Service can get it, and they are bound to keep it confidential. Access to a Customer’s site goes through the labeled “AeroCoreHC Support” account and is recorded in that site’s Audit Trail.
5. Security
We keep in place the technical and organizational measures in Annex 2, which are also described on our Security page. We may improve them, but we won’t reduce the overall level of protection during the Customer’s subscription.
6. Subprocessors
The Customer authorizes the subprocessors listed in Annex 3. We’ll tell the Customer’s administrator at least 30 days before adding or replacing one. If the Customer has a reasonable data-protection objection that we can’t resolve, it may end the affected part of the Service and get a refund of prepaid fees for the unused term. Each subprocessor is bound by data-protection terms at least as protective as this DPA, and we are responsible for its work.
7. Helping the Customer
Taking into account what the app does and the information we have, we’ll help the Customer respond to requests from individuals (to see, correct, delete or get a copy of their information), and with security reviews and assessments it is required to do. Most account and record changes can be made by the Customer’s administrators directly in the app. If we receive a request directly from one of the Customer’s users, we’ll pass it to the Customer and won’t answer it ourselves unless the Customer asks us to.
8. Security incidents
If we become aware of a breach of security that leads to accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Customer Personal Data, we’ll notify the Customer without undue delay and in any case within 72 hours. We’ll tell the Customer what happened, what data and how many people are likely affected, what we’re doing about it, and who to contact, and keep it updated. Notifying the Customer isn’t an admission of fault.
9. Audits
We’ll answer the Customer’s reasonable written security questionnaires, and make available the information needed to show we comply with this DPA. Once a year, or after a security incident, the Customer may have an assessment done, at its own cost, by itself or an independent auditor bound by confidentiality. It must give 30 days’ notice, and the assessment must be scoped so it doesn’t disrupt the Service or expose other customers’ data.
10. Where data is processed
Customer Personal Data is stored and processed in the United States. We won’t move it to another country without telling the Customer first and putting lawful safeguards in place.
11. When the Agreement ends
Within 30 days after the Agreement ends, the Customer may ask for a copy of its data in common formats. We’ll then delete Customer Personal Data from our live systems within 30 days, and from backups as they expire (at the latest 30 days after that), unless the law requires us to keep it. On request, we’ll confirm the deletion in writing.
12. General
Liability under this DPA is subject to the limits in the Agreement. If this DPA and the Agreement conflict on data protection, this DPA wins. The Agreement’s governing law and courts apply.
Annex 1: The processing
| Subject and purpose | Providing AeroCoreHC: turnover reporting, aircraft tracking, Pick-Up Sheets, Info Sheets, Post Dock reviews, CANN and parts tracking, chat, and the related security, support and backups. |
|---|---|
| Duration | The term of the Agreement, plus the return and deletion period in section 11. |
| What we do with it | Store, organize, display, transmit to the Customer’s users, back up, and delete. |
| Whose data | The Customer’s employees and contractors who use AeroCoreHC, and people named in the work records (for example MRO staff named on a Pick-Up item). |
| Kinds of data | Names, work email addresses, roles and stations. Work records and photos of aircraft and parts. Notes and chat messages. Audit Trail and sign-in records, including IP addresses. |
| Sensitive data | None intended. The Service isn’t designed for sensitive data, and the Terms of Service prohibit storing it. |
Annex 2: Security measures
- A separate site and database for each customer, and sessions locked to the customer’s own site.
- HTTPS with HSTS on all traffic. AES-256 encryption of off-site backups.
- Passwords stored as salted bcrypt hashes. Throttling of failed sign-ins. Secure, HttpOnly, SameSite cookies. Forced change of temporary passwords.
- Role-based access set by the Customer’s administrators. A labeled, audited support account for our own access.
- Protection against cross-site request forgery and framing. No third-party scripts or trackers.
- An Audit Trail of user actions, including sign-ins and downloads.
- Nightly backups, kept about a week on the server and 14 days off-site at a separate US location, checked automatically.
- Automated health monitoring every 15 minutes, with alerts. Automatic operating-system security updates. Code in a private repository, with automated tests.
- Incident notification within 72 hours (section 8).
Annex 3: Subprocessors
| 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 |
Signatures
Company:
Name and title:
Signature:
Date:
Name and title:
Signature:
Date:
Contact
UlfApp Software LLC, an Indiana limited liability company
Greenwood, Indiana
support@aerocorehc.com
