Privacy Policy

Last updated 4 October 2026

Draft — not yet reviewed by counsel. Do not treat this page as a complete or final statement of our data practices until it has been.

1. About this policy

This policy explains what personal information 10pm uptime collects, why, where it is kept, and the choices you have. 10pm uptime is operated by [LEGAL ENTITY NAME] (“we”, “us”) in Australia. We handle personal information in line with the Australian Privacy Principles, and we extend the rights in section 9 to everyone, wherever they live.

The short version: we collect what we need to run your monitoring, we don't sell it, we don't use advertising or analytics trackers, and our servers are in Australia.

2. Information you give us

  • Account details: your email address and password. We store the password only as a bcrypt hash and cannot read it. If you sign in with Google, we receive your email address, Google account identifier and name from Google; the name is used only to suggest an organisation name at signup.
  • Organisation details: the organisation name, its members and their roles, and invitations you send (including the invited email address).
  • Preferences: display time zone and theme.
  • Notification destinations: email addresses, ntfy topics, webhook and Slack URLs, and webhook signing secrets you configure.
  • Support messages: anything you send us by email.

3. Monitoring data

This is the data the Service exists to process. We treat it as belonging to your organisation; it is never visible to other organisations.

  • Check configuration: target URLs and hosts, request headers, request bodies, expected content and other settings. These can contain personal information or credentials if you put them there. For a private-definition check, the configuration lives only on your own monitor and we never receive it.
  • Results: pass/fail, timings, HTTP status codes, and short samples of responses and error messages. You can cap or switch off how much response and error text is sent to us per check.
  • Monitors: the name, region and location you give each of your own monitors, its software version and when it last reported.
  • Heartbeats: the time each heartbeat arrives and whether it reported up or down. We ignore and do not store any other parameters or message text sent with it.
  • Change history: a record of changes to a check's target and request content, kept to prevent abuse of the Service.

Checks you run on our shared monitors are executed on machines we operate, so those machines see the check's configuration and the target's responses. Checks run on your own monitors keep a local copy of their configuration and results on your infrastructure; that copy is under your control, not ours.

4. Information collected automatically

  • Server logs: when you or your monitors make a request, our servers log the IP address, the time, the path requested and the response status. Heartbeat tokens are removed from logged paths. Logs are used for security, abuse prevention and troubleshooting and are kept for [LOG RETENTION, e.g. 30 days].
  • Cookies: we set two cookies, both strictly necessary or a stored preference: a session cookie that keeps you signed in, and a theme cookie that remembers light or dark mode. We use no analytics, advertising or third-party tracking cookies. The plan page loads Paddle's checkout script, which may set its own cookies when you start a purchase — see Paddle's privacy notice.

5. How we use information

  • to run the Service: executing checks, evaluating alerts, sending notifications, and showing your dashboards, history and any public status page you turn on;
  • to manage your account and billing, and to send service messages such as email verification, password resets, invitations, security notices and changes to our terms;
  • to keep the Service secure and prevent abuse, including rate limiting and investigating misuse;
  • to provide support. When you ask for help, our staff may view your organisation's data, or temporarily view the app as your account sees it, to diagnose the problem. This access is limited to staff who operate the Service, is time-limited, and is used only for support and security;
  • to comply with the law.

We don't sell or rent personal information, use it for advertising, or send marketing email unless you have asked for it.

6. Who we share it with

Service providers that process data for us:

  • [HOSTING PROVIDER] — server hosting in Sydney, Australia, where the Service and its database run.
  • Paddle.com — payment processing and billing for paid plans, as our Merchant of Record. Paddle collects your payment details directly; we never see or store your card number.
  • Google — only if you choose “Sign in with Google”.

Account and alert email is currently sent from our own mail server.

Destinations you choose. When you configure a notification channel or turn on a public status page, you are directing us to send data there:

  • alert emails go to the addresses you enter; webhooks and Slack messages go to the URLs you enter; push alerts go to the ntfy server and topic you enter. Topics on the public ntfy.sh server can be read by anyone who knows the topic name, so choose one that is hard to guess. Once data leaves our systems for a destination you have chosen, its handling, retention and security are governed by that provider's terms and privacy policy, and we are not responsible for them.
  • a public status page shows, to anyone, the names, current status and 30-day uptime of the checks you choose to publish — nothing else.

Others: we disclose information if required by law or to protect the rights and safety of our users, the public or us; and to a successor if the Service is transferred, in which case this policy continues to apply to your data.

7. Where your data is kept

Our servers and backups are in Sydney, Australia. Some of the service providers above, and notification destinations you choose, may process data in other countries, including the United States and the United Kingdom. Where we use a provider overseas, we take reasonable steps to ensure it protects personal information consistently with the Australian Privacy Principles.

8. How long we keep it

  • Check results: raw results and hourly summaries are kept for the retention period of your plan (see Pricing), then deleted automatically.
  • Account and configuration data: for as long as your account and organisation exist.
  • Signup, invitation and password-reset links: expire after 24 hours, 24 hours and one hour respectively, and cannot be used afterwards.
  • After deletion: when your account or organisation is deleted, its data is removed from our live database straight away and from backups within 14 days.
  • Billing records: held by Paddle and, where we have them, kept for as long as tax law requires.

9. Your rights and choices

You can ask us to give you a copy of the personal information we hold about you, to correct it, or to delete it. Much of it you can view and change yourself in account and organisation settings, and you can export your checks. To close your account or make any other request, email hello@10pmuptime.com from the address on the account. We will respond within 30 days. If you are in the EU, UK or a similar jurisdiction, you also have the right to object to or restrict processing and to data portability.

If you are a member of someone else's organisation, that organisation's owner controls its monitoring data; we may refer requests about that data to them.

10. Security

We protect data with measures including: encryption in transit (HTTPS) for the web app and agent API; bcrypt-hashed passwords; monitor API keys, enrollment tokens and emailed links stored only as hashes, with the plaintext shown once; strict separation of each organisation's data; rate limiting of sign-in and other sensitive endpoints; and a shared monitoring fleet that refuses to connect to private or internal network addresses. No system is perfectly secure. If a data breach is likely to cause you serious harm, we will notify you and, where required, the Office of the Australian Information Commissioner.

11. Children

The Service is not intended for anyone under 18, and we don't knowingly collect their information.

12. Changes to this policy

We will update this policy when our practices change. For material changes we will email account owners and show a notice in the app before they take effect. The date at the top shows when it was last changed.

13. Contact and complaints

Questions, requests or complaints about privacy: hello@10pmuptime.com. We will respond within 30 days. If you are not satisfied with our response, you can complain to the Office of the Australian Information Commissioner, or to your local data protection authority.