Your chapter's money and data, protected.
Dueflow moves real money for real chapters, so security isn't a feature — it's the baseline. Here's exactly how we protect payments, accounts, and records.
Payments
Card and bank details never touch our servers
Every payment on Dueflow is processed by PCI DSS Level 1 certified payment partners. Card numbers and bank credentials go directly from the payer's browser to the processor — Dueflow's servers never see, store, or transmit them. We keep only what's needed for records: the payment amount, status, and the card's last four digits.
PCI DSS Level 1 processing
Payments run through certified processors that meet the highest level of card-industry security standards.
No raw credentials stored
Our database stores payment metadata only — never card numbers, CVCs, or bank login credentials.
Signed webhooks
Every payment event from our processors is cryptographically signature-verified before we act on it, with constant-time comparison.
Funds flow directly to your bank
Collected dues settle to your chapter's own account. Dueflow never holds or withholds your money.
Data protection
Encrypted in transit and at rest
All traffic to Dueflow is encrypted with TLS, enforced with HTTP Strict Transport Security. Your chapter's data is stored in an encrypted database, and every connection between our services is encrypted too. Secrets and credentials are managed in a dedicated secrets vault — never committed to code.
TLS everywhere
Every request to Dueflow travels over encrypted HTTPS, with strict transport security enforced at the edge.
Encryption at rest
Chapter data lives in encrypted storage with our infrastructure providers, including database and file uploads.
Vaulted secrets
API keys and credentials are injected from a managed secrets vault at deploy time and scrubbed from error reports.
Safe file uploads
Receipt and logo uploads require an authenticated session and are type- and size-restricted.
Access control
The right people see the right things
Every account requires a verified email before it can sign in, and sign-in attempts are rate-limited. Inside a chapter, role-based permissions decide who can move money and who can only view. Every query is scoped to your organization — members of one chapter can never see another chapter's data.
Role-based permissions
Admin, editor, and viewer roles per organization, with separate national and chapter access levels.
Verified sign-in
Email verification is required before first sign-in, with Google sign-in and one-time codes supported.
Organization-scoped data
Every record is tied to your organization. Cross-chapter access simply doesn't exist unless your nationals runs oversight.
Scoped API tokens
Developer API tokens are hashed at rest, bound to a single organization, and carry explicit permission scopes.
Monitoring
Watched continuously, scanned weekly
Errors and anomalies are monitored around the clock with automated alerting, and credentials are redacted from every report. Our codebase runs automated security scans weekly — static analysis for vulnerability patterns plus dependency audits — alongside secret scanning and review checks on every code change.
24/7 error monitoring
Automated monitoring and alerting on every production system, including scheduled-job health checks.
Weekly security scans
Scheduled static analysis (CodeQL) and dependency vulnerability audits run every week against the full codebase.
Every change reviewed
All code ships through pull requests with automated tests, lint gates, API-contract checks, and secret scanning.
Audit trails
Payments, reimbursements, approvals, and webhook events leave timestamped records — including who approved what, and when.
Security questions, answered
Found a vulnerability?
We work with security researchers acting in good faith. Report vulnerabilities to our security team and we'll acknowledge your report quickly, keep you posted while we fix it, and never pursue legal action for good-faith research.
/.well-known/security.txt