FAQ

No. Full Access is optional and off by default. It's required only for clipboard history, since reading the system clipboard needs it, and for keyboard haptics/paste. Typing, Japanese conversion and themes all work without it.

Only clipboard history and haptics/paste, as above. Full Access doesn't unlock anything else, and it doesn't give the keyboard network access either — it still has none, with or without it.

It checks only whether the clipboard changed, never what's in it, until you tap the capture control in the clipboard tab. That's the one moment the value is actually read — and it's the same moment that triggers iOS's own "Allow Paste" system prompt.

No. Any field iOS marks as secure disables the capture control entirely — there's nothing to tap.

No. There's no analytics, no advertising, no tracking SDK of any kind, and nothing gets sent anywhere for the simple reason that the extension has no networking capability at all.

Yes, with no ads and no subscription or in-app purchases at this time.

No. There's no sign-in anywhere in Copaky, in the keyboard or in the companion app.

Clipboard history lives only on the device that created it, by design. Without a cloud account, moving to a new phone doesn't bring it along.

Japanese, using azooKey's kana-kanji conversion; English, with a QWERTY layout; and Italian, which you can enable to get suggestions from an Italian dictionary on the Latin tab (full word prediction is still on the roadmap). Long-press also types accented characters for French, Spanish and other languages that share the Latin alphabet.

It adds Italian to the language-switch key's cycle and starts suggesting words from an Italian dictionary on the Latin keyboard. The key layout itself doesn't change — the accented-character long-presses were already there.

Not yet. Today, Italian gets suggestions from an Italian dictionary once "Use Italian" is on, plus the long-press accents — see Roadmap.

Copaky offers completions from the system's own English word list rather than a separate autocorrect engine layered on top — see Features for the distinction. If you do want typo fixing, an optional, experimental setting (off by default) corrects common English and Italian slips when you press space.

Nowhere but your device. Conversion happens entirely on-device, and Copaky has no code path that sends keystrokes anywhere.

In a private, app-only storage area on your device — an "App Group" container shared only between the Copaky app and its keyboard extension. It's never synced or uploaded anywhere.

A single item is capped at 50,000 characters (256 KB). Anything larger is silently skipped — not stored, and not cut off into something partial.

No. There's no crash-reporting or analytics SDK in Copaky at all.

No. Copaky is an independent fork of azooKey — credited, and grateful for it — but not affiliated with, endorsed by, or officially connected to the azooKey project. See Credits.

Not yet. Copaky is pre-release and still in active development; this site describes the current state of that work, not a shipped product.

Yes — Copaky is developed as an open-source project under the MIT License, the same license azooKey uses; the source is public at github.com/pettipol/copaky.

That's what Features is for. This FAQ sticks to the "why" and "what," not the step-by-step.