ಕನ್ನಡ ರಾಜ್ಯೋತ್ಸವ 2026

Data used by this website

The custom demo does not ask for a name, email, phone or bank details. It stores random session identifiers, hashed ownership and scanner capabilities, a fixed amount, attempt counts, status and timestamps in Cloudflare D1. The scanner capability travels in a URL fragment and is submitted to our backend to authorize that simulation.

Razorpay Test Checkout sends payment information directly to Razorpay. Our backend stores random session IDs, Razorpay order/payment identifiers, verification state, event IDs and timestamps. It does not store card numbers, CVVs or UPI PINs. Razorpay may request contact or payment details inside its own checkout and processes them under its privacy policy.

Cookies and browser storage

Essential HttpOnly, SameSite cookies associate your browser with an order and authorize your greeting. They are Secure over the production HTTPS site. Demo QR sessions last 15 minutes; test orders last 30 minutes. Greeting access lasts at most 10 minutes and cannot exceed its payment session. Session storage remembers whether you last used the demo or test checkout, so a refresh can restore the correct experience. There are no advertising or analytics cookies added by this application.

Why we process this data

To connect a payment result to the correct browser, prevent forged or reused payment claims, recover interrupted confirmations, deliver the greeting and diagnose failed attempts. Downloaded images and shared greeting text contain no private payment or session identifiers. The greeting image is composed in your browser.

Retention and infrastructure

Expired demo records become eligible for removal one day after expiry. Test payment-session records and webhook event IDs older than seven days are removed when another test order is created. Cleanup is opportunistic rather than a scheduled deletion guarantee; inactive databases and backups can retain records longer. Browser cookies expire independently.

Cloudflare may process IP addresses, request metadata and infrastructure logs to deliver and secure the site. Razorpay also keeps its own records. Infrastructure logs, provider records and backup retention follow those services’ settings and policies; they are not covered by the application’s database cleanup. The application does not deliberately write payment credentials or full provider payloads to logs.

Privacy requests

The data controller’s identity and privacy contact are awaiting client confirmation on the Contact page. A working request and deletion process must be confirmed before live launch. Removing local cookies ends browser access but does not itself delete backend records.