Privacy Policy

Draft. This document describes how the Hangar application handles personal data. It has not yet been reviewed by legal counsel. Have it checked against your jurisdiction and processing agreements before onboarding real users.

1. Controller

The controller responsible for processing personal data in the Hangar application ("Hangar", "the service") is:

Stagworks Contact and postal address: see the legal notice.

For data-protection enquiries, use the contact channel listed in the legal notice.

2. What Hangar is

Hangar is a fuel and oil accounting tool for flying clubs. A club records refuels, oil top-ups, oil changes and inspections for its aircraft, imports its Vereinsflieger flight-log export, and uploads photographs of the aircraft logbook (Bordbuch). Hangar computes consumption rates and maintenance due-dates from those records.

Hangar is used by named members of a club. It is not a public website and is not directed at the general public.

3. Categories of data processed

Account data. Email address, display name, hashed authentication credentials, account creation timestamp, and the timestamp and version of the Terms and this Privacy Policy you accepted at sign-up. Authentication is handled by Google Firebase Authentication.

Club and membership data. The clubs you belong to, your role description within a club, and invite codes you create or redeem.

Operational records you enter. Aircraft registrations and technical figures (tank and oil capacities, counter readings, next inspection), fuel and oil events, defect reports, and free-text comments. These may name a pilot or refer to a person.

Flight-log import data. The contents of the Vereinsflieger CSV export you upload: dates, times, aircraft registration, counter readings, flight duration, and the free-text Kommentar field, which can identify the pilot in command.

Logbook photographs. Images of physical aircraft logbook pages you upload, and the text transcribed from them. A page is stored under the SHA-256 hash of its bytes. Photographs are held in Google Firebase Storage.

Technical data. When you use the service, server and platform logs may record your IP address, timestamp, requested resource, referrer, user-agent and HTTP status, for delivery, security and error analysis.

4. Purposes and legal bases (GDPR Art. 6(1))

Purpose	Legal basis
Creating and operating your account, providing the service to your club	Art. 6(1)(b) — performance of a contract
Storing and reconciling the records, imports and photographs your club enters	Art. 6(1)(b), and Art. 6(1)(f) — legitimate interest in an accurate fleet record
Recording your acceptance of the Terms and this policy	Art. 6(1)(c) — legal obligation, and Art. 6(1)(f)
Security, abuse prevention, server logs	Art. 6(1)(f) — legitimate interest in a secure service
Any processing you separately consent to	Art. 6(1)(a) — consent, withdrawable at any time

Hangar does not use analytics, tracking or advertising technologies, and does not set non-essential cookies. A cookie or equivalent local storage is used only to keep you signed in and to remember your language and theme choice.

5. Who can see your data

Other members of your club. Membership is the permission model: every member of a club can read and write all of that club's data, including the records, imports, defect reports and logbook photographs described above. Role labels are descriptive, not access controls.

Processors. Google Ireland Limited / Google LLC provides Firebase Authentication, Firestore and Firebase Storage as our processor under a data processing agreement. The hosting provider for the application runs it under a comparable agreement.

Data is not sold, and is not shared for any third party's own purposes.

6. International transfers

Firebase services may process data on infrastructure operated by Google outside the European Economic Area, including in the United States. Such transfers are covered by the EU-US Data Privacy Framework where applicable, and otherwise by the European Commission's standard contractual clauses.

7. Retention

Account data is kept for as long as the account exists. Club records, imports and logbook photographs are kept for as long as the club retains them or until a member deletes them, since they form the fleet's maintenance history.

When you delete your account, your profile document is removed and you are removed from every club roster. Records you entered into a club remain with the club — they are the club's operational history, not personal correspondence — but are no longer linked to your account.

Server and platform logs are kept for a short period (typically no more than a few weeks) and then deleted, except where a specific security incident requires longer retention until it is resolved.

8. Your rights

Under the GDPR you have the right to access, rectification, erasure, restriction, data portability, and objection to processing based on legitimate interest, and the right to withdraw any consent with future effect. Hangar's profile screen lets you export your data and delete your account directly.

To exercise a right, or if a request cannot be completed in the app, contact us via the legal notice. You also have the right to lodge a complaint with a supervisory authority, in Germany the data-protection authority of your federal state.

9. Security

Traffic is encrypted with TLS. Access to club data requires a signed-in account that is a member of the club. No method of transmission or storage is perfectly secure, and no absolute guarantee can be given.

10. Automated processing of logbook photographs

What is automated. When you upload a photograph of a Bordbuch spread, an automated system — including a machine-learning model ("AI") for handwriting and layout recognition — reads the figures and free text off the image: dates, pilot names, counter readings, flight times, landings, carried-over totals, and the fuel, oil and defect notes on the right-hand page. The flight-log CSV import and the reading of the free-text Kommentar are rule-based and do not use a model.

Provenance is recorded. Each page stores which model and prompt version produced its figures, and the time it was read, so a later model change can be re-run cleanly.

Third-party processor. Handwriting recognition is carried out by {{AI_PROCESSOR}} under a data processing agreement. The photograph and the personal data it contains (including pilot names) are transmitted to that processor for the sole purpose of transcription, are not used to train the processor's models, and are retained by the processor only as long as the request. This processor may process data outside the EEA under the safeguards described in section 6.

No decision is made about you. The output is a transcription, not an assessment. It feeds the club's fuel and oil arithmetic; it does not produce any decision that has legal or similarly significant effect on a person within the meaning of GDPR Art. 22.

Human review. Every machine-read figure is shown to club members beside the photograph it came from, marked as machine-read, and is provisional until a member confirms it. A correction a member makes overrides the model and is stored as the authoritative value. The consumption-rate calculations continue to run on the CSV-sourced figures until a member has ruled on any disagreement between the two.

Legal basis. Art. 6(1)(b) and Art. 6(1)(f) — the legitimate interest in turning a paper logbook into a usable, checkable fleet record. You may object to this processing under section 8; a club can instead maintain its records from the CSV import and manual entry alone.

11. Changes

We may update this policy as the service changes. Material changes raise the policy version; when that happens you may be asked to accept the new version before continuing to use the service. The "last updated" date above always reflects the current version.