TalengineerTrust Center
Trust is infrastructure, not a slogan.
Every claim on this page maps to something the platform actually does — escrow that holds your money until you approve, a dispute process with a fixed evidence window, verified identities, and an evidence trail for on-site delivery. Here is exactly how each works.
How your money is held
Funds are held securely and released only when you approve each deliverable — a milestone is marked funded only after the payment actually clears, and it releases only on your approval.
You fund a milestone through Stripe Checkout. It is marked funded only after Stripe confirms the payment — nothing is ever “held” on trust.
The engineer works the milestone. On-site check-ins and completion photos are logged against it as it progresses.
You review the deliverable. Funds move only when you approve — the platform never auto-releases on a timer.
On approval, escrow releases to the engineer minus the platform fee, with a duplicate-transfer guard so a release can never fire twice.
What happens if something goes wrong
If you are not satisfied, opening a dispute freezes the milestone before any money moves. Both sides submit evidence within a fixed window, an admin reviews it, and the outcome determines where the escrowed funds go — including a full refund to your original card.
Either party to the project can open a dispute on a funded milestone. Doing so immediately freezes it to “disputed” — no funds can move.
Both sides have a 5-day window to submit evidence. Each party’s side is recorded server-side from their role — it cannot be spoofed.
A platform admin reviews the milestone spec and both evidence submissions before any funds move.
The admin rules for the engineer, for the employer, or a split. Rule for the employer and the full escrowed amount is refunded to the original card; a split refunds the balance not awarded.
Only one open dispute can exist per milestone, and a resolution is protected by an atomic guard so it can never double-pay or double-refund.
Who you are actually working with
Payment protection only matters if the people on the other side are real and accountable. Identity, tax, and insurance documents are verified before they count — and sensitive files never sit behind a public URL.
Employers submit company details for verification. Status moves from pending to verified after our team reviews the submission — typically within 24 hours.
Tax forms are stored in a private bucket that denies all public access. Even an admin can only view a file through a signed link that expires after 5 minutes.
Certificates of insurance and platform credentials are uploaded with issue and expiry dates, then verified or rejected by an admin — self-reported claims do not count on their own.
Proof the work actually happened
For on-site commissioning, the platform builds an evidence trail so a remote employer can trust a job done a continent away — location and delivery photos are captured against the milestone itself.
At check-in, the platform computes the distance from the job site on the server (clients cannot fake it) and records it against the milestone. Check-ins outside the geofence still succeed but are flagged for the employer to see.
A valid platform certification is required before an engineer can check in on-site — a second gate on top of assignment, so a revoked badge stops work at the door.
On completion, the engineer submits photos and notes that attach to the milestone, giving the employer a visual record to approve against before any funds release.
Talengineer is in its founding phase. We do not publish “companies served” counts we cannot yet stand behind — the protections above are what an early customer relies on, and they are live in the product today.
Protection you can see, on your first order
Post a project for free. Fund one milestone into escrow and watch every safeguard on this page work before you approve.
Post a Project — Free