Privacy Policy
Last updated October 8, 2026
1. Who is responsible
DGP Claims LLC, operating as Delayed Get Paid, is responsible for the personal information handled through this website and our claims service. Contact us about privacy at delayedgetpaid@gmail.com.
2. What we collect
Only what pursuing your claim needs: your name and contact details; the names of the other passengers on the booking, because compensation is per passenger and each one has to be named to be claimed for; flight and booking details; a description of the disruption; documents you upload, such as boarding passes, tickets, receipts, baggage reports and, where relevant, identity documents the airline requires; correspondence with us; your mailing address, because airlines and courts write to one; your electronic signature and its signing record (section 5); and, when there is money to send you, the payout details you choose to give us. The eligibility checker and calculator run in your browser and send us nothing. The claim form keeps your in-progress answers on your own device, and once you type an email address it also saves your progress with us so you can resume; section 4 covers that, and section 9 covers where the browser keeps its copy.
3. Why we use it
To assess and pursue your claim; to communicate with the airline, regulators, dispute-resolution bodies and, with your approval, partner law firms; to pay you; to meet legal obligations; and to run and secure this website. We do not sell personal information and we do not use it for third-party advertising.
4. If you start a claim and do not finish
Once you have typed an email address in the claim form, your answers so far are saved with us as you go, so that a resume link can restore them, on any device. If you stop before submitting we send at most one email with that link, ever, and our team can see the saved progress so they can help you finish by phone if you ask. If you decide not to claim, ignore the email and nothing further happens, or write to us and we delete the saved progress. An unfinished draft is kept until you finish it or ask us to delete it, so you or our team can pick it up again later. When it becomes a submitted claim, the separate resume snapshot is deleted after seven days because the claim record has taken its place. Files selected before submission are held privately with the draft so the resume link can restore them, for as long as the draft is kept; a file you remove from the form, or one left when a draft is deleted, is removed by the daily cleanup.
5. Your signature
When you sign the Authorization Agreement we keep the evidence that makes the signature worth something: the signature image you drew or typed, the exact text and version of the document you saw, the date and time, and the internet address and browser it was signed from. The same record goes into the signed PDF that is emailed to you. It exists to prove what was agreed and by whom, is stored with the claim file, and is shared only where the claim requires it, for example with an airline or court that asks for proof of authority.
6. Who sees it
The airline and other parties a claim genuinely requires (regulators, ADR bodies, courts); partner law firms when you approve legal escalation, including firms in Poland and Romania; and the service providers that run our infrastructure: website hosting (Vercel), database and document storage (Supabase), email delivery (Resend), and, where the anti-bot check is enabled on the signing step, Cloudflare Turnstile, which evaluates the request without advertising cookies. If you choose to reach us on WhatsApp using the button on this site, or opt in to claim updates over WhatsApp, those conversations run through WhatsApp and are subject to its own privacy terms as well as this one; email and the phone number below are always available instead, and the WhatsApp opt-in can be withdrawn at any time. The same goes for the optional passenger-rights news you can choose at signing: opt out any time and it stops. Three more services see a narrow slice: when you type your mailing address, the address you are typing (and nothing else about you: the request goes through our server, so the provider does not see your internet address) is sent to Google Places or, where that is not configured, to Photon, which is built on OpenStreetMap data, so that the address can be completed for you; when we check a flight's schedule, the flight number and date, which identify a flight and not a person, go to AeroDataBox; and where it is enabled, AI models from Anthropic read documents and correspondence for us: a boarding pass you photograph on the claim form is read so its details can be filled in for you to check (by Anthropic or, as an alternative, OpenAI), and on a submitted claim the documents you upload, the messages on the case and the case's details are read to sort the file, summarize it, translate it and draft our letters. The models see what a case worker would see, and their output is a suggestion to our team: nothing is sent to you, an airline or anyone else, and no decision about money is made, without a person on our team approving it. Providers process data for us under their own security and data-protection commitments, and some are located in the United States or the European Union, so your information may be transferred across borders with appropriate safeguards.
7. How long we keep it
For as long as your claim is active, and afterwards for as long as legal, accounting and dispute-resolution obligations require. When information is no longer needed, it is deleted. The record of what the AI models did on a claim (section 6), which is what they were shown and what they answered, is kept in full for one year so that our team can check their work, and after that only a summary of each run is kept: when it ran, what it was for and how it went, without the documents, messages or answers. The boarding pass read on the claim form is the exception: neither the picture nor what was read from it is stored; the record says only that a read happened and whether it worked.
8. Your rights
You can ask what we hold about you, ask for corrections, ask for deletion where the law allows, and withdraw a claim (see the Terms of Service). If you are in the European Union or the United Kingdom, you have the rights the GDPR and UK GDPR give you, including access, rectification, erasure, restriction, portability and objection, and the right to complain to your data-protection authority. US state privacy laws may give you similar rights depending on where you live. To exercise any of them, email delayedgetpaid@gmail.com.
9. Cookies, storage and sign-in
The public website sets no advertising or analytics cookies, and the cookie banner's choices work as described on the cookies page. The claim form keeps your in-progress answers in your browser's local storage for about a day so a refresh does not wipe them. Signing in to your account works by a six-digit code emailed to you; the account and the staff area each use one strictly necessary session cookie. If analytics are ever added, they will run only for visitors who accepted them on the banner, and this policy will change first.
10. Security
The site is served over HTTPS, documents are stored in access-controlled storage, and claim data is accessible only to authorized staff and a lawyer assigned to the claim when legal escalation requires one. No system is perfectly secure, but we collect little, guard it, and never hold payment details we do not need.
11. Other people on your booking
When you submit a claim for more than one passenger you confirm that each of the other adults has authorized you to do so, and their information is handled under this policy exactly as yours is: same purposes, same recipients, same retention, same rights. Any of them can contact us directly at delayedgetpaid@gmail.com to ask what we hold or to object. This service is for adults; claims for children traveling on a booking are submitted by a parent or guardian, and we collect the child's details only as the claim requires.
12. Changes
When this policy changes, the version and date on this page change with it. Meaningful changes will be flagged on the site.