Protected team access
Team access uses password-protected staff sessions with owner and editor roles. Publishing, uploads, enquiries and donation records require authorisation on every API request. Accounts must be created by the PORD administrator.
Safe forms and content
Forms use server-side validation, size limits, same-origin checks and submission rate limits. Database statements use bound parameters. Blog content is rendered through a limited Markdown format; scripts and arbitrary HTML are not executed. Image uploads accept JPEG, PNG and WebP signatures and are stored separately from application code.
Payment verification
Payment orders and subscription plans are created on the server. Razorpay checkout signatures and webhook signatures are verified. Payment status, amount, currency and order or subscription association are checked before a payment is marked paid. A browser success message alone is not treated as proof of donation.
Sensitive information
Card, bank and UPI credentials are handled by Razorpay. API secrets stay in server configuration. If tax-receipt requests are enabled, donor PAN values use authenticated AES-GCM encryption and are disclosed only to authorised staff for receipt processing.
Ongoing responsibilities
Security requires maintenance, access reviews, monitoring and responsible staff use. This website does not claim an independent security audit, OWASP certification, PCI certification or a guarantee that vulnerabilities cannot exist. Test-mode payment checks and a provider connection review are required before accepting live donations.
Report a security concern
Email pord.org93@gmail.com with a brief description and the affected page. Do not include donor details, passwords, payment credentials or exploit sensitive information. Ask the team how to share technical evidence securely.
Read the privacy notice ↗