Privacy notice
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)
- No accounts, no tracking. The site has no sign-in, sets no cookies of its own, and runs no analytics or advertising scripts.
- The request form sends your request to us. When you press Send, the name, company, email address and message you typed go from your browser to our service (api.verarails.com), which emails them to us. We use them only to reply to you and to arrange a walkthrough. We keep them in the mailbox that receives them; they are not stored in the VERA service database, we send you no automated email, and we do not sell them or share them for advertising. A short log line records that a request arrived (a reference number and the domain of your email address, not your name or message).
- Connection data. The site is delivered through Cloudflare, and its typefaces are loaded from Google Fonts. Those providers receive your IP address and ordinary request information when you load a page, and handle it under their own policies.
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:
| Category | What it includes |
|---|---|
| User accounts | Name, work email, role, the organization the user belongs to, last sign-in time |
| Sign-in security | A 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 records | An 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 data | Project name and address, site location, draw amounts and status, approvals and signatures, contractor names, lien-waiver records, site hazard-check results |
| Payment destination | A 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. |
| Documents | A 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 data | Borrower 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 records | Short-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
- The customer’s own signed-in users. Any user in the customer’s organization can read its project data; what a user can change depends on their role. Examiner accounts are read-only.
- VERA personnel, to operate and support the service. VERA is run by one operator. Sign-in to the application and to VERA’s decision service requires two-step sign-in.
- Service providers, only as far as each needs to do its job: Google Cloud (hosting, key and secret management, backup storage); Neon, which runs on Amazon Web Services (the database); Cloudflare (DNS, edge and system email); Google Fonts (typefaces for the website and the app); public hazard-data services, which receive a project site’s location when a hazard check is run; and the XRP Ledger, a public network that receives a hash only. During the pilot the ledger used is its test network.
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
- If your information is in VERA because of your job or your loan, ask your own employer or lender. They decide what is collected and are responsible for answering you. We help them respond. Deleting information may be limited by legal retention duties and by the hash-chained audit log.
- If you sent us a request or an email, write to ceo@verarails.com and we will tell you what we hold and delete it on request, unless we must keep it by law.
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.