Legal
KeepAnswers privacy policy
Last updated 13 August 2026.
KeepAnswers is a Chrome extension for people who administer their own Facebook groups. This policy explains exactly what it reads, where that goes, and how to get rid of it.
The short version: the answers KeepAnswers collects go from your browser to a Google Sheet in your own Google account. They do not pass through us. We do not run a server that receives them, and we could not show you your members' data if you asked us to, because we have never had it.
1. What the extension reads
KeepAnswers reads one page: the pending join requests page of a Facebook group you have added to its settings, and only when you are already signed in to Facebook as an admin or moderator of that group.
From each pending request it reads:
- The applicant's display name, as Facebook shows it on the request card.
- The link to the applicant's Facebook profile, and the numeric Facebook user id in that
link.
- Whether they have answered the group's membership questions.
- Their answer to each membership question you have mapped in the extension's settings.
- An email address, if one of your membership questions asks for one. Two values are
kept: the exact text they typed, and a cleaned address extracted from it. If what they typed is not an address, the cleaned value is left empty.
- The relative age of the request, as Facebook prints it, for example "2 days ago".
- The relative age of the applicant's Facebook account, as Facebook prints it, for
example "Joined Facebook 11 years ago".
- Up to 1500 characters of the raw text of the request card. This is kept so that if you
later find a question was mapped to the wrong column, the original text is still there to re-read rather than being lost.
That is the entire list. KeepAnswers does not read your news feed, your messages, your notifications, your friends list, your groups list, anyone's profile page, or any group you have not added to its settings yourself. On every Facebook page other than a group queue page you have configured, it does nothing at all.
It never reads or stores a password, a cookie, an access token or any other credential, for Facebook or for Google. It works inside the session you are already signed into.
2. Where that data goes
To your own computer. Everything collected is written to Chrome's local extension storage on the machine the extension is installed on. It is not written to Chrome Sync, so it is not copied to your other devices or to your Google account by Chrome.
To your own Google Sheet. When you connect a Google Apps Script web app in the extension's settings, KeepAnswers sends the collected records to that address. You create that web app, in your own Google account, following the instructions supplied with the extension. It writes into a spreadsheet you own. Nothing is sent until you paste an address in, and if you never paste one in, nothing is ever sent anywhere.
To your clipboard or your Downloads folder, if you use the "Copy for Sheets" or "Download CSV" buttons in the extension's popup. Those actions stay on your machine.
Nowhere else. There is no KeepAnswers server that receives member data. There is no analytics service, no error-reporting service, no advertising identifier, and no third party of any kind in the path between the Facebook page and your spreadsheet.
We do not sell data, share it, or use it for anything. We cannot: we do not have it.
3. The one thing that is sent to us
The extension checks that your licence key is valid. That check sends the following to `https://keepanswers.com/api/licence/verify`:
- Your licence key.
- A random identifier generated on your own device when the extension was installed. It
is not derived from your name, your email, your Facebook account or your hardware.
- The version number of the extension.
Our server reads only the licence key, answers "active" or "not active", and stores nothing from the request. The random install identifier and the version number are discarded.
Like any web server, ours receives your IP address as an unavoidable part of the request, and our hosting provider keeps short-term operational logs.
No member name, no email address, no answer, no group name and no group URL is ever included in a licence check. If the check cannot reach us, the extension keeps working and tries again later.
4. Who is responsible for the member data
You are. The people applying to your group are giving their answers to you, the admin of that group, in response to questions you wrote. KeepAnswers is a tool you run on your own computer to keep a copy of the answers you were already being shown.
If you are subject to the UK GDPR, the EU GDPR or a similar law, you are the data controller for that information. We are not a processor of it, because it never reaches us. Your obligations to the people applying to your group - telling them what you will do with their email address, and honouring a request to be deleted - are yours, and this extension does not change them.
A practical suggestion, not a legal one: say in the wording of your membership question what you will use the address for. It costs you nothing and it is the difference between a list that engages and a list that reports you.
5. How long it is kept
On your computer: indefinitely, until you delete it. Records are never expired or pruned automatically. This is deliberate, because a person who applied months ago and answered late would otherwise be lost.
In your Google Sheet: for as long as you keep the spreadsheet. That is entirely within your own Google account and we have no access to it, no visibility of it, and no way to change it.
On our servers: nothing about your members, ever. Your purchase record and licence key are kept for as long as your licence is valid, because a lifetime licence has to remain checkable.
6. How to delete it
Delete the local copy. Open the extension's settings, go to "Erase saved people", choose one group or every group, and confirm. This wipes the records held in Chrome. It does not touch your spreadsheet.
Delete everything the extension holds, including your settings. Remove the extension from `chrome://extensions`. Chrome deletes its local storage with it. Your licence key and your sheet address go too, so export your settings first if you plan to reinstall.
Delete the collected data itself. Delete the rows, the sheet, or the whole spreadsheet in your own Google Drive. To stop the extension being able to write to it at all, open the Apps Script project and remove the deployment.
Delete a single person's data, for example after a deletion request: delete their row from your spreadsheet, and use "Erase saved people" for that group so the local copy does not re-send them on the next visit.
Delete your account with us. Ask through the contact form and we will delete your purchase record and revoke your licence key. Note that this deactivates the extension's scheduled runs, and that a payment record we are legally required to keep for tax purposes is retained for as long as the law requires.
7. Account and purchase data
Separately from the extension, buying a licence creates an account on keepanswers.com. For that we hold your email address, your purchase record and your licence key. Payment is handled by Stripe; we never receive or store your card number. Stripe's own privacy policy governs what they hold.
8. Children
KeepAnswers is a tool for group administrators and is not directed at anyone under 13. We do not knowingly collect anything from children. What lands in your spreadsheet is determined by who applies to your group, which is a matter for you and for Facebook's own age rules.
9. Security
Data on your computer is protected by your computer and your Chrome profile. Data in your spreadsheet is protected by your Google account.
One thing genuinely worth your attention: the Apps Script web app you deploy is set to "Anyone" access, which means that URL is an unauthenticated endpoint and the secret you paste alongside it is the only thing standing in front of your spreadsheet. Keep both private. If either ever leaks, redeploy the script to get a new URL. The settings export file produced by the extension contains both, plus your licence key, so treat that file like a password.
10. Changes to this policy
If this policy changes in a way that affects what is collected or where it goes, the change will be published here and the date at the top will be updated. Material changes will also go out to licence holders by email.
11. Contact
Everything reaches us through the contact form, which goes to a real person's inbox. There is no published address, because an address on a marketing site fills with spam and a genuine privacy request is exactly the thing that gets buried in it.
Not affiliated with, endorsed by or sponsored by Meta, Facebook or Google. Facebook is a trademark of Meta Platforms, Inc. Google Sheets is a trademark of Google LLC.