Privacy Policy

Who operates this service

AIMemLink is operated by AIMemLink. For privacy questions, deletion requests, or to exercise your rights, email privacy@aimemlink.com.

Who this is for

The service is not intended for anyone under 16. By creating an account, you confirm you meet this age requirement.

Memory zones

Your memory has two zones. Public memory is served at your public URL. Private memory is only served on your secret link. Your private link returns both zones combined. Telegram saves append to private memory only.

Public memory

Your memory is served at a public URL such as https://aimemlink.com/username/public-memory.txt. Anyone who knows your username can read it. Public pages may be copied, cached, or reshared by third parties even if you later delete or change your memory here. Do not store passwords, API keys, one-time codes, or other sensitive data in public memory.

Private links and security

Every account also receives a private capability URL such as https://aimemlink.com/username/{32-hex}.txt. Anyone who holds the full URL can read your memory — there is no separate password on that link. Treat it like a secret key: do not paste it in public chats, screenshots, or shared documents.

You can rotate the private link from your dashboard if it leaks. Rotation stops future access via the old URL on AIMemLink, but cannot remove copies already made elsewhere (browser history, AI chat logs, backups, screenshots).

We send X-Robots-Tag: noindex on private responses and ask compliant crawlers not to index them. That is not a guarantee your link will never be discovered, cached, or copied.

MCP API keys (optional): If you generate an MCP key from your dashboard, it works like a bearer credential — similar to your private link, but for MCP clients such as an AI agent, IDE, or desktop assistant. We store only a one-way hash and a short prefix for display; the full key is shown once at creation. Revoke or regenerate from Dashboard → MCP access if it leaks. The same rule applies as for memory content: do not append passwords, API keys, or other secrets via MCP or Telegram.

What we collect and store

To run the service we process:

• Account: Firebase user ID, sign-in email (via Google or magic link), username, public and private memory text, private link token, optional MCP API key hash and prefix, profile version and timestamps.
• Consent record: which Terms/Privacy versions you accepted, when, and request IP and user-agent at onboarding.
• Telegram (optional): linked chat ID and short-lived link tokens when you connect Telegram.
• Activity logs: memory fetches and account actions (IP, user-agent, referer, country/city when available, action type, HTTP status, profile version). We do not store memory bodies, private tokens, or rejected secret content in these logs.
• Website analytics: page views, pages visited, referrer, device and browser type, and approximate location (country/city) via Google Analytics when you browse AIMemLink. This does not include your memory text or private link contents.
• Browser: your email may be stored locally in your browser during magic-link sign-in until sign-in completes.

Why we use it

We use this data to authenticate you, host and serve your memory URLs, connect Telegram when you ask, prevent abuse, keep audit records for security, demonstrate compliance with the policies you accepted, and understand how the website is used so we can improve the product.

Service providers

We use third-party infrastructure to operate AIMemLink. Data may be processed in countries other than yours, including the United States:

• Google Firebase / Google Cloud — authentication and database (Firebase Privacy).
• Vercel — hosting and request processing (Vercel Privacy).
• Google Analytics — website usage statistics (Google Privacy Policy).
• Telegram — optional bot integration when you link your account (Telegram Privacy).

If you paste a memory URL into an AI tool, that provider may fetch and store the content under its own policies. AIMemLink does not control third-party AI platforms.

Authentication

Sign-in is handled through Firebase Authentication (Google and email magic link). We do not store your Google password.

Retention

We keep your account and memory data while your account is active. Activity logs are kept for security and operations until we add automated retention limits. When you request deletion, we will remove your profile and memory from our systems within a reasonable time, subject to backups and logs that may persist briefly for security or legal reasons.

Your rights and deletion

You may request access, correction, or deletion of your personal data by emailing privacy@aimemlink.com from the address tied to your account. We may ask you to verify your identity before acting on a request. Self-service export and deletion may be added later.

Cookies and analytics

We use Google Analytics 4 to measure traffic on AIMemLink — for example which pages are visited, how you arrived, and general device or location information. Google Analytics may set cookies (such as _ga) for this purpose.

We do not use analytics for advertising, cross-site tracking, or selling personal information. Firebase Authentication may use browser storage or cookies that are necessary for sign-in.

A cookie preference banner may be added later. To ask about analytics data, email privacy@aimemlink.com.

Changes

We may update this policy as the product evolves. Material changes will be reflected in the version and effective date at the top of this page. New users must accept the current policies at onboarding.