🦀">
Privacy

Privacy Policy

No account. No analytics. No tracking. No leaderboard. This page describes exactly what leaves your device, which is almost nothing — and what happens if you write to support.

LAST UPDATED 6 SEPTEMBER 2026

The short version. Crabrix 1.0 has no account, no analytics and no leaderboard. Your code, your projects, your rating and your progress stay on your device: the app never transmits them. The only network requests Crabrix makes are the package and repository downloads you explicitly ask for. If you write to support — including through Report a problem — that email reaches a person, and this page says what happens to it.

Who is responsible

Crabrix is made by Serhii Ziborov, an independent developer. There is no company, no investor, and no third party with access to anything described on this page. Contact: .

What stays on your device

All of this is stored locally, and Crabrix never transmits any of it:

Deleting the app removes all of it. Crabrix keeps no copy and has no way to recover it. The only way any of it reaches anyone else is if you export it or paste it into a message yourself.

What leaves your device

1. Package downloads (crates.io)

When you add a dependency, Crabrix fetches it from the crates.io registry (index.crates.io and static.crates.io) over HTTPS. These are ordinary requests for public files. Crabrix sends no identifier with them and crates.io is operated by the Rust Foundation under its own privacy policy.

2. Repository import (GitHub)

If you import a public repository, Crabrix downloads its archive from github.com over HTTPS. Only the URL you typed is sent. No credentials are involved and no private repositories are accessed.

That is the complete list of requests the app makes. Both are for public files, both are started by you, and neither carries an identifier.

Optional support correspondence

If you choose Report a problem in Settings, Crabrix composes the report on your device and opens it in your own mail app, or copies the text when you ask it to. The app sends nothing: no message exists anywhere until you press send in your mail app, and you can edit or discard the draft first.

When you do send it, I receive the address you send from and whatever you chose to include. The report contains what you typed and, unless you switch the toggle off, four lines of technical detail: the app version and build, your iOS version and hardware model (for example iPhone14,4), the bundled compiler version and target, and whether the toolchain is installed. Crabrix does not attach your project files, your source code, your device name, or any identifier unique to you or your install. Anything else in the message is there because you put it there — so please remove passwords, tokens and private source before sending.

Support messages are used to answer you and to fix the problem, and for nothing else: no advertising, no mailing list, no profiling. They are kept while the problem is being worked on and deleted once it is closed, apart from any de-identified technical note needed to keep the fix from regressing. Use to ask for a copy of your correspondence, a correction, or its deletion. Your mail provider and mine handle delivery under their own terms.

A public GitHub issue is a different, public channel: anything you post there is visible to everyone, so do not put secrets or private project code in one.

What Crabrix 1.0 does not have

There is no Crabrix account, no leaderboard, no display name, no Game Center publishing, no online profile, and no server that stores anything about you. Your rating, ranks and achievements are calculated and kept on your own device. Your source code is never uploaded for compilation: the compiler runs inside the app.

Crabrix runs no service of its own — there is no Crabrix server, no account system and no board to store anything on. If ranking ever goes online, it will go through Apple's Game Center rather than through anything I operate, and this page will be updated before that version ships.

What Crabrix never does

Children

Crabrix is a programming tool suitable for all ages. The app itself collects no personal data from anyone, of any age: there is nothing to sign up for, nothing to publish, and no way for one user of the app to see another. Writing to support is the one thing that reaches a person, it is entirely optional, and it is an email the sender writes themselves.

Legal basis and your rights

Where the GDPR applies: Crabrix 1.0 runs no service and stores nothing about you on any server, so the app itself creates no controller-held record. Everything it knows about you is on your own device, and deleting the app deletes it.

The one exception is support correspondence. If you write to me, I hold that email — your address and what you chose to send — as the controller, in order to answer you and fix the problem. The lawful basis is legitimate interest in supporting the software you bought; you can object at any time by asking me to delete the correspondence. You may ask for access, correction, a copy, or erasure of it: . There is no other personal data to describe, because there is nowhere else it is held.

Retention: nothing the app stores is retained anywhere but on your device. Support emails are kept while the problem is open and deleted when it is closed, except for de-identified technical notes — a compiler version, a crate name, a stack shape — that carry no address and no personal detail.

Changes to this policy

If Crabrix ever collects something new, this page will say so before that version ships, and the date at the top will change. The app's App Store privacy details are kept in step with this page.