Support

No. Word Garner translates on the device first, using the translation engine built into your phone. That is free, works offline, and needs no account. An API key buys the things a machine translator cannot give you — the pronunciation, the short explanation, the example sentence, and made-up quizzes.

Open Settings ▸ AI service, choose a provider, and use the link there to open that provider’s console. Create a key in your own account, then paste it into the field — it saves itself. Test checks that it works.

Keys are pay-as-you-go and you are billed by the provider, not by us. Settings shows roughly what a hundred words costs on the model you picked. DeepSeek is the cheapest of the ones offered and is the default.

It is stored in the iOS Keychain or the Android encrypted preference store, on your device. It is sent only to the provider it belongs to, over HTTPS, directly from your phone. We never see it, and it is never included in diagnostics or backups.

Turn on Settings ▸ Capture ▸ Check a share before saving and every share opens a small sheet over the app you were reading, showing exactly what will be saved. Trim it to the word you meant and tap Save; the link is kept as the source and stays out of the field. It is off by default, because a share that lands without a word from anybody is what a share sheet is for — and a capture that arrived wrong can still be stopped and edited on the entry.

Reading apps do not agree on what a share contains. Kindle and Apple Books send the highlight with the book title after it, and Word Garner knows those shapes and keeps only the highlight. Other apps — Gospel Library among them — send a reference, the passage and a link, and nothing in the text says which part is which: “Mosiah 3:19” and the line beside it are both just lines.

For anything saved without trimming, Word Garner asks rather than guesses. A share it cannot read on its own waits on the home screen; tap it, pick the part you meant to keep, and the rest becomes the entry’s source, so the reference is not lost. Links are always dropped, and the app they point at is used as the source name where it is one we recognise.

Yes. Open the entry and tap Stop on the “Translating…” row. The entry stays, the reply is discarded even if it arrives afterwards, and the word can then be edited — which is not possible while a translation is in flight — and asked for again. This is the way out of a capture that arrived wrong: stop it, fix the text, retry.

A single capture is held to 600 characters — two or three sentences, which covers any highlight worth keeping as vocabulary. Sharing something longer is refused at the moment of sharing, with a message saying so, rather than saved and left untranslatable. The add screen shows its own, usually lower, limit as you type: that one depends on the model and the number of languages you chose, because the whole capture is reproduced once per language in the reply.

The same reasoning caps the other direction. A reply from a translation service is read up to 256 KB and refused past it, and each stored field — the translation, the pronunciation, the explanation, the example — is cut at its own limit. None of that affects an honest answer, which is thousands of times smaller. It is there so that a model stuck in a loop, or an endpoint answering with something that never ends, cannot fill the app's memory or grow the database without limit.

A capture that is too long for the model you chose comes back cut off. The app refuses an over-long capture while you are typing it and says what the limit is — shorten it, capture it in pieces, or choose a model that writes more. If a request simply failed, the entry keeps a retry button.

Writing a quiz means writing every question in every language in one reply, so a minute or two is normal. If it fails, ask for fewer questions. Remember that a made-up quiz is answered in one language by design.

Settings ▸ Data exports the whole vocabulary as a JSON file, or as an Anki deck. The JSON can be imported back into Word Garner on another device; importing never overwrites or deletes anything, it only adds what is missing.

The app writes periodic backups into its own folder on the device and keeps the last few. Those are local: if you lose the phone, they go with it. For a real backup, export to JSON and keep the file somewhere of your own.

Not for anything the app does today. A hosted engine, and hosted storage that survives a change of phone, are being considered for later; those would need one. They would be options alongside the device and your own API key, never a replacement, and the privacy policy is updated before any of it ships.

Delete individual words by swiping them away in the list, or uninstall the app to remove everything at once — vocabulary, settings, local backups and your stored API key. Nothing is held on any server, so there is nothing left behind.

Detection is a guess, and a word can belong to more than one language (Gift is German for poison). Open the word and use Language: … — change; the app records it as your decision and translates again, and nothing overrules it afterwards.

Yes, please — the report form, or the email address above. Concrete cases help most: the word you captured, what you expected, and what you got.