Legal
Privacy Policy
Last updated: November 11, 2026
Overview
Peek a Code is a free Chrome extension built by Presdin Works LLC (presdinworks.in). When you click its icon, it reads your most recent Gmail messages and shows the latest one-time password (OTP) or verification code, or a verify or magic link if the email has no code. This policy explains exactly what it accesses and what happens to that data.
The short version: Peek a Code has no server. Your emails are fetched by your browser directly from Google, read inside the popup on your device, and never sent to Presdin Works or to anyone else. We do not collect, receive, store or share your data.
Google API Limited Use Disclosure
Peek a Code's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Specifically: Gmail data is used only to show you the code or link from your own recent email. It is not used for advertising, is not used to train AI or machine learning models, is not transferred or sold to anyone, and is not used to build a profile of you. No human at Presdin Works can read your email through Peek a Code, because the data never reaches us.
What permission Peek a Code requests
Peek a Code requests one Google permission:
- gmail.readonly — lets the extension read your email messages. It is needed to find the code in the email you just received.
This scope is read-only. Peek a Code cannot send, delete, archive, label or modify any email or setting, and cannot access Google Drive, Calendar or any other Google service.
In the browser it also uses the identity permission (to sign you in with Google), the clipboardWrite permission (to copy the code for you), the storage permission (to remember your alert setting and, in browsers like Brave, your short-lived sign-in token, see below) and the scripting permission (to show the code card on a page, only after you allow it). Its only network access is to gmail.googleapis.com and Google's sign-in page.
If you choose "Allow on all sites" (optional), Peek a Code can run a small script on the pages you visit. On Gmail pages it also adds a small status button (a green or red dot, your signed-in account and an alerts switch). That script only draws the button. It does not read your emails, your inbox or any other content on the Gmail page, and it sends nothing anywhere; it only talks to Peek a Code's own background worker.
What data is accessed
Each time you open the popup (or press Refresh), Peek a Code asks Gmail for up to 10 messages in your inbox that arrived in the last 5 minutes and were not sent by you. For each one it reads:
- Subject and message body — searched for a code or a verify/magic link.
- Sender — shown next to the result so you know which email it came from.
- Date and time — used to pick the newest email and to show how long ago it arrived.
While the popup is open and no code has been found, it checks again every 3 seconds for up to 2 minutes. It does not download attachments.
Code alerts (on by default, you can switch them off). If you allow Peek a Code on all sites (optional), it can show a small card with your new code in the corner of the page you are on, and copy the code to your clipboard. To know when to look, a small script on the page checks whether the page has a code-entry box, by checking a box's own attributes (such as its name, placeholder, label and length). When it sees one, it asks the extension to check your inbox every 3 seconds for 2 minutes, using the same read-only access and the same 5-minute window. The script does not read what you type, the text of the page, or your email, and it sends no page information to us or to anyone else. Peek a Code does nothing in the background on pages without a code-entry box, or if you switch alerts off. You can say no to the all-sites permission and open the popup yourself whenever you want a code, and you can remove the permission at any time in your browser's extension settings.
What is stored, and where
On our servers: nothing. Peek a Code has no backend, no database, no accounts, no analytics and no logging. Presdin Works LLC receives no information about you, your emails, your codes or your use of the extension.
On your device: nothing kept. Email content is held in memory only while the popup is open and is discarded when you close it. Peek a Code does not save your emails, the codes it finds, or any history. The only things kept are your alert on/off choice, the ID of the last message a code alert was shown for (so it isn't shown twice; never its content), and the Google sign-in token. In Google Chrome, Chrome itself stores and manages it (through its identity feature) so you stay signed in. In other browsers such as Brave, the extension keeps the token (valid for about an hour) in the browser's session storage, which is cleared when you close the browser. In both cases the token stays on your device and is sent only to Google.
On your clipboard: when a code is found, Peek a Code copies it to your clipboard so you can paste it. Your clipboard is managed by your operating system and may be visible to other apps or clipboard managers you use; copy something else to replace it. Peek a Code only writes to the clipboard and never reads it.
Links: if an email has a verify or magic link and you click Open, the link opens in a new Chrome tab. The site that opens is the one the email points to and is subject to its own privacy policy.
Third parties
The only third party involved is Google, whose Gmail API your browser talks to directly under Google's Privacy Policy. We do not share data with advertisers, data brokers, AI providers or anyone else, because we never have your data.
Security
All communication with Gmail goes over HTTPS (TLS). Your sign-in token is managed by Chrome's sandboxed identity system and is isolated from websites and other extensions. The extension runs entirely inside your browser, and email text is never written to disk by Peek a Code. Peek a Code never logs email content.
Your choices and rights
- Revoke access at any time at myaccount.google.com/permissions.
- Uninstall the extension from Chrome to remove it entirely.
- Deletion requests: since we hold no data about you, there is nothing on our side to delete or export.
Children
Peek a Code is not directed to children under 13 and we do not knowingly collect any information from them.
Changes to this policy
If this policy changes, we will update the date at the top of this page. If a change affects how your data is handled, we will make that clear in the extension or on our website before it takes effect.
Contact
Questions about privacy? Email admin@presdinworks.in. Presdin Works LLC, presdinworks.in.