Security First

Your payment information is handled with the highest level of security. All payments are processed by Paddle, our Merchant of Record, which means Paddle is the authorized reseller of PeekPosting subscriptions and is responsible for payment processing, tax collection, and compliance in your region.

How Payment Processing Works:

• Step 1: You enter your payment information on our secure checkout page, hosted by Paddle
• Step 2: Your card data is encrypted and sent directly to Paddle (we never see or store it)
• Step 3: Paddle validates and processes the payment through secure banking channels
• Step 4: You receive an instant confirmation and email receipt from Paddle
• Step 5: Your subscription is activated as soon as payment is confirmed

Your PeekPosting account contains valuable business data and connected social media accounts. We implement multiple layers of security to ensure only you can access your account.

Account Recovery:

If you forget your password or suspect your account has been compromised, you can initiate account recovery through our secure password reset process. You'll receive a time-limited recovery link to your registered email address.

All your data is encrypted both in transit and at rest using industry-standard encryption protocols. Our infrastructure is built on secure, redundant systems to ensure maximum availability and data protection.

Infrastructure Security Measures:

• Firewall Protection: Multi-layered firewalls protect against unauthorized access
• Intrusion Detection: Real-time monitoring and alerting for security threats
• Network Segmentation: Isolated networks separate critical systems and data
• Regular Security Audits: Quarterly penetration testing and vulnerability assessments
• Patch Management: Automated security updates applied within 24 hours of release
• Access Controls: Role-based access with principle of least privilege

PeekPosting maintains compliance with international security standards and data protection regulations.

Data Protection Compliance:

• GDPR Compliance: Full compliance with EU data protection regulations including data subject rights
• Data Processing Agreements: Standard contractual clauses for international data transfers
• Privacy by Design: Security and privacy built into every feature from the ground up
• Transparent Policies: Clear privacy policy and terms explaining how we use your data
• Data Minimization: We only collect and retain data necessary for service provision

When you connect social media accounts to PeekPosting, we take extra precautions to ensure your connected accounts remain secure and protected.

What We Can and Cannot Do:

• ✅ We CAN: Publish posts you schedule, retrieve analytics, and view your profile information
• ✅ We CAN: Access publishing permissions and engagement metrics
• ❌ We CANNOT: Read your private messages or DMs
• ❌ We CANNOT: Change your password or security settings
• ❌ We CANNOT: Post anything you haven't explicitly scheduled
• ❌ We CANNOT: Delete your social media account

Despite our best efforts, security incidents can occur. We have a comprehensive incident response plan to quickly detect, respond to, and recover from security events.

Our Incident Response Process:

• Detection: 24/7 monitoring systems alert our security team immediately
• Assessment: Rapid evaluation of incident scope and severity
• Containment: Immediate action to prevent further damage or data exposure
• Eradication: Removal of threat and securing affected systems
• Recovery: Restoration of services and verification of security
• Communication: Transparent notification to affected users within 72 hours
• Post-Incident Review: Analysis and implementation of preventive measures

Responsible Disclosure:

• Report the issue to peekposting@gmail.com before public disclosure
• Provide detailed information to help us reproduce and fix the issue
• Give us reasonable time to address the vulnerability
• Avoid accessing, modifying, or deleting user data

We commit to acknowledging your report within 24 hours. We do not take legal action against security researchers who follow responsible disclosure practices.