Skip to main content

Version Docs Updated

Purpose

This guide covers data protection in the Rentiva infrastructure, GDPR/KVKK compliance, and incident response processes.

🔒 Security & Privacy Operations

Rentiva operates under the "Security by Design" principle, maintaining strict control over data from the moment it is collected to the moment it is destroyed.

🛡️ Security Layers and Tools​

🔑 Access Control (AuthHelper)​

All admin and API access passes through AuthHelper::verify_request().

  • Capability Checks: Operational actions can be restricted with the custom rentiva_financial_manager capability instead of manage_options.
  • API Key Rotation: API keys should be rotated every 90 days as a precaution against potential compromise.

🛡️ Input Security (SecurityHelper)​

Every value entering the database passes through SecurityHelper::validate_* methods:

  • XSS Protection: HTML content is filtered through a whitelist via wp_kses.
  • SQLi Protection: Raw SQL is prohibited; all queries are parameterized using $wpdb->prepare().

⚖️ Data Privacy (Privacy & GDPR)​

🧹 Data Anonymization​

When a user account is deleted or the legal retention period expires:

  • PrivacyManager::anonymize_user_data() is triggered, masking names, email addresses, and IP addresses as deleted_u_{id}.
  • Rule: Financial Ledger records are anonymized but not deleted, in order to preserve accounting integrity.

📅 Data Retention Policy​

  • Web Logs: Automatically purged after 30 days.
  • Audit Logs: Retained as read-only for 2 years as required by law.

🚨 Incident Response Protocol​

When a data breach or anomaly is detected:

  1. Isolation: Affected IP addresses are globally blocked via RateLimiter.
  2. Snapshot: The current state of the database is backed up for forensic analysis.
  3. Analysis: AdvancedLogger records are scanned to determine the scope of the breach.
  4. Notification: Affected users and authorities are notified within the legal timeframe (72 hours for GDPR).

🔄 Security Flow Diagram​

Section Summary​

  • Security operations follow the "Least Privilege" principle.
  • Ledger data is the most sensitive part of the system; direct intervention is prohibited.
  • Privacy and security are guaranteed through continuous monitoring.

Changelog​

DateVersionNote
23.04.20264.27.2English translation added.
19.03.20264.21.2Page updated with SecurityHelper and anonymization protocols.