About this policy
Amirreza Khodaee operates amirreza.me, a portfolio with accounts, bookmarks, developer tools, contact requests, live chat and job applications. This policy explains how information is handled when you use these features. For privacy questions or requests, use the contact page linked below.
Information you provide
An optional account stores name, email, profile image, role and sign-in information; passwords are stored as hashes. Guest conversations store your chosen name, email, email-confirmation status, messages, attachments and timestamps. Enquiries store your message and optional project details. Applications store the submitted name and email, message, optional phone, portfolio link, optional resume and review status. Website tools process input in your browser and do not create new account usage logs. Historical tool usage records may remain until removed by the administrator.
Google and other sign-in providers
If you choose Google, GitHub or LinkedIn sign-in, the provider shares the account identifier and profile information allowed by the sign-in flow, such as name, email and profile image. The authentication system may also store provider tokens and their expiry. This information is used to authenticate you and link your portfolio account. Google sign-in is for identity; the portfolio does not request access to your Gmail messages, contacts or Drive documents.
Why information is used
Information is used to answer enquiries, manage conversations, manually review applications, save optional bookmarks and limit abuse. Guest text chat needs no account or email confirmation; files and applications require a confirmed email. Email confirmation proves mailbox access, not identity. Emails include enquiry and application receipts, confirmation and access links, new-chat alerts to the administrator, reply notices to confirmed emails and application-status changes. Chat notices are grouped to reduce email volume. IP addresses support request limits, and infrastructure may generate security and diagnostic logs.
Cookies and browser storage
Account sign-in and guest access use private session cookies. A guest cookie expires after 30 days; clearing it removes this browser’s access but does not delete server records. Email access links expire after 15 minutes, work once and must remain private. Access tokens use URL fragments so they are not sent in HTTP requests or referrers. The site remembers language and appearance preferences, and the login page temporarily keeps the last email in session storage. The web app caches public assets; private API responses and account pages are excluded from runtime caching. Email confirmation opens an existing account first; otherwise it provides temporary guest access and does not automatically create an account. Signing in to an account with a confirmed email links confirmed guest history for that email. Unconfirmed history also requires that guest’s valid session in the current browser. Matching email text alone does not transfer history. Signing out ends both account and guest access in this browser. Session creation and last-activity timestamps are stored; the administrator can see recent guest activity and unexpired guest sessions. The site cannot detect whether a browser has deleted its cookie.
Access, service providers and external pages
The site administrator can access contact requests, chats, account information and applications to operate the service. Hosting, database and email providers process information needed to deliver those services. Data may be processed outside your country depending on the deployed infrastructure. Opening Google Calendar booking loads Google content only after you choose to show it; booking details go directly to Google. External project links and social networks have their own privacy policies. Personal information is not offered for sale.
Storage, retention and security
Records, chat attachments and resumes are stored in the database and protected by account or private-session access controls and administrator permissions. Notification emails use a database queue with SMTP retries; their text and HTML are cleared from the queue after delivery. Private chat text and uploaded files are not included in notification emails. Expired guest sessions and access tokens are cleaned up by the notification worker. Accounts, conversations, enquiries, applications and files have no automatic deletion deadline and remain until removed by the administrator; backups and security records may persist longer. No service can guarantee complete security. Avoid submitting unnecessary sensitive information.
Your choices and requests
Accounts are optional. With a confirmed email and private session you can return to an application, check status and update details or your resume. If you clear the cookie, request a new email access link. Entering another person’s email does not reveal their history. Account profiles and bookmarks can be edited. Use the contact page to request a copy, correction or deletion of messages, files or other records; confirming mailbox ownership may be needed to protect privacy. Data deletion is handled by the administrator. Your legal rights depend on applicable law.
Updates
Changes to this policy are published here with an updated date. If you have questions about how a feature handles your information, contact the site operator before submitting it.