HalyardCo
Where IV data goes

The Data's Journey

Each set of data we pulled, and the exact path it took — where it came from, who touched it, and where it lives now.

First, what is Cloudflare? It's a highly secure cloud platform that hosts our database — used by 42% of Fortune 500 companies and a recognized industry leader in online security. Every journey below ends in our Cloudflare, where IV data is kept separate from every other client's.
And what does "never learns from it" mean? HalyardCo opts out of having any data used in the training of any current or future LLM that Anthropic develops.
And who can reach the data? One agent has access to the database — it can be switched off at any time and is reviewed regularly by a software engineer. (The technical detail lives in our full data-practices document.)

1 · The Workday data

staff records

Staff and their assignments.

1

Starts in Workday

Staff names, roles, reporting lines, work phone, employee ID, and cost center.

2

We run a report

A person runs a report in Workday for just the information we need, and downloads it to a local computer.

3

An agent loads it in

That person hands the file to an AI agent, which reads it and loads it into our Cloudflare database.

4

It lives in Cloudflare

Now it sits in our secure Cloudflare — walled off from every other client's data.

5

Used to match records

Lines up the right staff with the right part of the work. Viewable only inside the GAPS 2.0 CRM.

🔒 password-protected

2 · The Salesforce data for thank-you cards

real donor names

The one and only pull that contains real donor names.

1

Starts in Salesforce

A list of the specific donors we're thanking right now — their real names and mailing addresses (not our whole donor list). The only place personal donor names appear.

2

A person pulls the report

A staff member runs the report in Salesforce for those donors and emails it in.

3

We hand it to an agent

We download the emailed file and hand it to an AI agent, which loads it into our Cloudflare database.

4

It lives in Cloudflare

Into our secure Cloudflare. Every time someone opens it, it's recorded — so we always know who looked and when.

🔒 password-protected + two-factor sign-in
5
then

Names are scrubbed

Our process then scrubs the names and addresses — leaving only a donor ID (a code with no name).

More secure than the old way: the alternative is thank-you-card writers working off a spreadsheet of donor names on their own phones and laptops. This keeps the names in one locked, logged place instead.

3 · The Salesforce data for shared-account income

account totals

How much came in, and for which accounts.

1

Starts in Salesforce

Income totals for each account — every account (a "GAU") has a name, and we keep the total that came in for it.

2

A person pulls the report

A staff member runs the income report; it's downloaded and handed to an AI agent that loads it into our Cloudflare database.

3

It lives in Cloudflare

Into our secure Cloudflare — walled off from every other client's data.

4

Used for reporting

Shows how much came in and for which accounts.

🔒 password-protected
More secure than the old way: the alternative is pulling this data onto our own computers into an Excel file to build slides or charts. This keeps it inside one secure, controlled place instead.

HalyardCo — a service of OBB Holdings LLC

A plain-language picture of how the data is handled today — drawn from our written data-practices.