Privacy Notice

Effective July 24, 2026 · Applies to the free US adult private beta

Please read this before entering wellness information. This beta is not represented as HIPAA compliant. Do not use it as a secure clinical-message system, upload records or lab reports, or enter another person’s information.

1. Scope and operator

This notice explains how the AI Motley private beta, currently operated by Isaac Meek in collaboration with Dr. Chris Motley, handles information at https://app.aimotley.com. It does not cover Practice Better, Dr. Motley’s practice systems, or other services you use separately.

2. Information We Collect

The first beta does not ask testers to submit payment details, voice recordings, uploaded documents, or another person’s health information.

3. How we use information

We use information to authenticate you; generate, personalize, and save chat responses; remember relevant context across sessions; provide plans and account tools; answer support requests; enforce safety and access rules; monitor cost and reliability; investigate errors or misuse; and evaluate whether the private beta is useful.

We do not sell tester information or use it for behavioral advertising. We do not use an individual tester’s content to train a new AI model without separate, express permission.

4. Service providers and data flows

ProviderWhat it does and may receive
RenderHosts the application and handles web requests and operational logs.
Supabase / PostgresStores accounts, consent, profiles, chats, plans, server-side sessions, support tickets, security events, and model-usage records.
AnthropicReceives the current message plus relevant profile, recent-chat, safety, and retrieved knowledge context to generate the normal AI response and background summaries.
OpenAIReceives search text to create retrieval embeddings and may receive the same response context if the configured Anthropic response path is unavailable.
PineconeReceives query vectors and returns matching excerpts from the AI Motley knowledge collection; it is not intended to store tester profiles or chat histories.
ResendProcesses email address and message content for verification, password reset, invitations, support, and user-requested plan email.
SentryReceives configured application error diagnostics. Default PII collection and performance tracing are disabled; chat content should not be intentionally sent.

5. Human access

Isaac Meek and Dr. Chris Motley may review tester profile, chat, plan, and support information when needed for tester support, safety review, beta-quality evaluation, or service operation. A person specifically authorized to provide technical support may receive only the access needed for that task. Do not include sensitive chat text in ordinary bug reports.

6. Browser and session storage

The browser stores an opaque session cookie. A draft message may remain only in the current browser tab’s session storage so it can survive a refresh; it is cleared after sending or logout and is not shared with another tab. Non-sensitive display preferences may remain in local browser storage.

7. Retention, export, and deletion

Chat history is currently limited by the product’s active-history cap, and plans are kept so the longitudinal experience works. We retain beta data while your account is active unless a shorter operational limit applies.

The JSON export in Settings includes primary account, profile, conversation, and plan data. It does not include every security, audit, model-usage, provider-email, or infrastructure record.

An account-deletion request disables access immediately and schedules core account, profile, chat, plan, token, and session data for deletion after a 30-day recovery period. Security and model-usage records are de-identified before the account row is removed. Provider logs, sent email, and backups may persist for their normal limited operational periods and are not individually editable from the app.

8. Security and incidents

We use invite-only access, verified email accounts, password hashing, server-side sessions, encrypted network connections, role-based application controls, database access policies, backups, and error monitoring. No system is perfectly secure. If we discover a qualifying incident involving tester information, we will investigate and provide notices required by applicable law.

9. Your choices

You can choose what wellness information to enter, review primary profile data in the app, export the primary account data described above, request correction through support, or request account deletion. You may withdraw from the beta at any time, but we cannot continue personalized chat after account deletion.

10. Adults and United States only

This beta is for invited adults age 18 or older located in the United States. Do not enter information about a child or another person.

11. Changes

We will update this notice when the actual beta data flow changes. Material changes may require a new consent version before you can continue.

Privacy questions or requests

Isaac Meek · support@aimotley.com