Terms of use

This version is 2.0 (Beta), effective Mon 26 Oct 2026.

1. Nature of the software

Ramp is an experimental, pre-release tool built by a single developer to explore how pre-flight briefing data could be assembled and how a flight school's records could be kept. It has not been independently audited, reviewed by certified aviation engineers, or tested against any aviation safety standard. Calculations may contain errors. Source data copied from POHs may be wrong.

2. Operational use is prohibited

You agree not to use any output produced by Ramp as input to a real flight decision. This includes, without limitation: take-off and landing distance calculations, weight and balance results, fuel calculations, route briefings, weather summaries, NOTAM summaries, and walk-around checklists. Ramp does not decide whether a flight goes. The pilot in command does. For every actual flight use the aircraft's POH, current AIS sources, certified flight planning tools, and the proper authorities.

3. No warranty

Ramp is provided "as is", with no warranty of any kind, express or implied. The developer makes no claim that any value displayed by Ramp is correct, current, complete, or fit for any purpose, aviation-related or otherwise.

4. Limitation of liability

To the maximum extent permitted by law, the developer shall not be liable for any direct, indirect, incidental, consequential, or punitive damages arising from use of Ramp, including without limitation any damages resulting from incorrect calculations, incorrect transcription of source data, software bugs, data loss, or service unavailability.

5. Personal data

Ramp stores person records (name, optional contact details, optional travel document details for GAR and GENDEC) for the account that entered them. These fields are encrypted at rest with a symmetric key. Who can read a record depends on whose record it is. A school's authorised staff can read the student and training records the school holds, according to their role at the school. In a personal account, only that account's user can read the records they entered. The developer does not sell user data. It is shared only with the services that run Ramp (hosting, card payments and, when you ask for an AI action, the AI provider), and otherwise only where the law requires. By creating person records you confirm you have a legitimate basis to hold the data, for example, it is your own information or you have the data subject's permission.

6. Beta access and changes

Access to Ramp during the beta is granted at the developer's sole discretion and may be withdrawn at any time without notice. Functionality, data structures, and these terms may change between deploys. Backups of your data are not guaranteed.

7. Acceptance

By ticking "I accept" when you sign in or accept an invitation, you confirm you have read these terms, that you understand Ramp must not be used for real flight, and that you accept the no-warranty and limitation-of-liability provisions in these terms.

8. Contact and reports

Questions or issues: contact the developer directly. Ramp has forms for occurrence reports and aircraft defect reports. They record the report for your school or account. Ramp is not a regulator's mandatory reporting channel, and a report filed in Ramp does not satisfy any duty to report. Report to the aviation authority as the law requires.