Your conversations are not public or sold for advertising. Lika uses protected infrastructure and AI services to respond, and our team does not routinely read conversations. You can export saved data or request deletion.
Emotional-support conversations can be deeply personal. This policy explains what Lika stores, which services process it, the limited situations in which an authorized person may see it, and what happens when you request deletion.
What we collect
Telegram account data: your Telegram user ID and the basic profile fields Telegram sends to the bot, such as first name, username, and language.
What you share: messages, voice notes and transcripts, images, diary entries, exercise answers, screenings, goals, preferences, and reminders.
Personalization data: facts and themes Lika derives from your conversations, relationship notes, summaries, and semantic vectors used to find relevant memories. Raw vector values are not included in a Telegram export.
Service and analytics data: feature use, message counts, errors, onboarding and payment-funnel events. Product events are designed to use a pseudonymous key rather than your raw Telegram ID where practical.
Subscription data: plan, amount, currency, checkout and payment status, renewal status, and provider transaction identifiers. Lika does not receive or store your full card number.
Messages to support: your email address and the information you choose to include if you contact us outside Telegram.
Why we use it
To reply, remember useful context, and provide the features you choose.
To send reminders and check-ins only when they are enabled.
To manage limits, subscriptions, payments, and account support.
To prevent abuse, keep the service reliable, diagnose failures, and improve flows using aggregate or pseudonymous patterns.
To show crisis resources and run the safety flow described below.
AI and service providers
A message may be sent to a specialist provider only when its feature is used. Current integrations can include:
Telegram for message delivery, account identifiers, and Telegram Stars payments.
Anthropic and OpenRouter for language-model responses. OpenRouter may route a request to the model provider selected by Lika.
Groq for voice transcription and ElevenLabs for generated voice when you use those features.
Self-hosted Ollama for semantic embeddings where that deployment is enabled.
PostHog for website product analytics when analytics is configured. Website session recording, automatic click capture, and advertising profiles are disabled. We also honor supported browser privacy signals and the device-level choice below.
Meta Pixelfor website page-view measurement and ad attribution when analytics is enabled. Lika does not send conversations, voice notes, diary entries, screening answers, or other emotional-support content to Meta. Meta may receive browser and device information under its own privacy terms. The Pixel stays off in Lika's private admin area and follows the same browser signals and device-level choice below.
Hosting, storage, backup, and payment providers needed to run the service. The payment provider is shown before you pay.
Website analytics on this device
We use limited, cookieless product events to understand whether the site is useful. Session recording, automatic click capture, and advertising profiles are disabled.
We aim to send each provider only what is needed for the requested operation. Provider retention and model-training terms vary by service and configuration. We are verifying the exact deletion coverage and do not promise that every processor removes a copy instantly after a Lika account deletion.
Human access and safety
The team does not routinely read your conversations and does not review them for advertising. Authorized operational access can occur when it is reasonably necessary to handle a support request, investigate a security or reliability incident, or debug a failure. Access should be limited to the minimum data needed for that task.
Lika is not an emergency service. If automated checks detect language suggesting self-harm, Lika can show crisis resources and schedule an automated follow-up. The operator alert contains a pseudonymous incident label and signal type, not your name, Telegram ID, answers, or conversation excerpt. This safety flow is not live monitoring by a therapist. If you are in immediate danger, contact local emergency services or a crisis line.
Your choices and rights
Export: open Account settings or send /exportin your private chat with Lika. The personal ZIP includes data linked to your account but omits provider secrets, charge IDs, binary embedding vectors, other people's identifiers, and anonymous aggregates.
Delete: open Account settings or send /delete. Lika uses two confirmations and tries to stop every linked renewal method before erasure. If a renewal cannot be stopped, deletion is paused so you are not left with an unmanaged subscription.
Correct or limit: update your preferences and reminders in Settings, ask Lika to forget a saved item where that control is available, or contact us.
Telegram copies:deleting your Lika account does not remove messages from your Telegram app. Use Telegram's own controls to delete those chat copies.
Deletion and retention
After a confirmed request, Lika's deletion flow looks for and clears known active account records, conversations, saved memories, personal usage metrics, and linkable checkout analytics from its primary stores. The bot returns a request ID and reports stages it could not verify rather than claiming that every copy is already gone.
Known active service data: the deletion flow clears records it finds in primary stores and records a pseudonymous erasure marker. Delayed background writes are blocked; if you later send /start, Lika creates a new clean account generation.
Temporary files and logs: uploaded voice and document temp files are removed after processing, including error paths. Application files rotate daily with limited history, while container and platform logs are currently bounded by size. A verified seven-day maximum across every log location remains a target, not a current guarantee; security-incident evidence may require a separately documented period.
Backups: Lika includes an AES-GCM encrypted daily-backup and verified restore workflow with a 14-day rotation and erasure-marker replay before restored data can be used. Production key setup, scheduling evidence, and every local or off-site copy still require deployment verification. A deleted record may remain in a protected backup until rotation; restore must reapply its erasure marker before service resumes.
AI and other processors:copies follow each provider's applicable terms; provider-specific deletion coverage is still being verified.
Payments: a provider or Lika may need to retain minimum transaction records for fraud prevention, accounting, disputes, or legal obligations. The exact legal schedule is being confirmed and is not represented as immediate deletion.
Security
We use access controls, protected network transport, secret management, data minimization, and database cleanup measures designed to reduce unauthorized access. No online service can promise perfect security. Please avoid sending information you do not need Lika to process, protect your Telegram account, and contact us if you suspect a problem.
Age and policy changes
Lika is for people aged 18 or older. We may update this policy when features, providers, or legal requirements change. The current date appears at the top of this page; material changes may also be announced in the bot.
Contact
To ask a privacy question, exercise a right, or request the status of a deletion: info@heylika.com
A simple promise: Lika is built to help, not to turn private conversations into an advertising product. We will keep explaining our practices in plain language and make export and deletion requests easy to find.