Security
How we protect your data
Household income records are sensitive. This page describes, in plain terms, how Verifikor stores that information, who can see it, and how it is handled.
Where your data lives
- Verifikor runs on Railway, a cloud hosting provider, in its US West region in the United States.
- Account and certification data is stored in a managed PostgreSQL database.
- Uploaded documents are stored as files on a dedicated storage volume attached to the application. They are not publicly accessible: a file is served only to signed-in users of the organization that owns it.
- All connections to Verifikor use HTTPS. Requests made over plain HTTP are redirected to HTTPS.
Who can see your data
- Each customer's data is kept separate. Your team sees only your organization's properties, households, documents, and records.
- Access within your organization is set by role. You choose each team member's role and can change it or deactivate the account at any time.
- Our staff access a customer account only to provide support, and every such access is logged.
Admin
Manages the organization, its properties, team members, and billing.
Compliance Reviewer
Reviews cases, approves certifications and exceptions.
Staff
Creates and works cases and documents. Cannot finalize certifications or approve exceptions.
Auditor (read-only)
Views the properties and records they are given access to. Cannot make changes.
Sign-in
- Passwords are stored only in hashed form (bcrypt), never as readable text. Our staff cannot see your password.
- Sign-in sessions are stored on our servers. The session cookie is sent only over HTTPS and cannot be read by scripts on the page.
- Sessions expire automatically, and you can reset a forgotten password by email.
Certification records
- Records can't be edited after they're certified. A correction or recertification creates a new record that points to the earlier one, and the original is preserved.
- Every change is logged with who, when, why.
- Any certification can be re-checked at any time: Verifikor re-runs the same program rules on the information saved with the record and confirms the result still matches. Each re-check is itself logged.
- On audit day, you can prove what you certified on any date.
Documents and AI
- When a document is uploaded, it is read automatically to pull out income and asset figures.
- A person on your team reviews those figures. Values read from a document are not treated as verified until your staff approve them.
- Eligibility is decided by fixed, versioned program rules written into our software, never by AI. The same inputs always produce the same answer.
- Documents are read by OpenAI through its API. Under OpenAI's published API data policy, data sent through the API is not used to train its models, and OpenAI keeps abuse-monitoring logs for up to 30 days unless the law requires longer.
Service providers
We use the following service providers (subprocessors) to run Verifikor. Each receives only the information needed for its task.
| Provider | Purpose |
|---|---|
| Railway | Application hosting, database, and file storage |
| OpenAI | Reading income and asset details from uploaded documents |
| Resend | Sending email |
| Twilio | Sending text messages to tenants |
| Stripe | Subscription billing and payment processing |
We will update this list before adding or replacing a provider that handles customer data.
Reporting a security issue
If you believe you have found a security issue in Verifikor, use the contact form on our About page with a description and the steps to reproduce it. Please do not access or change other customers' data while investigating.
Questions about security for your portfolio? Use the same address and we'll reply by email.