Identities don't survive it. The workflow does.

Three layers of protection

This is not a blanket redaction. A generic scrub would black out the very connections that make a company's record worth anything. Identities do not survive it; the workflow does.

Why the agreement comes before the upload

It is the question owners ask most, and a fair one. Sensitive material cannot be removed from data nobody holds, and nobody should hold your data without a signed agreement that says exactly what may be done with it. So the order is fixed:

1. Agreement. The data license agreement lists the systems and date ranges in scope. Before it is signed, nothing leaves your systems.
2. Secure upload. Your team exports copies from your own systems and uploads them through the data partner's secure upload. No passwords are shared with anyone.
3. Integrity check. Within up to 45 days the data partner confirms what arrived matches your intake: the right systems and date ranges, nothing missing and nothing extra.
4. Sensitivity removal, with your sign-off. Sensitive material is removed and personal information is transformed. Ask to review a de-identified sample before anything is shared.

What is learned, and what is not

AI developers want the shape of the work: how a request becomes a decision, a job and a finished outcome. Not your customers.

What the model learns

• How a request becomes a decision, a job and a finished outcome.
• Where experienced people make judgment calls, and what they weigh.
• How exceptions get handled and mistakes get corrected.
• How information moves between systems never built to talk to each other.

What it does not learn

• Who any particular person is. Identifiers are transformed before anything is shared.
• Your customer list, as a list to sell or market to.
• Anything retrievable as a record. It is not a search index of your business.
• Your competitive position. Nothing in the result traces back to you.

Your business is one voice in a very large chorus. Models are trained across thousands of companies; they learn what this kind of work looks like in aggregate.

Regulated and sensitive data

• Account and card numbers are never part of the deal.
• Privileged and private conversations are removed.
• Patient health information is handled by a certified healthcare data partner under a BAA. HIPAA questions are answered by the data partner's team.
• Specific sensitive items, such as certain clients' files, can be excluded. Leaving out whole systems lowers the offer.

Retention and deletion

The data is encrypted in transit and at rest and handled by the fewest people needed to do the work. The raw upload is deleted within 120 days; only the de-identified copy is kept under the agreement.

What AI customers must sign

• A contractual bar on trying to identify any person in the data.
• Confidentiality terms covering the de-identified copy.
• Use limited to AI training and research.

Nothing is published or sold as a report about your company.

Employees and customers

Be upfront. We provide a plain-language notice you can share with your team that explains what is copied and what is removed. Rights and notices for your jurisdiction are reviewed with the data partner's team. Questions about data rights are answered there, not by us.

What PayStreak Labs holds

The details from your application: contact information, headcount, years of records, the systems you named and your estimate. Never company records, files, logins or credentials. See our privacy policy.