The short version
How we protect information sent through this website, and how to report a security issue responsibly.
How we protect your enquiryLink to this section
Validated twice
Name, email and message are checked in the browser and again on the server before saving.
Private storage
Enquiries are stored in a private, secure cloud database. Public visitors cannot read, change or delete them.
Credentials stay server-side
Database credentials are kept on the server, never in the browser.
Write-only channel
The form only accepts new enquiries and returns a confirmation, never stored submissions.
Rate limiting
Repeated submissions from the same network or email address are limited.
Spam protection
A hidden field helps reject automated spam.
Product boundariesLink to this section
This page describes the company website's enquiry handling. Chitly and AstroSaathi are separate services; consult their own privacy and security information before sharing personal information. The interactive previews on this website do not create live calls or consultations.
Report a security issueLink to this section
Email security@praxxel.com
Use a clear subject such as “Security report: [affected page or product]”.
Describe the issue
Include the affected URL or product, what you found and its possible impact.
Add minimal reproduction steps
Give the smallest set of steps needed to reproduce it.
Remove sensitive data
Strip personal information, passwords and access tokens from screenshots and examples.
Our security contact is also published in /.well-known/security.txt.
Safe reporting guidelinesLink to this section
Don't access others' data
Only test with accounts and data you own.
Don't disrupt services
No denial-of-service, spam or destructive testing.
Keep details private
Don't publish sensitive details before the issue is addressed.
For non-security support questions, please use support@praxxel.com.
Our approachLink to this section
No security system can guarantee that an incident will never occur, so this page describes only measures that are in place today. We do not claim independent certification, a security audit or a bug-bounty programme.
