Introducing Built-in Log Analyzer for FPV Flights in UAV Desk

Thanks a lot for taking the time to review the platform so thoroughly — I really appreciate your detailed feedback.

Regarding your note about the predecessor: you’re absolutely right to point this out. I wasn’t fully aware of all the issues you mentioned. Based on your feedback, I’ve gone through the system and implemented fixes wherever possible to address these concerns.

On your first question about sensitive data:
All of the fields you mentioned (GPS tracks, license numbers, addresses, etc.) are entirely optional. Users can decide themselves what they want to provide. Data is transmitted securely via HTTPS and is only accessible to the respective user.

For authentication and account-related functionality (including billing), I rely on Clerk, which is a well-established and security-focused provider. The goal here is to avoid handling sensitive authentication logic myself and instead depend on proven infrastructure.

Regarding your second point about data residency:
You are correct — the platform currently runs on infrastructure providers such as Vercel, Neon, Clerk, and Cloudflare, which are primarily US-based.

To give some context: I’m running this platform as a side project, which originally evolved from another project I had published as a self-hosted Docker solution. After receiving multiple requests for a cloud-based version, I decided to rebuild it as a hosted service. To keep costs manageable while still providing a reliable global platform, I chose these larger providers.

At the moment, there are no concrete plans to introduce a separate EU-only infrastructure. That said, I’m definitely open to suggestions if you know of strong EU-based alternatives — I’d be very interested in exploring them. So far, I haven’t come across a setup that would offer a comparable ecosystem with purely EU-based providers.

Thanks again for your valuable input — this kind of feedback is extremely helpful.