Trust & privacy
Instrumenting work inside a mission organization is a governance question.
So we answer it on a page you can send to your board, rather than in a contract appendix nobody reads. Everything here is a commitment we will put in the agreement.
Six commitments
Everyone instrumented is told first, in writing
Before any endpoint agent is deployed, every person it will run on receives written notice describing what is captured and why. This is not negotiable, and we will not waive it at a client's request.
Raw screen images are never stored or transmitted
Computer vision runs at the endpoint and sends structured metadata only. This is an architectural property of the platform, not a configuration setting somebody could change later.
We do not instrument the people you serve
Congregants, members, students, clients, and beneficiaries are never under instrumentation. The signal layer covers the staff and teammates delivering the services we are contracted for, and nobody else.
Your data is never used to train models
Not ours, not a third party's. It is not pooled across clients and it is not sold, shared, or licensed to anyone for any purpose.
You can see everything we can see
There is no vendor-only view. Any signal, report, or process map we use to make a claim about your operation is available to you in full.
Exit does not require our cooperation
Thirty days' notice, no penalty. Data, documentation, credentials, and system access are handed back in full. We keep no hostage.
What this is not
The clearest way to describe a monitoring capability is to say what it will not be used for.
- It is not surveillance of your congregation, members, or clients. The signal layer instruments the staff and teammates delivering the services we are contracted for — nobody else.
- It is not keystroke logging or screenshot archiving. Computer vision runs at the endpoint and sends structured metadata; raw screen images are neither stored nor transmitted.
- It is not deployed without disclosure. Every person under instrumentation is told, in writing, before it starts. For a mission organization that is not a legal nicety, it is the whole ballgame.
- It is not a performance-policing tool we will help you point at your own employees. If that is what you want, we are the wrong firm.
Everything else people ask
Who is behind SignalImpact?
SignalImpact is a dba of Dataken Inc. Dataken has run its OLi AI platform in production for over five years, capturing roughly a million work signals a day across commercial deployments. SignalImpact packages that platform, plus the operational stack and the people to run it, for mission organizations.
What is the AI actually for?
Two things. It tells you where the hours in your operation really go — which processes are slow, which steps are rework, which software nobody opens. And it produces evidence that the work we are contracted to do is being done, which is the question every board asks about an administrative vendor and the one almost nobody can answer with data.
Why can we not just buy AI enablement ourselves?
You can buy it. The problem is the second half. Enterprise AI tooling is priced for organizations with IT budgets and sold to organizations with staff to configure it, read it, and act on what it finds. A congregation with two administrators has none of those. We operate it for you rather than licensing it to you, which is what makes it viable at this scale.
Do we have to leave the software we already use?
No. We sell a full operational platform and we would rather you were on it, but plenty of engagements start with us working inside OmegaFi, ShulCloud, Blackbaud, or whatever you already own. If a migration is not worth doing, we will say so.
Do you do fundraising?
No. No donor development, no grant writing, no capital campaigns, no list rental. Those are relationship jobs that belong to your team. Our contribution is giving your people back the hours currently going to reconciliation and password resets.
Where are the back-office teammates based?
Offshore, delivered with an established BPO partner. We state that directly rather than calling them a global team and letting you discover it later. They are employed with benefits rather than contracted piecework, dedicated to your organization rather than shared across a pool, and you interview and select the person yourself.
How do we explain offshore support to our board or our donors?
The honest case is capacity. An organization that can fund half an administrative role locally can fund a full dedicated one this way, which usually means program staff stop doing data entry at night. You are told exactly who is doing your work, and the signal reporting means you can show the board what was delivered. If offshore support is still not right for your organization, say so — the other services stand on their own and we will scope without it.
Is this monitoring software you are installing on our people?
It instruments the delivery team working your engagement, and every person under instrumentation is notified in writing before it starts. It is not deployed on your congregation, members, students, or clients. We will not help you point it at your own employees as a performance-policing tool — if that is the requirement, we are the wrong firm.
Are screenshots stored?
No. Computer vision runs at the endpoint and transmits structured metadata. Raw screen images are neither stored nor transmitted — an architectural choice Dataken made deliberately, and also the reason the approach scales.
Are you a 501(c)(3)?
No. SignalImpact is a commercial dba of Dataken Inc. serving nonprofit and member organizations. We are a vendor to the sector, not part of it, and we would rather say so plainly than blur the line.
How do we get out?
Thirty days' notice, for convenience, no penalty. Your data, documentation, and system access are yours throughout and handed back in full on exit — including an export of everything in the operations platform. A firm that needs a long lock-in has told you something about its confidence.
If your question is not here, ask it directly at [email protected]. If the honest answer is one we would rather not publish, that is a reason to publish it.