Effective Date: October 1, 2024
At TripHistorian.com ("we", "our", "us"), we value your privacy and are committed to protecting your personal information. This Privacy Policy outlines how we collect, use, and safeguard your data when you use our services, including logging in with Google or email, and uploading your flight logs.
We provide two methods for account creation and authentication:
You can upload flight logs from the following third-party services:
When you upload flight logs, we collect and store flight-related data such as flight dates, times, routes, and airline details. We do not collect or store any personally identifiable information (PII) contained in the logs beyond the minimum necessary for login and logout processing.
We use Firebase Analytics to understand how users interact with our services. This may include data like app usage, device information, and general geographic location (country-level). However, this data is anonymized and cannot be used to personally identify users.
The data we collect is used for the following purposes:
We do not share your personal data with third parties except where required by law or with your explicit consent.
We implement industry-standard security measures, including encryption, to protect your data from unauthorized access, disclosure, or alteration. While we strive to protect your information, no method of transmission over the internet or method of electronic storage is 100% secure. Therefore, we cannot guarantee its absolute security.
You have the following rights regarding your data:
We may update this Privacy Policy from time to time. We will notify you of any significant changes by posting a notice on our website or within the app. Continued use of our services after such changes constitutes your consent to the updated policy.
If you have any questions or concerns regarding this Privacy Policy or your data, please contact us at i@triphistorian.com.
By using our services, you acknowledge that you have read and understood this Privacy Policy and agree to our data practices.