Trust
AI help, without handing over the controls.
Four things you can check before you sign up: where your data lives, who decides, how time is recorded and how your people are treated.
Your database and files in the EU
Your database runs in Paris. Your files stay in Cloudflare's EU jurisdiction, private by default.
Where it lives
- Database
- Postgres in Paris (eu-west-3)
- Files
- Cloudflare R2, EU jurisdiction
- Sharing
- Private, short-lived signed links only
Details: Your database and files in the EU
- Every file link handed to an AI agent is written to the audit trail.
- Photos are of objects and places, not people: AI Assist asks for a retake when it sees a face.
- AI Assist, once you switch it on, sends the step it checks to Anthropic's API. Anthropic is listed with every other subprocessor in the privacy policy.
You approve everything
The AI proposes. A person approves every phase, and anyone can stop for safety.
Who decides
- Every phase
- A person approves it before anyone gets a step
- Every AI suggestion
- Confirmed by the person holding the object
- Spending limits and access
- Enforced by TaskQ itself, not by the AI
Details: You approve everything
- Each phase waits in your approvals inbox with its steps, dependencies and a preview of every step screen filled with real data. Reject it with a comment and Claude reads it.
- Purchases above your limit wait for approval. TaskQ records requests and invoices; it never moves money.
- Stop for safety alerts the orchestrator at once, and that step is never reassigned automatically.
- AI Assist stays off until you switch it on, with a monthly cap you set. If it pauses, the work carries on.
- Want more speed? Auto-approval by risk level is optional, on Premium, and off until you turn it on.
Built for Portuguese labour law
Employees, contractors and volunteers each get their own kind of time record. Clocking records the site the person chooses, never GPS.
Time records by regime
- Employees
- Clock-in, clock-out and breaks, kept five years
- Contractors
- Time per step; they always set their own schedule
- Volunteers
- Attendance per session, for certificates and reports
Details: Built for Portuguese labour law
- Employee records follow article 202 of the Portuguese Labour Code: start and end times, breaks, daily and weekly totals, kept five years and ready to consult at any time. Work outside the premises is signed off by the worker within 15 days.
- Contractors never clock in, and their schedule always stays with them: under article 12, start and end times set by the client point to an employment contract.
- Every record exports to CSV by regime. Employee time records are kept five years on any plan.
Fair to your people
No scores, rankings or comparisons. Every assignment says why.
How steps are assigned
- Uses
- Availability, site access, free tools and qualifications
- Never uses
- Scores, individual times or detail level
- Every step
- Carries its reason, in plain words
Details: Fair to your people
- Assignment is done by plain, deterministic code, not by AI.
- A typical reason: “Has access to Workshop, caliper free, free until 18:00.”
- Durations are learned per type of task, never per person.
- Each person chooses how much detail they want. It never affects who gets what.
- Your agent never sees time records, detail preferences or individual durations.
- The week's workload is shown for planning and never compared between people.
Data location
Know where your data lives
What sits where, and what travels when you switch AI Assist on.
- Database in Paris
- Postgres in the EU (eu-west-3), with row-level security keeping each workspace apart.
- Files in the EU jurisdiction
- Private by default and opened only through short-lived signed links.
- Your Claude, your account
- Claude connects through OAuth to the one workspace you choose. Your Claude plan is separate and billed by Anthropic.
- AI Assist, on your terms
- Off until an admin switches it on. Each call to Anthropic's API carries only the step being checked, its place and its evidence, with no name beyond the operator's first name.
You stay in charge
Nothing reaches your team until you approve it
The approvals inbox is the console's home screen. Approve a phase and each step goes out with the reason it went to that person.
- Approve or reject each phase, with a comment Claude reads.
- Preview every step screen with real data before it goes out.
- Every assignment carries its reason, in plain words.
Security
Security, one line each
OAuth for agents
Your agent signs in with OAuth, and each token is bound to one orchestrator and sees only that workspace.
Row-level security
Each workspace's data is fenced off by row-level security, and every request is scoped to your workspace.
Sandboxed step screens
Custom step screens run in a sandbox with no network access; the camera and uploads always belong to the app.
Signed webhooks over HTTPS
Standard Webhooks signatures, HTTPS only, private addresses blocked, and only admins can create them.
Put it to the test on a real job.
Map one cabinet, send one step, approve one phase. You keep the final say.
Free for up to 3 people. No card.