Every scope, timesheet, screen capture, approval, and payout is logged and reviewable. Card and bank details never touch our servers. Below is exactly what we do, what we don't, and how we handle the edge cases.
No surprises about what lives on our servers. Sensitive payment and identity material stays with the regulated providers that own it.
Built so contractors can sign on without giving up the rest of their machine, and so clients can verify work without a privacy panic from the operator's side.
Screen activity captures are evidence for the weekly timesheet review, not surveillance. They are visible to the named client approver during the review window and to Anastasis support if a dispute is opened, then archived per the retention policy above.
The weekly cycle is the same for every client and every operator. Approval cutoff Monday. Charge Tuesday. Payout target Friday for funded, approved hours.
Auto-built timesheet from tracked work plus any explained adjustments. Status moves DRAFT → PENDING.
Named approver reviews each row, evidence, and notes. Anything not declined or disputed by the deadline auto-approves.
Our payments provider runs the weekly charge against the client's card on file. Anastasis sees the result, never the card number itself.
Approved net (gross minus the 15% platform fee) is sent to the contractor's connected payout account. The payout provider owns downstream bank withdrawal, cards, and FX.
Every scope, timesheet, approval, and report is audit-logged. If a dispute opens, it's adjudicated against the record. Most resolve in under 48 hours.
If a client declines a row or asks for adjustment, the contractor sees the reason and can revise. Anastasis support is included in any thread the client or contractor escalates. Funds in transit hold until resolution.
If an operator isn't a fit — ever, not just in the first 30 days — we rematch at no cost. No capped window, no placement fee, no "credit" games. The previous engagement closes cleanly with the documented record intact.
No "admin sees everything" buckets. Each role on the platform sees only what its job requires.
The candidates applying to your roles, their packets, your own engagements, your timesheets and approvals queue, your billing status. No view into other clients' data, no view into a contractor's other engagements.
Your own profile, applications, engagements, timesheets, evidence, payouts, and notifications. No view into other contractors' applications or rates, no view into a client's other operators.
The minimum needed to run vetting, dispute adjudication, and payout reconciliation. Every admin action is audit-logged and surfaced in the affected user's activity history.
If a security, data-handling, or process question matters to your decision and isn't covered above, send it over — we'll either answer in the next call or document it on this page.