Privacy Architecture
We treat your digital footprint with the same precision we apply to our game engines. This policy outlines the mechanics of how data flows through Wide Horizon Z’s digital infrastructure.
It is a manifesto for minimal data retention and transparent operations.
01. Minimal Input
We only request essential contact information to facilitate studio partnerships and engine inquiries.
02. No Tracking
No invasive behavioral analytics. We do not sell, rent, or trade your personal data to third parties.
03. Full Control
You own your data. Request deletion or export at any time via our dedicated channels.
The Entry Point
Wide Horizon Z operates as a static showcase. Consequently, we do not utilize persistent databases for user accounts or authentication. The "entry point" is strictly limited to the Contact form.
What we collect:
- Identity: Name (provided voluntarily).
- Communication: Email address (required for response).
- Context: Message content (your inquiry details).
What we process:
We use standard, encrypted email protocols to communicate. Data transmitted via the contact form is routed directly to our internal secure email server and is not stored in a web-accessible database.
Data Protocol
Secure Direct Link
Evaluation & Robustness
This privacy framework is evaluated against a "Zero-Trust" architecture principle. We assume that the web is hostile; therefore, we collect nothing we don't strictly need. The robustness of this system relies on the absence of complex databases. By avoiding SQL or NoSQL structures, we eliminate the risk of large-scale database breaches. The limitation here is purely functional: we cannot "remember" returning visitors or offer personalized experiences, which is a deliberate trade-off for security. (See Trade-offs below).
Trade-offs & Mitigations
-
1.
No User History We cannot track return visits or load previous messages. Mitigation: We archive correspondence locally for continuity if you email us directly.
-
2.
Form Reliance Connectivity issues during submission may result in lost data. Mitigation: Client-side validation checks connectivity before submission.
-
3.
Legal Jurisdiction Data is stored in accordance with Italian (EU) law. Mitigation: Explicit consent captured in contact logs for GDPR compliance.
Data Governance Questions?
If you suspect a data breach or wish to have your information purged from our local records, please reach out directly to our privacy officer.
Ready to collaborate?
Visit our dedicated channel for inquiries and collaboration.
Open Contact Channel