Privacy Statement

Account Data

Your e-mail address and an optional display name, collected during signup. Used for authentication and to identify your account.

Server Log Data

Our hosting provider (Railway) automatically records for every request: IP address, browser user-agent, requested URL, HTTP status code, and timestamp. These logs are used solely for operating, monitoring, and securing the service.

Google Login Data

If you choose "Continue with Google", the following data is received from your Google account via Supabase OAuth: e-mail address, Google account ID (sub), display name, and profile picture URL. For Google-side processing please refer to Google's own privacy policy: https://policies.google.com/privacy .

User-Uploaded Files

You may upload Quad thumbnail images and Betaflight CLI dump files. These files are stored on Supabase Storage (S3-compatible, EU region Frankfurt, eu-central-1).

Note on image EXIF metadata: Uploaded images may contain EXIF metadata, including GPS coordinates if the photo was taken on a smartphone with location services enabled. This application does not automatically strip EXIF data at this time. If you wish to protect your location, please remove EXIF data from images before uploading.

Quad Sharing Data

If you opt in to Quad Sharing, selected portions of your Quad data (component list, All-Up Weight, Betaflight PIDs and rates) are made publicly accessible to anyone who has the share URL without requiring a login.

Sharing is fully opt-in and disabled by default. You control which sections are visible and can revoke sharing at any time — the public URL then returns a 404.

Owner name masking is enabled by default: your display name is hidden from the public share page unless you explicitly unmask it as the owner.

Quad View Counter

Public Quad share pages record a session-deduplicated view count. A session identifier is used to avoid counting the same visitor multiple times during a single browsing session. No persistent tracking cookie is set; the session identifier expires when the browser session ends. This is technically necessary for the sharing feature to provide owners with aggregate visit statistics.

Account Data

Art. 6(1)(b) DSGVO — contract fulfillment. Your e-mail address is necessary to provide the service you registered for.

Server Log Data

Art. 6(1)(f) DSGVO — legitimate interest in operating, monitoring, and securing the service.

Google Login Data

Art. 6(1)(b) DSGVO — contract fulfillment. Google account data is processed to enable login to the service.

User-Uploaded Files

Art. 6(1)(b) DSGVO — contract fulfillment. Quad images and Betaflight dumps are processed to enable the core Quad management features.

Quad Sharing Data

Art. 6(1)(a) DSGVO — explicit consent, given via the in-app Quad Sharing toggle. Consent can be withdrawn at any time.

Quad View Counter

Art. 6(1)(f) DSGVO — legitimate interest in providing the Quad owner with aggregate visit statistics without tracking individual visitors.

Account Data

Your account data is retained until you request deletion of your account. You can request deletion of your account and all associated data directly within the application via your Profile page → Delete Account. This triggers the 3-step GDPR erasure workflow (confirmation e-mail + final confirmation page).

Server Log Data

Server logs are retained by the hosting provider (Railway) for a maximum of 7 days and are then automatically deleted.

User-Uploaded Files

Uploaded Quad images and Betaflight dump files are retained until you delete the associated Quad, or until you delete your account.