Role and entity-scoped access
Credit Reaper supports owner, admin, member, viewer, and assigned-entity access patterns.
Security
Trust foundations for Credit Reaper.
This page describes current access and architecture choices without claiming certifications or compliance programs that are not in place.
Trust model
What exists today and what is planned.
Audit history
Credit line, transaction, note, and status changes can be reviewed through audit-backed activity.
Environment separation
Public, preview, and production API/database environments are separated outside the browser app.
Account access controls
Workspace identity, role, and entity access controls are designed to limit records to authorized users.
No frontend secrets
The browser app only uses public environment variables and does not contain database credentials.
Private document access
Supporting documents are kept behind workspace permissions and served through controlled access paths.
Next step
Review related trust pages.
Security, compliance, privacy, and cookie pages are early access review materials and should be reviewed before broad commercial launch.