Privacy Policy
This page explains what may be processed when you use ClayQR Studio, what the browser-based generator does, and what still depends on the website's hosting and configuration.
1. Who operates ClayQR Studio?
ClayQR Studio is operated by [INSERT LEGAL OPERATOR NAME] (“we”, “us”, or “the operator”). Contact: [INSERT CONTACT EMAIL]. Grievance contact, where applicable: [INSERT GRIEVANCE CONTACT NAME AND EMAIL]. Business address, if required for your operation: [INSERT BUSINESS ADDRESS, IF APPLICABLE].
Do not publish this page until the operator identity and working contact details are correct.
2. Information you enter
The generator lets you enter text, URLs, contact information, or other text content. It may also let you select a very small image and encode its data as text. The current front-end implementation creates QR codes in your browser using a client-side JavaScript library. The app code does not intentionally send the entered QR content to a ClayQR application backend because no application backend is included in this static version.
However, browser-based processing is not a promise that no information ever leaves your device. Your browser, network, hosting provider, content delivery network (CDN), extensions, or other configured services may process technical information or make requests. Do not enter confidential, highly sensitive, or third-party information unless you are comfortable with the risks.
3. Uploaded image files
Image-data mode is experimental and accepts PNG, JPEG, GIF, or WebP files up to 700 bytes. The file is read locally by the browser as a data URL and that data is used as QR content. The QR code does not host the image and a scanner may show the encoded data as text instead of displaying the original image. Larger images are rejected by the interface. If you later add an image-hosting workflow or backend, update this policy before enabling it.
4. Technical information and hosting logs
The hosting provider may receive and retain standard request information such as IP address, user-agent, requested path, referrer, timestamps, and security or performance logs. The exact data, retention period, and access controls depend on the selected hosting provider and account configuration. Review the provider's current privacy documentation and settings before launch.
Hosting provider: [INSERT HOSTING PROVIDER, E.G. CLOUDFLARE PAGES]. Hosting/log retention details: [VERIFY AND INSERT CURRENT CONFIGURATION].
5. Third-party libraries, CDNs, and fonts
The current site loads the QRCode.js library from cdnjs and requests DM Sans and Manrope fonts from Google Fonts. These services may receive technical connection data, including IP address and browser information, when resources are requested. If a CDN or font request fails, QR generation may not work as expected. You can reduce third-party requests by hosting reviewed library/font files yourself, subject to their licences, and then updating this notice.
Dependencies currently referenced: QRCode.js from cdnjs.cloudflare.com and fonts from fonts.googleapis.com / fonts.gstatic.com. Verify current library versions, integrity options, licences, and provider terms before production deployment.
6. Cookies, analytics, and advertising
The supplied static code does not intentionally set analytics cookies, run an analytics package, or include advertising scripts. Hosting infrastructure or future additions may behave differently. If you add analytics, advertising, session tools, or other tracking, disclose the tools, purposes, data categories, controls, and relevant consent choices here before enabling them.
7. Purposes and legal basis
Content entered into the tool is used to generate the QR code requested by the user. Technical information may be processed to deliver, secure, troubleshoot, and maintain the website. The precise legal basis and applicable notices depend on the operator, deployment, users, and actual processing. Obtain appropriate legal advice for your circumstances.
8. Retention and deletion
The current app does not include an application account or database to save generated QR content. The generated preview and selected image data are held in the active browser page while it is being used. Closing or reloading the page will normally clear this in-memory state. This does not control copies, browser caches, downloads, screenshots, hosting logs, or information processed by third parties. Their retention practices are governed by their own configurations and policies.
9. Security and limitations
We aim to use a simple, browser-based approach that can reduce the need to transmit entered content to an application server. No website, device, browser, network, or download can be guaranteed perfectly secure. Keep your browser updated, avoid untrusted QR content, and do not encode sensitive information into a QR code that others may scan or copy. A QR code can point to a deceptive or harmful destination; check links before opening them.
10. Your choices and privacy requests
You can choose not to use the generator, avoid entering sensitive information, and clear the page or remove a selected image. Depending on applicable law and the actual processing involved, you may be able to request access, correction, erasure, grievance handling, or other privacy assistance. Details and rights may vary by situation and applicable commencement provisions.
Submit a request using [INSERT CONTACT EMAIL] or visit Privacy Requests. Do not send passwords, payment-card details, or unnecessary sensitive data. We may ask for proportionate information to verify and respond to a request.
11. India-specific legal references
The Digital Personal Data Protection Act, 2023 and the Digital Personal Data Protection Rules, 2025 may be relevant depending on the facts, the information involved, the operator's role, and the provisions that are in force at the relevant time. Commencement and implementation may be phased. The operator must verify the latest official notifications, applicable provisions, and any other relevant Indian laws before making legal-compliance claims. This policy is not a certification of compliance and is not legal advice.
12. Children and third-party links
The site is a general-purpose utility and is not specifically designed to collect children's personal data. If you believe personal data has been submitted inappropriately, contact the operator using the details above. The website may link to third-party sites; we do not control their content or privacy practices. Review their policies before using them.
13. Policy updates
We may update this notice when the site, services, law, or processing practices change. The effective date at the top will be revised when changes are made. Check this page periodically.
14. Contact and grievance handling
Privacy contact: [INSERT CONTACT EMAIL]
Grievance contact, where applicable: [INSERT GRIEVANCE CONTACT NAME AND EMAIL]
Response process: we will review requests, seek only proportionate clarification where needed, and respond in accordance with applicable requirements and practical limitations. No specific response deadline is promised by this template.