Privacy
What we hold, and what we never see
The short version
- Your alerts stay on your server. Shorthop is software you run yourself. Alert titles, labels, notes, people and history live in your installation's database. We never receive them.
- We run two small services for you: the push relay, which delivers pages to the Shorthop app, and Shorthop Watch, which pages you when a check stops pinging. This page lists everything they store.
- A page carries no alert content. The phone gets generic text and an opaque id, then fetches the details from your server. The one exception is a Watch page, which carries the name you gave the check (see below).
- The app has no analytics, no tracking and no crash reporting. It talks to your server only.
- This website sets no cookies and runs no analytics.
Who we are
Shorthop is a trading name of Mattias Holmberg, sole trader, registered in Malta, Flat 713, Highgrove, Triq Il-Kwarta, Swieqi SWQ 2045, VAT MT33211117. For the data on this page about your account and billing, we are the controller.
Questions or requests: privacy@shorthop.io.
What we store
| What | Why | Kept |
|---|---|---|
| Your account (an "installation"): organisation name, contact email, VAT number, country and billing address. Your installation key is stored only as a one-way hash. | To run the service for you, contact you and invoice you. | While you are a customer. |
| Your card: only a label such as "VISA ··1234, expires 12/28" and Viva.com's reference for the card check. You type the card on Viva.com's own page; the number never reaches us. | To show you which card we charge, and to charge it. | Until you remove the card or close your account. |
| Phones: the push token, platform (iOS or Android), the label your team gave it (for example "Anna's iPhone"), when it signed in and out, when we last heard from it, and any "not seen for 30 days" warning. | To deliver pages, to count phones for your bill, and to sign out phones that have gone quiet (always with a warning first). | While your account exists. |
| Deliveries: when a page was sent, to which phone (our internal id), and whether Apple or Google accepted it. Never what it said. | To show you that a page went out, and to find faults. | While your account exists. |
| Watch checks: the name you gave the check, its schedule and state, when it last pinged, and the short note your job sent with the ping (at most 200 characters). Never the IP address or headers of a ping. | To notice when a check stops pinging and page you. | Ping history: 30 days. The check itself: while your account exists. |
| Monthly statements, invoices and payment attempts, each with a copy of your name, email, address, country and VAT number as they were at the time, and, for EU business customers, the VIES check of your VAT number. | Malta's tax rules require us to keep invoices and the records behind them. | 10 years, and never deleted early, even if you close your account. |
| Our own staff log: what our staff did to your account and when (for example, rotating a key or signing out a phone). | Accountability, and to answer your questions about changes. | While your account exists. |
| Sign-up and sign-in links: the email address, a one-way hash of the link, when it expires and whether it was used. A sign-up link also holds what you typed in the form until you confirm it. | So that only someone who can read the address can create or open an account. | One day after the link expires or is used. Unconfirmed sign-ups are not kept. |
| Rate-limit counters: a hash of your key or ping token and a count. | To protect the service from floods. For the sign-up and sign-in forms this is a hash of your IP address; the address itself is not stored. | Minutes. |
When you close your account, we delete everything above within 30 days, except the statements, invoices and payment records, which the law makes us keep for 10 years.
What we never store
- Alert content: titles, descriptions, labels, runbook notes or anything else from your Shorthop installation.
- The names or contacts of the people in your installation, apart from the phone labels above.
- Push payloads, your raw installation key or ping tokens.
- The IP address, user agent or headers of a Watch ping.
- Your card number.
The one exception: Watch pages
When a Watch check stops, your Shorthop server may be the thing that is down, so the page cannot ask it for details. A Watch page therefore carries the check's name, its state and two times (the last ping and when it went down). That text passes through Expo and Apple or Google, and the same facts go to your contact email. The ping note is never sent; it is shown only inside your own Shorthop. Name your checks with that in mind.
Who else sees it
We use these providers to run the service. Each sees only what it needs:
| Provider | What it gets | Where |
|---|---|---|
| Google Cloud | Hosts the relay, Watch and their database. | EU (Finland) |
| Expo, Apple (APNs), Google (FCM) | A phone's push token and the notification: generic text and an opaque id, or a Watch check's name and state. | United States |
| Amazon Web Services (SES) | Watch emails and receipts with the invoice attached, sent to your contact email. | EU (Frankfurt) |
| Viva.com | Your contact email, the amount and our payment references. You enter the card on Viva.com's page. | EU |
| European Commission (VIES) | Your country and VAT number, to check it. | EU |
| Cloudflare | Every request to our sites and services passes through it (encryption and protection against floods), including your IP address. | Global |
Where a provider is outside the EU, the transfer relies on that provider's safeguards under the GDPR, such as the European Commission's standard contractual clauses or the EU–US Data Privacy Framework.
Your team's phones
The phone labels and push tokens belong to people in your organisation. For those we act on your behalf (you are the controller, we are the processor), and you decide which phones are signed in. Signing a phone out in your Shorthop stops pages to it at once. The data processing agreement sets out what we commit to for that data.
Legal basis
- Contract: running the relay and Watch, and billing you.
- Legal obligation: keeping invoices and the records behind them.
- Legitimate interest: keeping the service secure (rate limits, our staff log) and finding delivery faults.
Your rights
You can ask us for a copy of what we hold about you, to correct it, to delete it (apart from the tax records above), to restrict or object to how we use it, or to receive it in a portable format. Write to privacy@shorthop.io; we answer within a month.
You can also complain to Malta's data protection authority, the Information and Data Protection Commissioner.
This website
The site sets no cookies, stores nothing in your browser and runs no analytics or tracking. Cloudflare serves it, so like any website it sees your IP address to deliver the page.
Changes
If the relay or Watch starts storing something new, this page changes first, and the date at the top changes with it. If you are a customer, we will email you about any change that affects your data.