Companies / Claimory / Subprocessors
Claimory provides body shop management software for collision repair shops that handle insurance claims. It serves collision repair shops and their customers.
Summarized from its homepage on 8 Nov 2026.
Subprocessors of Claimory
Claimory declares 21 subprocessors, including AI providers Anthropic, OpenRouter.
From the company's own list.Read the source
| Subprocessor | Purpose |
|---|---|
| Cloud data centers in the United States where Supabase hosts our database and file storage. | |
| Artificial intelligence provider (Claude model family) that runs the Claimory AI assistant chat, Claim Audit, document and photo reading, and email inbox drafts, replies and summaries. Receives claim and contextual data during AI feature usage (see Section 5). Operates under zero-training terms for API customers. | |
| Bot and abuse detection on public forms (trial signup, contact, demo request) using Cloudflare Turnstile. Cloudflare receives minimal browser and network metadata needed to score automated traffic. | |
| Powers the optional email integration, and only when a shop chooses to connect its own Gmail or Google Workspace mailbox, with an app password from its Google Account, to send and receive claim email inside Claimory. Google receives the messages, attachments, and mailbox details for the account the shop connects, plus the app password, which Claimory sends to Google only to sign in to that mailbox, used only to send and sync that shop's claim email. For a mailbox connected before app passwords, through Google's older sign-in connection, Claimory also sends Google that connection's sign-in tokens until the shop reconnects it with an app password. | |
| Measures whether Claimory's own ads led to a signup, including Enhanced Conversions. Google receives ad-click and conversion identifiers, and for Enhanced Conversions a scrambled version of your email that cannot be read back, used only to match a signup to an ad. Loaded only after you accept marketing cookies (see Section 9). | |
| Artificial intelligence provider (Gemini models) that runs activity note polishing, the AI Manager console, AI help with app errors, and the embeddings behind knowledge search. Receives only the data scoped to the active request. | |
| Powers the optional email integration, and only when a shop chooses to connect its own Gmail or Google Workspace mailbox, with an app password from its Google Account, to send and receive claim email inside Claimory. Google receives the messages, attachments, and mailbox details for the account the shop connects, plus the app password, which Claimory sends to Google only to sign in to that mailbox, used only to send and sync that shop's claim email. For a mailbox connected before app passwords, through Google's older sign-in connection, Claimory also sends Google that connection's sign-in tokens until the shop reconnects it with an app password. | |
| Checks whether a password a person is choosing appears in a known data breach, so we can warn them before they use it. It receives only the first 5 characters of a one-way hash of the password, plus the IP address and browser details any web request carries, never the password itself. | |
| Would power an optional Microsoft 365 and Outlook email integration, but that connection is not offered today: no shop can connect an Outlook or Microsoft 365 mailbox, and none is connected, so Microsoft receives no Claimory data. | |
| NHTSA (U.S. Department of Transportation) | Vehicle identification number (VIN) decoding through the public NHTSA vPIC database to auto-fill a vehicle's year, make, and model, and a lookup of NHTSA safety recalls by year, make, and model for the vehicle on a claim. NHTSA receives only the VIN submitted for decoding, or the year, make, and model sent for a recall lookup, plus the IP address and browser details any web request carries; no personal contact details are sent. |
11 more subprocessors
See the full list with purpose, location and first seen date.
Create a free accountWork email, no card. Already have one? Log inQuestions about Claimory
Vendor's own statement, retrieved from the source URL on the date shown. StrataDB does not verify the underlying claim. Data sources.
See Claimory's full stack
Every vendor with its source and date, and an alert when Claimory adds or drops one. The same lookup works for any company.
- Every company and vendor, with its public source
- 100 API calls a month, plus MCP and the Chrome extension
- Work email only. No card, no sales call