Privacy Policy
Updated October 2026
Who this covers
This policy describes data used to operate Hug.Me, an adults-only AI voice companion service. Companions are software, not real people.
Account and companion data
We receive account information such as your email from your sign-in provider. We store the companions you create, your likes, call history and duration, settings, minute balances, billing references, and selected memories. A browser cache supports the app on your device. Portraits may be served through public image URLs even when a companion is private.
Voice, transcripts, and memory
Live audio is processed to recognize speech and generate spoken replies. Text from the conversation is sent to AI providers and may be used after a call to extract selected memories for future calls. For completed calls, we store the final user and companion text turns as part of your account’s call history. Memories may contain sensitive information you choose to share. You can pause memory, inspect and edit its facts, or clear a companion’s memories. We do not intentionally keep full audio recordings as a user-history feature.
Service providers
Supabase supports authentication and database storage. LiveKit carries real-time audio and hosts the voice agent. Deepgram transcribes speech. OpenRouter and the selected model hosts generate replies and memory facts. RunPod supports voice synthesis and configured generation services. Vercel hosts the web app. Configured image generation can use OpenAI or another operator-selected image provider. Google may provide sign-in and analytics. Stripe handles card setup and payments when enabled. These providers receive the data needed for their function and may retain operational data under their own policies. We do not promise that third-party processing is zero-retention.
Payments and age confirmation
Stripe receives card details directly. We store Stripe account and transaction references, an adult attestation timestamp, and the credit-card check result. We do not retain the submitted date of birth or full card number. A hashed card identifier prevents repeat free trials, including after account deletion; it is not used for advertising.
Safety notifications
Automated safeguards may recognize explicit self-harm statements and provide human crisis resources. We count referral notifications by day. The counter tables do not contain user identifiers or conversation text. Operational logs may contain call correlation identifiers and timing information. Normal conversation processing and memory rules still apply. Read Safety & support for the protocol and its limitations.
Call diagnostics
We store operational call events to troubleshoot service problems, including timestamps, call correlation identifiers, error types, connection states and service response codes. These diagnostics are available only to authorized operators and do not contain conversation text, audio recordings, passwords or access tokens. They are separate from your saved transcripts.
Analytics and browser storage
Google Analytics may collect pages visited, device/browser details, and approximate location. It loads automatically without a permission popup; previously saved browser opt-outs are honored. Essential browser storage keeps your session and app preferences. We do not put conversation text or companion memories into analytics events.
Retention and your choices
Call history, including complete text transcripts, and selected memories remain until you clear them or delete the account. Ended operational call metadata and call diagnostics are pruned after 12 months by a daily job. Clearing visible history deletes its stored transcripts but does not reset call quotas or remove separate usage/billing records while the account exists. Clearing browser data does not delete your cloud account. Removing data from active storage may not immediately remove it from backups or provider operational records. Use the memory controls, Clear history in your profile, or Delete account. Account deletion closes calls, removes uploaded account portraits from active storage, cancels Stripe billing when present, and removes active Hug.Me account records. Required transaction records may remain at Stripe, and the hashed trial-card identifier remains without the deleted user link. Contact us for access, correction, or export requests.
What we do not do
We do not sell your personal conversations or use them to build advertising profiles. Fictional companions are not intended to identify real people.
Questions
Contact support@hug.me for privacy requests. Do not send card numbers, passwords, or private recordings in an email.