Skip to content
/docs/faq

Help

FAQ

The questions people actually ask, answered from the code.

Every answer here describes verified behavior, not intentions. Anything deeper lives in the rest of these docs — and the source is public.

Is Levix free?

The software is free and open source under the MIT license. Two things can still cost money: AI features call a provider on your own API key (whatever that provider charges), and WhatsApp traffic uses the phone or server's own internet connection.

Does it read or store my chats?

It doesn't archive messages. The only things kept about incoming traffic are a per-message forward counter (used by !score, expiring after 30 days) and a last-seen row per sender. Deleted and edited messages are not captured. What it does keep: the AI conversation history for chats where you talked to the bot (wiped with !del or !delall) and the long-term memory you explicitly ask it to save.

Is this an official WhatsApp product?

No. Levix is independent, open-source, and unaffiliated with WhatsApp or Meta. It links to your account as a linked device, the same mechanism WhatsApp Web uses. Note that WhatsApp's terms restrict unofficial automation — see the site's Terms of Use for the honest version of that risk.

Do I need an AI API key?

Not to use Levix. All the non-AI commands — todos, scheduling, groups, media, utilities — work with zero keys configured. AI features switch on once the active provider's key is set in the panel. Pointing the provider at a local Ollama or LM Studio server makes even the AI fully local, with no key and no third party.

Which AI does it use?

Whichever you pick in the panel: Google Gemini (the default), OpenAI, Anthropic, or any OpenAI-compatible endpoint — Groq, OpenRouter, Ollama, LM Studio. Image generation (!generate) always runs on Gemini regardless of the chat provider. A conversation survives switching providers mid-flight — history is stored in one canonical format.

One WhatsApp account per install?

Yes — one linked session per installation. To move phones or change accounts, unlink first (Connection → Unlink), which clears the account's derived state. Linking a second instance on the same WhatsApp account can get the older link replaced, the way WhatsApp Web sessions do.

Does it speak Arabic?

Yes. The control panel is fully bilingual (Arabic RTL and English), and the bot's replies follow !lang — Arabic, English, or auto-detect per message.

Does it work on 32-bit phones?

Yes — every release ships two Android APKs: levix-android-arm64.apk for 64-bit phones (almost everything since 2016) and levix-android-armv7.apk for 32-bit-only devices. Both need Android 10 or newer.

Is it on Google Play?

Each release includes the Android App Bundle (.aab) used for Google Play. Until a Play listing goes live, install the APK from the release assets or this site's download page — Android will ask you to allow installs from your browser once.

What does it cost in battery and RAM?

On Android, roughly 0.1–0.5% CPU while idle and 90–140 MB of RAM. The app runs as a foreground service with a notification — that's what keeps Android from killing it, and the per-manufacturer battery settings are in Android → Keeping it running.

Where is my data, and how do I wipe it?

One directory holds everything — levix where prints it: ~/.levix for npm installs, ./data in a clone, the levix-data volume under Docker, the app's private storage on Android. Delete it (or uninstall the app) and nothing remains anywhere: there is no Levix cloud holding a copy.

Is it safe to paste my API keys into the panel?

Keys are sealed at rest with AES-256-GCM using a key kept in a separate 0600 file next to the database, so a leaked database alone doesn't reveal them. The panel never shows a key again after you save it — it only reports that one is configured. And the software phones nothing home: no telemetry, no crash reporting, no statistics.

How do updates work?

The install command is the update command: npm install -g levix-bot pulls the latest version, and the server installer re-runs the same way. Docker: pull and recreate the container. Android: download the newer APK and install it over the app — database, pairing, settings and password stay intact. Standalone binary: replace the file.

Can it really run 24/7 on my phone?

That's the design: a foreground service, reboot survival, and automatic reconnect when connectivity returns. Manufacturer battery managers are the usual obstacle — the fix is a few settings, documented per brand in Android → Keeping it running.