Legal

Security Information

How Pixirain protects accounts, payments and files, and how to report a vulnerability to us.

Last updated 12 October 2026

1. Payment architecture

The website opens Razorpay Checkout for payment; it does not present its own card-number or CVV form. The application handles order references, amounts, payment identifiers and status, and may hold a token reference for a payment method saved with Razorpay. Those transaction records are personal data and are protected accordingly.

Payment callbacks are sent to a server endpoint for signature verification, and the separate Pixirain backend has a Razorpay webhook route that checks signatures and records event IDs. These code controls do not prove how a live Razorpay merchant account, settlement, escrow or production TLS configuration is set up.

2. Accounts and files

Account access uses authentication controls, and access to project information is checked on the server. A separate storage provider is used for project uploads. No online service can promise absolute security. Use a unique password, protect your sign-in device and report activity you do not recognise.

3. Reporting a concern

Report a suspected account or payment problem to hello@pixirain.com. For a security vulnerability, write to hello@pixirain.com with enough detail to reproduce it, without including another person’s private data. We will review the report and respond through an appropriate channel.

Questions about this policy

Write to hello@pixirain.com . You can also raise it through the contact form, and signed-in users can open a support ticket from their account.

Other policies