Privacy policy
HitherGate connects your devices to your remote machines. This page says what we collect to do that, why, who else handles it, how long we keep it, and how to have it removed.
Who we are
HitherGate ("we") runs hithergate.com, the HitherGate console at console.hithergate.com, the control plane at api.hithergate.com, and the relay at derp.hithergate.com. Questions about this policy or your data go to support@hithergate.com.
What we collect
When you sign in
You sign in with Google or GitHub; we never see or store a password. From the provider we receive and keep:
- which provider you used and your account ID there;
- your email address;
- your name, as the provider shows it.
We ask Google only for openid, email and profile, and GitHub only for read:user and user:email. We do not get access to your mail, files, repositories or anything else in those accounts.
When you use HitherGate
- Organizations and teams: their names, who belongs to them and with which role, and the access rules you set.
- Devices and remote machines: the names you give them, their operating system, public keys and certificates, when they were last online, and service events such as a restart. A machine's network address inside HitherGate is stored encrypted.
- Audit log: a record of administrative actions in your organization (who did what, to what, and when), visible to your organization's admins.
- Session cookie: signing in to the console sets one cookie that keeps you signed in. It cannot be read by scripts, lasts at most 12 hours, and ends after 2 hours without use. We use no advertising or analytics cookies.
- Network information: IP addresses of the devices that connect to our servers. The relay needs them to pass traffic between your devices, we use them to limit abuse, and they appear in our hosting provider's request logs.
If you join the waitlist
The email address you send us, used only to contact you about early access.
What we do not collect
Traffic between your devices and your remote machines is end-to-end encrypted. When it passes through our relay, the relay forwards encrypted packets it cannot read. We do not see the pages, sign-ins or data you reach through HitherGate. We do not sell personal data, show ads, or track you across other sites.
How we use it
- to sign you in, run your organization, and connect your devices;
- to keep the service secure: rate limits, abuse prevention, and investigating problems;
- to answer you when you contact support, and to send messages about the service itself.
Who else handles it
- Google Cloud hosts HitherGate: the console, the control plane, the database, the relay and our logs, in Google's europe-west1 region (Belgium).
- Google and GitHub handle sign-in when you choose them, under their own privacy policies.
- Google Fonts serves this website's typefaces, so your browser's request for them reaches Google.
We share data otherwise only when the law requires it.
How long we keep it
- Account, organization and device data: for as long as your account exists.
- When you ask us to delete your account, we delete it within 30 days. Database backups that still hold it expire within a further 14 days.
- Request logs at our hosting provider: about 30 days.
- Sign-in sessions: at most 12 hours.
Security
Connections to HitherGate use TLS. Data is encrypted at rest by our hosting provider, and sensitive fields such as machine addresses are encrypted again by HitherGate. Each organization's data is isolated from every other organization's in the database.
Your choices
Email support@hithergate.com to get a copy of your data, correct it, or delete your account. You can also remove HitherGate's access at any time from your Google or GitHub account settings.
Children
HitherGate is not meant for children under 16, and we do not knowingly collect their data.
Changes
If we change this policy, we update this page and its effective date. For significant changes we also tell signed-in users before they take effect.