DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to review AIKON privacy and API spending before going live with AIKON

Check data retention, limits and billing controls before you point real API keys at your phone server.

Credentials. Provider API keys are billed to your account, so store them only on the server and set a spending limit in each provider's console.

Who it is forA non-developer owner of a new AIKON server who is about to add paid API keys and wants to avoid surprise charges.

The problemEach message is a paid API call, and chats, photos and voice messages are stored on your server, so the costs and retention need checking first.

The outcomeYou know which limits the server enforces, where the data lives and how long it stays, and you have set a spending limit at each provider.

What you need first

  • A Nokia S40 or S60 phone (tested on the Nokia 6300 and Nokia E63)
  • A Docker host with a public IPv4 address and TCP 443 open (a $4-6/month VPS is enough)
  • An API key from at least one provider: Claude, OpenAI, Gemini or Grok
  • Docker, OpenSSL or LibreSSL, and SSH access to the server
  • For building the phone app: JDK 11+ and make
  • For building the server: Go 1.26+

Steps

  1. Read the Privacy and cost section of the README, focusing on the 30-day chat retention and the note that logs contain no message text.
  2. Confirm the per-device daily request, output-token and web-search limits the server enforces before you add keys.
  3. Set a spending limit in each provider's console for every key you add with server/deploy/set-key.sh root@<server-ip>. (inferred, check the README)
  4. Decide whether to turn on voice messages, which go to OpenAI's speech-to-text and are billed to your OpenAI key.
  5. Revoke the device or run Settings > Reset setup on the phone if the memory card leaves your hands.

Prompt for your agent

Read the Privacy and cost section of the AIKON README and list every place data is stored, for how long, and every cost that is billed to my API keys. Expected output is a short checklist with one line per item, with the spending-limit step marked as a manual action. Verify that you did not invent any limit numbers that the README does not state.

Caveat. The README says web searches are billed per search and their results count as input tokens, so check the provider's pricing before you rely on search for news or weather.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page