Privacy Policy

Last updated: October 24, 2026

Echolify and its product MyEcho ("we," "us," "our") are operated by IN-CONTEXT LLC, a Texas limited liability company. This policy explains what data we collect when you use myecho.echolify.ai or echolify.ai, why we collect it, and the choices you have.

For the purposes of the EU and UK General Data Protection Regulation (GDPR), IN-CONTEXT LLC is the controller of the personal data described here, except where Section 1 says an echo owner is. You can reach us about anything in this policy at privacy@echolify.ai.

1. Information we collect

Account information. When you sign up, we collect your name, email address, a password (which we store only as a salted, hashed value — never in plain text), and the public link handle you choose.

Persona content you provide. Anything you write into your echo's persona — bio, tagline, voice traits, role or industry, profile photo, and appearance settings — is stored so your echo can use it to answer questions.

Documents you upload. If you use "Enrich with a PDF" (a resume, LinkedIn export, or company profile), we store the uploaded file and the text extracted from it. Because this is your own self-disclosed information about yourself or your business, we store it as-is, unredacted.

Conversations. We log chat messages from three surfaces: your own test-chat with your echo, visitors chatting with your public echo, and Echolify Help, our help assistant (in MyEcho, in Nico's menu, or on echolify.ai). Echolify Help is part of MyEcho even when you open it inside Nico, so those conversations are logged as described here, not stored with your Nico data. Before storage, we automatically strip common patterns of personal information — email addresses, phone numbers, credit card numbers, U.S. Social Security numbers, and IP addresses — from these logs. This is an automated, pattern-based filter; it is not a substitute for keeping sensitive details out of chat in the first place. The one exception is contact details a visitor leaves for the echo owner, described next.

Contact details visitors leave for an echo owner. Unless its owner has switched this off, an echo asks its visitors for their name, an email address or cell number, and what they're looking for, so the owner can follow up. Sharing these is always optional, and the echo keeps helping either way. When the feature is on and a visitor types an email address or phone number into a chat on an echo's public link or website widget, we save the visitor's name (if given), those contact details exactly as typed (not redacted, since the owner needs them to reply), and a short AI-written summary of what the visitor wanted and whether the echo resolved it. To write that summary, the conversation is sent to Anthropic (see Section 4). Only that echo's owner can see these entries, in their Contacts list, where they can add their own follow-up notes and archive entries. For these details, the echo owner is the controller: they decide whether and how to follow up, and they are responsible for using the details lawfully. We store and process them on the owner's behalf to provide the Contacts feature, using the service providers named in Section 4, and we don't use them to market our own products to you. To have contact details you left with an echo removed, you can ask the echo owner, or email privacy@echolify.ai with the email address or phone number you shared and we will delete them.

Usage and analytics. We set an anonymous, randomly generated identifier in a cookie to measure things like page views, which features get used, and to apply fair-use limits on how much you or a visitor can chat per day. We also attach this identifier to the redacted chat logs described above, so we can tell one visitor's conversation apart from another's and read a conversation as a thread rather than as loose messages. With each visit we also record the visitor's approximate country, which our infrastructure provider Cloudflare works out from the connection without us storing the IP address, and the browser's preferred language. Echo owners see visits to their own echo only as anonymous totals: where visitors came from (for example a search engine, LinkedIn, or the owner's own website), device type, country, language, the time of day they chat, and how conversations go, such as how long they last and whether a visitor tapped a link, email address or phone number in a reply (we record only that it was tapped, and for a web link its website, never the address or number). Countries, languages and referring websites with fewer than five visitors are grouped together or left out, to make it harder to single out an individual visitor. We do not store IP addresses, region, city or precise location, and we do not use this identifier for advertising.

Apps you connect to Nico. If you connect an AI app to Nico (see Section 4b), we keep a record of the connection — the app's name and the web address it signs in from, what you allowed it to do, and when it connected and was last used — and a log of each request it makes: what kind of request and how many of your facts it returned, but not which facts or what was asked.

Feedback you submit. If you report a bug or suggest a feature through Echolify Help, we store what you tell us so our team can review it.

Billing information. If you subscribe to MyEcho Pro or MyEcho Pro Plus, Stripe collects and stores your payment details directly — we never see or store your full card number. We keep a record of your subscription status and Stripe's identifiers for your customer/subscription so we know which plan you're on.

2. Cookies

• Session cookie — keeps you signed in. Required for the product to work.
• Visitor identifier cookies — anonymous, non-signed correlation IDs (one set by our marketing site, one by the app) used for analytics and daily usage limits, described above.

These are first-party cookies that the product relies on to run and to protect itself from abuse, and the analytics they support are anonymous and shown only in aggregate (Section 1). We rely on our legitimate interests for them (Section 3b), and you can object at any time (Section 8).

We don't use third-party advertising or tracking cookies.

3. How we use your information

• To operate your account and your echo, and to let visitors chat with it.
• To generate AI replies — your chat messages and your persona content are sent to our AI provider (see Section 4) so it can produce a response.
• To prevent abuse, including daily message limits per account and per visitor.
• To improve the product — for example, reviewing the questions visitors ask your echo (including ones it couldn't answer, shown as "unanswered questions," and aggregate, anonymous visitor insights such as where visitors came from and their country and language) so you can decide whether to teach it something new.
• To give echo owners the contact details their visitors chose to leave, with a summary of what each visitor wanted, so the owner can follow up.
• To send you account-related email, such as a signup verification code, and security alerts, such as when Nico pauses an app you connected because it read an unusual amount.
• To reply to bug reports and suggestions you send us through Echolify Help, for example to tell you an issue you reported is fixed.
• To operate Nico, the private AI workspace included with paid plans — storing the documents you upload there, sending them to our AI provider to draft knowledge entries you review, and answering your private chats using the entries you have approved.
• To let AI apps you connect to Nico read the knowledge you chose to share with them, and — only if you allowed it — suggest new or edited entries, which change nothing until you approve them. Knowledge entries can therefore come from a connected app's suggestion, not only from a document. When an app asks a question in plain language, the question and the titles of the facts it may read can be sent to our AI provider to pick the relevant ones.

3b. Our legal bases (EEA, UK and Switzerland)

Where the GDPR applies, we rely on these legal bases:

• Performing our contract with you — running your account, your echo, Nico, AI replies, billing for a paid plan, and the account email that goes with it.
• Legitimate interests — keeping the service secure and available (daily usage limits, abuse prevention, error and failure logs), letting visitors chat with a public echo, and anonymous and aggregate analytics about how the product and each echo are used (Sections 1 and 2). We weigh these against your rights, and you can object at any time (Section 8).
• On an echo owner's behalf — for contact details a visitor leaves for an echo owner, the owner is the controller and decides the legal basis. We process those details on the owner's instructions to provide the Contacts feature (Section 1, Terms §6).
• Legal obligation — keeping billing records for as long as tax and accounting law requires.

4. Who we share data with

We don't sell your data. We share it with the service providers that make the product work:

• Anthropic (maker of the Claude AI models) processes the messages sent to your echo, your test-chat messages, conversations with Echolify Help (in the app and on echolify.ai), PDFs you upload with "Enrich with a PDF" (to draft your bio), and — for paid plans — the documents and private chats in Nico, in order to generate replies. When a visitor leaves contact details, Anthropic also processes that conversation to write the owner's summary of it.
• Cloudflare provides the infrastructure we run on — our database, file storage, compute, and the email service used to send verification codes and security alerts. If Anthropic is temporarily unavailable, a backup AI model run on Cloudflare's own platform (Workers AI) generates replies to messages sent to your echo, your test chat, and the MyEcho help assistants. Nico has no backup model.
• Stripe processes payments if you subscribe to MyEcho Pro or MyEcho Pro Plus — we never see or store your card details ourselves; Stripe handles that directly under its own privacy policy.

If you connect Nico to an AI app you choose (for example Claude.ai or ChatGPT), what that app reads is sent to its provider and handled under your own account and agreement with them, not by us. That provider is not our service provider, and you can disconnect the app at any time.

We may also disclose information if required by law, or to protect the rights, safety, or property of Echolify, our users, or the public.

International transfers. We are based in the United States, and these providers process data in the United States and other countries. When we transfer personal data from the EEA, UK or Switzerland, we rely on the European Commission's Standard Contractual Clauses (and the UK and Swiss equivalents) as included in each provider's data processing terms, or on the EU-U.S. Data Privacy Framework and its UK and Swiss extensions where a provider is certified under it. You can ask us for more detail at the address below.

4b. Nico, your private workspace (paid plans)

MyEcho Pro and MyEcho Pro Plus include Nico, a private AI workspace at assistant.echolify.ai. It is separate from your public echo, in ways worth stating plainly:

• Nothing in it is public unless you publish it. Documents and knowledge entries you keep there are private by default. A knowledge entry becomes readable by visitors to your public link only when you explicitly publish it, and unpublishing makes it unreachable again immediately.
• It is stored encrypted. Documents you upload are encrypted at rest under a key unique to your account, as are your knowledge entries and private chats.
• It has its own sign-in. Reaching Nico requires your MyEcho password plus a second factor — an authenticator app, a recovery code, or a passkey. If you open Nico from MyEcho within a week of signing in to MyEcho, that sign-in stands in for the password, but Nico still asks for your second factor. Apps you connect (below) are the one exception: you approve each with your password and second factor once, and it can then read for up to 30 days without asking again.
• Your private chats stay private. The AI conversation inside Nico is never used to answer questions from visitors to your public echo.
• You can connect AI apps to it. You can let an AI app you use, such as Claude.ai or ChatGPT, read your Nico knowledge. You approve each app yourself and choose what it may read — everything you have approved, or only the facts you published to your echo — and whether it may suggest entries for your review. Apps never receive your documents, your private chats, or any fact you mark "Hide from apps". You can see each app's recent activity and disconnect it in Nico at any time. Resetting your password or two-factor setup disconnects every app, and if an app reads an unusual amount at once, Nico pauses it and emails you.
• Your echo's unanswered questions can appear there. When your public echo couldn't answer a visitor's question, a short summary of that question is shown in Nico so you can answer it with a fact. To suggest which of your approved facts might be related, Anthropic is given the question together with the titles of your approved facts. You decide what, if anything, gets published. These questions are never added to your private chats, never sent to apps you connect, and never copied into your facts.

As elsewhere in the Service, Anthropic processes documents and chat messages in Nico in order to generate replies, and Cloudflare stores them. If you lose every second factor, we can reset your two-factor setup after verifying your identity — that restores your access, and does not change who can read your documents.

5. Data retention and deletion

We keep account and persona data for as long as your account exists. The following is removed or reduced automatically on a schedule:

• Redacted conversation logs — deleted after 12 months, so an echo's visitor insights cover at most its last 12 months of conversations. Until then they carry the anonymous visitor identifier described in Section 1, so a conversation can be read as a thread; they are not linked to a public profile or to any other identifying information about the person who sent them.
• Browsing details on visits — after 90 days, the page visited is removed, the referring address is cut down to just its website (for example linkedin.com), and the browser description is cut down to the device type (phone, tablet or computer). We keep that reduced record, with the visit's country and language, because it feeds the owner's anonymous visitor totals and counts toward the owner's usage allowance.
• The link between a visitor identifier and usage records — removed after 90 days.
• Failed sign-in and failed email records — deleted after 90 days.
• Expired one-time codes (signup, email verification, password reset) — deleted 7 days after they expire.
• Billing records — kept for as long as tax and accounting law requires, even after an account is deleted.

Feedback and questions sent to Echolify Help on echolify.ai without an account are kept so our team can review them — ask us to delete yours.

Contact details a visitor left for an echo owner (Section 1) are kept until the owner's account is deleted, or until we remove them at the visitor's request, made to us directly or passed on by the echo owner. An owner archiving an entry hides it from their list but does not delete it.

We also keep a copy of the instructions your echo was running on when it produced a reply, so we can tell later why it answered the way it did. These contain your own persona content, not visitors' messages.

Nico is stored separately. The documents you upload there, your knowledge entries (whether drafted from a document, a chat, or an app's suggestion), your private chats, and the records of apps you connected live in their own database and file storage, apart from the rest of MyEcho. We keep them for as long as your account exists, and we don't delete them on a schedule.

Deleting your account covers both. To request deletion of your account and associated data, contact us at the address below. We remove your MyEcho data and your Nico data — including the uploaded documents themselves and anything you had published to your public echo, which stops being readable straight away — and every app you connected loses access. Copies an app already received are held by that app's provider under your account with them, so delete those with the provider. We keep a dated record that a deletion took place, identified by a one-way hash rather than your email address.

6. Security

Passwords are hashed with PBKDF2 and never stored in plain text. Traffic to our site is encrypted with HTTPS. No method of storage or transmission is 100% secure, and we can't guarantee absolute security.

7. Children's privacy

MyEcho is not directed at children under 13, and we do not knowingly collect information from them. In the EEA and UK, you must also be old enough to agree to this processing yourself under your country's law (between 13 and 16, depending on the country). If you believe a child has provided us information, contact us and we will delete it.

8. Your choices and rights

You can review and edit most of your account and persona data directly from the app. Depending on where you live — and always if you are in the EEA, UK or Switzerland — you also have the right to:

• Access the personal data we hold about you and get a copy of it.
• Portability — receive the data you gave us in a structured, machine-readable format (we provide JSON, plus the files you uploaded to MyEcho and a list of what Nico holds — Nico's contents are available to you directly inside Nico).
• Correct data that is inaccurate or incomplete.
• Delete your data (see Section 5).
• Restrict how we use your data while a question about it is resolved.
• Object to processing based on our legitimate interests, including the analytics described in Sections 1 and 2.

To make a request, email privacy@echolify.ai from the address on your account. We'll respond within one month, and we may ask you to confirm your identity first. If you're a visitor rather than an account holder, tell us roughly when and on which echo you chatted, since we don't hold your name or email (unless you left them for the echo owner). For contact details you left with an echo owner, you can also go to that owner directly, since they are the controller of those details. You also have the right to lodge a complaint with your local data protection authority.

9. Changes to this policy

We may update this policy as the product changes. We'll update the "Last updated" date above when we do; material changes will be communicated where practical.

10. Contact us

Questions about this policy or your data? Email privacy@echolify.ai. For product or account support, email support@echolify.ai.