What this site does with your details

Who I am

I'm Ankit Dimri, a software engineer in Dehradun, India. This site, portfolio-nine-orcin-33.vercel.app, is mine and I run it myself. For any question about your details, or to have them deleted, email dimri.ankitdimri@gmail.com.

What it collects, and why

• Schedule a call. When you book a call, you give your name, your email, the time you picked and your time zone, and if you like, a phone number and a note. They're used to put the call in my Google Calendar with a Google Meet link and to send you the invitation, which Google Calendar emails to you. The event, with your name and email, stays in my calendar. Your phone number and note aren't in it: they come to me in an email. I use your phone number only about the call, for example if it needs to move. So the form can't be used to send invitations to other people, the server counts the calls booked for each address for a week, and from each IP address for a day, under a one-way code made from it (a hash), never the address itself.
• The contact form. Your name, email and message are saved in my database and emailed to me, so I can reply. So the form can't be used to flood my inbox, the server counts the messages from each email address and each IP address for a day, under a one-way code made from them (a hash), never the address itself; past a few, your message is still saved and I read it in my database.
• The resume builder. What you type stays in your browser until you ask for the PDF. Then your email address and your resume are saved in my database for 30 days, or until your plan ends, so the link in the email works, and deleted after that. Only you and I can see them: you with that link or by signing in, and I on an admin page only my address can open. The email comes from my Gmail, with a link to download your PDF and a link to edit or delete the resume sooner. It greets you by the first name on your resume; nothing else you typed is in it. The PDF is made from the saved resume each time you open it.
• Paying for PDFs. You pay through Razorpay, on the page the email's link opens: your UPI ID, card or bank details go to Razorpay, not to me. I keep the address the PDF was sent to, what you paid and when, and Razorpay's order and payment numbers, for my accounts; with a plan, the date it ends too, and if I refund a payment, when. Each payment's order ID and status (paid, failed or refunded) come to you by email, from my Gmail. Razorpay handles the payment under its own privacy policy.
• Paying by UPI. Until card payments open, the page the email's link opens shows my Google Pay QR code and UPI ID. A UPI payment happens in your UPI app, between your bank and mine: the site never sees it. As with any UPI payment, I see the name your bank has for you, your UPI ID and the amount, and I use them for nothing else. To unlock your PDF, you send me the payment's reference number: I keep it with the amount, the address and the date, to find the payment in my account and for my accounts. One I couldn't find is deleted after 30 days.
• Signing in (optional). To see your saved resumes on any device, you can sign in with Google, which tells me your email address and name, or with a one-time link emailed to you. Your account is that address, your name, the dates you joined and last used it, and, while you're signed in, your drafts (up to 5 versions), saved as you type so you can carry on from another device. It's deleted with its drafts 30 days after you last used it if you have no saved resume, or at once with “Delete my data”. There are no passwords.

That's all. There are no newsletters, and nothing is sold, shared for advertising or used for anything other than what's above.

Google Calendar, Gmail and Google user data

The site's server uses Google's Calendar API with my Google account only. It checks when I'm busy (not what my events are), so it can show free times, and it adds the calls you book to my calendar with a Google Meet link. It also uses Gmail's API, with my account, to send the resume builder's emails: it can send email, and can't read any. If you choose “Continue with Google” to sign in to the resume builder, Google tells the site your email address and name, and nothing else; it never reads anything else of your Google account.

The use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

The services that handle it

• Vercel hosts this site, and makes the resume builder's PDFs.
• Render runs its server (the API), behind Cloudflare.
• Neon is the database where contact messages, resumes (for 30 days), accounts with their drafts, and the counts that stop repeated requests (below) are saved.
• Google holds the calendar events and the Meet calls, sends the resume builder's emails from my Gmail, and signs you in if you continue with Google.
• Resend sends the emails that tell me about messages and bookings.
• Razorpay takes the payments for PDFs and plans.

Each one handles the details only to provide its service. As with any website, their logs may briefly record your IP address. The server also uses your IP address to stop repeated requests: in memory only, except that for sign-in emails, ₹1 payments, contact-form messages and calls booked it keeps a count for a day, and for sign-in emails a count for each address for an hour, under a one-way code made from them (a hash), never the IP address or email address itself.

In your browser

No cookies, no analytics, no tracking. Your browser keeps a few things in its local storage: light or dark theme, the 12- or 24-hour clock for the scheduler, the brain map's settings, and the resume builder's draft and any job posting you paste into its ATS check, and, if you sign in, your session (for 30 days, or until you sign out), a random code that makes an email's sign-in link work at once only in the browser that asked for it (for an hour), and, signing in from the builder, a note to take you back to it (for an hour). They never leave your device, unless you ask for your resume's PDF or sign in (above). The map of Dehradun in the footer loads from OpenStreetMap only if you open it, and Razorpay's payment window only when you pay. The project demos and this site's activity numbers, in the Work section, load from GitHub as you scroll to them.

How long it's kept, and your choices

• Calendar events and contact messages are kept until I delete them. If a call is cancelled, I delete its event.
• A resume from the builder is deleted 30 days after you ask for its PDF (or when your plan ends, if that's later), or sooner with the link in the email or in My resumes.
• Payment records, refunded ones too, are kept for my accounts. Orders that were never paid are deleted after 7 days, payments that failed after 30, and a plan's end date when it ends.
• An account, with its drafts, is deleted 30 days after you last used it when it has no saved resume, or at once with “Delete my data”.
• The counts that stop repeated requests are deleted within 8 days.
• An encrypted backup of the database is kept on GitHub for up to a week, then replaced by the next one, so what's deleted is gone from it within a week too. It holds no sign-ins and none of those counts.
• Email me to see, correct or delete what you've sent, and I'll do it.
• You can decline or remove the calendar invitation at any time.

Changes

If this page changes, the date at the top changes with it.