Privacy

Privacy notice

Last updated October 17, 2026

VERA holds as little personal information as it can. This notice covers two things: this website, and the VERA service, which is built for banks and lenders.

1. Who we are

VERA Platform LLC, a Wyoming limited liability company (“VERA”, “we”). Questions about this notice: ceo@verarails.com.

2. This website (verarails.com)

3. The VERA service (app.verarails.com)

The VERA service is built for banks and lenders. When a customer puts information about its loans, projects and people into VERA, the customer decides what is collected and why. VERA handles it on the customer’s behalf as a service provider, under a written agreement signed before the service is used. The service holds:

CategoryWhat it includes
User accountsName, work email, role, the organization the user belongs to, last sign-in time
Sign-in securityA salted one-way hash of the password; an authenticator secret (encrypted by the application before it is stored) and hashed backup codes; the user’s public signing address. VERA never holds a user’s private signing key or signing passphrase
Activity recordsAn audit log of who did what and when, with a network address for each action. Because the site and the app are delivered through Cloudflare, the address recorded may be the provider’s rather than the user’s own.
Project and draw dataProject name and address, site location, draw amounts and status, approvals and signatures, contractor names, lien-waiver records, site hazard-check results
Payment destinationA project’s routing and account numbers, encrypted by the application before they are stored. The Bank Desk and the release notice show the last four digits only.
DocumentsA fingerprint (hash) of each supporting document, made in the user’s browser, and a reference to it. The service has no feature for uploading the document itself
Other project and organization dataBorrower name and an optional loan number on each project; funding source names and amounts; counterparty names and notes; subcontractor contact emails; invitation email addresses
Network recordsShort-lived network-address records used to spot abnormal traffic

What the service is designed not to hold. The database has no fields for Social Security numbers, dates of birth, payment-card numbers or government ID numbers. The customer agreement asks customers not to enter them in free-text fields.

4. How we use it

To run the service for the customer: to sign people in, enforce approvals, apply release checks, produce the audit record, provide examiner access, keep the service secure and give support. We do not sell data, and we do not use customer data for advertising.

5. Who can see it

6. Where it is kept

Customer data is stored in the United States (Google Cloud us-east1; Neon on Amazon Web Services us-east-1). VERA staff may reach the service from outside the United States, over encrypted connections, to run and support it. Notice emails go to the addresses the customer gives us. The public ledger receives only a hash, which carries no names, amounts, account numbers or documents.

7. How long we keep it

Retention periods for a customer’s data are set in the customer’s agreement with VERA. The audit log is hash-chained, so a changed or removed entry shows up when the log is checked. The database refuses edits and deletes of log entries. Nightly database backups are set to be deleted after 35 days. Short-lived traffic data used to spot abnormal activity is deleted by an hourly job once it is 48 hours old. Our hosting provider also keeps standard request logs, including network addresses, for its own set period.

8. How we protect it

Two-step sign-in is required on every account. Bank account details and authenticator secrets are encrypted by the application before they are stored, and connections use TLS. See the Security page for more.

9. Your choices

10. Children

This website and the service are for businesses and are not directed to children.

11. Changes

We will update this notice when our practices change and will show the date above. We will tell customers before a material change that affects their data.