Last Updated: December 15, 2025
At Pixazo, security is a top priority. We are committed to protecting the confidentiality, integrity, and availability of customer data entrusted to us.
Pixazo (previously known as AppyPie Design) is a product registered under Pixazo LLP, a limited liability partnership incorporated in New Delhi, India (LLPIN: AAF-5370), with its principal place of business at 165, NSEZ, Noida, 201305, India.
This Security page outlines the technical, administrative, and organizational measures Pixazo takes to safeguard data processed through our platform.
1. Security Governance
Pixazo follows industry-recognized security best practices and internal policies designed to:
- Protect customer and platform data
- Prevent unauthorized access
- Detect, respond to, and recover from security incidents
Access to systems and data is limited to authorized personnel based on the principle of least privilege.
2. Infrastructure & Hosting Security
Pixazo is hosted on secure cloud infrastructure providers that follow global security standards.
Security measures include:
- Secure data centers with physical access controls
- Network firewalls and traffic filtering
- DDoS mitigation and monitoring
- Regular infrastructure patching and updates
3. Data Encryption
Pixazo protects data using encryption best practices:
- Data in transit is encrypted using HTTPS / TLS
- Data at rest is encrypted using industry-standard encryption mechanisms
- Sensitive credentials and secrets are stored securely and are never exposed in plain text
4. Application Security
Pixazo applies security controls throughout the software development lifecycle (SDLC), including:
- Secure coding practices
- Code reviews and testing
- Dependency and vulnerability monitoring
- Protection against common threats such as SQL injection, XSS, and CSRF
5. Access Controls
- Role-based access control (RBAC) is enforced across internal systems
- Multi-factor authentication (MFA) is used where applicable
- Administrative access is logged and monitored
6. API Security
Pixazo APIs are secured using:
- Authentication tokens / API keys
- Rate limiting and abuse detection
- Monitoring for unusual activity
Users are responsible for protecting their API credentials and must rotate keys if compromised.
7. Monitoring & Incident Response
Pixazo continuously monitors systems for suspicious activity.
In the event of a security incident:
- We promptly investigate and mitigate the issue
- Affected systems are isolated if necessary
- Customers are notified in accordance with applicable laws and contractual obligations
8. Data Backup & Recovery
- Regular backups are performed to protect against data loss
- Backup data is encrypted and stored securely
- Disaster recovery processes are in place to ensure service continuity
9. Vendor & Third-Party Security
Pixazo works with trusted third-party vendors for infrastructure, payments, analytics, and support services.
All vendors are evaluated for security practices and are contractually required to safeguard data.
10. Compliance & Privacy Alignment
Pixazo security practices are designed to support compliance with applicable data protection and security regulations, including:
- GDPR (EEA)
- India Digital Personal Data Protection Act (DPDP), 2023
- LGPD (Brazil)
- PIPEDA (Canada)
- PIPA (Japan)
Security controls work in conjunction with our Pixazo Privacy Policy.
11. Customer Responsibilities
While Pixazo implements strong security controls, customers are responsible for:
- Securing their account credentials
- Managing user access permissions
- Protecting API keys and integration secrets
- Ensuring compliance with applicable laws when using Pixazo
12. Reporting Security Issues
If you believe you have discovered a security vulnerability or incident related to Pixazo, please report it responsibly.
Security Contact:
Email: [email protected]
We appreciate responsible disclosure and will investigate all legitimate reports.
13. Changes to This Security Page
Pixazo may update this Security page to reflect changes in our security practices or regulatory requirements. Updates will be posted on this page.
English Version Controls
In the event of any inconsistency between translations, the English version shall prevail.
