Skip to content
SECURITY & RELIABILITY

Security

YAGIRO is designed around minimizing unnecessary movement of business data and automatically verifying software changes.

Browser-local processing

Reconciliation and the experimental spreadsheet tools process file contents in your browser. Contents are not sent to the validation API or an AI service. XLSX uses the first sheet and stored cell values; formulas are not recalculated.

Data boundary

Beta validation aggregates interaction events for reconciliation workflows and experimental systems. Sample and real-file milestones use separate events. Stored dimensions are date, event name, language, a fixed workflow or experiment ID, and aggregate count. Counts are interaction signals, not unique people or verified demand.

Automated verification

GitHub Actions checks Reconciliation and Experiment Factory unit tests, privacy and validation tests, Playwright browser E2E tests, dependency security auditing and production builds. Visual Audit images support visual review.

Production monitoring

Synthetic production checks are scheduled every six hours and cover language switching, CSV reconciliation, recipe persistence and experimental review flows. Monitor failures can automatically create a GitHub Issue.

Synthetic monitoring data

Production monitoring uses repository-owned test fixtures only. Customer Excel and CSV files are not used for monitoring, and synthetic monitor activity is excluded from demand-validation analytics.

Security limitations

No software or security system can be guaranteed to be completely free of defects or vulnerabilities. YAGIRO is currently a beta and uses testing, monitoring, and dependency auditing to reduce these risks.

Last updated: September 27, 2026