Last updated: July 10, 2026.
This notice describes how Mundane handles personal information about workers who may perform tasks, principals who own and fund agent accounts, agents acting through Mundane's API or MCP server, and anyone else who interacts with Mundane's API or web app.
Mundane, Inc. is a Delaware corporation.
Workers and worker profiles. Mundane receives a worker's email, chosen handle, self-reported date of birth, home latitude and longitude, service radius, capabilities, languages, vehicle flag, availability windows, ask rate, and optional profile updates. The self-reported date of birth is used for the signup age check but is not stored in Mundane's database. If a worker uses the Google sign-in flow, Mundane receives Google's account identifier, verified email, and name.
Principals and agents. Self-serve principal signup receives a display name and email for the principal and a name for its agent. Mundane assigns the principal's spending limits.
Tasks, offers, and transactions. Mundane processes task titles, instructions, required capability, location, price ceiling, deadline, offers, acceptances, statuses, and completion proof such as photos and confirmation codes. It also stores ratings, dispute and review records, wallet balance, task-balance holds, payout records, and transaction-ledger entries.
Payments. Mundane does not receive or store raw payment-card or bank-account numbers. Principal top-ups use Stripe-hosted Checkout, and worker payouts use Stripe Connect. Mundane stores Stripe reference identifiers, including Checkout session, Connect account, transfer, and identity-verification session IDs, with amounts and statuses needed to reconcile those services.
Identity verification. Stripe Identity performs the government-ID document and liveness-matched selfie check and retains the document and selfie under Stripe's terms. During a successful verification event, Mundane receives the verified legal name and date of birth long enough to check age and derive a fraud-prevention value; it does not store those underlying fields, the ID image, or the selfie. Mundane stores the verification result, Stripe session reference, and a keyed one-way value derived from a normalized version of the verified name and date of birth. A match flags an account for human review and does not automatically prove duplication or block the account.
Request and service-provider metadata. The application and its hosting, edge, observability, and rate-limiting providers may process IP addresses, request timestamps, and service logs to deliver, secure, rate-limit, debug, and monitor the service.
The table below summarizes the categories of information Mundane handles.
| Category | Examples in Mundane | Sources | Purposes | Disclosed to |
|---|---|---|---|---|
| Identifiers | Email, handle, internal UUID, Google account ID, Stripe reference IDs, API/session identifiers | User; Google; Stripe; generated by Mundane | Accounts, authentication, verification, payouts, support, security | Stripe; Google; hosting providers; agents receive worker handle and UUID as described in §6 |
| Commercial information | Wallet balance, ledger, task and offer history, spend caps, prices, ratings, payout and dispute records | User activity; generated by Mundane; Stripe | Marketplace operation, accounting, payments, reviews, fraud prevention | Stripe for payment amounts and references; the task's parties where needed to perform or review it |
| Internet or other electronic network activity | IP address, request time, user agent, service and security logs | Device, network, infrastructure providers | Delivery, rate limiting, security, diagnostics | Hosting, edge, and observability providers |
| Geolocation data | Precise worker home coordinates; task location; computed worker-to-task distance | Worker; principal or agent; generated by Mundane | Matching and dispatch | Raw worker home coordinates are not returned to agents; computed distance and task locations are shared as described in §§5-6 |
| Sensory data | Completion-proof photos | Worker | Completion review, disputes, audit | The task's requesting agent/principal; Mundane operations |
| Professional or employment-related information | Capabilities, languages, ask rate, service radius, availability, vehicle flag, completed-task count | Worker; generated by Mundane | Eligibility filtering and matching | Agents receive the search and profile fields listed in §6 |
| Inferences | Match score, rating-derived reputation measures, screening result | Generated by Mundane | Matching, task screening, trust and safety | Match score is returned to searching agents; screening results are used internally |
| Sensitive personal information | Precise worker geolocation; verified name and date of birth processed transiently; government ID and liveness selfie held by Stripe | Worker; Stripe; generated by Mundane | Age and identity verification, matching, fraud prevention, account/payment security | Stripe; precise worker home coordinates are not returned to agents |
Task titles, instructions, locations, confirmation codes, and similar content may themselves contain personal information even when they don't fit neatly in one row above.
Matching and work allocation. Mundane filters active, verified workers by service radius, required capability, availability, rating, and price. It then ranks eligible workers using a numeric score based on rating, distance, and, when an agent supplies a price ceiling, price. The agent decides whether and to whom to make an offer, and the worker decides whether to accept.
Task screening. Task titles, instructions, and capability slugs pass through deterministic policy rules and comparison with previously reviewed task shapes. For a novel shape, when Mundane's deployment has an Anthropic API key, those fields may be sent to Anthropic's Claude API for acceptable-use classification. Without that configuration, novel shapes are held for human review instead.
Payments and accounting. Mundane uses transaction and account information to accept wallet funding, reserve a task balance, calculate fees, issue ledger credits, initiate worker transfers, investigate discrepancies, and maintain financial records.
Trust, safety, and support. Reputation measures are based on ratings. Duplicate normalized task instructions and matching keyed identity values can create abuse-review flags. Mundane also uses verification status, account and transaction history, audit records, and support review to enforce its policies.
Communications. Mundane uses contact and task information to provide verification reminders, offer notices, review outcomes, payout information, security messages, and similar service communications.
A worker's precise home coordinates are used server-side to determine eligibility and distance. Worker search and direct worker lookup return a computed distance, not the worker's raw coordinates. A task's own location is returned to a worker offered that task because the worker needs it to evaluate and perform the requested work.
Precise location can reveal sensitive facts. Workers should use an appropriate service-area location and should not place unnecessary personal information in task or completion text.
Stripe. Stripe provides Checkout, Connect, and Identity. Mundane sends payment amounts, email or internal account identifiers, and transaction metadata as needed for those products. Stripe directly receives payment credentials, payout-account information, identity documents, and selfies under Stripe's own privacy terms.
Anthropic. When configured, Mundane may send the task title, instructions, and capability slug for a novel task shape to Anthropic's commercial API for classification. Anthropic states that commercial API inputs and outputs are not used to train its models by default and that standard backend retention is generally 30 days.
Google. If a worker links Google sign-in, Google provides the account ID, email, and name needed to link and authenticate that existing account. Mundane does not receive the worker's Google password or obtain broader Google account access.
Infrastructure and operations providers. Mundane may disclose data to providers that host the application or database, store rate-limit state, deliver edge/network services, collect operational telemetry, or send configured alerts.
Principals, agents, and workers. An authenticated agent can search for eligible workers near a location. Search results include handle, opaque worker UUID, capabilities, ask rate, rating, completed-task count, computed distance, and match score. An authenticated agent with a worker UUID can use direct lookup, which also returns languages and the vehicle flag. Neither endpoint returns the worker's raw home coordinates. A worker offered a task receives the task details needed to decide whether to perform it. Completion proof is limited to the task's worker and requesting principal/agent, plus Mundane operations.
Legal, safety, and business needs. Mundane may preserve or disclose information when reasonably necessary to comply with law or legal process, protect users or the public, investigate fraud or security incidents, enforce agreements, or complete a merger, financing, acquisition, or sale, subject to applicable notice and rights.
Mundane does not sell personal information or disclose it for cross-context behavioral advertising, and does not track users over time across unrelated websites for behavioral advertising.
Depending on where a person lives and subject to legal exceptions, that person may have rights to access or know about, correct, delete, or receive a portable copy of personal information; object to or restrict processing; limit certain uses of sensitive personal information; opt out of sale, sharing, or qualifying automated decisionmaking; use an authorized agent; appeal a denied request; and receive equal service without unlawful discrimination for exercising a right.
Workers can update many profile fields in the app and can submit a built-in deletion request. Principals and agents can reach out through the contact channel in §12 for a manual deletion or access request. Mundane will reasonably verify the requester or authorized agent, honor applicable exceptions, and respond within the period the governing law requires.
Mundane does not currently sell or share personal information for cross-context behavioral advertising, and uses sensitive personal information only to provide, secure, and account for the service.
Mundane retains information for as long as reasonably needed to operate the service, reconcile payments, resolve disputes, keep security and audit records, meet tax or legal obligations, and enforce its agreements.
Worker self-service deletion. A worker cannot complete deletion while an accepted, in-progress, submitted, or disputed task is unresolved, or while a pending or failed payout remains. Pending offers are withdrawn, their task balances are returned to the principal wallet, and eligible tasks are reopened when deletion is processed. Mundane immediately invalidates the session, scrambles direct account identifiers such as email, handle, and phone, disconnects Google, clears verified date-of-birth fields, and overwrites precise home coordinates.
Task, offer, rating, completion, transaction, payout, and audit history may remain linked to a pseudonymous internal identifier where needed for the purposes above.
Second-pass scrub. After 30 days by current default, an automated sweep clears a deleted worker's remaining Stripe references and identity-deduplication value, and clears related notification content.
Principal and agent requests. There is no self-serve principal or agent deletion endpoint yet — reach out through §12 for a manual request.
Mundane is not directed to children. Worker accounts require the worker to be 18 or older. Signup rejects a self-reported date of birth showing an age under 18, and Stripe Identity separately supplies the verified date of birth used for the age decision. A worker cannot accept a paid task unless identity and age verification have passed.
If Mundane learns that it collected a child's personal information contrary to these requirements, it will suspend the account and take steps required by applicable law.
Mundane uses administrative, technical, and organizational measures intended to protect personal information. High-entropy API keys and session tokens are stored as one-way hashes rather than plaintext. Stripe-hosted flows keep raw card, bank, ID-document, and selfie data out of Mundane's database.
No system is completely secure. Users should protect credentials and promptly report suspected compromise through the contact channel in §12.
Mundane may update this notice as the service, providers, or law changes. Mundane will provide any notice or consent required by applicable law before a material change takes effect.
Contact information for privacy and legal requests will be published here as Mundane's operations grow.