ianium Labs

Privacy policy

Last updated November 15, 2026

This policy covers every website, app and service from Ianium Labs. It starts with what applies to everything, then has a section for each product so you can read only the one you use. If a product section and the general text differ, the product section wins for that product.

Who we are

This policy is issued by Ianium Labs (“we”, “us”). We are the controller of the personal data described here. Questions or requests: [email protected].

The short version

  • We collect as little as each product needs to work.
  • We do not sell personal data or show ads based on it.
  • Our apps are built to keep your data on your device. Anything that leaves it is described in that app’s section below.
  • You can ask us to access, correct or delete your data at any time.

This website (ianiumlabs.com)

Contact form

If you send an enquiry we receive the name, company, email address, services and message you type. We use it only to reply to you. The form has a per-IP rate limit and a hidden spam field, so your IP address is processed briefly to apply them.

Newsletter

If you subscribe we store your email address and send you a welcome email and new-article emails. Every email has an unsubscribe link. Unsubscribing removes you from future sends.

Email sent to us

Mail sent to any address at ianiumlabs.com is received by our email provider, Resend, and forwarded to our inbox.

Spam protection

Our forms use Cloudflare Turnstile to tell people from bots. It checks your browser and IP address when you use a form, under Cloudflare’s own privacy policy.

Analytics

We use Umami, a privacy-focused analytics tool that we host ourselves. It counts page views and referrers and sets no cookies. It does not follow you across sites and does not store your IP address. This applies to ianiumlabs.com and to our product websites, castlei.ianiumlabs.com and helastash.ianiumlabs.com, so none of them show a cookie banner.

Castlei

Castlei is a chess app for Android. It is built to work on your device: your games, studies, drills and statistics stay there unless you choose to back them up.

Data that stays on your device

Games with variations and comments, engine analysis, repertoires, drill schedules, puzzle history, statistics, installed puzzle packs and preferences live in the app’s private storage. We do not receive them unless you use cloud backup, export a file or send a diagnostics report yourself. Uninstalling removes them from your device. Reminder notifications are scheduled on your device and send nothing to us.

Account (optional)

You only need an account for cloud backup. If you sign in, we use Firebase Authentication with Sign in with Google and receive your account ID, email address, display name and profile picture address. We use them to sign you in, keep your backups private to you and answer your requests.

Cloud backup

When you back up, the app uploads an archive of the data above to Cloud Firestore, stored in your own private area in a Google data center in the United States (multi-region). Only your account can read or delete it, enforced by security rules. It is encrypted in transit and at rest by Google and does not include your email address. We keep your latest copy (up to five versions with Castlei Plus). Backups are removed when you delete them, when older versions are replaced, and when you delete your account.

Crash reports, performance and analytics

Each of these is on by default and has its own switch in Settings → Privacy and diagnostics.

  • Crash reports (Firebase Crashlytics): stack trace, error type, a short scrubbed message, app and engine versions, device model, OS version and a Firebase installation ID. Messages are cleaned of board positions, PGN headers and file paths first. Kept 90 days.
  • Performance (Firebase Performance Monitoring): timings such as app start, engine speed, import and backup durations, with device, network type, app version and approximate country.
  • Usage analytics (Firebase Analytics): which screens and features are used and game outcomes as broad categories, with a Firebase installation ID, device and app details and approximate location from your IP address (the address itself is not stored). We do not use advertising identifiers and ad personalisation is off.
  • Announcements (Firebase Cloud Messaging and In-App Messaging): a messaging token and installation ID, so we can send occasional announcements. Turn them off in Settings → Notifications.
  • Remote settings (Firebase Remote Config): the app downloads configuration values, which involves your IP address and installation ID.

We never collect your positions, moves, comments, game titles or file contents as analytics or crash data, and this information is not linked to the content of your games.

Feedback and diagnostics you send

Settings → Send feedback sends your message, an optional email address, up to three screenshots (check them first, they can show anything on your screen), the app version, Android version and language, and an anonymous account identifier. If you switch on Include diagnostics, the on-screen diagnostics snapshot is added: it holds versions, which switches are on and counts, never games, positions, names or email. Reports are kept until dealt with and no longer than 12 months.

Purchases (Castlei Plus)

Payments are handled by Google Play. We never receive your card or payment details, only confirmation that the purchase is active on your Google account.

Deleting your account

You can delete your account and every cloud backup in the app (Settings → Account → Delete account and cloud data), or follow the steps on our Castlei account deletion page.

Castlei website

The Castlei website at castlei.ianiumlabs.com uses the same cookie-free Umami analytics described under “This website”. It sets no analytics cookies and has no consent banner. Like any web host, our server keeps standard logs (such as IP address and requested page) for security and operation.

The former Castlei site at castlei.andwati.com is being retired. While it remains online it uses Google Analytics cookies only if you choose Accept in its banner, and not at all if you decline or your browser sends a Global Privacy Control or Do Not Track signal.

Helastash

Helastash is an Android app that tracks spending by reading M-Pesa confirmation messages on your device. It is designed so your transactions never leave your phone. Helastash has not launched yet; this section describes how it is built and will be reviewed before release.

What it reads

With your permission (SMS access, requested after you read an explanation), Helastash reads incoming M-Pesa messages and, once you allow it, imports matching messages already in your inbox. It extracts the amount, date and merchant. Messages from other senders are ignored and are not stored.

What it stores

Parsed transactions are stored in a database on your device, encrypted with a key held in the Android Keystore. The original message text is deleted after it is parsed, unless you switch on the option to keep it. Messages that could not be parsed are kept so you can review them, regardless of that option. Helastash requests no access to your contacts, location or broad file storage.

What leaves your device

  • No account is needed and your transactions are not uploaded. The only exception is the optional message sample described below, which you send yourself.
  • Anonymous crash and usage reports are sent only if you opt in. They never contain message text, amounts, merchants, names, phone numbers or balances. Advertising identifiers are off.
  • You can export all your data as a file, and share a crash log with us manually if you choose.
  • If we add backup to your own Google Drive, the data will be encrypted on your device first and this section will be updated before it ships.

Sharing an unreadable message (optional)

If Helastash cannot read a message, it appears in the review queue. There you can choose to send us a masked sample so we can teach the app that format. Nothing is sent unless you tap send, and you see the masked text first.

  • Before sending, the app keeps only the fixed words that M-Pesa messages are built from, such as “confirmed”, “sent” and “balance”. Names, merchants, phone numbers, transaction codes, account numbers, amounts, balances, dates, times and links are replaced with placeholders such as <NAME> and <AMT>. A word the app does not recognise is masked rather than sent.
  • We receive the masked text (up to 600 characters), the sender (M-Pesa or Fuliza only), the app and parser versions and a timestamp. We do not receive your name, phone number or account, and the sample itself carries no identifier. As with any request, Google’s servers see your IP address in transit.
  • Samples are stored in Google Cloud Firestore. A repeat of the same shape is stored once, and each phone can send at most 20 a day. Because samples carry no identifier, we cannot tell which one came from you, so we cannot delete a specific sample on request.
  • We use samples only to improve message parsing. They cannot be read or changed by other users of the app.

Helastash website

The Helastash website at helastash.ianiumlabs.com uses the same cookie-free Umami analytics described under “This website”. It has no forms and collects nothing else. If you email us to ask about the launch, we use your address only to reply to you.

Your controls

Settings lets you view what is stored, export everything, and delete everything (which removes the database, preferences and encryption key and returns the app to first-run). Because the data is on your device, we cannot access or delete it for you. Steps are on our Helastash data deletion page.

Why we use data

  • To provide the services and features you ask for. Basis: performing our agreement with you.
  • To keep our products working and improve them (crash, performance and usage data). Basis: our legitimate interest in reliable products, and your consent where the law requires it, which you can withdraw using the switches in each app.
  • To answer messages and requests and send newsletters you asked for. Basis: legitimate interest and your consent.
  • To meet legal obligations.

Who we share data with

We do not sell personal data and do not share it with advertisers or data brokers. We use these providers to run our services, each under its own terms and privacy policy:

  • Google (Firebase, Google Play, Sign in with Google) for Castlei.
  • Resend for email sending, receiving and the newsletter.
  • Cloudflare for form spam protection.
  • Our hosting provider, which keeps standard server logs such as IP address and requested page for security and operation.

These providers may process data in the United States and other countries. Where required, transfers rely on safeguards the provider offers. We may disclose data if the law requires it.

How long we keep data

Data on your device stays until you delete it or uninstall the app. Castlei cloud backups and accounts are kept until you delete them. Crash, performance and analytics data are deleted automatically after the provider’s retention period. Enquiries are kept as long as needed to deal with them. Newsletter addresses are kept until you unsubscribe.

Your choices and rights

Depending on where you live (for example under the Kenya Data Protection Act, the EU and UK GDPR, or California privacy law) you may have the right to access, correct, delete or export your personal data, to object to or restrict processing, to withdraw consent, and to complain to your data protection authority, such as the Office of the Data Protection Commissioner in Kenya.

To use these rights email [email protected], from the address linked to your account where relevant. We may need to confirm it is you. Castlei users can also delete their account and backups inside the app.

Children

Our products are not directed at children under 13 (or the higher age required where you live) and we do not knowingly collect their personal data. If you believe a child has given us data, contact us and we will delete it.

Security

Data is encrypted in transit, Castlei backups are protected by per-account security rules, Helastash’s on-device database is encrypted, and we limit access to our systems. No system is completely secure, so we encourage you to keep your own exported backups.

Changes to this policy

We may update this policy as our products change. The “last updated” date above shows the latest version, and we will tell you in the relevant app about significant changes.

Contact

Ianium Labs
[email protected]