Memory Engine privacy policy

Last updated: 2026-10-14

Memory Engine is a program that runs on your own computer and keeps your notes there as plain Markdown files. This policy says what the program sends out, to whom, and why. It covers the program and the license service behind it. The website has its own policy at aiwithmo.com/privacy.

The short version

• Your notes, session notes, search index and settings stay on your computer. We keep no copy and cannot read them.
• Some text does leave your computer. Every case is listed below, and most of it goes to the AI tool you already use, not to us.
• What we receive is small: a license check about once a day, an update check, and your purchase details through our payment provider.
• If you connect Google Calendar, your events go between Google and your computer. They do not pass through our servers and we do not store them.
• We do not sell your data, use it for advertising, or use it to train AI models.

Who is responsible

Memory Engine is made and sold by Mohamed Khair Arabi, trading as AI With Mo, in Istanbul, Turkey. In this policy "we" means him. For anything about your data, write to aiwithmo0@gmail.com.

What stays on your computer

Everything Memory Engine writes: pages, work logs, session notes, facts, people and project pages, the search index, backups and settings. They are ordinary files in a folder you own. You can open them in any editor, move them, back them up or delete them. We hold no other copy.

What leaves your computer

Text leaves your computer only through the channels below.

Sent to your AI provider

These go to Claude Code, Codex or your own API key, under your own terms with that provider. They do not come to us.

Session summaries and fact checks

What is sent

A size-limited excerpt of an AI session: your messages, the assistant's replies and short tool output. Also the notes your AI tool keeps about itself and, when a fact needs a second check, that fact with its quote.

When

In the background, after your sessions, so the AI can write the notes.

Summary cards and the dashboard chat panel

What is sent

Text from one subject in your notes and the best matches from your own vault, or the question you type.

When

When you press the button or send the message.

Task and note updates

What is sent

Your note and the current lines of the pages involved, or the open-thread lines of your session notes.

When

When you use those dashboard actions or run the task scan.

Before session text, summary cards and chat messages are sent, an automatic filter removes keys, tokens and passwords it recognizes. If the filter fails, nothing is sent. The filter works on patterns, so a secret written out in ordinary sentences can get through. Keep passwords out of your AI sessions. Task and note updates send text from your own notes and what you type, without that filter.

Google Calendar events are never part of any of these. They are not added to session text, summaries, chat messages or task updates.

Sent to services we run or control

License check

What is sent

The fields listed in the next section.

When

When you activate, then about once a day.

Update check

What is sent

A request for a small public file that names the newest version. The server sees your IP address and the program name memory-engine-update. No license key.

When

At most once a day. You can turn it off by setting update.enabled to false.

Update download

What is sent

Your license key, to receive a download link.

When

Only when you ask for an update.

On Windows, the installer can also download Python and Claude Code from Microsoft and Anthropic, after you say yes. Nothing from your notes is sent.

We never receive your notes, work logs, session text, prompts, summaries, file names, folder paths, the names of your projects or people, the AI tool and model you use, or your Google Calendar events. The one exception is anything you choose to send us yourself, for example in a support request.

The license check

Each license works on one computer at a time. To enforce that, the program contacts our license server, which runs on Cloudflare.

When you activate, the program sends your license key and a one-way code made from your computer's hardware ID (the ID itself stays on your computer). It also sends the program version, your operating system and processor type, and the Python version. To recognize a reinstall on the same computer, it sends one-way codes made from your account name and computer name, a random install ID that the program creates, a short fingerprint of some of the program's own files, and a marker that links your copy to your license. The last item is a device label. It starts as something like "Mac arm64", and you can change it to any text up to 40 characters.

About once a day the program renews the license. It sends the signed token the server gave it earlier, the install ID, the device code, the program version, the Python version and the file fingerprint. If the server cannot be reached, the program keeps working for up to 30 days and tries again.

Like any web server, ours sees your IP address. We keep a coded form of part of it, plus the country, for up to 90 days.

The server stores your license, the device code (coded again with a secret that only we hold), the install ID, the device label, version and platform details, the dates and country of your check-ins, how many times you have moved your license, and a log of license events. It does not store your license key, your email address or your hardware ID in readable form. When it checks a purchase with Lemon Squeezy it receives your order details, including your email address, and keeps the address only as a one-way code, so that we can find your license when you write to us.

You can see the exact activation request by running the command mem license explain.

Payments

Lemon Squeezy is the merchant of record. It takes your payment, collects and pays sales tax and VAT, and keeps your billing details under its own privacy policy. We receive your email address, the order reference, the product and the amount. We never see your card number.

Google Calendar

Memory Engine can show your schedule next to your notes, and it can create or move calendar events when you ask it to. This is optional and stays off until you press Connect with Google.

What you are asked to allow

When you press Connect with Google, the program first shows a notice inside the program that says what it will do and why, and waits for you to press Continue. Then Google's own sign-in and consent window opens in your browser. Memory Engine asks for two permissions:

• https://www.googleapis.com/auth/calendar.events: view and edit events on all your calendars
• https://www.googleapis.com/auth/calendar.calendarlist.readonly: see the list of calendars you are subscribed to

What each permission is for

• The events permission lets the program show your upcoming events in the dashboard, and create or move an event when you ask it to. It changes your calendar only because you asked.
• The calendar list permission lets the program show which calendars you have, so you can choose which ones to display.

The program uses them for nothing else.

Where the data goes

Your events go between Google and your computer. They do not pass through any server of ours, so we never receive them, we do not store them, and nobody at AI With Mo can read them. When you ask the program to create or move an event, it sends that change from your computer straight to Google.

The sign-in token that Google issues is stored on your computer only. Events are held in temporary storage on your computer while the dashboard shows them. The program does not copy them into your notes, your search index, your backups or your logs, and it does not put them into any prompt or message it sends to an AI tool. Events can contain the names and email addresses of other people. They get the same treatment.

What we will not do

We will not sell your Google Calendar data, share it, use it for advertising or profiling, use it to decide credit or lending, or use it to create, train or improve any machine learning or AI model.

Limited Use

Memory Engine's use and transfer of information received from Google APIs to any other app will adhere to Google API Services User Data Policy, including the Limited Use requirements.

Google's policy is at https://developers.google.com/terms/api-services-user-data-policy.

To stop

Press Disconnect in the program's calendar settings. The program deletes the token and any calendar data on your computer and tells Google to revoke the token. You can also remove access from your Google Account at any time at https://myaccount.google.com/permissions.

How long data is kept

On your computer, your files stay until you delete them. We hold no copy of your notes.

On our side, the coded IP information and country from the license check are deleted after 90 days. A license record is kept while the license exists, and afterward for as long as we need it for support, refunds and accounting. Lemon Squeezy keeps order records under its own rules. Our hosting providers may keep ordinary access logs under their own rules. Google Calendar data is not kept by us at all.

Deleting your data

To delete what is on your computer, delete the Memory Engine folder, or use the program's own forget command for single pages. To remove the Google Calendar connection, use Disconnect, as above.

To delete what we hold, email aiwithmo0@gmail.com from the address you bought with, or quote your order reference. We delete the device and check-in records attached to your license and keep only the sale record that tax and accounting rules require. We reply within 30 days.

Who else handles data

• Your AI provider, for the rows above that go to it, under your own agreement with it.
• Cloudflare, which hosts the license server.
• Supabase, which hosts the public release file and the update download service.
• Lemon Squeezy, which takes payment and acts as merchant of record.

These companies run services in several countries, including the United States and countries in the European Union. Each applies its own safeguards for transfers.

Your rights

Depending on where you live, for example under the EU GDPR or Turkey's KVKK, you may ask us to give you the data we hold about you, correct it, delete it, or limit how we use it, and you may complain to your local data protection authority. Write to aiwithmo0@gmail.com.

Security

Connections to our servers use HTTPS. Every positive answer from the license server is digitally signed, and the program checks the signature before it trusts it. The license folder on your computer is readable only by your own user account.

Children

Memory Engine is not meant for people under 16, and we do not knowingly collect data from them.

Changes

If we change this policy, the date at the top changes. If we ever want to use your Google Calendar data in a new way, we will update this page and ask you again inside the program before we do.

Contact

Mohamed Khair Arabi, AI With Mo, Istanbul, Turkey. Email: aiwithmo0@gmail.com