Privacy
Privacy policy
How authentication and data handling work on this portfolio, especially for Recruiter Concierge.
This page applies to aviral-malik.in and www.aviral-malik.in. Last updated: 19 July 2026.
Purpose of login
Google or Microsoft login is used only to establish a session for the Recruiter Concierge chatbot. Sign-in is not used for marketing lists, advertising profiles, or unrelated account systems.
Scopes and access
This application does not request access to Gmail, Outlook, contacts, calendars, Drive, OneDrive, or other mailbox or file contents. Authentication is limited to basic identity information needed to complete OAuth sign-in.
Identity information during login
Google or Microsoft may return basic identity information as part of the login profile (for example, name, account subject identifier, and email address). This portfolio may temporarily process that information to create and validate a secure chatbot session. Temporary session handling is separate from long-term database storage.
Email and the database
The application does not persist your email address in its database. Email is not written to DynamoDB as a stored field or partition key.
Usage limit records
To enforce the Recruiter Concierge allowance of up to 20 questions per seven-day window, the application stores a pseudonymous HMAC identifier derived from the OAuth provider and account subject. The stored usage record contains only the protected identifier, message count, reset time, and TTL. It does not store your email address.
Chat history
After you are signed in, questions and answers you send through the Concierge may be stored temporarily under the same pseudonymous identifier so the conversation can continue within the session window. These records expire via TTL and can be cleared from the chat UI. Clearing chat history does not reset the usage counter.
Contact form
If you use the contact form, the details you submit (such as name, email, and message) are sent by email so I can reply. That flow is separate from Recruiter Concierge OAuth and is not used to create the chatbot usage identity.
Privacy requests
For privacy questions or requests related to this site, use the contact page. I will review requests about Concierge authentication, usage records, or contact-form messages.
Questions? Use the contact page. →