Know what each record supports
Public proof is read-only. Source age and missing data stay visible. Paper evidence and past performance do not guarantee future results.
Public proof is read-only. Source age and missing data stay visible. Paper evidence and past performance do not guarantee future results.
Your customer account manages membership and listed access. Owner controls require separate authorization. Paid access does not authorize trading execution.
Review subscription prices, setup fees, and application requirements in Plans & Setup. Any checkout must match the published billing arrangement.
Read the Privacy Policy, Terms of Service, and Risk Disclosure. Customer account and billing records stay outside the public interface.
Updated October 20, 2026.
PMO Bot provides a public evidence preview and customer account workspace. New purchases are paused until customer tools are verified. A setup request records your needs. It does not take payment, activate a subscription, reserve capital, or enable trading.
PMO Bot offers software, research, dashboards, reports, and educational content. These do not constitute investment advice or a guarantee of trading results. Public paper evidence is simulated evidence. A customer account does not grant access to owner controls or broker execution.
Use an email address you control. Protect your sign-in credentials. Do not send passwords, broker keys, or API secrets through setup requests or email. Account access and advertised plan capabilities remain separate from provisioned customer tools.
Existing members retain billing management through their workspace and the Stripe billing portal. Review the amount, interval, renewal date, and cancellation confirmation in your billing record. Opening the portal does not cancel a subscription. Complete the cancellation there and retain its confirmation. For billing errors or refund requests, contact PMO support with your receipt. For purchases completed on or after October 20, 2026, paid digital software, subscriptions and setup services are final and non-refundable except where applicable law requires otherwise. Prior written terms remain unaffected. Read the no-refund policy below before purchasing.
Tool availability, delivery requirements, setup fees, recurring charges, and applicable cancellation and refund terms must be stated before new purchases reopen. Displayed plan prices are proposed arrangements during the preview.
For account, setup, billing, or privacy help, use Contact & support. These terms do not remove applicable statutory rights.
Updated October 20, 2026.
PMO Bot stores customer email addresses, account identifiers, verification status, and password hashes for email sign-in. Google sign-in supplies identity and email information. Setup requests store your name, email, selected plan, notes, and optional phone number. Existing billing records associate customer accounts with Stripe customers, subscription status, and plan entitlements.
A protected customer session cookie keeps you signed in. Session records expire after 14 days. Email verification and password recovery use expiring single-use tokens. Security checks and request limits use request metadata, including IP-derived rate-limit keys. Cloudflare operates hosting, database storage, security checks, and transactional email. Google handles Google sign-in. Stripe handles payment and billing-portal interactions.
Public pages display read-only evidence. Customer purchase history, passwords, broker keys, and operator tokens are excluded from public account and evidence responses. The space intro uses session storage to remember whether it has played. External font requests use Google Fonts.
Expired session and authentication-token records are cleaned up by scheduled maintenance. Account, setup-request, and billing records do not have the same automatic expiry. Contact PMO support to request access, correction, or deletion of your information. Billing and security obligations affect which records require retention. Do not include passwords or broker secrets in your request.
Transactional email supports account verification and recovery. A setup request is recorded in PMO's customer database. Save the displayed reference for support. This preview does not subscribe you to a marketing mailing list.
The optional Windows customer runtime stores broker API credentials locally with current-user Windows encryption. Its worker reads provider balances and order state directly for its permitted role. The PMO pairing API receives device version, profile revision and acknowledgement metadata, not broker keys, balances or order history. Customer cloud tokens do not grant broker order permission. Revoking a PMO device does not revoke a provider key.
Trading involves loss risk. Prices, liquidity, spreads, fees, slippage, and outages affect results. Leverage increases both gains and losses. No strategy, reward-to-risk ratio, historical result, or paper result guarantees a profit.
PMO's public proof feed reports paper evidence and engineering observations. It does not certify customer live execution, provider readiness, or profitability. Multiple display lanes sometimes share one journal. Count shared evidence once. Cached or stale evidence is labeled and does not establish current status.
Free accounts, setup requests, and subscriptions do not authorize live orders, connect customer broker credentials, or grant owner controls. Any future customer trading product requires its own verified integration, execution safeguards, applicable account permissions, and explicit authorization.
Software and educational content are not investment advice. PMO does not guarantee funded-account approval, capital allocation, returns, or recovery of losses. Evaluate the product's verified capabilities and costs before making a financial commitment.
Customer AI inference is not provisioned by the desktop companion. In a configured PMO AI operator deployment, a selected remote model provider receives the submitted prompt and retrieved context included with that request. Configured integrations include OpenAI, Anthropic and Google. Local-model routes depend on the deployment.
Chats and reviewed process lessons are stored in the deployment records. A proposed lesson requires approval before reuse. A lesson is process guidance, not permission to execute trades or alter controls. This feature does not train PMO-owned model weights.
Provider retention and training settings depend on the provider account and selected service. PMO does not promise zero provider retention. Do not submit secrets, account credentials or material you are not authorized to send. Request record access or deletion through Support. No fixed automatic deletion period is currently implemented for deployment chat or approved lesson records.
The desktop pairing code expires after ten minutes and is approved through your verified PMO account. A device receives only profile-read and profile-acknowledgement permissions. Its token expires after 30 days and is revocable per device.
Cloud records store a token hash. The companion stores its token through Windows current-user encryption. Its local profile file contains setup, risk preferences and current plan capabilities. Broker API credentials entered into the local setup window are encrypted with Windows current-user DPAPI. The customer worker reads balances and order state directly from the selected provider. These credentials, balances and order records are not uploaded through the PMO pairing API. The cloud receives version, profile revision and acknowledgement metadata. No owner credentials or broker passwords are bundled.
Broker integrations in the separate operator deployment require their own minimum permissions and provider-specific revocation. Alpaca paper execution requires paper trading permissions on your own paper account. Other customer observation roles need only their documented read permissions. This release requests no withdrawal permission. Customer live crypto orders require the separately authorized local Alpaca lifecycle. Owner account approvals are never copied. Use the provider dashboard to revoke a broker key when applicable. Revoking a PMO device does not revoke a broker key.
Support tickets store their subject, category, description, reply, timestamps and account association in PMO’s Cloudflare customer database. Do not include credentials. Device revocation preserves its security record. Account, ticket and deployment retention requests are reviewed through Support.
The free Windows companion is delivered through the release endpoint with its version, byte size and SHA-256. It is unsigned. Its customer live worker starts with entries disabled and requires each customer’s account-specific approval and validation. Paid tools follow existing entitlements and verified provisioning.
New purchases remain paused. Published plan prices are proposed arrangements. Before sales reopen, the checkout must state tool availability, delivery timing, recurring and setup charges, cancellation effective date, and the applicable refund terms. Existing members use their billing portal and receipt for their current arrangement. Statutory rights remain unaffected.
PMO Bot was created by Maurice Morrison. For account, product, billing or privacy requests, use the account-linked Support form or email maddmoepicasso@picassomoes.com. This page does not claim a regulatory registration or brokerage license.
Effective October 20, 2026. Policy reference: PMO_DIGITAL_FINAL_SALE_20261020.
All purchases of PMO paid digital software, subscriptions, and setup services are final and non-refundable, except where applicable law requires otherwise.
Applies to purchases completed on or after October 20, 2026. Prior written agreements and mandatory consumer rights are unaffected.
Review tool availability, delivery scope, system requirements, fees, and the license before paying. Downloads and account access do not transfer ownership of PMO intellectual property.
Cancel future subscription renewals through the billing portal. Retain the confirmation and its effective date. Cancellation does not itself refund an existing charge.
Report duplicate, unauthorized, or incorrect charges through a Billing ticket with a receipt reference. Billing review does not promise a voluntary refund and does not restrict rights required by law.
A purchase licenses the stated PMO access. It does not transfer source ownership or grant permission to resell, redistribute, or share PMO credentials without a separate written agreement. Third-party licenses retain their own terms.
Monday–Friday, excluding U.S. federal holidays, 10 a.m.–4 p.m. Eastern. Timezone: America/New_York.
First human reply target: 2 business days. Billing review target: 5 business days. These are service targets, not guaranteed deadlines. Ticket references are provided when the request is saved. PMO support is not an emergency trading service.
Open a support or billing ticket. New purchases remain paused until advertised paid-tool delivery is verified.