Log inRequest early accessStart free trial

Trust Center

How we look after your company.

What hlpr does today to protect your data, described plainly. When something here changes, we update this page.

System statusPrivacy Policy

Sign-in

  • Two-factor sign-in (an authenticator app) is required for every company owner and every hlpr administrator.
  • Passwords are at least 12 characters and stored only as salted hashes.
  • Two-factor secrets are encrypted at rest.
  • Sign in with Google is offered too. It reaches only accounts that already exist or have an invitation, joins an existing account only once its email address is verified (by the invitation link, or a link we email), and owners and administrators still enter their two-factor code after it.
  • You can see your active sessions and sign out of all others.

Keeping companies apart

  • Every company's records carry its ID, and Postgres row-level security lets a request read and write only the company it was made for. This is enforced by the database itself, not only by application code.
  • People are invited into a company with a role: owner, member, advisor or read only.
  • One sign-in can own several companies; each stays fully separate.

Your connections

  • Keys and tokens for connected tools are encrypted with AES-256-GCM, bound to the company and the tool they belong to, so a key copied elsewhere cannot be decrypted.
  • Finance and sales connections (Stripe, QuickBooks, Shopify, PayPal, HubSpot) are read-only.
  • A company's own API is read only with GET requests to the endpoints its CEO approves, at public addresses only, and redirects to another site are refused so the key never leaves for it. A webhook address is stored only as a hash.
  • For Google, you choose which services to share, and you can disconnect any tool at any time.

What seats may do

  • Seats propose by default. Each action they can take starts as a draft you approve, edit or reject.
  • A seat acts on its own only in an area you have turned on, and you can turn it off at any time.
  • Seats can never decide register items, change autonomy or reopen decided items. These rules live on the server, in the same checks every request passes.
  • Data that seats read from your tools is treated as data, never as instructions to follow.
  • Kill switches stop a single seat, a whole company or the entire platform at once.

A record of everything

  • Every decision and every change to the register or to settings writes an audit log entry in the same database transaction.
  • The audit log is append-only: a database trigger refuses edits and deletions.
  • When you delete something for good, the audit log keeps a note of what it was, so the history survives.

Infrastructure

  • All traffic is encrypted with HTTPS (TLS), with HTTP Strict Transport Security.
  • The application and database run in the United States (DigitalOcean, New York). Uploaded files are stored with Wasabi in the United States.
  • Servers accept SSH only with keys, from an allow-listed address, behind a cloud firewall. Security updates install automatically.
  • The servers are backed up weekly by our host.

AI providers

  • Seats think and write with Anthropic's Claude models through Anthropic's commercial API. Anthropic's commercial terms say it does not train its models on data sent through the API by default.
  • Voices and speech to text in live meetings use the providers listed below, only while a meeting is running.

Inside hlpr

  • Our admin tools show accounts, usage and cost, not your company's content.
  • Our engineers can reach the production database to run and support the service, and do so only for that.
  • We run our own company on hlpr, under the same rules as yours.

Sub-processors

The companies hlpr relies on to run the service, and what each one handles.

CompanyWhat it does for hlprLocation
DigitalOceanHosting: application servers and databaseUnited States (New York)
Wasabi TechnologiesFile storage: documents you upload and seat picturesUnited States
AnthropicAI models (Claude) that do the seats' thinking and writingUnited States
DeepgramSpeech to text in live meetingsUnited States
ElevenLabsSeat voices in live meetingsUnited States
LiveKitCarrying people's voices between them in live meetings (not stored)Global: the region nearest each caller
Google (Gemini API)Generating seat pictures from your descriptionUnited States
ResendSending account emails: invitations, sign-in links and noticesUnited States
StripePayments for hlpr plans (card details go to Stripe, never to hlpr)United States

Tools you connect yourself (Stripe, HubSpot, Google and the rest) are your own vendors; hlpr reads from them on your behalf.

Certifications

hlpr has not completed a SOC 2 or ISO 27001 audit, or an independent penetration test, yet. We will say so here when we have. If your company needs a security questionnaire answered, write to us.

Report a security issue

If you think you have found a vulnerability, email security@hlpr.ai with the details and how to reproduce it. Please give us a reasonable time to fix it before sharing it publicly, and do not access other people's data or disrupt the service while testing. We will reply and keep you posted.

Questions

Security and privacy questions: security@hlpr.ai or privacy@hlpr.ai.