QR Code Generator and Code Studio
Effective date: 11 Sept 2026
Operator: Lalit Bahel
Privacy contact: hello@lalitbahel.com
1. Scope of this policy
This Privacy Policy explains how information is handled when you use the QR Code & Barcode Generator on lalitbahel.com, the Code Studio – QR & Barcode Generator Chrome extension, or contact us about these tools.
The website and the installed extension are separate environments. Statements specifically about the extension describe Code Studio version 0.2.0. They should not be read as promises that every page, hosting service or third-party component on lalitbahel.com operates without network requests or data processing.
2. Information you choose to provide
Depending on the feature you use, the tools may process website addresses, text, contact-card details, email addresses and message content, phone numbers, SMS or WhatsApp messages, and location coordinates that you enter.
Wi-Fi code creation uses the network name, security settings and password you provide. UPI code creation uses payment-request information such as a UPI ID, payee name, amount and note. These features do not read saved passwords, access bank accounts, execute payments or verify whether a payment occurred.
Logo and QR-scanning features process image files that you choose. Camera scanning processes camera frames after you start the scanner and your browser grants access. Decoded content may contain personal or sensitive information, depending on what the original code contains.
The extension can also use a current-page URL, link URL, selected text or image source URL when you invoke its toolbar or right-click actions. It does not automatically collect unrelated page content.
3. How the extension processes information
Code Studio 0.2.0 performs code generation, QR design, export preparation and QR decoding locally in your browser. Editor content, chosen logo files, scanner images, camera frames and decoded results are not uploaded or transmitted to the developer, analytics services, advertising services or partner websites by the extension’s code tools.
This information is used to carry out the code-related actions you request. Local processing still involves handling information; it does not mean that no information is used.
The extension has no account sign-in, persistent code library, cloud backup, advertising SDK or telemetry component. It does not track scans of exported codes or provide managed dynamic redirects. It does not use code content to train AI models.
Exporting a code creates a file containing the information you chose to encode. Anyone who can read or scan that code may be able to access its contents. A QR code is not a method of encrypting or hiding information. Share codes containing passwords, private links, contact details or payment-request information only with intended recipients.
4. Extension permissions and camera access
activeTab: Allows the extension to use the current tab’s URL after you invoke it to create a code. It is not used for ongoing browsing surveillance.
contextMenus: Provides right-click actions for a page URL, link URL, selected text or image source URL. The image action encodes the image address; it does not fetch or scan the clicked image.
storage: Supports temporary transfer of your selected content from the popup or a right-click action to the full editor through extension session storage.
This release does not request broad host access, inject scripts into websites, read browser cookies or saved passwords, or maintain a browsing-history log.
Camera scanning starts only after you choose the camera action and the browser grants access, either through an existing permission or a new prompt. The extension does not request microphone access. Camera frames are decoded locally and are not recorded or uploaded by the extension.
The camera stream stops when a result is found, you stop scanning, the scanner closes, or the editor becomes hidden or closes. You can revoke camera permission in your browser. Image-file scanning remains available without camera access.
5. Extension storage and retention
Open-editor content, design choices, chosen logos and decoded results are held in the editor’s memory. The extension does not provide a persistent archive of previous work or use Chrome Sync for code content. Clearing or closing the editor ends its active in-memory work; this is not a guarantee of forensic erasure from your device or browser.
A temporary session-storage record can transfer selected content to the full editor. The editor URL contains a random identifier rather than the content itself. A record can be consumed once and cannot be consumed after 60 seconds.
Records are removed when consumed and during expiration cleanup. If Chrome suspends the background worker before cleanup runs, an expired record can remain in session storage until later cleanup or the end of the browser session, but the editor cannot consume it after expiry.
Downloaded files remain wherever your browser saves them until you delete them. Copied content is subject to your operating system’s clipboard and clipboard-history settings. Closing or uninstalling the extension does not automatically remove those files or copied content.
6. Website delivery, cookies and other services
The web-based generator provides browser-based code generation. Loading the website is nevertheless different from using the locally installed extension: your browser must connect to the infrastructure that delivers the page and its resources.
Website delivery, security, optional analytics, embedded services and support systems must be considered separately from QR and barcode generation. The extension’s local-only statements do not establish how these website services handle information.
[COMPLETE BEFORE PUBLICATION: Describe the website generator’s actual handling of entered content, chosen logos, scanner images and decoded results. Confirm which values remain in browser memory or browser storage and whether any are transmitted. Identify any recipient, purpose and retention period. Do not copy the extension’s local-only guarantees without verifying the website implementation.]
[COMPLETE BEFORE PUBLICATION: Identify the actual hosting, security, CDN and other website providers that receive visitor data. State what technical information is logged, such as IP addresses, requested URLs, timestamps and browser information; explain its purpose, retention and relevant processing locations. Identify any external scripts, fonts or embeds that receive visitor requests.]
[COMPLETE BEFORE PUBLICATION: State whether the generator page uses cookies, local storage, analytics, tag managers, advertising or session-replay tools. List the services actually enabled, data used, purposes, storage duration and available choices. Explicitly confirm when these are absent. Explain whether code inputs and scanner content are excluded from measurement. Include the actual consent or opt-out controls where applicable.]
You can manage cookies and site storage through your browser settings. Blocking website resources or clearing stored preferences may affect how the web generator works. These browser controls do not delete downloaded files or information you have separately sent to us.
7. Support enquiries
When you contact us by email or a website form, we receive the information you choose to send, such as your name, email address, message, technical details and attachments. Our email and support service providers also process that correspondence to deliver the service.
We use support information to respond to your request, investigate the issue you report and maintain relevant support records. We retain it for as long as reasonably necessary for those purposes and any applicable legal obligations. You can contact us to request deletion, subject to those obligations.
Sending a support message is separate from local code generation. Use example data where possible and do not send passwords, banking credentials or confidential codes. If you intentionally send a code or screenshot, people handling your enquiry may need to view that specific material to help you.
8. External destinations and disclosures
Scanning a QR code in the extension displays its decoded content and does not automatically open a destination. If you choose Open link, visit the developer’s website, or open a message or payment link in another application, the selected destination or application handles that action under its own privacy practices.
A destination may receive information encoded in the link you deliberately open. The extension does not certify that a destination is safe, verify a payee or confirm a payment.
We do not sell or rent the extension’s locally processed content, use it for advertising, or disclose it to a data broker. We do not have a developer-held copy of that content merely because you generated or scanned a code.
Website and support information may be handled by the service providers disclosed in this policy. Information we actually hold may also be disclosed where legally required or necessary to address security incidents or protect legal rights, subject to applicable law. These circumstances do not give us access to content that exists only on your device.
9. Security
The extension limits exposure of code content by processing it locally and requesting permissions for its stated features. Access to your device, exported files and clipboard remains subject to your browser, operating system and device security.
No software, website or storage method can guarantee absolute security. Keep your browser updated, review unfamiliar decoded links before opening them, and avoid publishing codes that contain information you intend to keep private.
10. Your choices and privacy requests
You can choose what to enter, edit or clear editor content, remove a selected logo, stop camera scanning, revoke browser permissions, clear relevant site data, delete exported files or uninstall the extension.
Depending on the law that applies to you, you may have rights concerning personal information we hold, including access, correction, deletion, restriction, objection, portability or withdrawal of consent where processing relies on consent. You may also be able to raise a concern with the relevant data-protection authority.
Contact hello@lalitbahel.com to make a request. We may ask for information reasonably needed to verify your request, without asking you to provide unrelated sensitive data. We will address requests as required by applicable law.
We cannot retrieve, correct or delete codes that exist only on your device and have not been shared with us. You control those local files and browser data.
11. Chrome Web Store Limited Use disclosure
Code Studio’s use of information obtained through Chrome extension permissions is limited to providing its disclosed code-creation, customization, export and QR-scanning features, in accordance with the Chrome Web Store User Data Policy, including its Limited Use requirements.
The extension does not use or transfer this information for personalized advertising, unrelated profiling, creditworthiness assessments or lending purposes. Locally processed code content is not made available to us for human review. Material that you deliberately provide for support is handled only for the disclosed support purpose, subject to applicable policy and law.
12. Changes to this policy
We will update this policy when relevant features or information-handling practices change and revise the effective date above. Where required, we will provide additional notice or obtain consent before introducing a new use of personal information.
A future feature is not covered by a local-only promise merely because an earlier release operated locally. Changes involving accounts, cloud storage, analytics, remote processing or other recipients must be reflected in the policy and relevant product disclosures.
13. Contact
For privacy questions or requests, contact:
Lalit Bahel
Email: hello@lalitbahel.com
Location: Sri Ganganagar, Rajasthan, India
Website: https://lalitbahel.com/
Contact page: https://lalitbahel.com/contact/