Your keyboard should not be a data pipeline.

This notice applies to the Glyder keyboard app, including its keyboard service and settings screens, and to the Glyder landing and waitlist website at glydertype.com.

It does not apply to other apps where you use Glyder to type. Those apps have their own privacy practices for the text, searches, messages, or forms you submit to them.

It also does not govern pages run by someone else that Glyder links out to. The feedback form (section 06) is hosted on Google Forms, so Google's own privacy policy applies to the page itself and to how they handle the request your browser makes to it. This notice covers what we do with a response once we receive it.

Text and gestures. As a keyboard, Glyder has to process characters, taps, and swipe paths so it can enter text and show suggestions. This processing happens on your device. Glyder does not keep a full record of everything you type.

Learned words. Words you type may be added to a local personal dictionary so future suggestions better match your vocabulary. You can review or delete learned words from Glyder's settings.

Touch calibration. Glyder may learn numeric touch offsets for keys to improve tap and swipe accuracy. This calibration data is not text content.

Phrase habits. To predict your next word, Glyder counts how often you follow one word with another, so a phrase you type constantly stops being corrected. Two limits on this, both deliberate. It is counts only: how many times two words followed each other, with no timestamps, no ordering, and no record of sentences, capped at a few thousand pairings and pruned to the ones you use most. And a pairing is only ever counted when both words are already in Glyder's built-in dictionary, so a name, an address, a medical term, or an account number cannot be stored at all, however often you type it. That is not because it is filtered out afterwards, but because there is no way for a word Glyder did not already ship knowing to enter. You can see how many pairings are held, and delete them, in Settings → Learned Words.

Clipboard. While Glyder is your active keyboard, it watches clipboard changes so its clipboard panel can offer recently copied text as a one-tap paste. Up to 20 recent items are held in the keyboard's memory and clear automatically after one hour, or when the keyboard process restarts. Recent items are never written to disk.

Pinned clipboard items. You can pin as many items as you like. This is a deliberate exception to the above: the point of pinning is that a snippet is still there tomorrow, so pinned items are saved to Glyder's private app storage and survive the one-hour clear and a keyboard restart. Only what you pin yourself is stored this way, it stays until you unpin or delete it, and Glyder never drops a pin on its own to make room for a newer one.

Sensitive clipboard content. Items the source app flagged as sensitive, and anything that looks like a payment card number, are masked behind dots until you tap to reveal them.

Password and sensitive fields. When another app marks a field as a password field, Glyder disables learning, suggestion generation, dictionary updates, autocorrect, and the on-screen swipe trail for that input. Nothing typed into a password field is added to your dictionary or calibration data, none of it is counted as a phrase pairing, your existing phrase habits are not even consulted there, and nothing about it is shown above the keyboard where it could be read over your shoulder.

Incognito and no-learning fields. Some apps ask keyboards not to learn from a field even though its text is ordinary and visible. Every field of an incognito browser tab, and many password managers, do this. Glyder honours that request. Suggestions, autocorrect, and everything else that helps you type carry on exactly as normal, but nothing that would outlive the field is kept: no word is added to your dictionary, no touch calibration is recorded, no phrase pairing is counted, and no emoji is marked as recently used.

Recent emoji. The emoji you pick are remembered so the ten most recent can be offered again on the quick-emoji row. They are stored in Glyder's private app storage on your device, and you can clear them by clearing the app's data.

This is the main thing the keyboard app sends off your device, so it is worth being exact about. When Glyder crashes, freezes, or hits an internal error, it records what went wrong and, unless you have turned this off, sends that record to Sentry (sentry.io, Functional Software, Inc.), an error tracking service acting as our data processor, where only we can see it. Reports are kept for 90 days and then deleted.

What a report contains. An error code from a fixed list we wrote; a stack trace of Glyder's own code (function names, file names, line numbers); a short trail of the error codes and Glyder settings-screen names leading up to the failure; numeric measurements from a fixed list, such as how many touch points a gesture had or how long an operation took; your device's manufacturer, model, CPU architecture, OS version, screen size and orientation, free and total memory and storage, and battery level; Glyder's own version; whether a session ended in a crash, which is what produces a crash rate per release; a snapshot of what Glyder's threads were doing if the keyboard froze; and a random identifier for your installation, generated by Glyder itself.

That identifier is not your advertising ID, not Android's device ID, not Apple's IDFV, not derived from any hardware or account, and is not linkable to you or to anything outside Glyder. It exists only so that one person hitting a bug fifty times is distinguishable from fifty people hitting it once.

There is exactly one such identifier, which matters more than it sounds. Reporting tools normally attach an identifier of their own alongside any you supply, and a second identifier you cannot reach would quietly defeat the reset below, because reports either side of it would still be linkable through the one that did not change. Glyder removes the identifier its reporting library generates and makes the library use Glyder's own instead. You can replace it at any time from Settings → Diagnostics → Clear, which takes effect immediately rather than at next launch, and nothing sent afterwards can be tied to anything sent before.

What a report does not contain. None of the following is ever sent: text you typed or swiped, touch coordinates, which keys you pressed, suggested or corrected words, your clipboard, your learned words, your touch calibration, your keystroke timings, the name of the app you were typing into, your IP address, your device's name, timezone, or locale, or any screenshot or view snapshot.

How that is enforced. On iOS, Glyder builds each report by hand and the report format has no field capable of carrying any of the above. On Android, Glyder uses the Sentry SDK (for automatic crash capture, freeze detection, and per-release crash rates, none of which are achievable by hand) and constrains it: the Sentry component capable of recording the screen is not included in the Android build at all, so no setting or future default can reach it; error message text is erased before sending, because a message is the one place a typed word could realistically end up; and the trail of prior events is filtered by an allowlist, so anything a future SDK version starts collecting by default is discarded rather than quietly sent. That is a weaker guarantee than the iOS one (code that runs, rather than a format with nowhere to put the data), and we would rather say so than blur the difference.

Reading it and turning it off. Crash reporting is on by default, because a keyboard that fails silently is a keyboard we cannot fix. Settings → Diagnostics lists every error recorded on your device in plain text, so you can check this page against reality rather than take it on trust, and switching off “Send error reports” there stops all uploads and discards anything queued. Glyder keeps recording locally so you can still read and share reports yourself.

Glyder Pro is sold through the App Store and Google Play. To know whether you own it, Glyder uses Adapty (Adapty Tech Inc.), which receives: a random identifier created on your device (not your name, email or Apple/Google account), your store purchase records for Glyder, your device model, operating system version, app version and language. Glyder turns off Adapty's collection of the advertising identifier and of your IP address. Nothing you type is ever sent. On iPhone, the 7-day trial is a free ($0) App Store purchase, so Apple and Adapty see that you started it. On Android, the 7-day trial is recorded only on your device.

On Android, Glyder's keyboard service requires android.permission.BIND_INPUT_METHOD. This is a system permission Android requires of any app that acts as a keyboard: it lets the operating system bind to Glyder's keyboard service, and it grants Glyder no additional access to your device or your data.

Glyder also requests android.permission.INTERNET, used for two things: uploading the crash reports described above, and checking your Glyder Pro purchase (see Purchases). If you switch crash reporting off, the only network connection Glyder makes is the Glyder Pro purchase check, which the Glyder app (never the keyboard) makes when you open it. The keyboard itself never connects to anything for purchases; it only reads the unlock state saved on your device.

Two more Android permissions give Glyder no access to your data. android.permission.VIBRATE lets keys give haptic feedback, and com.android.vending.BILLING lets the Glyder app buy Glyder Pro through Google Play. Glyder requests no other permissions on either platform. On iOS, the keyboard asks for “Allow Full Access”, which iOS requires for a keyboard to reach the network or share data with its own container app. Glyder uses it for crash reporting, for keeping your settings in sync between the keyboard and the app, and so the keyboard can see that you have unlocked Glyder Pro in the app.

If you submit the waitlist form, we collect the name and email address you provide. We use that information to send Glyder launch, availability, and early access updates.

Waitlist submissions are sent and stored on Google's services. The website may also generate standard hosting logs, such as request time, browser type, IP address, and requested pages, for operation, security, and troubleshooting.

Feedback form. Settings → Support in the app links out to a feedback form hosted on Google Forms. Opening it leaves Glyder and loads a page from Google in your browser, so it is Google, not the app, that receives the request. The keyboard itself sends nothing when you tap the link. What we then receive is whatever you chose to type into the form. Responses are stored on Google's services and are visible only to us.

The form does not require a Google account, and it does not require you to identify yourself. It has one optional email field, which exists for a single purpose: so we can reply to you. Leaving it blank is a complete, perfectly usable submission. The only thing you give up is a response. If you do fill it in, we use that address to answer your feedback and for nothing else: not a mailing list, not the waitlist, no marketing.

Otherwise, please treat the form as you would a public suggestion box: do not paste passwords, card numbers, or anything else confidential into it, because whatever you write is what we get. Feedback is used to decide what to build and fix, and nothing else.

The website currently loads fonts from Google Fonts. Your browser may contact Google to download those font files.

On-device keyboard data is used only to provide and improve your own typing experience within Glyder. It is not used for advertising, profiling, or cross-app tracking.

Waitlist information is used to communicate with you about Glyder, maintain the waitlist, prevent spam or abuse, troubleshoot the website, and comply with legal obligations.

Feedback you send through the form is used to understand what people want changed and to prioritise the work, and, if you left an email address, to reply to you. It is not merged with any on-device data, because there is nothing to merge it with: nothing about your typing ever leaves your phone, and the form records no identifier tying a response to an installation.

Learned words, touch calibration, and phrase-pairing counts are stored in a local database private to the app. On Android the app declares android:allowBackup="false", which means this data is deliberately excluded from Android's automatic cloud and device backup. It exists only on the device you are using, and is not copied anywhere when you set up a new phone. Recent emoji and pinned clipboard items live in Glyder's private preference store and are excluded from backup the same way.

Backups you make yourself. Glyder Pro includes Settings → Backup and restore, which exports your learned words, phrase-pairing counts, touch calibration, banned words, and a fixed set of Glyder settings as a single file. Glyder never makes this file on its own and never uploads it. You choose where it is saved (the system save dialog on Android, the share sheet on iOS), and from then on it is handled by whatever app or service you saved it to. Pinned clipboard items and the crash-report identifier are never included. Restoring a backup merges it into the data already on your device.

Local app data remains until you delete it through Glyder settings, clear the app's storage in device settings, or uninstall Glyder. Waitlist information and form feedback remain until they are no longer needed for the purposes above or you ask us to delete them, subject to any legal requirements. One consequence of the email field being optional is worth stating plainly: if you left an address, we can find your response and delete it on request, and if you did not, we cannot, because there is then nothing in the response to identify which one was yours. That is a reason to leave the field blank if you want no trace, and a reason not to put anything confidential in the form either way.

The Glyder app does not share typing data with us or with third parties. It transmits only the crash and error reports described in section 03, which go to Sentry as our data processor, and the purchase records described in section 04, which go to Adapty.

For the website, the waitlist, and the feedback form, we may use trusted service providers, including website hosting providers and Google services, to operate the site and store submissions. We may also disclose information if required by law or necessary to protect users, the site, or the Glyder project.

Glyder does not currently use Google Analytics, ad pixels, or behavioral advertising trackers on this landing page. We also do not currently respond to browser Do Not Track signals because the site does not use behaviorally targeted tracking.

If we add privacy-friendly analytics or other tracking technology later, we will update this notice to explain what is collected and why.

You can choose not to join the waitlist, and you can send feedback without leaving an email address. If you have joined the waitlist, or left an address on a feedback response, you can ask us to review, update, or delete that information. Depending on where you live, you may have additional rights under privacy laws that apply to your personal information.

In the app, you can review or delete learned words, reset touch calibration, unpin or delete pinned clipboard items, read and clear recorded error reports and turn reporting off, clear Glyder's app data, uninstall Glyder, or switch to another keyboard at any time.

Glyder is not directed to children, and we do not knowingly collect personal information from children through the waitlist website.

Glyder's local keyboard data is protected by your device's app storage sandbox and your device's security settings. We recommend keeping your device, browser, and operating system up to date.

Crash reports and purchase checks are sent over HTTPS, only to the configured Sentry and Adapty endpoints.

No electronic transmission or storage method can be guaranteed to be perfectly secure, but we aim to keep the data surface as small as possible.

We may update this notice as Glyder evolves. If Glyder's data practices change materially, we will update this page and change the "Last updated" date above.

Glyder is made by Tank Innovations, which is responsible for the information described in this notice.

Questions about this notice or Glyder's data practices can be sent to support@glydertype.com.