Constantly Creating // Brutalist Protocol
Silence is architecture.
Protocol 02 // Privacy
静謐構造
Data is treated like a tokonoma: minimal, intentional, unseen by outsiders. We gather only what powers the build, encrypt it, then purge the remnants. Silence is part of the interface.
Logs cycle through rotating keys; credentials sit behind hardware tokens; access is whitelisted per project cell. Curiosity is not a valid reason to view information.
Collection Minimalism
We capture only what serves production: name, role, contact window, brand assets, and research inputs. Anything extraneous is refused or redacted. Analytics run through privacy-safe tooling with IP obfuscation.
Storage & Encryption
Assets live inside isolated cloud containers with role-based keys. Design files sit on zero-trust storage; credentials use a hardware-backed vault. Access logs are monitored daily and reviewed weekly.
Rights & Requests
Request exports, corrections, or deletion at any time. We verify identity, respond inside one business day, and execute within five. Compliance frameworks observed: GDPR, CCPA, and the spirit of Japanese APPI.
Directives
Clauses
Usage
Information fuels strategy, design, and development only. No advertising pools, no resale, no undisclosed research.
Retention
Active project data persists for the project duration plus 180 days for QA continuity. Afterward it is shredded unless contractual law demands longer retention.
Incident Response
Should a breach occur, we notify affected contacts within 24 hours with impact scope, mitigations, and remediation timeline.
Third Parties
Vetted collaborators receive the minimum data required. They are audited twice annually and bound to immediate purge obligations.
Contact Nodes