Privacy Policy
Last updated 15 October 2026
- We keep your email, a hash of your password, your plan, and your usage this month — not the text, questions or pictures you send.
- What you send goes to one of our AI providers only when you press something that needs an answer, and only to make that answer.
- Most of Fevle runs on your computer. What you copy, paste, snip or share is never sent to us — only a daily count of which buttons you used, as the Terms of Service say.
- No ads, no trackers, no selling of data. The website sets no cookie until you sign in.
- To keep accounts safe we record sign-ins and other security events, with the IP address and browser they came from, for 90 days — and you can see your own on your account page.
- You can delete your account, and what we store about it, yourself, at any time.
- Who we are
- What we collect, and why
- What you send for an answer
- What stays on your computer
- Who else handles it
- Where it is processed
- Legal bases
- How long we keep it
- Your rights
- Security
- Children
- Changes, and contact
1. Who we are
Fevle is run by [LEGAL_NAME is not set] ("we", "us"). We are the controller of the personal data described here. For anything in this policy, write to [CONTACT_EMAIL is not set].
This policy covers the Fevle app for Windows and macOS, the Fevle service it talks to, and this website.
2. What we collect, and why
We collect only what is needed to run your account and the online features. In full:
| What | Why | Kept |
|---|---|---|
| Account: your email address and whether you have confirmed it, a one-way hash of your password (never the password itself) and when it was last changed — if you made the account with Google and have not added a password, there is none, when the account was made and last signed in to, the language Fevle shows, and when you agreed to the terms. With your address we keep its plain form — for a Gmail address, without its dots or anything after a +, so that [email protected] is kept as [email protected] beside it; we mail only the address you gave. | To sign you in and run your account, and so that one inbox has one account: a new account is not made for another spelling of an address that already has one. | Until you delete the account. |
| Signing in with Google, if you use it: your Google account's ID, and the email address Google gave us the last time you signed in with it. We ask Google for your email address only — not your name, picture, contacts or anything else — and we never see your Google password. | To recognise you when you sign in with Google, and to show you on your account page which Google account is connected. | Until you disconnect Google on your account page, or delete the account. |
| Sign-in security: if you turn on two-step sign-in, its secret (encrypted) and your recovery codes (as one-way hashes); how many wrong passwords were typed since the last right one, and — if pausing sign-in after too many is turned on — until when it is paused; whether the account is active, suspended or closed, and the reason you were given. | To protect your account from somebody who has, or is guessing, your password. | Until you delete the account, or turn two-step sign-in off. |
| Security events: accounts made, sign-ins (with a password or with Google), wrong passwords, pauses, password, Google and two-step changes, computers approved, sign-in tokens presented again or from another machine, and sign-ups refused because the network had made its new accounts for the day — each with the time, the IP address and the browser it came from. | To protect your account and the service, to show you your recent activity on your account page, to investigate abuse, and to limit how many new accounts one network can make in a day, so the free plan is one each. | 90 days, then deleted; and until you delete the account, if sooner. One exception: when an account made in the last day is deleted, the time it was made and the IP address it was made from are kept, with nothing else, until that day is over, and deleted within a day after — so deleting an account does not make room for another. |
| Links and codes we mail you: one-way hashes of the link and code that confirm your address or reset your password. | To check them when you use them. | Until used or expired (a day at most), then deleted within a day. |
| Support requests: your address, what you wrote to us and our answers, and our team's notes on the request. | To answer you, and to remember what was said. | Two years after the request was last touched, then deleted; and until you delete the account, if sooner. |
| Our team's records: notes and labels our team keeps about your account when helping you, offer codes you used, and a log of every change our team makes to an account — who made it, when, and what changed. | To help you consistently, to honour offers, and so that every change our staff make can be checked afterwards. | Notes and offers until you delete the account. The change log is kept as a permanent record of our own staff's actions; it keeps only the address the account had, and nothing else about you. |
| Plan and usage: your plan, its current period, how much of that period's usage you have used, and Paddle's customer and subscription IDs and status. | To give you your plan's usage and keep billing in step. | Until you delete the account. |
| Billing: the card your plan is charged to as Paddle describes it — its brand, last four digits and expiry month, never its number; each payment, refund and credit — when, how much, the tax, what it was for, and Paddle's reference and invoice number; any credit our team gave you; and, if you cancel a plan, the reason you chose and anything you wrote, if you gave them. | To show you your payments and receipts on your account page, to help when you ask about a payment, and to learn why people cancel. | Until you delete the account; a reason for cancelling, until you keep the plan or buy one again. |
| Usage records: for each request that counts as usage — when, which feature or action, how many units it took and what it cost. Not what the request said or what came back. | To measure your usage, and to check our prices against our costs. | Until you delete the account. |
| Feature counts: for each day, how many times you used each of Fevle's buttons, the choices on its cards, its snip editor, its tray menu and your shortcuts — for example "Copy, 12 times on 6 October". Each count is one of a fixed list of names; there is no place in it for what you selected, typed, copied or snipped, and that is never sent. | To learn which features people use, and which they don't, so we can improve Fevle. Part of using Fevle with an account, as the Terms of Service say and as you agree when you sign up; sent only while you are signed in to the app. | One year, then deleted; and until you delete the account, if sooner. |
| Signed-in computers: each computer's name, when it signed in and was last used, a fingerprint of a key made on that computer, and hashes of its session tokens. | To keep you signed in, to show where you are signed in, and to refuse a session copied to another machine. | While the session lasts — it ends when you sign out or end it, or after 90 days unused — and 30 days after, then deleted. |
| Website sessions: a hash of the token in your sign-in cookie, when it expires and was last used, the IP address and browser it was signed in from, when it last signed in with Google, and when it last gave a two-step code. | To keep you signed in on this website, to list the browsers you are signed in on so you can sign any of them out, and to know how recently a session proved who is using it. | 14 days at most, then 30 days, then deleted. |
| Server logs: IP address, time, the address requested, and the result. | Security, preventing abuse, and fixing faults. | Up to 30 days. |
| Sign-in attempts: the IP address a sign-in, sign-up or token request came from, and a hash of the address it tried, in memory only. | To slow down password guessing. | A minute for the IP address, fifteen for the address tried; never written down. |
Updates. An installed copy of Fevle asks our service every few hours whether there is a newer version for your system, saying which version it is running. When an update installs, or fails to, it sends one line saying which versions it was between, at which step it failed and a short error code. Neither carries your account, an identifier for your computer, or anything you selected, typed or copied, and they are sent whether or not you are signed in. We keep them only as daily totals — "1.4.2 checked 120 times on 9 October", "the update to 1.5.0 failed while downloading 3 times" — for 400 days, to know when an update is safe to give to everybody and when to stop it. Which machines get an update first in a gradual rollout is decided on your computer from a random number that never leaves it.
We also count visits to this website as daily totals — how many people opened each page, made an account, started a download or a checkout, and which site linked here. No IP address, cookie, browser fingerprint or other identifier is stored for this, so the counts cannot be traced back to anybody.
We do not ask for your name, phone number, address or date of birth. We do not use advertising or third-party analytics trackers. The feature counts above stay with us: they are used only to improve Fevle, never for advertising, and never shared.
3. What you send for an answer
Ask AI, Translate, reading a translation aloud, correcting a sentence, and questions about a snip need an answer from the service. When you press one of them — and only then — Fevle sends the service what that answer is about: the text you selected, anything you typed, the earlier messages of the same conversation, and a snip or picture if you asked about one.
- We pass it to one of our AI providers to produce the answer, and send the answer back to you. If that provider cannot answer, we may pass the same request to our other AI provider instead.
- We do not store it. It is held in memory while the answer is made and then discarded. It is not written to our database or our logs.
- Our AI providers process it on our behalf, under terms that do not allow them to use your content to train or improve their models. Each may keep it for a limited period to detect abuse of its service, as its terms require.
Please don't send things you aren't allowed to share, or sensitive personal data you don't need an answer about.
4. What stays on your computer
These are kept on your own computer, in a folder named .fevle in your user folder, and are never sent to us: your settings and keys, pinned apps, the Paste list (in memory only, unless you turn on keeping it — a restart to finish an update hands its words straight to the new version without writing them down), Ask AI's favourites, recent and custom actions and its last ten conversations, your sign-in session with the key that proves it came from your computer, and what Fevle knows about updates: which it offered you and when, what you postponed or agreed to, and a short log of what it installed. The spell check is your operating system's own dictionary.
Copy, Paste, Cut, Snip and its editor, Share, New Tab and Window work entirely on your computer: what they work on is never sent to us. Only how often each one is used is counted, as described in section 2. Counts not sent yet wait on your computer for at most a month, and are discarded when you sign out. Uninstalling Fevle removes the program; delete the .fevle folder to remove these too.
5. Who else handles it
We use a small number of providers, each only for its part:
- Our AI providers — two of them; each request goes to one, and to the other only if the first cannot answer it. They produce answers from what you send for one, as described in section 3.
- Our hosting provider — runs the service and stores its database and logs.
- Our mail provider — sends the mails that confirm your address, reset your password, warn you about your account's security, and answer your support requests.
- Cloudflare — protects this website from attacks, and runs the robot check (Turnstile) on the sign-in, sign-up, password-reset and contact forms. That check looks at signals from your browser to tell people from robots, under Cloudflare's privacy policy; it is not used for advertising.
- Google — only if you choose Continue with Google: your browser goes to Google's sign-in page at accounts.google.com, and Google tells us your Google account's ID, your email address and whether Google has verified it. What happens on Google's pages is covered by Google's privacy policy. We tell Google nothing about you beyond asking it who you are.
- Have I Been Pwned — when you choose a password, the first five characters of a hash of it are sent to its Pwned Passwords service, which answers with every known-breached password that starts the same way; the match is made on our side, so neither your password nor its full hash leaves our service.
- Paddle.com — sells paid plans as our reseller and Merchant of Record. Paddle collects your payment details, billing address and tax information directly, under its own privacy notice; we never see your card number. Paddle tells us your customer and subscription IDs, which plan you bought, whether payments succeed, each payment's amount, tax and invoice number, refunds, and your card's brand, last four digits and expiry month. When you update your card, you give it to Paddle on Paddle's own checkout.
Ask us at [CONTACT_EMAIL is not set] and we will tell you who these providers are.
When you use Share, New Tab, Window or search by image, Fevle opens that service — WhatsApp, Telegram, Gmail, Outlook, iCloud Mail, a search engine — in a window or your browser, and what you send there is governed by that service's policy, not ours.
We disclose data to authorities only when the law requires it. We do not sell personal data, and we do not share it for advertising.
6. Where it is processed
Our providers may process data in countries other than yours, including the United States. Where the law requires it, transfers are covered by safeguards such as the European Commission's standard contractual clauses.
7. Legal bases
Where the GDPR or similar laws apply, we rely on:
- Contract — to provide your account, the online features and your plan.
- Legitimate interests — to keep the service and your account secure (security events, the robot check, the breach check, our staff's change log), prevent abuse, fix faults, help you when you ask, count visits anonymously, count which of Fevle's features are used so we can improve them, and keep Fevle up to date and safe by counting update checks and failed updates. You can object; see your rights.
- Legal obligation — to keep records the law requires, and to answer lawful requests.
The website's four cookies are strictly necessary for signing in, so they need no consent; see the cookie policy.
8. How long we keep it
As in the table in section 2. When you delete your account from your account page:
- a paid subscription is cancelled at once (if you want a refund, ask before deleting — see the refund policy);
- your account, its usage records, its feature counts, its billing history, its signed-in computers, its website sessions, its security events, its support requests, and our team's notes about it are deleted from the live database immediately, and every session signed in with it stops working — except, for an account made in the last day, the time it was made and the IP address it was made from, kept with nothing else until that day is over;
- our staff's change log keeps its entries about the account, with the address it had, as the record of what our staff did;
- copies in backups are overwritten within 30 days as the backups roll over;
- Paddle keeps the records of past payments that tax law requires of it.
9. Your rights
Depending on where you live, you have the right to access the data we hold about you, to correct it, to delete it, to receive a copy in a portable form, to restrict or object to how we use it, and to complain to your data protection authority.
- Delete your account yourself from your account page, at any time.
- Change your password there too, and sign out of every computer at once.
- Object to the feature counts by writing to us, and we will delete those we hold. Counting itself is part of the Terms of Service you agreed to, so it stops when you sign out of Fevle or delete your account; signing out also discards what Fevle had not sent.
- For a copy of your data or any other request, write to [CONTACT_EMAIL is not set]. We answer within 30 days, and may ask you to confirm that the account is yours.
California residents: we do not sell or share personal information, or use it for targeted advertising. You may ask to know, correct or delete what we hold, and we will not treat you differently for asking.
10. Security
Passwords are stored only as Argon2 hashes of a keyed hash, so a copy of our database alone is not enough to guess them, and a new password is checked against known breaches. Wrong passwords are slowed down, and signing in can be paused after several, with a mail to tell you. If you sign in with Google, we check Google's answer ourselves, signature and all, and accept it only for an address Google itself runs (Gmail or Google Workspace). You can turn on two-step sign-in with an authenticator app; our own staff must. Everything travels over HTTPS. Fevle never sees your password: you sign in in your own browser, and the session it gets is tied to a key that never leaves your computer, so a copied token is useless anywhere else. Sessions expire and rotate, and you can end any of them from your account. This website runs no scripts of its own; the four forms robots target load Cloudflare's robot check.
No system is perfectly secure. If a breach affects your data, we will tell you and the authorities as the law requires.
11. Children
Fevle is not for anyone under 18, and we do not knowingly collect data from them. If we learn that an account belongs to someone under 18, we delete it. If you believe a child has made an account, write to us.
12. Changes, and contact
When this policy changes, the date at the top changes with it. If a change matters to how your data is used, we will tell you before it takes effect.
Questions or requests: [CONTACT_EMAIL is not set].