Privacy notice
Last updated: November 15, 2026
Who we are
DigiRDP, LLC, operating HostCrust · 30 North Gould St, Sheridan, WY 82801 · hello@hostcrust.com
This company is responsible for your data on this website (the "controller"). HostCrust is presented as HostCrust by RackVolt. The HostCrust app at app.hostcrust.com has its own section below.
What we collect on this website
If you take the survey
Your answers about you and your servers (role, company size, number of servers, where they run, who looks after them, whether your team uses agent tools on servers, compliance status, your part in buying, country and whether your company sells server services), your work email and whether we may email you. Also your answers about recent server problems, how you prove patches and test backups, how people get into your servers, what you'd need before letting automation change production, what you'd pay for and at what price, and what you'd like to do next. We record the tag in the survey link (for example ?src=email) and, if you came from our home page, the campaign tags in the link you followed (for example utm_source) and the website that linked to us (domain only).
If you ask to talk to a person or request early access
Your name, work email, company, time zone, the times that suit you (optional for early access) and your message. The request is stored on our server and emailed to our team's mailbox, which is on the same server, so we can answer it.
If you filled in our earlier application form
Before HostCrust launched, our home page had an application form. If you sent it, we hold your answers: role, company size, number of servers, where they run, who looks after them, which agent tools your team uses on servers, compliance status, your part in buying, country, whether your company sells server services, your work email, whether we may email you, anything you wrote in the optional box, which of two headlines you saw, and the campaign tags and referring domain described above. The form is closed and collects nothing new.
If you use Patch Proof
The inventory you paste or upload (your server's operating system release, kernel versions, installed package names and versions, and whether a reboot is pending) and the optional name for the report. Our website passes it to the Patch Proof service on the same server, which builds your report in memory and sends it back to your browser. We don't store the inventory or the report name. We keep only an anonymous count: the operating system release and how many issues of each kind were found, with no report name, package list or IP address. The same abuse limit as the forms applies.
If you only visit
Without cookies, we count page visits, whether pricing was seen, and clicks on "Start free", our free tools, the survey, the talk and early-access form and Patch Proof, with the campaign tags and referring domain described above. These counts carry no name, email, IP address or visitor ID.
To count each action only once, your browser stores a few small values in its local storage (which actions were counted, and the campaign tags). They stay on your device and you can clear them at any time in your browser settings.
If your browser sends a Global Privacy Control signal, we don't count your visit or actions at all.
To keep the site working and safe
To stop abuse, our server limits how often forms can be sent from one network. For that it keeps a one-way, keyed hash of your IP address for up to 2 hours; the hash isn't stored with your answers. Like most websites, our hosting provider and our security and content-delivery provider also keep standard technical logs of requests (such as IP address, time and page) for security and troubleshooting.
Why we use it
- To answer your request to talk or for early access, and to email you about HostCrust and our research if you said we may.
- To understand the problems teams have and what they'd pay for. Survey results are only reported in aggregate.
- To build the Patch Proof report you asked for, and to count anonymously which systems people check.
- To see which pages and links help people understand HostCrust.
We don't sell or share your information for advertising, and we don't use it to build advertising profiles.
Where website data is stored, and who else handles it
Survey answers, talk and early-access requests, earlier applications and visit counts are stored on our own server, in Canada.
We share data only with these recipients, which handle it for us:
- our hosting provider (servers in Canada)
- a security and content-delivery provider, which every request to this website passes through
- service providers that help us process and review responses
Some of these providers may process data outside Canada, including in the United States.
How long we keep website data
Survey answers, talk and early-access requests and earlier applications are deleted by 31 January 2028. Visit counts are kept only in aggregate: they never carry a name, email, IP address or visitor ID, and on that date we reduce them to daily totals. Abuse-prevention hashes are deleted after 2 hours. Patch Proof inventories are not kept at all.
The HostCrust app (app.hostcrust.com)
This section covers the app at app.hostcrust.com and the HostCrust agent you install on your servers. The company named under "Who we are" runs the app. The rest of this notice covers this website.
For the data your servers send (their names, status, inventories and action output), we act on your organization's behalf: your organization decides which servers to connect and what they may do, and we use that data only to provide and secure the service for your organization. In privacy-law terms, we're your organization's processor for that data. For your account, your sign-in history and the emails we send you, we decide how the data is used, as we do on this website. If your organization needs a data processing agreement, ask us at hello@hostcrust.com.
What the app stores
- Your account: your email address, and when you signed up, confirmed it and last changed your password. We store a hash of your password (argon2id), never the password itself. Your two-factor secret is stored encrypted, and your 10 recovery codes only as hashes.
- Your team: the organizations you belong to, their names and your role in each. If you don't name your organization when you sign up, we name it "My team". Invitations hold the invited person's email address and role.
- Sessions: for each signed-in browser, when it started and was last used, its browser description (user agent) and how you passed two-factor sign-in. The cookie holds a random ID; we store only a hash of it. Sessions don't store an IP address. Sessions started before we stopped storing it (15 November 2026) keep theirs until they end, at most 7 days after sign-in.
- Sign-in history: security events on your account, each with its time and IP address: sign-up, sign-ins and failed attempts, two-factor checks, password resets and changes (including wrong current passwords), new recovery codes and sign-outs.
- Abuse limits: short-lived counters of attempts per IP address and per account. Email addresses in them are replaced by a keyed hash. IP addresses are kept as they are.
- Your servers: the name shown in the app, the server's operating system details (from
/etc/os-release), its kernel and agent versions, which kinds of action its own settings allow, and the IP address it last connected from. The name is the server's hostname unless you choose one when you install the agent. You can rename it in the app. - Server status: each time the agent checks in (about every half minute), it sends the server's uptime and load, memory use, disk use for each local file system (with its mount point), the names of failed services, whether a reboot is needed, and the kernel's boot ID. We keep only the latest status and the latest IP address.
- Patch Proof inventories: when the agent starts, once a day, after every patch and when someone asks for a refresh, the agent sends the contents of
/etc/os-release; the running kernel's release, build and architecture; the file names of installed kernel images; whether a reboot is pending and which packages asked for it; and every installed package with its version, architecture and source package (on RPM-based systems, also its vendor). Inventories contain no hostname, IP address or user names, and no other file contents. We store each inventory with the security findings we work out from it. - Action requests and approvals: for each action someone asks for, the server, the action and its exact parameters (for example package names, a service name or, if your organization allows it, a shell command), the reason given, who asked, the policy that applied and its deadlines. For each decision, who approved or rejected it, their role, when they last passed two-factor sign-in, and any note.
- Action output and checks: each action's exit code and times, the last 64 KB of its output and of its error output, a summary of what changed (for example package versions before and after), and the check we run afterwards (for example which vulnerabilities were closed). Output holds whatever the command printed on your server. That can include file paths, service names, user names, IP addresses and log lines.
- Receipts: an append-only, hash-chained record of your organization's events. It covers the organization's creation and renames; invitations, members joining, role changes and removals; servers added, renamed, revoked, archived and unarchived (with the server's name); policy changes; Patch Proof results (counts only); and every step of every action, from request and decision to result and check. New entries name people only by account ID (an invitation, by its own ID). The app shows the current email address of people who are still members of your organization; anyone else appears as "former member" with their ID. Entries written before this change, made on 15 November 2026, may contain email addresses. Entries also keep what people typed or set: reasons, notes, shell commands, and organization and server names. For an action's output, a receipt holds only a fingerprint (SHA-256) and the length, not the output itself. Receipts can't be edited or deleted one by one, because the chain proves nothing unless it stays whole. They're deleted together with the rest of the organization's data (see "Deleting your account or organization" below).
- Receipt anchors: once a day while your receipts change, we email your organization's owners who have confirmed their email address the newest receipt's number and hash. We also record that number and hash in our server logs and in an append-only file.
- Emails we send: address confirmation, password reset and password-changed notices, invitations, approval requests and reminders, receipt anchors and two-factor lockout warnings. We keep each email's recipient, subject, status and times. We delete its text once it's sent, because the links in it work like passwords.
- Server logs: our web server logs each request with its time, method, page (with any token removed), status, size and duration, the IP address it came from, and the address of our security provider's server it passed through. The app's own logs record each request's time, method, page, status, duration and a request ID, with no IP address or email address. Apart from that, the app's logs hold IDs and counts, never passwords, tokens, email addresses, inventories or action output.
Paid plans aren't available yet. When they start, a payment processor will handle payments, and we'll update this section before then.
Why the app uses it
- To run the service you signed up for: show your servers and their patch status, run the actions your policy and approvers allow, check the result and keep the receipts.
- To keep accounts and servers safe: two-factor sign-in, limits on attempts, your sign-in history and investigating abuse.
- To send the emails the service needs.
- To see how the service is used: a daily internal report to our team counts sign-ups, servers and actions, and lists new accounts by email domain (free email providers grouped). It never includes names or email addresses.
We don't sell app data, share it for advertising or use it to build advertising profiles.
Where app data is stored, and who else handles it
The app and its database run on our own server in Los Angeles, in the US. Every night we copy an encrypted backup of the database to a separate server we operate in Canada, and keep another copy on the app server. The key that opens the backups is kept offline, on no server.
These recipients handle app data for us:
- our hosting provider (the app server in Los Angeles)
- a security and content-delivery provider, which every request to the app passes through, including the agent's
- an email delivery provider, which sends the app's emails (they reach it encrypted, through our server in Canada)
- service providers whose tools we use to run and support the app, who may see app data when they do
App data is stored in the US, and its backups in Canada. Some of these providers may also process it in other countries.
How long the app keeps it
While your organization uses HostCrust:
- Sessions end after 12 hours without use, or 7 days after sign-in. We delete them within an hour after that.
- Links in our emails expire after 30 minutes (password reset) or 24 hours (address confirmation). We delete them 7 days after they expire.
- Sign-in history is deleted after 12 months.
- Our daily internal report emails are deleted from our team mailbox (on our mail server in Canada) after 90 days.
- Email records (recipient, subject, status and times) are deleted after 90 days. An email's text is deleted as soon as it's sent.
- The text of an action's output (what the command printed on your server) is deleted 12 months after the action finished. We keep its fingerprint (SHA-256 and length), which its receipt also holds, and the action's status, exit code, times, summary of what changed and check results.
- For each server we keep the 3 newest inventories in full (more while a patch is being checked). Older ones keep only a summary: the operating system, kernel versions, package counts, issue counts and packages from outside the distribution.
- The app's own logs are deleted after 90 days; a copy in the server's system log is deleted sooner, after about 4 weeks. They don't contain IP addresses or email addresses.
- Web server logs are deleted after 14 days. They contain IP addresses, which we keep that long for security.
- Abuse-limit counters, which contain IP addresses, are deleted after about a day.
- Backups are encrypted and stored in Canada, and deleted after 35 days. The copy on the app server is deleted after 7 days.
- Your account is kept until you ask us to delete it, or until the last organization you belong to is deleted. Everything else (your organization, its members and invitations, its servers including revoked ones, inventory summaries, and its actions with their approvals, checks and receipts) is kept while your organization uses HostCrust, and deleted 30 days after the organization closes.
Deleting your account or organization
- How to ask: deleting an account or an organization isn't in the app yet. To delete yours, ask us at hello@hostcrust.com.
- When an organization closes (because you asked us to delete it, or because our terms with your organization ended), we delete all of its data, receipts included, 30 days after it closes. Only a record without personal data stays: the organization's ID, its receipt numbers and hashes in our append-only file, and a line in our deletion log, so we can show that other organizations' receipts weren't changed. Export your receipts first: admins and owners can still download them in the app until then. We also delete the accounts of its members who don't belong to any other organization. Records of emails we sent to people who were invited but never created an account are deleted by the 90-day limit on email records, which can be later.
- Backups: deleted data can remain in our encrypted backups for up to 35 more days, until those backups are deleted.
- Your own account: if you're the last owner of an organization that still exists, first make someone else an owner, or ask us to delete the organization. When we delete your account, we delete your memberships, sessions, sign-in history, two-factor details, recovery codes, email links, invitations sent to your address, queued emails to it, abuse-limit counters for your account, and the account itself. If you ever approved or rejected an action, we keep an anonymous account record instead (no email address, no password, disabled), because approvals can't be changed.
- What stays after your account is deleted: receipts keep your account ID, and entries written before 15 November 2026 may also keep your email address, because changing a receipt would break the record the organization relies on. The reasons, notes and commands you wrote, the approvals you decided and the actions you requested stay with the organization; the actions no longer link to your account. Copies stay in receipts your organization already exported, which can include your email address. For a limited time, data also stays in our backups (up to 35 days), web server logs (14 days) and the app's own logs (90 days, without IP addresses or email addresses).
What you can see, export or change in the app
- See: your Account page shows your email address, when you joined and last changed your password, how many recovery codes are left, and your 20 most recent sign-in events with their IP addresses. Every member of an organization sees its members and roles, its servers and their status and Patch Proof results, and its actions with their output and receipts. Admins and owners also see open invitations.
- Export: any member can download the receipt for one action (as JSON or a printable page) and the Patch Proof report for a server's latest inventory. Admins and owners can download the organization's receipts, up to 366 days at a time. In receipt exports, the hashed records hold no email addresses, except entries written before 15 November 2026. A separate list outside the hashed records gives the email addresses of current members and of invitations that were never accepted; former members appear only by ID. The printable page shows people the same way.
- Change: you can create new recovery codes, change your password (in the app with your current password and an authenticator code, or with an email link), and sign out. Admins can rename the organization and its servers, revoke a server (its agent stops and its waiting actions are cancelled, but its data stays), archive a revoked server to hide it from the list (nothing is deleted), change roles, remove members and cancel invitations. Only owners can change or remove another owner.
- Not in the app yet: deleting your account or an organization, leaving an organization yourself, deleting a server or its data, changing your email address, and exporting your account data, sign-in history, inventories or action output. Ask us for any of these at hello@hostcrust.com.
How we protect it
- Every user signs in with a password and an authenticator app. Approving a change needs an authenticator code from the last 12 hours; recovery codes can't approve.
- Each organization's data is kept apart in every database query, and our tests try to reach another organization's data through every page.
- The app's own database account can't edit or delete receipts or approvals, and the database refuses such changes too. They're removed only when a whole organization's data is deleted, by a documented procedure that needs separate administrator access.
- Connections are encrypted. The app server accepts web traffic only through our security provider, and its database can't be reached from the internet.
- The agent connects out to the app, and nothing connects in to your servers. Each server's own settings decide which kinds of action it will run.
- Backups are encrypted. We tested restoring them on 14 November 2026.
Your choices
You can ask us to show, correct or delete what we hold about you, on this website or in the app, at hello@hostcrust.com, and change your mind about emails at any time. Residents of some US states, the UK and the EU have these rights by law; we offer them to everyone.