Privacy Policy

Amicus may collect account identifiers, profile and onboarding choices, subscription status, usage counters, device and error information, support messages, and the content you choose to send in conversations or calls.

Payment card details are handled by Stripe and are not stored by Amicus. Amicus stores payment status, customer identifiers, plan, renewal period, and purchase records needed to provide paid access.

Text messages, conversation summaries, selected memories, relationship state, and call summaries may be stored so a companion can continue the relationship across sessions. Amicus does not expose model prompts, embeddings, or hidden system instructions in the user memory interface.

Real-time calls send audio and avatar-session data to the configured call provider. The current product does not intentionally store raw call audio; call duration, status, and a summary may be retained.

Screen sharing begins only after you choose a screen, window, or tab in the browser picker. Downscaled snapshots are captured periodically when the screen changes and sent to the configured vision provider for analysis. Screenshots are discarded after analysis and are not stored by Amicus.

Password, payment, banking, and identity screens are automatically skipped. Amicus retains session duration, usage counters, analysis counts, latency, estimated cost, and optional text summaries or relationship memories, not the captured images. You can stop sharing at any time.

Amicus uses Supabase for accounts and database storage, an OpenAI-compatible text model provider for conversation generation, Anam for real-time avatar calls, RevenueCat and Apple for mobile purchases, Stripe for website payments, Vercel for application hosting, and Expo for mobile push-notification delivery. Each provider processes only the data needed to perform its role under its own agreement and privacy terms.

Amicus does not use private conversations to train an Amicus-owned model. Conversation data is sent to configured AI providers only to generate responses, summaries, safety classifications, and memories that provide the service. Amicus configures production providers so submitted private content is not used to train their general-purpose models where those controls are available.

Account data is kept while an account is active and as needed to operate the service. Users can delete individual memories, clear conversations, export available data, or delete an account. Account deletion removes the Amicus account and associated service data; narrowly scoped billing, fraud-prevention, safety, or legal records may be retained when required by law or to establish, exercise, or defend legal claims.

Amicus uses essential session and preference storage. The current analytics layer records product events without conversation text; it must not receive messages, access tokens, card data, or saved memories. See the Cookie Policy for details.

Security controls include server-side entitlement checks, row-level database policies, signed payment webhooks, restricted service credentials, and rate limits. No system is perfectly secure; suspected incidents should be reported promptly.

You may request access, correction, export, or deletion through Settings or Support. Rights vary by location. Identity verification may be required before fulfilling a request. Contact support@amicusapp.us.