Privacy
What we know about you, and what we don't.
Short version: your gift is yours. We never put its contents in a link preview, never send them to an AI model, and never let a search engine index them.
Last updated 21 August 2026
Who we are
ApnaSurprise is operated by Pawan Kushwah, at Tiwariganj, Lucknow, Uttar Pradesh, 226028, India. For anything on this page, write to apnasurprise@gmail.com.
What we collect
When you build a gift
The gift itself: the recipient's first name, your name, the relationship and occasion you picked, whatever you write, the photos you upload with their captions, the soundtrack you choose, and the PIN if you set one. This is the product — we cannot store a gift without storing the gift.
You do not need an account to do any of this. A draft is tied to a signed cookie in your browser rather than to an identity.
When you pay
Your email address and phone number, the plan and add-ons you chose, the amount, and the identifiers Razorpay gives us for the order and payment.
We never see your card. Card details are entered on Razorpay's own checkout and go straight to them. Nothing resembling a card number, CVV or UPI PIN reaches our servers or our database.
When you make an account
Your name, email address, and a password we store only as a hash — we cannot read it, and a reset link is the only way back in.
While you use the site
If you allow it, which step of the builder you reached, the occasion you picked, the page path, the referring site, and a random session id that lets us tell one visit's steps apart from another's. It carries no name and no email. If you decline, none of it is collected — see cookies below.
A published gift also counts how many times it has been opened. That is a single number on the gift, for the person who made it. We do not log who opened it, when, or from where.
What never leaves
This part is enforced in code, not by policy:
- The AI drafting helper never reads your gift. When you ask for suggested words, what we send is the occasion, the relationship, the tone, the language, and up to four short fragments you typed as hints. The recipient's name, your name, the finished message, the photos, your email and your phone are all withheld — the model writes a placeholder and your browser substitutes the real name locally, so a name never crosses the wire. The request schema strips anything else, so it cannot happen by accident.
- Link previews contain no gift content. The card that appears when you paste a gift link into a chat is generated text only — never one of your photos — because a forwarded link would otherwise leak the gift into every group it passes through.
- Gifts are not indexable. Every gift page is served with
noindex, nofollowand excluded in robots.txt, so a shared link cannot turn up in a search result. - We do not sell or rent anything to anyone, and we run no advertising or third-party tracking pixels.
Cookies and storage
Two categories, and only one of them is a choice.
Essential — always on. A signed cookie recording which gifts belong to this browser, so you can find what you built without an account; and a session cookie if you sign in. Refusing these would lock you out of something you paid for, so we do not offer that as an option. They contain no advertising identifiers and are readable by nobody but us.
Measurement — off until you say yes. The step-by-step builder analytics described above, plus the random session id it uses, stored in your browser's session storage. Nothing is written or sent until you accept the banner, and choosing “No thanks” keeps it off permanently on that browser. Your answer is remembered in local storage under sm_consent; clearing site data will ask you again.
There are no cookies from ad networks, social platforms or analytics vendors, because we do not embed any.
Who else touches your data
Only the services that make the product work, each doing one job:
- Razorpay
- Takes the payment. Receives your email, phone and the amount; handles your card details entirely on their own systems.
- Cloudflare R2 or Supabase Storage
- Holds the photos you upload, so gift pages can serve them.
- Resend
- Sends the receipt with your gift link, and password-reset emails. Receives your email address and the link.
- Google (Gemini)
- Generates suggested wording, under the strict limits described above. Never receives your gift, your name, or the recipient's.
- Upstash
- Counts requests for rate limiting, so one person cannot brute-force a gift PIN. Stores a hashed key, not an identity.
- Netlify
- Hosts and serves the site.
Some of these operate outside India, so your data may be processed abroad. We use them under their standard terms and send each the minimum it needs to do its job.
How long we keep it
- Published gifts — for as long as the gift exists, because the whole point is that the link keeps working. Deleting a gift from My gifts takes it offline immediately.
- Drafts you never paid for — kept so you can come back and finish, and removed during routine cleanups.
- Orders and receipts — retained as long as tax and accounting law requires, which we cannot delete on request.
- Sessions and reset links — expire on their own; reset links work once.
Your rights
You can ask us for a copy of what we hold about you, ask us to correct it, or ask us to delete it — including your account and every gift on it. Write to apnasurprise@gmail.com from the address on the account and we will act within 30 days. Deleting a published gift breaks its link permanently; we will say so before doing it, not after.
If you would rather not be measured at all, decline the banner — no account or email required.
Children
This is not a service for children. We do not knowingly collect data from anyone under 18, and if you believe a child has sent us information, write to us and we will remove it.
Complaints
Our grievance officer is Pawan Kushwah, reachable at apnasurprise@gmail.com. If something about how we handle your data is not resolved to your satisfaction, you may escalate to the Data Protection Board of India.
Changes
When this page changes in substance we update the date at the top. The wording lives in version control, so every revision is dated and reviewable rather than quietly swapped.