Privacy Policy

EstiLedger helps private aviation buyers evaluate whether an aircraft can operate safely at the airports they care about. We cross-reference FAA aircraft performance data with airport runway constraints from public aviation datasets. This policy explains what information we collect, how we use it, and how we protect it.

Account information. If you sign in, we store your email address, an optional display name, and your Google account identifier when you use Google sign-in. We use this to authenticate you and operate your account.

Mission and lookup data. When you run a suitability analysis, you may enter an aircraft registration (for example, N51EE) and airport ICAO codes (for example, KTEB and KASE). In the current MVP, analysis runs in your browser with preview data. As features expand, we may store saved mission profiles (such as departure and arrival airports, passenger count, range, or budget) in our database when you choose to save them.

Technical data. Our hosting infrastructure processes standard request logs (such as IP address, browser type, and timestamps) needed to deliver the service, prevent abuse, and maintain security.

We use collected information to:

• Operate accounts, authentication, and admin access;
• Run aircraft and airport lookups against FAA and OurAirports reference data;
• Store mission profiles and analysis history when you save them;
• Improve reliability, security, and abuse prevention; and
• Respond to support requests.

We do not sell your personal information. We do not use your data for third-party advertising profiles.

Aircraft performance and airport runway information displayed in EstiLedger is derived from public sources, including FAA registry data and OurAirports. That reference data is not personal information about you. We ingest and cache it to power lookups and suitability scoring.

We use essential cookies to keep you signed in (an httpOnly session cookie). We do not use third-party advertising cookies. You can sign out at any time to end your session.

We rely on trusted infrastructure providers to run EstiLedger, including:

• PostgreSQL — application database (hosted on Cogertir infrastructure);
• Google — optional OAuth sign-in;
• Google Cloud — deployment and object storage infrastructure.

These providers process data on our behalf under their own terms and privacy policies. Sensitive credentials (such as database connection strings and API keys) are kept on the server, not exposed in the browser.

We retain account and saved mission data for as long as needed to operate the service. You may contact us to request deletion of your account, subject to legal or operational requirements.

We use industry-standard measures such as encrypted connections (HTTPS), signed session tokens, and server-side access controls. No method of transmission or storage is completely secure.

EstiLedger is not directed at children under 13, and we do not knowingly collect personal information from them. If you believe a child has provided us personal information, contact us and we will take appropriate steps to delete it.

We may update this Privacy Policy from time to time. We will post the revised version on this page and update the “Last updated” date above. Continued use of EstiLedger after changes become effective constitutes acceptance of the updated policy.

Questions about this policy or your data? Email contact@estiledger.com.