Inkboard privacy policy.

The short version

• Typing, glide decoding, autocorrect and personal learning run on your device. We do not receive a stream of your keystrokes.
• Handwriting recognition runs locally after a language-model download. Google’s ML Kit also collects technical diagnostics, described below.
• Voice recognition may send audio to your device’s speech-service provider. Optional AI tools send text only when you choose an AI action: directly to your selected provider with your own API key, or through Inkboard’s server to Anthropic with managed beta access.
• You do not need an Inkboard account. We do not sell your personal information or use your keyboard content for advertising.

Keyboard access and personal learning

When you enable and use Inkboard, it handles key presses, glide gestures, text you enter, corrections, and text the focused editor makes available around the cursor. This supports text entry, punctuation, suggestions and editing. It does not use an accessibility service to read other apps. Text you insert is passed to the app you are writing in, whose own privacy practices then apply.

Personal learning saves words, word sequences, casing preferences, correction patterns and useful phrases locally. This can include names or email addresses that you type. Accepted handwriting and dictation can contribute to this learning; AI-generated output is excluded from the normal personal-learning model. The personal dictionary is encrypted on your device and is not uploaded to us or sent as a dictionary to an AI provider.

Inkboard refuses AI outright in password, passcode and payment fields, regardless of settings and regardless of how you arrived at the field. Nothing typed in such a field is sent anywhere.

Handwriting and Google ML Kit

Inkboard processes stylus stroke positions and timing, the writing area, and a small amount of preceding text using Google ML Kit Digital Ink Recognition. Recognition takes place on your device; handwriting strokes are not sent to an AI writing provider for recognition. Google supplies the language model through an internet download.

The ML Kit SDK collects technical data for Google’s diagnostics and usage analytics: device and app information, installation or device identifiers, configured language, feature configuration and version, input/output sizes, performance measurements, events and error codes. This is separate from local recognition of your writing. See Google’s ML Kit data disclosure and Google’s privacy policy.

Voice dictation

Dictation uses microphone permission and Android’s configured speech-recognition service, which may be provided by Google or another provider. That service receives your speech and may process audio online, along with technical information needed to provide recognition. Offline processing is not guaranteed; the provider’s settings and privacy policy apply.

Inkboard receives the recognised text for review, editing and insertion. It does not save audio recordings itself. Continuous dictation can listen across several phrases until you stop it. You can stop dictation with the microphone control or revoke Inkboard’s microphone permission in Android settings. Sending a transcript to AI is a separate action.

Optional AI writing tools

AI tools are optional. You can use your own provider API key or, if you are a closed-beta tester, Inkboard-managed access. AI is refused outright in password, passcode and payment fields, regardless of settings and regardless of how you arrived at the field. Nothing typed in such a field is sent anywhere.

Using your own API key

This mode supports Anthropic and OpenAI and is unchanged. When you choose an AI action such as Rewrite or Ask AI, Inkboard sends your preview text or instruction, the requested action, model choice, and the device’s current date, time and time zone directly to that provider over HTTPS. Your API key authenticates the request, and the provider also receives connection information such as your IP address.

Share focused-field text is off by default. If you enable it while using your own API key, AI requests can also include surrounding and selected text exposed by the current editor, the host app’s package name, and the field hint. This setting controls extra context in the own-key mode; turning it off does not prevent the preview text itself from being sent when you use AI.

Your provider API keys are never compiled into the app. On your device, they are held in Android’s EncryptedSharedPreferences. Requests in this mode do not pass through Inkboard’s server, and Inkboard’s server records nothing about them. Read Anthropic’s privacy policy and OpenAI’s privacy policy, and check your provider account settings before sending sensitive text.

Remove saved keys in Inkboard settings to stop using the corresponding provider. Removing a key does not revoke it at the provider or delete requests already sent.

Inkboard-managed access during the closed beta

Inkboard-managed access is the default AI mode for closed-beta testers. A tester redeems a one-off invitation code; there is no account, email address or password. Inkboard’s server then issues a device token. The token is stored on the server only as a SHA-256 hash, never in plain text, and expires after 60 days. Per-user usage limits apply, and the beta service may be limited, paused or withdrawn.

In this mode, text is sent only when you deliberately tap an AI action: Rewrite or Ask AI. Ordinary typing, swipe/glide typing, handwriting recognition, autocorrect and word prediction run on your device; they do not transmit your text.

The app sends only:

• the selected text;
• the name of one operation: rewrite, grammar, tone, shorten, expand, reply or instruct;
• a random per-request identifier; and
• an access token issued by Inkboard’s server.

The surrounding contents of the text field are not sent in managed access. The extra focused-field context described for the own-key mode is not sent in this mode.

The request travels over HTTPS to Inkboard’s server, which runs on Cloudflare Workers with a Cloudflare D1 database. Cloudflare processes the request in transit as Inkboard’s hosting provider. Inkboard’s server receives your text, adds its own instructions and forwards the text over HTTPS to Anthropic’s API at api.anthropic.com, using Inkboard’s credentials and the claude-haiku-4-5 model. Anthropic generates the reply. In this mode, Inkboard processes your text as well as Anthropic, and Inkboard’s developer pays the cost rather than the tester.

Before the first AI request, Inkboard shows a panel explaining that the selected text will leave the device, and you must accept before anything is sent. If you decline, nothing is sent and typing, swipe, handwriting and dictation continue to work normally. Declining is not remembered, so Inkboard asks again the next time; accepting is remembered.

HTTPS provides TLS encryption in transit. The text is readable by Inkboard’s server and by Anthropic. Requests are pseudonymous, not anonymous: they are linked to a per-installation identifier and a hashed access token. See Anthropic’s privacy policy and Cloudflare’s privacy policy.

We store usage metadata, a short-lived copy of the AI’s reply, and invitation-redemption records separately. Their contents and different retention periods are described under managed-beta retention and deletion below.

You can switch to your own API key or disable cloud AI entirely in Inkboard Settings. The rest of the keyboard works without cloud AI, including typing, glide typing, handwriting recognition and personal learning.

Clipboard, emoji and settings

Clipboard history is enabled by default. While Inkboard has access to the system clipboard, it can keep recent text clips in encrypted local storage so you can paste them again. It skips clips marked sensitive by Android and filters some obvious authentication codes and secret patterns, but these checks cannot detect every sensitive item.

Unpinned clips expire after one hour and are removed when history is next checked. Pinned clips can remain longer, subject to the history limit. You can delete individual clips, clear the history, or switch history off, which also clears it. Clearing Inkboard’s history does not necessarily clear Android’s current clipboard or another app’s copies.

Inkboard also stores preferences, the last input mode and recent emoji usage locally. Recent emoji are kept in app-private preferences; the personal dictionary, clipboard history and saved API keys use encrypted storage.

Support messages and this website

If you contact us, we receive the name, reply email, subject and message you provide, plus any information you choose to include. We use these to answer you, investigate problems and improve Inkboard. Do not send passwords, API keys or private writing samples.

The app’s bug-report feature prepares an email draft in your email app, or offers a copyable report if no email app is available. Bug reports can include Inkboard and Android versions, manufacturer and model, screen dimensions, input mode and the last AI error details. Review the draft before sending; it is not an automatic upload of your keyboard history.

The website contact form uses FormSubmit to deliver messages to our Gmail inbox. Its reCAPTCHA spam check can process browser, device and network information and use cookies. FormSubmit retains submissions for 30 days in its submission archive; this does not set the retention period for messages delivered to our inbox. See FormSubmit’s privacy policy and Google’s privacy policy.

Cloudflare hosts this website and processes connection and request information, such as IP address, requested page and browser details, to deliver and protect it. It also hosts and processes requests for Inkboard’s managed-beta AI server, as described above. Pages using Google Fonts also contact Google to load their typefaces. This privacy-policy page uses local system fonts. See Cloudflare’s privacy policy and Google Fonts’ privacy information.

Security and when information is shared

Inkboard’s provider requests, managed-beta server requests and this website use HTTPS. Sensitive local stores use Android-backed encryption, and the app disables standard Android cloud backup. Device-manufacturer transfer or backup tools may behave differently. No device, storage method or network connection can be guaranteed completely secure.

Text you insert is shared with the app you write in. Information is sent off the device for the services described above: handwriting diagnostics and model downloads, online speech recognition, optional AI, and website hosting and message delivery. Those services may process data outside your country. Their policies explain their own retention and international processing.

We use support information to administer enquiries and fix problems, not to build advertising profiles. We may disclose information we hold if required by law or necessary to address fraud, security threats or protect legal rights. We do not receive or centrally store your on-device personal dictionary or clipboard history.

How long information is kept and how to delete it

• Learning: local words, phrases and correction statistics remain until cleared or pruned by the app. Use Clear everything Inkboard has learned in Inkboard settings to reset them.
• Clipboard: use the individual delete or clear-history controls. Unpinned entries use the one-hour expiry described above; pinned entries do not have that expiry.
• Keys and preferences: remove saved API keys in Inkboard settings. Android’s Clear storage / Clear data control, or uninstalling Inkboard, removes its app-local stores, including recent emoji. Device backups, provider records and text already inserted into another app are separate.
• Writing previews: strokes and draft text are working data for the current editing session. Clear or discard previews when finished. Accepted text may remain in the destination app and contribute to local learning as described above. The separate stored copy of a managed-beta AI reply is described below.
• Support: we retain correspondence only for as long as needed to respond, investigate the related issue and meet applicable legal obligations. When it is no longer needed, we delete it. You can request earlier deletion; if a legal obligation requires us to retain part of it, we will explain this.
• Third-party records: deleting local app data does not delete information already processed by Google, a speech service, an AI provider or another app. Use that service’s privacy controls or contact it about those records.

Managed-beta usage metadata — 90 days

We retain managed-beta usage metadata for 90 days. An hourly cleanup job deletes usage rows older than 90 days. Each usage record contains:

• a SHA-256 hash of the device’s access token, not the token itself;
• which operation was used;
• which AI model was used;
• counts of input and output tokens;
• the estimated cost;
• the response time;
• whether the request succeeded, and an error category if it failed; and
• a timestamp.

The prompt text and the AI’s reply are not stored in this usage record. There are no database columns for them in the usage record.

Short-lived stored copy of the AI’s reply

Separately, we store a short-lived copy of the AI’s reply, not the user’s input, so that retrying a failed or duplicated request returns the same answer instead of generating a second one. This stored reply stops being used after five minutes and is deleted by a cleanup task that runs hourly, so it may persist for up to approximately one hour before deletion. The 90-day usage-metadata period does not apply to this stored reply.

Invitation-code records — until the beta ends

We also store the invitation code a tester redeemed, the random installation identifier the app generates for that purpose, and the date it was redeemed. We keep these records for the duration of the beta so access can be revoked, and delete them when the beta ends. They are not covered by the 90-day usage-metadata period.

To request deletion of usage metadata associated with your access token, contact Inkboard, use “Privacy request” as the subject, and say that you want your managed-beta usage metadata deleted. Do not include your access token, API keys or private text in the message. Clearing local app data or uninstalling Inkboard does not delete these server records.

Your choices and privacy contact

You can leave AI unconfigured, switch from managed access to your own API key or disable cloud AI entirely in Inkboard Settings. The rest of the keyboard works without cloud AI. You can also keep focused-field sharing off in the own-key mode, decline microphone permission, disable clipboard history, clear learned information, switch keyboards or uninstall Inkboard. There is no Inkboard account to delete; managed-beta server records are separate and are described above.

To ask about information we hold, request access, correction or deletion, or raise a privacy concern, send us a note through the Inkboard contact page and use “Privacy request” as the subject. Include only enough detail to identify your earlier enquiry or beta invitation, not your access token or API keys. We cannot remotely read or erase data stored only on your device, but can help you find the relevant controls. Depending on where you live, you may also have rights to object to processing or complain to your local privacy regulator.

If you believe a child has sent us personal information through support, contact us so we can address it. This policy does not replace a service provider’s age restrictions.

Changes to this policy

We will update this page and its date when Inkboard’s data handling changes. Material changes that require notice or consent will be explained before the relevant processing begins.