Chrome Extension · Privacy Policy
VerifyFill is developed and owned by Kristijonas.
VerifyFill is a Chrome extension that exists so you can finish signing in to websites without constantly switching between Gmail and the site you are on. When a service sends a verification code or a confirmation link to your email, this application finds it and helps you use it on the page where you are trying to log in or create an account.
VerifyFill provides the following features:
After you install VerifyFill and sign in with Google:
VerifyFill only works if it can (1) know which Google account you connected, (2) read recent Gmail messages that may contain a verification code or link, and (3) interact with the browser tab where you are trying to sign in. This section explains every type of user data the extension requests, the exact purpose of each request, what is read, what is stored, what is not collected, and what you can do to stop access.
OAuth scope: https://www.googleapis.com/auth/userinfo.email
Why we request it: You sign in with Google to connect your Gmail account to the extension. We need your Google account email address so the extension can confirm sign-in succeeded and show you which account is currently connected in the extension popup.
What we read: Your Google account email address only.
What we do with it: Display it in the extension popup so you know which Gmail account VerifyFill is using. It is stored locally on your device while you remain signed in.
What we do not do with it: We do not sell it, share it with advertisers, use it for marketing, or send it to a VerifyFill server.
OAuth scope: https://www.googleapis.com/auth/gmail.readonly
Why we request it: Websites send verification codes and email confirmation links to Gmail. Without read access to your inbox, VerifyFill cannot detect those codes or links and cannot offer to autofill them. Read-only access means the extension can read mail but cannot send, delete, label, or modify any message.
What we read: Only when you are signed in, VerifyFill queries your Gmail inbox for messages that match all of the following limits:
How we use what we read: The extension scans subject and body text only to detect verification codes or email confirmation / sign-in links, then offers to fill them on the website you are using. Message content is processed in your browser on your device.
When we read Gmail: After sign-in; approximately every 1 minute while signed in; when you click Check now; when you focus a verification input or land on a “check your email” page.
What we do not do with Gmail data: We do not upload email to a VerifyFill server, do not read your entire mailbox, do not use Gmail data for advertising or resale, do not send or modify email, and do not access Gmail when you are signed out.
Why we need it: To show a fill prompt near the correct input and autofill a code or open a link on the page where you are signing in. Page interaction happens locally in the extension; we do not track general browsing history or send page content to a server.
What may be stored: Sign-in state, connected email address, OAuth tokens via Chrome, and IDs of messages/codes/links you already used. Not a copy of your full inbox.
VerifyFill does not request Google Drive, Calendar, Contacts, Photos, send-mail access, delete-mail access, or your Google password.
VerifyFill communicates only with Google’s own services (Google Sign-In and Gmail API). Google’s handling of data is covered by Google’s Privacy Policy.
You can sign out in the extension, revoke access in your Google Account permissions, or uninstall the extension at any time.
VerifyFill is not directed at children under 13, and we do not knowingly collect personal information from children.
We may update this policy from time to time. The “Last updated” date at the top of this page will reflect the latest version.
Owner: Kristijonas
Email: [email protected]
Website: https://verifyfill.krispi.org/
Privacy policy: https://verifyfill.krispi.org/privacy.html