Handshake AI’s license page names several familiar systems as examples of sources it buys. Describe your records in those systems, the retained period and links between them.
What is named on the license page
The source examples include Gmail, Google Drive, Outlook, Slack, QuickBooks and ServiceTitan. The page states a company minimum of 20 or more full-time employees and three or more years in operation. These are source examples and company criteria, not a universal export specification.
Sources: Handshake
Turn the source list into a workflow description
Suppose a fictional service company uses a field-service platform, email and accounting software. A source list says those tools are present. A collection description explains that job J-204 has a customer request, a scheduled visit, a completion note and an invoice referring to the job. The latter is a much clearer object to discuss.
Keep each connection honest. If the invoice uses a separate job number entered manually, record that. If emails contain only the customer name, they may need a narrower date and subject check. Do not silently convert a likely relationship into a verified one.
| Inventory question | Good answer shape |
|---|---|
| What work? | Completed maintenance jobs |
| Which records? | Job rows, visit notes, invoices and selected email threads |
| What period? | Observed dates for each group |
| What links? | Job reference present on notes and invoices; email link unverified |
| What remains open? | Photo attachment availability and earlier job history |
Separate business age from record age
A company may have operated for ten years but changed its job system two years ago. Its accounting archive could run longer than its field-service notes. List those spans separately. If you have only checked a current screen, say observed in current account rather than claiming a downloadable ten-year archive.
The shortest span does not erase older records. It simply changes the description: a recent connected service collection, plus an older accounting collection whose links may differ. This framing avoids both overstating a complete history and discarding the older material.
Ask about the collection, rather than the logo
A targeted question can name the source example and then describe the proposed scope. For instance: we use a named field-service system and have job notes plus invoices sharing job references for a verified period; should those groups be scoped together? The answer should come from the provider’s review, not from the presence of a logo on this site.
- Confirm which account and operating entity hold each group.
- Record actual earliest and latest dates separately.
- Name the linking reference and where you observed it.
- Distinguish attachments from links pointing to attachments.
- Leave uninspected exports and formats as questions.
Use the inventory in the first conversation
Carry the same collection description into the inquiry so the company facts and record facts stay consistent. Your inventory can be useful before a detailed sample exists: it identifies the work, the available evidence and the next check needed to define the scope.
Questions about this comparison
Does three years in operation mean three years of retained exports?
No. Operation age is a company fact. Available record history must be checked separately.
What if our system is not listed?
Describe the collection and ask which parts are relevant.
Sources
- Data Partnerships | Handshake AI (license / interest form page)Handshake · Checked 2026-10-10