Claimed

Privacy

What Claimed collects, why, and how to make it stop. Last updated 29 October 2026.

The short version

Claimed sends a photograph of a receipt to our server, reads it, and sends back what it says. That photograph and what we read from it are stored so the app can build your claim later. Nothing else about you is collected, and nothing is sold, shared or used for advertising.

What we hold

What we do not hold

Who else sees a receipt

To read a receipt we send the photograph to Anthropic's Claude models through the Vercel AI Gateway. They process it to answer that one question and do not use it to train models. Our server and database run on Vercel and Neon, in Europe.

To suggest who a receipt is for, we send its shop name, town, date and total, the names of the people and companies you claim from, and the shop names, towns and dates of up to three receipts each of them paid for before, to OpenAI's models through the Vercel AI Gateway. They process it to answer that one question and do not use it to train models. Never the photograph or your bank details.

We send email, such as sign-in codes and company invites, through Resend. They see the address it goes to and what the email says, and nothing else.

When something goes wrong in the app or on our server, we send the error, the app version and the phone's model and system version to Sentry, in Germany. How long our server takes to do each step goes to Grafana Cloud, in Sweden. Neither gets a receipt, your name or your email address.

When you ask Ask Claimed something, we send your question, and the records it looks up to answer it, to Anthropic's Claude models through the Vercel AI Gateway. For your own receipts and claims that means their shop names, amounts, dates, descriptions and who you claim from. In a company, it means the claims you can already see, with the claimant's name, the receipt details and the company's spend policy. We never send the photograph, your bank details, or anything you couldn't see yourself, and the models do not use it to train. We don't keep the conversation. When Ask Claimed suggests a change, nothing happens until you confirm it. We keep the suggestion until it expires ten minutes later, or for 30 days after you confirm it, so you can see and undo it. In a company, a confirmed change is kept with the company's records, the same as one you make yourself.

Some small judgments go to TypeSafe's Jev model. When a receipt is for a company whose spend policy has rules written in plain words, we send its shop name and your description, so Jev can say whether a rule applies: as you write the description, and again when you send the claim. To suggest who a receipt is for, we send its shop name with the names of the people and companies you claim from, which may include your own business's name, and the shop names of receipts they paid for before. While someone writes a company's spend policy, we send the policy's sentences, and nothing else, so Jev can point out ones that could be read more than one way. To suggest what a company may ask for, we send your description with the policy's own sentences about it, and nothing else. To tell an approver whether a reply answers their question, the question and the reply, as written, are sent, and nothing else. To group claims that look routine for approvers, a claim's shop names and descriptions and the same person's shop names from the last 90 days are sent. To spot the same receipt twice, we may send two of your receipts' shop names and the places they were bought, or their two descriptions, and nothing else. To suggest an account for each line of an export, the policy's account sentences, and each receipt's shop name, description and the policy sentence that covered the receipt, are sent. To answer simple questions in Ask Claimed faster, the first question you type, as you wrote it, is sent to decide which answer it needs. Apart from what you type there, never the photograph, the receipt's amount, the date or your bank details. TypeSafe is based in the United States. It does not use what we send to train models, processes it under a data processing agreement with the EU's standard contractual clauses, and keeps it only as long as that purpose needs.

When you send a claim, the finished PDF goes wherever you send it, using your own mail app. We are not in the middle of that and we do not see who you sent it to.

If you connect Gmail

Connecting Gmail is optional. If you connect it, Claimed asks Google for permission to read your email (the gmail.readonly permission). We use it only to find receipts, invoices, bookings and refunds and add them to Claimed.

What we look at. Claimed searches your mail from the last 90 days for two kinds of message: ones Gmail itself files under Purchases, and ones with a PDF attached. It then reads only the messages those searches return: their sender, date, subject, text and PDF or image attachments. We never load images or links inside an email.

What we keep. We show you what we found and you choose what to file. For each receipt you file we keep the attachment, or a page made from the email's text, with who sent it, when and its subject. Receipts you do not file are deleted after 30 days, and we keep only a scrambled reference so we do not show them to you again. Emails that are not receipts are not kept. We never send, change or delete your email.

Who else sees it. Receipts found in Gmail are read the same way as a photo, by Anthropic's Claude models through the Vercel AI Gateway, which do not use them to train models. TypeSafe helps decide which emails Claimed's searches found are receipts. For each one we send TypeSafe the sender's domain, the subject line and the first line or two of the email, and nothing else: no address, no attachment, nothing about you. To suggest which receipts belong to one trip, we may send TypeSafe two receipts' shop names and places, and nothing else. We do not sell Gmail data, use it for advertising, or use it to train or improve AI models for anyone else. No person at Claimed reads your email. The only exceptions are if you ask us to look at a specific receipt and agree to it, if it is needed to investigate abuse or keep the service secure, or if the law requires it.

Stopping. Disconnect Gmail in Settings at any time. We remove our access at Google and delete everything we found that you did not file. You can also remove Claimed at myaccount.google.com/permissions.

Claimed's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Corrections, and why we keep them

Every time the app asks you to check something and you answer, we record what we read, what you said, and how confident we had been. We keep the times we were right as well as the times we were wrong, because you cannot tell whether a confidence score means anything from mistakes alone.

This is the only thing in Claimed that exists to improve the product rather than to serve you directly, which is why it is described here rather than buried. It is tied to your account and is deleted with it.

How long

Receipts and their readings are kept until you delete them or delete your account. We do not expire them on a timer, because a claim you have not sent yet is a claim you still need.

Deleting everything

Settings, then Delete account. It removes your account, your receipts, their readings and your corrections from our servers, and it takes effect immediately. Receipts already on your phone stay on your phone until you delete the app.

If Gmail is connected, deleting your account also removes our access at Google and deletes everything we found there.

You do not have to email anyone and there is nothing to ask us for.

Where to reach us

hello@claimed.zip.

Children

Claimed is a tool for claiming work expenses and is not directed at children.

Changes

If this changes in a way that affects what we collect, the app will say so before it takes effect rather than only changing the date at the top.