Privacy policy.
In plain English.

1. The short version

FliqKey does not upload your typing or learned keyboard data to us. We do not receive, sell, or use that on-device data for advertising. Visiting this website or contacting support involves separate data handling, described below.

2. What stays on your device

FliqKey processes text context and keyboard input locally to provide typing, suggestions, corrections, and swipe recognition. To personalize these features, it may retain:

• Learned or approved words, protected spellings, replacement rules, correction preferences, and word-level correction history.
• Aggregate word and short-context usage counts, touch calibration, confirmed suggestion and swipe choices, and personal model parameters.
• Swipe practice words and simplified gesture shapes that you explicitly save. Ordinary typing does not save raw swipe trails.
• Keyboard settings, saved layouts, emoji recents and favorites, and your selected skin tone.
• Snippets and text expansions you explicitly save, including any personal information you choose to put in them.

Full messages and sentences are not automatically stored as a typing history. Temporary input context and deletion-recovery text are used in memory for editing. Snippets are different: they contain the text you deliberately save.

FliqKey does not collect clipboard contents or directly access your address book. iOS may supply names or shortcuts through its supplementary keyboard lexicon; FliqKey keeps that cache temporarily and excludes it from Private Session.

3. App and keyboard storage

The companion app’s playground and the system keyboard maintain separate private learning stores. The app cannot read or erase the system keyboard’s learned data.

The app can make configuration, imported words, explicitly shared protected spellings, and optionally saved swipe practice examples available to the keyboard through local storage shared between the two. This sharing stays on your device. The keyboard does not write its private learning back to that shared storage.

Turning off sharing stops future sharing when the keyboard reads the updated settings. Removing a shared word does not necessarily remove a copy already learned by the keyboard; use the keyboard’s own Forget or reset controls as well.

Private learning files use iOS file protection and are excluded from device backups. These protections reduce exposure; no storage system can guarantee absolute security.

4. Your controls, retention, and deletion

Learning records remain in local storage until you remove or reset them, or the app’s bounded storage and aging rules remove or update them. FliqKey does not keep a server copy of your keyboard learning.

• Pause automatic learning: open the keyboard’s sliders menu → Learning & privacy and turn off Learn from my typing.
• Start a Private Session: use the controls overview. This pauses learning and correction history and clears temporary input state when the session ends. It does not erase existing saved learning.
• Manage individual memories: open Learning & privacy → What FliqKey remembers to review, edit, or remove saved spellings, rules, and swipe examples.
• Reset learning: open Learning & privacy → Reset learning to clear a category or choose Reset all learning. Some resets also reset related personalization so removed words no longer influence it.
• Remove saved content: delete snippets, shared spellings, or saved practice examples in their respective controls.

Apply these controls separately to the playground and system keyboard when you want to clear both. Because we cannot access their private stores, support cannot remotely retrieve or delete your local learning.

5. iOS and the apps you type into

The app receiving your text controls how it uses, stores, or transmits that text. FliqKey’s Private Session does not change that app’s behavior. Apple’s services and other apps have their own privacy practices.

Secure fields normally use Apple’s keyboard. FliqKey also disables learning for credential and payment field types and filters likely sensitive tokens. These safeguards cannot recognize every possible secret, so avoid deliberately saving sensitive information in words, rules, or snippets.

6. This website

The web playground keeps entered text in page memory. It does not send that text to a FliqKey service or save it to browser storage. Reset clears the demonstration; reloading or leaving the page discards it. The web demonstration does not use the native learning engine.

This website does not add advertising trackers or behavioral analytics. Its hosting provider processes the connection and request information needed to serve the site, which may include your IP address, browser information, requested URL, and request time. Hosting or error-reporting services may retain diagnostic logs for operation and troubleshooting. These records are separate from native keyboard learning.

7. Messages you send to support

If you email us, we receive your email address, message, and any attachments you choose to send. Our email service providers process this correspondence to deliver and store it. We use it to answer your request and investigate issues you report, not to personalize your keyboard.

We retain support correspondence as needed to handle your request, follow up on issues, and meet applicable legal obligations. You can contact us to request access to or deletion of correspondence you have sent.

Please do not send passwords, private conversations, or other sensitive information. Hide personal text in screenshots before attaching them.

8. Privacy questions and requests

Contact Bylt by Zac at hello@byltbyzac.com with questions about this policy or requests concerning information you have sent us. Mention FliqKey so we can identify the product you are asking about.

For data stored only on your device, use the controls described above. For information you send to support, we may need to confirm that a request comes from the sender before providing or deleting correspondence.

9. Updates to this policy

We will update this page and its last-updated date when FliqKey’s privacy practices change. This policy describes the current development version; changes to features or services will be reflected here.