Privacy and account data
Updated October 31, 2026. This describes the software's current behavior. Your instance operator controls its deployment, recipients, backups and any additional retention obligations.
What is stored
The service stores organisation and worker profiles, hashed login/API credentials, routing settings, task requests and responses, messages, credit/hold/payment history and operational logs. Sensitive credential answers are excluded from normal browser/API history views. Do not put secrets in ordinary task descriptions.
Who can access it
Organisation administrators manage their team and customer records. A worker sees work assigned or offered to them and their own payment records. Freelancers see a public brief before claiming, rather than a customer's private request. Your operator has infrastructure access and controls recovery copies.
Providers and local storage
If enabled by the operator, AI triage sends task context to Anthropic, notifications send relevant task details to configured email/webhook/Slack destinations, and payment providers receive the information needed for their configured flow. The optional PayPal integration is sandbox-only and disabled by default. The console keeps your login token in this browser's local storage until sign-out; a shared computer should be signed out after use. No advertising tracker is included in the console.
Optional public website analytics
On public signup, freelancer application, self-hosting and this privacy page only, Analytics choices lets you allow or turn off Google Analytics, Mixpanel and Betterloop. They stay off until you allow them on this browser. Allowed analytics may use random device identifiers and cookies for basic page and fixed usage events. Form values, task contents, prompts, account or worker identities, private work, invite links and full URLs are not sent. Advertising features, session replay and text capture are disabled. Browser Do Not Track or Global Privacy Control keeps analytics off. The authenticated console and invite page do not load these trackers. Your choice can be changed at any time.
Export and closure
Sign in and open Account to download your profile and payment records or close your account. Exports exclude secrets, shared task content and other accounts. Contact your instance operator for task-content access, correction or further privacy requests; self-hosted users can contact the operator who gave them access.
Closing clears profile contact details, notification channels, skills, current payout destination and login access. It retains an anonymous account identifier and shared task/message and financial history for work records, disputes and reconciliation. Original payment recipients already stored in payment attempts remain with those records. Closure does not erase money owed or count as a payment. Finish or release active work first; the last owner must add another owner.
Retention and recovery copies
This release does not automatically purge financial records or old payment attempts. Completed unpaid requests and their shared messages expire after the configured retention window (30 days by default; setting RETENTION_MS to 0 keeps them). Requests with payout records are retained for reconciliation. Credential answers use a shorter expiry (10 minutes by default). The operator must review retention needs, restrict access and handle further deletion requests against backups and applicable obligations. Existing backup copies may retain older profile data until they expire under that operator's backup policy. Restoring a backup requires reapplying later account closures before reopening user access.
Software support
Report a non-private software issue. Do not post contact details, task contents, credentials or payment records in public issues. Private account and retention requests belong with the operator who controls your instance.
Hosted contact form
For humanindaloopai.com, use the private hosted contact form. It sends your name (if given), reply email and message through the shared Betterloop contact relay to Resend and the operator's email inbox. It does not create an account or send you an automatic confirmation. Do not include credentials, payment details or private task contents.
The relay keeps delivery references, state/timestamps and hashed submission/rate-limit information, not the full name, reply address, message or raw IP in its database. Delivery metadata has no automatic expiry; old rate rows are removed on later requests, without a fixed deletion time. Full emails remain with Resend and the operator's inbox under their own retention. Contact submissions are separate from console account export/closure; this software does not automatically erase those email copies. Hosting providers may maintain their own technical logs.
Your text stays in this page after an unconfirmed send so you can retry. Closing or reloading the page can lose that draft; it is not saved in browser storage. An independent self-hosted instance must use its own operator for account/task/privacy requests; this hosted form cannot verify or recover its accounts.