Account and service metadata
Tenant identifiers, digest-only API-key records, quota usage, request IDs, resolution metadata, structured outcomes, and operational timestamps.
Legal · effective July 10, 2026
Privacy notice
This notice describes how Mo Sharif, operating ResolveMesh from Colorado, United States, handles information across the website, private pilot, support, agent interfaces, and billing surfaces.
Collected data
Metadata needed to operate the resolver
ResolveMesh minimizes collection at the service boundary and separates private operational records from public aggregates.
Billing metadata
Stripe customer and subscription identifiers, plan status, and webhook event identifiers. ResolveMesh does not receive full payment-card details.
Communications
Information you voluntarily send when applying for access, requesting support, or discussing provider participation.
Data boundary
Content the service is not designed to retain
Intent text is processed transiently for resolution and demand normalization. Public demand intelligence contains coarse aggregates, never raw request text or tenant identity.
Raw prompts and documents
Do not submit source content, examples, files, or personal profiles.
Credentials
Do not submit API keys, OAuth grants, cookies, or provider secrets.
Provider output
Do not send or report provider response bodies or tool output.
Use and retention
Operate, secure, bill, and improve the service
We use information to authenticate tenants, enforce quotas, produce resolutions, record outcomes, prevent abuse, administer subscriptions, answer support, and publish privacy-thresholded demand aggregates.
Retention
Private normalized demand observations are retained for 90 days; the public demand window covers 30 days. Other account, billing, outcome, security, and support records are retained only as long as reasonably necessary for operation, legal obligations, disputes, and enforcement.
Public output
A demand cluster publishes only after at least 20 unresolved events from at least five independent tenants in the rolling 30-day window. Published output is category-level aggregate data.
Processors and disclosure
A small operating stack
We disclose information only to operate the service, complete transactions, comply with law, or protect rights and safety.
Stripe
Stripe hosts Checkout and Customer Portal and processes payment, fraud, billing-address, and subscription information under its own privacy terms.
Hosting and infrastructure
Service data may be processed by hosting, database, logging, and security providers used to run ResolveMesh.
Forward Email routes support@resolvemesh.com to the operator mailbox at mo@codelit.io; messages pass through those mail systems.
Choices
Contact the operator directly
We do not sell personal information or share it for cross-context behavioral advertising.
Requests
Contact support@resolvemesh.com to request access, correction, or deletion where applicable. We may verify identity and retain records when law or security requires.
International processing and changes
Information is processed in the United States. We will post updates here with a revised effective date and provide additional notice when required.