Privacy Policy

1. Who we are

Klaimly is a flight delay compensation service operated by Klaimly Ltd ("we", "us", "our"), a company registered in England and Wales under company number 17321388, with its registered office at 66 Paul Street, London, England, EC2A 4NA. We are the data controller responsible for your personal data.

We are registered with the Information Commissioner's Office (ICO), registration reference ZC189775.

Contact: support@klaimly.co.uk

2. What data we collect

We collect the following categories of personal data:

• Identity data: full name as it appears on your booking
• Contact data: email address, phone number (optional)
• Flight data: flight number, airline, departure and arrival airports, date of travel, booking reference
• Disruption data: type of disruption, delay duration, description of events. For denied boarding claims, this also includes whether you had valid travel documentation, how late you arrived at your destination, and whether you volunteered to give up your seat
• Verification data: a one-time code sent to your email to confirm it belongs to you, deleted automatically once used or after 10 minutes
• E-signature: your electronic signature on the Letter of Authority authorising us to act on your behalf. If an airline requires a signature that matches your identity document, we may ask you to sign the Letter of Authority again
• Supporting documents: where the airline or a national enforcement body requires them to verify your identity or eligibility, or to support your claim, we may ask you to upload documents such as your passport or photo ID, boarding pass, booking confirmation, receipts for expenses, or a bank statement. We only ask for these when they are needed for your specific claim, you upload them yourself through a secure private link, and they are shared only with the airline or enforcement body handling your claim
• Payment data: if your claim is won, we may ask for your bank account holder name and either a UK sort code and account number, or an international IBAN and SWIFT/BIC, together with the billing address registered to that account. This is used solely to pass on to the airline so it can pay your compensation directly to you. We never use these details to move money ourselves
• Technical data: IP address, browser type, device information, cookies (see our Cookie Policy)
• In-progress claim data: if you start a claim but don't finish it, your name, email, phone, and flight details may be temporarily stored in your browser's local storage so you can resume where you left off. This is cleared automatically once you submit your claim, or you can clear it yourself by clearing your browser data

3. Why we collect it and our legal basis

4. Who we share your data with

We only share your data where necessary to process your claim or operate our service:

• Airlines: to file and pursue your compensation claim, including any supporting documents the airline requests to verify your identity or progress your claim, and, once your claim is won, your bank account details and billing address so the airline can pay your compensation directly to you
• National enforcement bodies: if your claim is escalated, including any supporting documents they require to determine it
• Supabase: database and document storage hosting (EU region, encrypted at rest, restricted to our servers only)
• Resend: transactional email delivery (verification codes and claim updates)
• FlightLabs: your flight number, departure and arrival airports, and travel date may be sent to verify flight status and delay times. No other personal data is shared with this provider.
• Vercel: website hosting

We never collect or store payment card details. Compensation is paid to you directly by the airline, and our 5% fee is settled by bank transfer or payment link from an emailed invoice, never through this website. The only bank details we ever collect are your own, and only so we can pass them to the airline for your compensation payout, never to move money on your behalf.

We do not sell your personal data to any third party. Ever.

5. International transfers

Some of our service providers are based outside the UK/EEA. Where data is transferred internationally, we ensure appropriate safeguards are in place, including Standard Contractual Clauses (SCCs) approved by the European Commission, or the provider is certified under an adequate framework.

6. How long we keep your data

We retain your personal data for the following periods:

• Active claims: for the duration of the claim plus 12 months
• Completed claims: 6 years from the date of the flight (matching the EU261 limitation period)
• Uploaded documents: supporting documents you upload (identity documents, boarding passes, receipts, bank statements) are kept only for as long as needed to progress and settle your claim, and are deleted once the claim is closed, or sooner on request
• Marketing preferences: until you withdraw consent
• Technical logs: 90 days

After these periods, your data is securely deleted or anonymised.

7. Your rights

Under UK GDPR and EU GDPR, you have the following rights:

To exercise any of these rights, email us at support@klaimly.co.uk. We will respond within 30 days.

8. Security

We take the security of your data seriously. We use encryption in transit (TLS/SSL), encryption at rest, access controls, and regular security reviews. Your claim data is stored in a database that only our own servers can access directly; it is never exposed to the public internet. Documents you upload are held in a private storage area that is not publicly accessible and can only be opened by us through short-lived, single-use links.

9. Children

Our service is not directed at anyone under 18. We do not knowingly collect data from children. If you believe we have collected data from a child, please contact us and we will delete it promptly.

10. Changes to this policy

We may update this policy from time to time. We will notify you of significant changes by email or by posting a notice on our website. The "last updated" date at the top of this page indicates when the policy was last revised.