Model Pilot

Privacy and Data Use

Privacy Policy

This Policy explains how Umbrella AI LLC processes data for Model Pilot on model-pilot.com.

Effective date: 2026-08-28 Version: 2026.08 Commercial creator service

1Operator and Contact

Operator: Umbrella AI LLC, a Wyoming limited liability company
Product: Model Pilot
Email: [email protected]
Company details: Legal Notice

2Our Data Roles

Umbrella determines how it uses account, security, support, product-administration, and business records. For Fanvue messages, fan profiles, and related interaction data processed under a creator's settings and instructions, Umbrella generally acts as a processor or service provider for that creator.

3Data We Process

  • Account data: email, username, password hash, account settings, policy-acceptance version and time.
  • Fanvue authorization data: Fanvue user UUID, display name, handle or profile details returned by authorized APIs, OAuth scopes, access and refresh tokens.
  • Fan and conversation data: Fanvue UUIDs, conversation and message identifiers, message content, timestamps, subscriber/follower segment, language, status, reply relationships, interaction history, summaries, and profile notes.
  • Media and commerce context: attachment identifiers, URLs or locally processed files, media type, price, currency, paid status, transaction/event context, and related metadata.
  • Future Fanvue app entitlement data: buyer UUID, app/plan identifiers, payment or subscription reference, gross amount, currency, status, renewal/cancellation state, and timestamps. Model Pilot does not receive payment-card details from those app-payment events.
  • Technical and security data: request metadata, IP address in security/access logs, browser/device information, timestamps, errors, audit events, and abuse-prevention signals.
  • Support and communication data: support requests, account emails, delivery status, and information you choose to provide.
  • Legacy billing records: historical plan, subscription status, invoice references, limited payment-method metadata, and transaction records from the former billing integration.

4Sources

We receive data from you, your team, your browser/device, Fanvue through OAuth and authorized APIs/webhooks, service providers acting for us, and records generated when the Service operates.

5Why We Process Data

  • Provide, personalize, maintain, and troubleshoot the Service.
  • Authenticate accounts and protect users, Fanvue integrations, and infrastructure.
  • Generate, schedule, route, and record creator-authorized communications and workflows.
  • Provide support, notices, and account administration.
  • Measure reliability, usage, and cost; prevent abuse and fraud.
  • Maintain entitlement, transaction, reconciliation, tax, audit, and legal records where applicable.
  • Improve features using appropriately limited operational information and creator-configured examples.

6AI and Automated Processing

Model Pilot sends selected prompts, messages, summaries, media, and relevant context to configured AI or inference services to generate replies, classify intent, understand media, summarize conversations, and support creator workflows. Output may be stored with conversation and usage records. We limit context to what the requested feature needs, but creators must not submit data they are not authorized to process.

Creators control whether and how automation is enabled and remain responsible for required AI/bot disclosures and review. Model Pilot does not make employment, credit, housing, insurance, health-care, or similarly regulated eligibility decisions about fans.

7Current and Future Billing Data

Access is currently free and no payment method is required. When paid access becomes available, checkout will occur through Fanvue as merchant of record. Fanvue will process payment instruments, billing address, applicable transaction taxes, receipts, refunds, disputes, and chargebacks under its own terms. Model Pilot will receive only the buyer/app/plan identifiers and entitlement/payment status information needed to grant access and reconcile service usage.

Historical records from the former Stripe integration may remain available for invoice access, support, reconciliation, fraud prevention, and legally required retention. No new public checkout is offered through Stripe.

8Recipients and Service Providers

Depending on enabled features, recipients may include Fanvue (OAuth, platform APIs, app entitlement and future merchant-of-record billing), Cloudflare (delivery and security), Resend or another email provider, hosting/database/backup providers, configured AI and inference providers, error logging or monitoring providers, and professional advisers where required.

Legacy Stripe records may continue to be processed for historical transactions. We do not sell personal data and do not use fan data for cross-context behavioral advertising.

9International Processing

Umbrella is a United States company and service providers may process data in the United States or other countries where they operate. Provider contracts and security measures are selected according to the data and service involved.

10Retention

We retain data only for as long as reasonably needed for the account, requested features, security, support, dispute resolution, reconciliation, or legal obligations. Retention depends on record type and creator configuration. Account deletion removes or schedules deletion of account-linked operational data, subject to limited backups, fraud/security records, legal holds, and historical transaction records that must be retained.

11Regional Availability

The Service is not offered to persons or businesses established in the European Union or European Economic Area and is not marketed there. Model Pilot does not use IP-based country blocking, Cloudflare country gates, billing-country checks, or invasive residence verification to enforce this restriction. Incidental technical access does not alter the intended market. If we become aware that an account does not meet the regional eligibility rule, we may restrict or terminate it.

12Cookies and Local Storage

We use technically necessary cookies and local storage for login security, sessions, CSRF protection, requested theme/interface preferences, and dismissal of the cookie information notice. We do not use analytics or marketing cookies on these public pages.

13Your Privacy Requests

Subject to applicable law and our role, you may request access, correction, deletion, or a portable copy of account data and may appeal or exercise additional state privacy rights where available. Send requests to [email protected]. We may need proportionate information to authenticate a request.

14Age Restriction

Model Pilot is a commercial creator service for companies, sole proprietors, and individual professional creators aged 18 or older. No formal business entity is required. The Service is not directed to children; do not create an account or submit children's personal data.

15Security

We use administrative, technical, and organizational safeguards designed for the sensitivity of the data, including access controls, encrypted transport, scoped OAuth, secret handling, audit records, and incident response. No system can guarantee absolute security.

16Changes and Contact

We may update this Policy as the Service, providers, laws, or business model change. The current version is published here. Material changes may also be communicated through the Service or account email. Questions and requests: [email protected].