Who is responsible for your information?
WordEase AI is operated by Samuel Alexander Bennett, trading as WordEase AI, a UK sole trader and the controller of personal information handled to provide WordEase. Contact support@wordease.co.uk about privacy or your information. Our legal contact details are in the Terms of Service.
What happens on your device
Normal typing, local spelling assistance, Suggestions, personal learning, themes and keyboard settings work on your device. Suggestions can use the text around the cursor and locally learned words, names, email addresses and phrases to help you type. Personal learning is stored locally; it is not sent to our AI provider simply because you type.
Clipboard & Images uses Android clipboard access to offer copied text and image previews for pasting. Clipboard text history and pinned items are stored on your device. If you choose a Screenshots folder, WordEase uses the read access you grant to show relevant images from that folder. Pasting an image shares it with the receiving app; it does not submit the image to cloud AI. The receiving app handles pasted or sent content under its own policies.
You can manage local learning and clipboard items through WordEase’s settings and controls. Clipboard expiry follows your selected retention settings; pinned items may remain until you remove them. Deleting your online account does not itself erase local learning, clipboard history or files in your chosen folder. Android’s app-storage controls can remove WordEase’s local data. Files outside the app and content already pasted into another app are separate.
When text goes to cloud AI
AI Grammar, Rewrite, tones, Rewrite Strength 1–3, Translation and Ask AI use online processing. The text you submit, along with the selected mode, language and other settings needed for the request, passes through our Firebase/Google Cloud backend to OpenAI to generate a result.
Translation has an incoming-message workflow: while you have activated Translation, copying an incoming message can automatically submit that copied text for translation when AI access is available. Translating your reply submits the reply text. Ordinary local spelling does not use cloud AI.
Ask AI processes the question or text you type or paste. It does not automatically inspect the screen of the app you are using or identify products in images. Review what you submit, including information about other people, and avoid sending passwords, payment credentials or information you are not entitled to share.
Our implemented AI service processes message text and AI responses to complete your request but does not save them in its usage ledger or operational telemetry, or retain responses for later replay. This is different from claiming that no provider ever retains content. OpenAI may retain API content for abuse monitoring or legal purposes under its own controls. We request that completions are not stored as application history; this does not enable zero data retention. OpenAI states that API data is not used for model training by default unless the customer opts in. See OpenAI’s API data controls.
Your account and account emails
Firebase Authentication handles email/password sign-in, the account identifier, email address, verification status and authentication/session information. Passwords are passed to Firebase for authentication; WordEase does not put them in its usage records or saved account forms. Firebase processes credentials and technical connection information to secure accounts.
Verification, password-reset and relevant account messages are sent through Firebase Authentication. These are service messages. If you contact support, we receive your email address, message and any attachments you choose to send. Our support mail uses Fasthosts and Google’s mail services. Please do not email passwords.
Usage, purchases and security records
Our backend records account and random request identifiers, timestamps, AI feature/model, input/output usage counts, cost and allowance information, request status, failures and denial reasons. We use these records to operate Free, introductory and Pro access, prevent duplicate charges and requests, reconcile usage and understand aggregate service use and upgrades. These records are account-linked, not anonymous, but do not include message bodies, clipboard content, AI responses, inferred message topics or hashes of your text.
For Pro purchases, Google Play handles checkout and payment details. WordEase receives purchase identifiers/tokens, subscription plan and lifecycle information, such as renewal, expiry and cancellation status, to verify and associate access with your WordEase account. We do not receive your full payment-card details through this integration.
Firebase App Check and Google Play integrity services help verify genuine app requests. Authentication, hosting and cloud providers can process technical connection and security information, including IP addresses and service logs. Our own content-free telemetry does not mean those providers collect no technical data. The current Firebase project also permits Google to use Firebase Service Data for insights and improvements to non-Firebase Google services. Google distinguishes this service information from customer content.
Why we use information
We use account details, submitted AI requests and purchase information to provide the service you request and fulfil our contract with you. We use proportionate operational and security records for our legitimate interests in running a reliable service, preventing fraud and abuse, enforcing allowances and reconciling purchases. We use records where necessary to meet legal obligations. These purposes do not give us permission to retain unrelated information indefinitely.
Service providers and international processing
Google/Firebase provides authentication, backend hosting, database and integrity services; OpenAI processes submitted AI text; Google Play manages purchases; and Fasthosts and Google handle support email. Information may also be disclosed where legally required or necessary to protect legal rights. We do not sell your personal information.
Providers may process information outside the UK, including the United States. Google’s published Firebase privacy information describes its UK Extension to the EU–US Data Privacy Framework; OpenAI’s published data-processing addendum incorporates standard contractual clauses and the UK Addendum for UK data. Applicable provider agreements and UK transfer safeguards must cover those transfers; contact us for details or a copy of the relevant safeguards. See Firebase’s privacy information and Google’s Privacy Policy.
Retention and account deletion
You can request deletion through WordEase → Settings → Account → Delete Account, or use the email request route on our Account Deletion page. In-app deletion requires recent password confirmation and explicit confirmation. Once the backend records the request, it blocks new account/cloud AI access and removes the Firebase login. If removal cannot finish immediately, the request remains queued for completion.
The current implementation retains account-linked allowance, request, purchase, security and deletion records after login deletion. It does not immediately erase every backend record. Purchase ownership and financial reconciliation records help prevent an old subscription being transferred to a different account, including an account recreated with the same email address.
Retention must be limited to what is needed for outstanding transactions, reconciliation, security investigations, fraud prevention and applicable legal duties. The approved retention policy is 30 days for ordinary operational events and 90 days after reconciliation for settled request detail. On account deletion, eligible information can be removed sooner. Minimal records preventing replay of an old request, renewed introductory access or incorrect purchase transfer are separate from analytics. Necessary holds and unresolved liabilities prevent cleanup. The cleanup service is prepared locally but has not yet been activated for launch. Contact us to request deletion of associated data or to understand any necessary retention; records without a continuing justified purpose must be removed. Routine support correspondence and detailed deletion-case evidence are kept for 12 months after closure, unless a justified hold applies. A minimal marker can remain to prevent a deleted account being reactivated. Records needed for a sole trader’s tax return are normally kept for at least five years after the relevant 31 January filing deadline; this does not apply indiscriminately to AI telemetry. Provider-held records follow the providers’ applicable retention and deletion processes.
Deleting your WordEase account does not cancel a Google Play subscription. Manage or cancel it separately through Google Play.
One-time introductory access
To prevent another introduction being granted when an account is deleted and recreated, the launch service uses a keyed fingerprint of a verified email address. This is a protected matching value, not the email in readable form, but it remains personal data. We retain only the eligibility record while the one-time introductory offer exists and review its necessity annually. It is not used for marketing or to analyse your messages. A verified email is needed before a new introduction can be granted.
Your rights
Depending on the circumstances, UK data protection law gives you rights to access, correct or erase your information, restrict processing, object to processing based on legitimate interests, and receive certain information in a portable format. Where processing relies on consent, you can withdraw it. These rights have legal limits, including where records must be kept for a lawful purpose.
Email support@wordease.co.uk to exercise your rights. We may need to verify your identity without requesting your password. You can also complain to the Information Commissioner’s Office (ICO).
This website and policy updates
The website and Try WordEase simulator do not send simulator examples to the live AI backend or sign you into WordEase. The current site code contains no analytics or advertising trackers. Hosting providers may still process ordinary connection logs. Following an external link takes you to that provider’s service.
We will update this policy when our processing changes and make material changes clear. The date above identifies this version.