Privacy, in plain words

The short version

We do not collect personal data from the app. There is no account, no analytics SDK, no advertising and no third-party tracker in Ferric. The only personal data we ever hold is an email address you type yourself into the waitlist form on this website.

The app runs on-device

Ferric compiles and runs your Rust code 100% on your iPad. It does not send your code, your projects, or your keystrokes to any server. There is no account and no sign-in required to use the app. Your projects live in the app's own storage on your device and in the Files app, and you decide what leaves it.

When the app uses the network

Ferric reaches the network in only two situations, both driven by you. First, it may download its compilation toolchain from Ferric's CDN so the app itself can stay small. Second, in Pro mode, the build engine downloads the crates.io packages you list as dependencies. Both requests are anonymous: they carry no account, no identifier and no content of your code.

Purchases

Purchases are handled by Apple through StoreKit. Apple processes the payment; Ferric never sees or stores your card details. We use your App Store receipts to validate your license — that check happens on your device.

The website

On getferric.dev, if you join the waitlist we store your email address (in Cloudflare D1) for the sole purpose of letting you know when Ferric launches. We do not sell or share it. You can ask us to delete it any time by emailing support@getferric.dev.

The site is served through Cloudflare (hosting and Turnstile anti-spam), which may log standard technical server data. There are no third-party advertising trackers.

Children

Ferric is a programming tool suitable for learners of any age, and because it collects no personal data from the app, using it does not require a child to hand over anything about themselves. The website waitlist is meant for adults; please do not submit an email address for someone under 13.

Contact

Questions about privacy? Email us — a human replies.

See also our Terms of Use and Support page.