For RL environment companies
Ship real worlds without shipping real identities
You have the design partner. The workflow data is exactly what the lab wants. The PII inside it is why the delivery is stuck.
GraphReplica is a managed service: we handle the de-identification and hand you a replica you can ship. Setup takes about an hour. First safe dataset in under a week.
One customer, three files, one grader
The identity changed. The task did not.
The same customer is "Ortiz, Nancy" in the CRM, "Nancy Ortiz" in a ticket, and "Mrs. Ortiz" in a call note. Toggle the world. Watch what the agent, and the grader, can still do.
Every form of one real customer maps to one synthetic person. Mrs. Ortiz becomes Mrs. Delgado.
crm_accounts.csv
tickets/tkt_88213.eml
Hi, this is at . Please update our renewal quote to 240 seats. Thanks,
notes/call_log.txt
10:42 · Left a voicemail for about the 240-seat renewal on acct_2189.
3 name forms · 1 person · 1 stand-in. "Ortiz, Nancy", "Nancy Ortiz", and "Mrs. Ortiz" were resolved to one entity before anything was replaced.
Episode · task_047_renewal
Tap any highlighted identity to trace it across the files.
acct_2189 and the 240 seats never change. One account stays one person.
Why deliveries stall
Per-file masking keeps the secret and breaks the world
The standard fix for PII is the reason the environment stops working.
The world breaks
Each file gets masked on its own, so one real customer becomes three unrelated strangers. Joins stop resolving and graders fail on the redaction. Your team debugs the environment while the defect sits upstream in the de-identification.
The variant leaks
Per-file matchers miss name variants. Mrs. Ortiz slips through as real PII, straight into your lab deliverable. The export is broken and leaking at the same time.
The identity is not the workflow. Change the identity. Keep the workflow.
What you get
From stalled delivery to shipped environment
The realism labs pay for is locked inside your partner's walls. GraphReplica gets the world out without the PII.
A world that grades and ships
One account keeps one stand-in across the CRM, the tickets, and the trace. Lookups resolve and graders score the agent, so the lab sees model behavior instead of redaction noise.
Both reviews pass
Your partner needs every identity handled before anything ships. Your lab needs no raw PII in the deliverable. GraphReplica hands off a validated replica with the audit report to prove both.
A pipeline, not a project
The first delivery sets up the pipeline. When the lab asks for harder tasks or the partner's workflow changes, the next release runs through it instead of a new negotiation.
We run GraphReplica on a sample of design-partner data. You get back a world that joins, grades, and ships.
Where GraphReplica sits
The privacy layer between your design partner and your environment
Real workflow data moves through a chain. GraphReplica owns exactly one link in it. You own the rest.
Owned by the partner
Design partner systems
CRM, tickets, email, documents, traces. The real work, full of raw identities.
Managed by Secludy
GraphReplica
Resolves entities, replaces each with one stand-in, validates the result. The only stage Secludy owns.
The handoff
Safe replica
Identities replaced, relationships intact. This is what reaches your pipeline. Raw PII does not.
Owned by you
Your environment pipeline
Tasks, graders, rewards, evals, benchmarks. Yours. GraphReplica touches none of it.
Your customer
Frontier lab
Receives the environment you built. Your deliverable, your relationship.
GraphReplica does not generate the workflow. It de-identifies the one that actually happened.
Under the hood
One entity, one stand-in, every artifact
The same real entity gets the same stand-in everywhere. Realism carries over. Identities do not.
One entity, one stand-in, every artifact
GraphReplica resolves which rows, tickets, and threads belong to the same account before it replaces anything. IDs never move.
Realistic stand-ins, not masking
Stand-ins keep the same industry, format-valid emails and IDs, and dates shifted within bounds, across CSV, JSONL, Parquet, EML, PDF, and images.
Proof with every run
Every run ships a leak check, a consistency check, and an audit report you can hand to your partner and your lab.
Delivered as a managed service
Secludy runs the whole de-identification: detection, replacement, validation, audit. Your team never builds a redaction pipeline and never touches raw PII. You get the replica and the report.
For your partner
Evidence that every identity was replaced before anything shipped.
For your lab
Evidence that no raw PII entered their pipeline.
For your team
A failed rollout means the agent failed, not the redaction.
What happens next
From first call to first dataset
No committee, no months-long evaluation. You judge the replica on your own data.
A short call
Bring one workflow and the thing blocking it. We scope the sample together.
A sample run
We run GraphReplica on a sample of the partner's workflow data, end to end. Setup takes about an hour. Your team never touches raw PII.
Compare and ship
You check the replica against the source: joins, lookups, graders. If it holds, it ships. First safe dataset in under a week.
Ship the world, not the PII
Bring one workflow and the thing blocking it. We run GraphReplica on a sample, and you judge the replica yourself.