Privacy Policy

1. Who we are

Tech Sewak operates the website at techsewak.com and related member services. For privacy requests, use the Contact channels published on this site. Do not send passwords or one-time codes by email.

2. Personal data we process

• Account & identity: name, email, phone, organisation role, and authentication identifiers from Google, Microsoft, or LinkedIn when you choose that provider for social sign-in.
• Membership & events: registration details, attendance records, and service communications needed to run programmes.
• Donations: donor name, email, amount, and payment-partner references when checkout is configured. This site does not store full card numbers. Tax-receipt treatment is outside this notice.
• Technical: security logs, session tokens, and—only if you consent on this browser— optional analytics or experience data described in the Cookies Policy.

3. Purposes and lawful basis

• Create and secure member accounts; authenticate sessions
• Operate events, donations, and authorised member portals
• Send transactional notices (security alerts). This application does not email 80G tax receipts.
• Meet legal, tax, and audit obligations where applicable
• Optional website features — Experience & Preferences, Social Media Interactions, and Analytics & Performance — only after website cookie consent on that browser

Account creation requires a short privacy consent checkbox linking this Policy and the Cookies Policy. That account consent is separate from browser cookie preferences.

4. Sharing

We share data only with parties needed to run a feature you use, or when required by law. We do not sell personal data. Partner attendee lists are shared only with explicit consent and purpose limits.

The application is built to call these parties when the feature is configured or used: Google, Microsoft, and LinkedIn for social sign-in; Cloudflare for DNS, TLS, and CDN when the public hostname is proxied; the MySQL database on the host that runs this site; Razorpay for donation checkout only when payment keys are configured (this site does not store full card numbers); and an SMTP or email relay for transactional mail when configured. If email is not configured, the server logs a masked recipient and subject, not the message body. Google Analytics loads only after analytics cookie consent. Phone one-time codes are created on the server; this codebase does not connect an SMS provider. This paragraph names code paths. It is not a completed contract review, a data-processing agreement, or a tax or 80G certification.

5. Retention

We keep account and transaction records for as long as needed for membership, legal, and audit purposes, then delete or anonymise them. Cookie preference records store category choices, version, timestamp, and an anonymous browser consent id — not passwords.

6. Security

We use HTTPS, short-lived sessions, rate limits on authentication, server-side access control, and input validation. OAuth client secrets are stored in server environment variables or in encrypted server-side records. They are not placed in the browser.

7. Your rights (DPDP)

You may request access, correction, or erasure where applicable, and withdraw consent for optional processing. Withdraw website cookie consent anytime via Cookie Settings. You may escalate to the Data Protection Board of India as provided under DPDP.

8. Children

Membership services are intended for adults and authorised organisational users. We do not knowingly create accounts for children without verifiable guardian consent as required by law.

9. Changes

Material changes to cookie categories bump the cookie consent schema version and may re-prompt the website banner. Policy version numbers above are updated when this text changes.