Responsibility and scope
This policy covers the Keybordia app, its iOS keyboard and the Messages extension. It describes processing carried out by the app and information that may be transmitted when a network feature is requested.
For questions or requests concerning data processing, users can contact support through the contact form.
This policy should be read alongside iOS settings and the information displayed at the time of each action. A new feature that changes the data used, recipients or purposes will require an update to this page before its public deployment.
Entered and generated data
When users request suggestions, Keybordia transmits the text provided, selected mode, optional intent, tone, length and, where applicable, the suggestion and requested adjustment to be rephrased. The keyboard may transmit context text accessible in the field if the user launches an AI request from the keyboard.
In conversation mode, entered messages and generated replies are saved locally on the device. To respond, the app may include recent conversation messages in the request. The keyboard may transmit the accessible context of the field being used. Transmission takes place only after a generation action by the user and their explicit consent given in the app.
Suggested texts and selected reactions can be copied or inserted at the user's request. Keybordia does not send a message to the recipient on the user's behalf; the third-party app being used then controls sending.
Clipboard and keyboard
The clipboard is read only when the user taps the corresponding paste command. Pasted text is placed in the composition field so the user can review, edit or delete it before any generation.
The keyboard inserts the characters the user taps. Field context may be accessible to the extension depending on iOS, the field type and enabled permissions; it is not collected for AI assistance without a generation action by the user.
Full Access to the keyboard may be necessary for network features and must be enabled by the user in iOS settings. Secure fields or certain apps may hide their contents from third-party keyboards; Keybordia cannot bypass these system restrictions.
On-device storage
The app's conversation history is saved in a local file protected by iOS file protection mechanisms. It is retained until deleted through the interface or until the user deletes the app's data.
Language, theme, background, favorite and reaction preferences are stored locally or in the shared group between the app and its extensions. The personal API key, when used, and the random device identifier are stored in the shared iOS Keychain.
Deleting a conversation from history removes that conversation from Keybordia's local storage. It does not retroactively delete data already transmitted to a provider to process a request.
Recipients and AI processing
Before using an AI feature, users choose in the app whether to authorize transmission of the texts they select. This choice is saved on the device and shared with the keyboard extension; without consent, AI features transmit no requests. Consent can be withdrawn in the app settings. Other keyboard features remain available.
When generation is requested, Keybordia transmits to a function hosted by Supabase the text provided or selected, the mode and, depending on the feature, recent context, intent, tone and length settings. Accessible field context may be included when the request is launched from the keyboard. The function forwards the necessary prompt to OpenAI to produce suggestions.
A personal OpenAI API key, if configured by the user, is stored in the iOS Keychain and transmitted to the Supabase function for the relevant call. It is also sent directly to OpenAI when the user requests its verification. Its use may result in direct billing by OpenAI depending on the user's account and terms. Supabase also receives the connection's IP address to apply the shared limit, a random installation identifier for per-device quotas and, for certain subscriptions, proof of a StoreKit transaction.
AI requests are processed by Supabase and OpenAI to provide the requested suggestions. Processing by these providers is subject to their privacy policies and service settings.
When users send a request through the support form, their name if provided, email address, subject and message are sent to us so our team can respond.
Purposes, safeguards and limitations
Data is used to provide requested features, return generated texts, apply usage limits, save conversations locally, respond to support requests and maintain the security and technical operation of the app and website.
The client code currently in the repository does not declare any third-party advertising or analytics SDK. Any operational logs produced by hosting or AI providers must nevertheless be documented based on production configurations before the final public launch.
Reasonable safeguards are implemented, including iOS-protected storage and encrypted network transport provided by HTTPS services. However, no system can guarantee absolute security; users should avoid sending secrets or unnecessary sensitive data.
User choices and rights
Users choose whether to authorize AI features in the app. They can withdraw or restore consent in settings; without consent, no text is sent to AI services. They can also use the keyboard without AI, erase a draft, delete a conversation, remove their personal key in the relevant settings and uninstall the app.
Depending on their place of residence and applicable rules, users may have rights of access, rectification, erasure, objection, restriction or portability regarding personal data. To exercise these rights, they can contact support through the contact form.
A request concerning data transmitted to a provider may require verification with that provider and does not automatically delete logs retained by providers as part of their services.
Updates and contact
This policy may be updated when features, providers or legal obligations change. The last revision date is shown at the top of the page so users can identify the version they are reading.
In the event of a significant change concerning data or its use, the publisher will indicate that change in the app or by appropriate means where required. Use of a feature remains subject to the choices and permissions displayed by iOS.
To exercise a right or ask a question, users can contact support through the contact form.