1. What does the app do?
Güven Braille Keyboard is a keyboard app that enables Braille typing on Android devices. The app converts Braille input into text, provides audio feedback, and aims to offer an accessible Braille typing experience when TalkBack is enabled.
2. What permissions does the app request?
In its core version, the app does not request common dangerous Android permissions such as location, contacts, camera, microphone, SMS, or file management permissions.
The core version of the app also does not request internet permission.
Keyboard activation
This is required for an Android input method app to enter text. The Braille keyboard can write text into edit fields only after it is enabled as a keyboard.
Accessibility service
This is required to show the Braille overlay while TalkBack is enabled and to support an accessible typing experience.
This service is used to display the Braille surface, provide necessary audio feedback, and support the accessible typing flow.
This service is not designed to control the device generally, run hidden automation, or perform actions without the user's knowledge.
3. What does the app ask for during first setup?
During the first setup screen, the app clearly informs the user that it works offline, that typed content is not sent outside the device in the core flow, that dangerous Android permissions are not requested, and that only keyboard activation and the accessibility service are required.
4. Does the app use the internet?
The core typing flow of the app is designed to work offline. In the current version, internet permission is not requested, typed text is not sent to a remote server in the core workflow, and Braille translation, feedback, and field behavior are processed on the device.
5. What data is processed on the device?
The app processes some data on the device as part of its core functionality. This may include typed text, active field context, Braille cells and their conversion into text, and events required for audio feedback.
This processing is necessary to provide the typing experience. Passwords, credit card and banking information, private messages, and conversations are processed on the device in the core typing flow and are not automatically sent outside the device.
6. What data may be stored on the device?
The app may store local data such as selected Braille profile and typing preferences, touch, swipe and multi-touch settings, calibration information, screen dimming and privacy preferences, password field feedback mode, and user-defined shortcuts.
This data is stored so the app can function properly.
7. Diagnostics and issue reporting
The app may keep limited technical diagnostic logs for debugging and product stability. These logs may include technical information such as where settings were loaded from, IME and accessibility lifecycle events, commit, delete or link failures, and session traces in debug mode.
These logs are not automatically sent outside the device. A diagnostic report may be copied to the clipboard, shared by the user, or exported through the issue reporting flow with a short note. This sharing happens only when the user explicitly starts it.
The diagnostics and issue reporting flow is not designed to automatically export sensitive typed content.
8. Is data shared with third parties?
Based on the current core behavior of the app, typed content is not shared for advertising or marketing purposes, the core typing flow does not depend on a remote server, and there is no automatic cloud synchronization flow.
If third-party SDKs or services are added in the future, this privacy policy and the Google Play Data Safety declaration will be updated accordingly.
9. How can you delete your data?
Users can remove local data by uninstalling the app, clearing the app data, or using relevant reset options inside the app.
10. Children
This app is not designed as a product specifically targeted at children.
11. Contact
For privacy and support questions, you can contact us at: