Data Infrastructure

Privacy Policy

Last Protocol Audit: December 21, 2025

1. Information Integrity

We maintain strict data collection protocols to optimize structural planning services.

  • Account Identity: Managed via authenticated email and profile verification.
  • Structural Data: All architectural inputs and system schemas provided by users.
  • System Logs: Transactional logs focused on resource usage and error analysis.
  • Financial Protocols: Managed via authorized third-party processors. No card data is stored on our primary infrastructure.
2. Data Processing Protocols

Data utility is restricted to the following engineering objectives:

  • Architectural Synthesis: To generate system schemas and PRDs based on authenticated inputs.
  • Infrastructure Management: To maintain system stability and resource allocation.
  • AI Governance: Inputs are processed via secure API; however, our enterprise service agreements prohibit model training on user data.
3. Storage & Systems Security

3.1 Infrastructure: PlanovaPilot utilizes Supabase (PostgreSQL) with full encryption protocols at rest and during transmission.

3.2 Session Persistence: We utilize secure, HTTP-only protocols for session management and anti-CSRF protection.

4. Data Rights

Users retain full authority over their structural data:

  • Access: Retrieve a complete schematic of collected data.
  • Deletion: Initiate full data purge protocols by contacting the support channel.
  • Portability: Request architectural data in standard structured formats.

System Administrator: support@planovapilot.xyz