Beta notes, plainly stated.

Where does my writing go?

For a supported transform, selected text is passed from the host editor to the on-device model and the editable result is returned to the keyboard. The intended path has no cloud fallback, account, sync, chat, or hidden web view.

Source and generated text live in process memory for the request. They are cleared after the request and when the keyboard process shuts down unless you explicitly copy or insert the result. The host app then owns inserted text under its own rules.

What does setup involve?

Keyline will ask you to enable an input method in Android settings. AI is optional: ordinary typing, suggestions, language switching, clipboard, emoji, and keyboard settings remain available when the model is absent.

The beta model is an explicitly downloaded, quantized GGUF artifact of approximately 1.5 GB installed size. Setup will explain the download size, show progress, support cancel and retry, and offer Wi-Fi-only download. You can use the keyboard without AI.

What are the trade-offs?

• Local inference can use more battery and may warm the phone.
• English is the first language for Fix, Rewrite, Shorter, Tone, and Custom.
• Translate is limited to English ↔ French only after both directions pass testing.
• Unsupported languages are rejected safely rather than silently guessed.
• Model download needs storage; deleting it removes AI until you download it again.

What permissions and diagnostics exist?

The keyboard needs the permissions Android presents for an input method. Keyline does not request a secret shortcut around those controls. Telemetry is off by default. If you opt into crash diagnostics, the diagnostic record is metadata only; source and generated text are not retained by default.

Open-source notices and licenses will ship with the beta. The release identifiers, supported Android range, and exact model hash will be recorded before distribution. No performance number is promised here before it is measured on a defined device.

What is not in this beta?

There is no cloud fallback, general chat, voice input, image understanding, document upload, custom model sideloading, team console, subscription billing, or cross-device history. Keyline is a writing action inside a keyboard, not a separate destination.

Before you download

Plan for roughly 1.5 GB of free storage before installing the AI model. The keyboard itself remains useful without the model, so you can enable it first and add local AI only when the setup screen and your phone are ready.

Use Wi-Fi for the model download if that is your preference. The beta setup is intended to show the artifact size, download progress, cancel action, retry action, and the space it occupies after installation. A cancelled or failed download must not leave you guessing whether AI is ready.

Deleting the model is reversible: it gives storage back and disables the AI transforms until you download it again. Your ordinary keyboard settings and non-AI typing should remain available while the model is absent.

Battery, heat, and control

Local inference is work your phone has to do. A short rewrite can use more power than ordinary typing, and repeated requests may make the phone warm. Keyline does not promise a fixed battery cost because it depends on the model, device, request, and thermal state.

You remain in control of when the model is used: choose a transform only when you need one, review the editable result, and insert it yourself. If the phone is warm, battery is low, or the result is not useful, keep typing without AI. There is no cloud fallback silently taking over.

The first beta is deliberately constrained rather than a general assistant. It is meant to help with focused writing actions, not to keep a conversation, monitor other apps, or run tasks in the background.

Languages and translation

Fix, Rewrite, Shorter, Tone, and Custom start with English. Translate is a narrower experiment: English to French and French to English only after both directions pass testing. The language boundary is shown in setup and in the action picker.

For an unsupported language, Keyline should reject the request clearly rather than silently produce a confident-looking guess. This is a limitation of the first beta, not a promise that every language is supported.

If something goes wrong

A local product still needs visible failure states. An unavailable model should leave the ordinary keyboard usable and explain how to retry the download. A rejected language should name the limitation. A full or low-storage device should be told what to free before trying again.

If the waitlist form cannot save in the browser, it shows an error instead of claiming success. You can enable site storage and retry, or use the download-and-restore request flow to keep a portable copy. The request contains a short email hash and consent metadata, not the email body.

If you choose to share a diagnostic record in the beta, it is optional and metadata-only by default. Keyline does not promise that the host app, Android, or every third-party keyboard behavior follows the same data policy; inspect those products separately.

What will be documented before release

The beta release notes will identify the supported Android range, exact model artifact and hash, open-source notices and licenses, permissions requested by the input method, and any known device-specific limitations. These details are intentionally not invented before a build is tested.

Keyline is not yet a released keyboard, and this page is not a download link. The waitlist is a request for a future launch note, not an account, purchase, or guarantee of access.