Beyond the BeatSIYAA’S PULSELAB
Documentation library

Privacy / PUBLIC-SAFE SUMMARY

Local data, protected writes and backup limits

Implemented protection with explicit recovery limits

Research records remain on the study iPhone in their own mode directory. Local atomic writes use iOS complete file protection, with rollback after a failed write. Raw samples use append/deduplication rules and preserve session provenance.

App-specific backups use authenticated AES-GCM encryption and a device-bound Keychain key. Creation and restore require device authentication. Restore checks integrity and mode before replacing data.

An opt-in 7 PM reminder prompts a backup; it is not an automatic guarantee that a Mac backup exists. Replacement-device/Mac key recovery is not implemented, so the current backup is not a complete phone-loss recovery solution.

The approved handling policy excludes participant research data from GitHub, prompts, evidence logs and external AI tools. Public website assets are selected independently of study storage.

Retention is purpose-limited, with annual review. Final duration, key recovery and deletion-audit details remain parked; no completed deletion system is claimed.

Supporting workspace artifacts

Source locations identify the original artifacts in the private project. Raw files are not publicly served. Hashes identify the reviewed source snapshot; they are provenance, not external certification.

Download public-safe provenance