Privacy Policy

Last updated: 4 October 2026

Information you provide

When you contact Xender Secrets by email, WhatsApp or another linked service, we may receive the information you choose to provide, such as your name, contact details and project requirements.

How information is used

Information you provide may be used to respond to enquiries, discuss requested services, deliver agreed work, maintain business records and meet applicable legal obligations.

Third-party services

This website may link to third-party services such as WhatsApp and LinkedIn. Their handling of information is governed by their own policies. Xender Secrets does not control those external services.

Cookies and analytics

The current website does not intentionally set advertising or analytics cookies. Infrastructure providers may process limited technical information necessary to deliver and secure the website.

Your choices

You may contact us to ask a privacy-related question or request correction or deletion of information you previously supplied, subject to records we may need to retain for legal or legitimate business purposes.

Contact

Privacy enquiries: Sahilsharma171098@gmail.com.

Account registration

When you create a customer account, we store the name and email address you provide, a one-way derived password hash with a unique salt, account timestamps, and server-side session records needed to keep you signed in. We do not need or intend to store plaintext passwords. Authentication cookies are used to maintain signed-in sessions.

Orders and enquiries

When you submit an order or enquiry, we may store the information needed to process it, including your name, email address, phone number, delivery address, order items, order value and request status. This information is used for fulfilment, customer support, business records and applicable legal obligations.

Community activity

Community posts, comments and display names are public. We store the content you publish, engagement records such as likes, basic activity counts and reports submitted for moderation. Do not post passwords, payment credentials, private identity documents or another person’s private information.

Email OTP and social sign-in

If you use email OTP, we process your email address and temporary verification-code records needed to complete sign-in. If you use Google, GitHub, Facebook or X sign-in, the provider may send us an account identifier, display name and—where the provider makes it available—an email address. Provider access tokens are used only to retrieve the sign-in profile during authentication and are not intentionally stored as long-term account credentials.