Policy

Privacy should support clarity, not become another source of ambiguity.

This overview summarizes how Recuro approaches workspace data, reminder metadata, and account-scoped operational records.

Data minimization

Recuro is intended to store obligation context, schedules, reminder settings, and the operational data required to make recurring workflows reliable.

Collection

  • Only operationally relevant fields
  • Scoped account access
  • User-controlled workspace data

Notification data handling

Reminder delivery metadata may be retained to help users understand what was sent, what failed, and whether a fallback path was used.

Notifications

  • Delivery observability
  • Failure and retry context
  • Channel-aware auditability

Need more detail about how data is handled?

Reach out through support if you need environment-specific clarification for staging, deployment, or internal use policies.