Identity and Authorization
Cloudflare Access verifies approved email identities with short-lived sign-in codes. PerfectCents then applies its own membership and role check. Both layers must permit access before a private workspace opens.
Administrative controls are separate from financial workspaces. An administrator can manage member status and roles without receiving a view of another member’s balances or transactions.
Encrypted and Masked Data
Sensitive financial and profile fields are encrypted before they are written to the database. Account and routing numbers appear masked by default and are revealed only in the authorized user’s private account view.
HTTPS protects information in transit. PerfectCents does not request or store bank passwords, PINs, or security-question answers.
Application Safeguards
Protected requests require authenticated membership. State-changing requests use same-origin checks and a trusted-request marker, while rate limits, strict browser security headers, private cache controls, and structured input validation reduce common application risks.
Security-relevant administrative actions create metadata-only audit entries without exposing financial contents.
A Smaller Connection Surface
PerfectCents uses manual entry and has no Plaid or direct bank connection. Institution URLs are stored only as user-provided links and are not used to retrieve credentials or account information.
What Users Should Do
- Protect the email account used for sign-in with a strong password and multi-factor authentication when available.
- Sign out on shared devices and keep devices updated.
- Never store credentials, PINs, recovery codes, or Social Security numbers in PerfectCents.
- Handle CSV and PDF exports as sensitive files.
- Report unexpected access or behavior promptly.
For setup walkthroughs, visit the PerfectCents Help Center ↗.
Questions and Reporting
PerfectCents is operated by RazorFXNetworking.com. Contact: L. Williams, Tulsa, Oklahoma. Visit the contact page for the current public contact channel.
Include a clear description of the issue, but do not send passwords, one-time codes, or full account numbers.