— I — What we collect
The minimum to make this work.
We collect only what's needed to fulfill your order, run the protocol, or comply with Indian law. Specifically:
From shoppers (web2)
- Order details — name, shipping address, phone, email, order contents.
- Payment metadata — Razorpay payment ID and status (we don't store your card).
- Communications — emails you send us, support tickets.
From wallet users (web3)
- Wallet address — the public address you connect with. This is not personal information by itself but is linked to your on-chain activity, which is permanently public.
- Sign-in signature — the plaintext message you sign to prove ownership of the address.
- Transaction hashes — references to mints, burns, redemptions you initiated.
From creators
- Wallet address, display name, optional bio, submitted artwork files, payout history.
- Email if you choose to provide one for status notifications.
Automatic from any visitor
- Standard server logs: IP address, user agent, timestamps, requested URLs. Used for abuse prevention and capacity planning.
- When you visit a page reached through one of our paid advertising campaigns, we load a conversion pixel from the platform that brought you — we may run campaigns with Google Ads, Meta (Facebook & Instagram), X (Twitter), and similar networks. These pixels share an event-level record of the visit (page URL, referrer, anonymized identifier) with the platform that ran the ad, so they can measure which ads bring real customers. Pixels are loaded via Google Tag Manager only when a campaign is live; outside of active campaigns no third-party tracking SDK is loaded.
— II — What we use it for
Operational, not marketing.
- Fulfillment — passing your shipping address and order to Qikink so they can print and ship.
- Communication — sending order confirmations, shipping updates, defect or cancellation responses.
- Protocol operation — verifying your wallet signed in correctly, attributing on-chain actions to the right account.
- Creator payouts — calculating and disbursing $PRANA payouts to approved creators.
- Support — replying to emails you send us, with the context of your account/order.
- Fraud prevention — detecting and blocking obvious abuse patterns (chargebacks, repeated fraudulent orders, contract exploits).
- Legal compliance — keeping records required by Indian commerce, tax, and accounting law.
When we run paid advertising campaigns, we use conversion pixels to attribute a visit to the ad that brought you (so we know which ads work) and we may build campaign-specific audiences with the ad platforms for follow-up promotion. We do not sell your data, build cross-site behavioural profiles beyond what the ad platforms themselves do, or train external AI systems on it.
— IV — On-chain & wallet data
Public by design.
Ethereum is a public ledger. Once you connect your wallet to Indraloka, interact with our contracts, or burn/transfer/redeem any token, that action is permanently recorded on Ethereum and visible to anyone with a block explorer.
Indraloka cannot edit, delete, or "forget" on-chain activity. If you want privacy on your purchases, consider using a fresh wallet for each order or routing through a privacy-preserving relay before transacting. We do not provide privacy infrastructure beyond what Ethereum itself offers.
— V — Payments
Card data never touches our servers.
Card and bank details for INR purchases are handled entirely by Razorpay, a PCI-DSS Level 1 compliant payment processor. We receive a payment ID and status; we never see your card number, CVV, expiry, or bank credentials. Cryptocurrency payments flow through smart contracts directly — no credentials are exchanged off-chain.
For refunds in INR, we ask Razorpay to issue the refund to the original payment method. For PRANA refunds, we send PRANA to the wallet you transacted with. We never request seed phrases, private keys, or wallet passwords for any reason.
— VI — Cookies & storage
Functional, not advertising.
We use a small set of browser storage items, all functional:
- localStorage flags — to remember which mandala welcome nudges you've seen, your cart contents, and whether your wallet is connected.
- Session cookies — for admin/creator portal sign-in (encrypted, server-side session ID only).
- Ad attribution cookies — only during active campaigns. When you visit a page reached through one of our paid ads on Google, Meta, X, or a similar network, the platform's pixel may set its own cookies so it can attribute the visit (and, if you check out, the purchase) to its ad. These cookies are set by the ad platform, not by us, and you can clear them anytime via your browser settings. Outside of active campaigns no third-party tracking cookie is set.
You can clear these at any time through your browser settings. Doing so will reset cart state and require you to reconnect your wallet on next visit, but does not delete your account or order history on our side.
— VII — Retention
How long we keep what.
- Orders & shipping data — 7 years (required for Indian commercial & tax records).
- Wallet addresses we've issued PRANA to — indefinitely, since the on-chain record is permanent regardless.
- Email correspondence — 3 years from last reply, then archived or purged.
- Server logs — 30 days, rotated automatically.
- Creator submissions (rejected) — 90 days, then deleted.
- Creator submissions (approved & printed) — retained while the creator agreement is active.
— VIII — Your rights
What you can ask us to do.
You can write to connect@indraloka.shop with any of the following requests. We respond within 30 days:
- Access — get a copy of the personal data we hold about you.
- Correction — fix any data that's wrong (e.g. shipping address).
- Deletion — have us delete data we no longer need to retain. Subject to legal retention requirements (orders, taxes) and the inherent permanence of on-chain data.
- Export — receive your account data in a portable format (JSON).
- Object to processing — withdraw consent for any non-essential use of your data.
For verification, we may ask you to send the request from the email address on the account, or to sign a message from the wallet address in question.
— IX — Changes to this policy
If something changes, we tell you.
We may update this policy as the protocol grows, vendors change, or law evolves. Material changes that affect what we collect or how we use it will be communicated to active users by email, and the "Last updated" date above will reflect the change. Minor wording or structural edits may happen without notice.
For any privacy question or concern, write to connect@indraloka.shop. We're a small team — your message goes to a person.