SECURITY AT R4ACO

Careful by
design.

The information behind an ACO deserves thoughtful protection. Here’s how access, credentials and history are kept in their proper place.

01

CREDENTIAL CUSTODY

A separate home for credentials.

Retailer credentials are stored in AWS Secrets Manager, apart from ordinary operational records. Staff can replace them without revealing the stored values.

02

SENSITIVE ACTIONS

Your sign-in, with clear limits.

Authorized staff can export using their Discord sign-in. Every download checks current permissions and an unexpired selection tied to the same user, workspace and login session. Customers cannot access operator credential files.

03

ACCESS BOUNDARIES

Your workspace stays yours.

Current membership and permissions are checked for protected operations. Another business’s owner does not become an administrator of your workspace.

04

ACCOUNTABILITY

A history you can follow.

Submission, assignment and export history remain attached to the operation. Important configuration and security actions leave a safe audit record.

05

PAYMENT DATA

No card-number or CVV storage.

R4ACO does not currently store card numbers or CVV. Profile exports have blank payment fields and are not checkout ready.

06

HONEST READINESS

Clear about what is verified.

Integration setup, external import compatibility and deployment checks remain separate requirements. We do not claim PCI, SOC 2 or other compliance certifications.

YOUR NEXT DROP STARTS HERE

Make room for
a better operation.

Request access

Your team. Your customers. One workspace.