Privacy Policy
Last updated: 12 October 2026
1. About this policy
UptimeAgent is a product of Mozilor Limited, company number 11946756, at 3 Warren Yard, Wolverton Mill, Milton Keynes, MK12 5NW, United Kingdom. In this policy, “UptimeAgent”, “we”, “us” and “our” refer to Mozilor Limited in connection with the UptimeAgent service.
This policy explains how we handle personal information when you visit our production website, use the UptimeAgent application, connect a supported integration such as Slack or Microsoft Teams, view a status page or contact us. It covers our production services; separately identified development and test environments are outside its scope.
For privacy questions or requests, email support@uptimeagent.com or write to Privacy contact, UptimeAgent, Mozilor Limited at the address above.
We act as a controller when deciding how personal information is used for account administration, business operations, security and support. We act as a processor when handling personal information in customer monitoring configurations, logs and incident content on an organisation’s instructions.
If your organisation provides your account, its administrators can manage your access and workspace information. Its privacy notices also apply. Requests concerning information we process on its instructions may need to be handled by that organisation with our assistance.
2. Information we collect and its sources
Personal information is information that identifies or can be linked to an individual. Account identifiers, IP addresses, URLs and log entries can be personal information even when they do not include a name.
| Category | Information | Source |
|---|---|---|
| Account and workspace information | Names, email addresses, account and workspace identifiers, roles, memberships, invitations, preferences and authentication records. | You, your organisation’s administrators and your account activity. |
| Monitoring and incident information | Monitor names and endpoints, configured credentials and headers, check results, response times, availability, failing regions, incident records and limited failing-response content. | You or your organisation configure the monitors; our systems generate results and receive responses from those endpoints. |
| Customer logs | Log messages, attributes, service and instance identifiers, environment and runtime details, request diagnostics and process metrics. | Your systems through the collector configured by you or your authorised technical team. |
| Integration information | For Slack: workspace and channel details, permissions, an access key, matched member identifiers and names, connection records and delivery information. For Microsoft Teams: the connection details needed to post to the channel you choose, the channel name, connection records and delivery information. | You, your organisation, the integration provider and integration activity. |
| Technical and security information | IP addresses, browser or device information, request paths and queries, authentication activity, monitored URLs, service errors and diagnostic records. | Your browser or device and our website, application, authentication, monitoring and hosting systems. |
| Support information | Contact details, messages, attachments and relevant account context. | You, support interactions and the account information supplied to our support provider. |
| Public content | Information published through status pages and badges, and technical information generated by visits to them. | Your organisation, visitors’ browsers and hosting systems. |
You or your authorised technical team enable log collection by configuring the optional collector on your systems. You can adjust supported settings, disable the collector or revoke its installation token. Stopping collection does not delete logs already collected.
Submit only information needed for the service. Use designated credential fields for required credentials, and avoid including unnecessary personal information, passwords or other secrets in log text, support messages or public content.
3. Why we use information
We use information to administer accounts and workspaces, authenticate users, run monitoring checks, collect configured logs, detect and investigate incidents, deliver alerts, operate integrations, publish requested status pages, respond to enquiries and protect the service.
For our controller activities, the following legal bases apply where required by UK or EEA data protection law:
| Purpose | Legal basis |
|---|---|
| Create and administer accounts, authenticate users and provide requested features | Performance of a contract with you or your organisation. |
| Deliver configured alerts and essential account or security messages | Performance of a contract with you or your organisation. |
| Answer support enquiries | Performance of a contract with you or your organisation. |
| Protect security, prevent abuse, troubleshoot faults and improve reliability using operational diagnostics and support feedback | Our legitimate interests in protecting users, maintaining service availability and resolving service problems; legal obligations where applicable. |
| Meet legal requirements and handle legal claims | Compliance with applicable legal obligations, or our legitimate interest in establishing, exercising or defending legal claims. |
When relying on legitimate interests, we balance those interests against the rights and freedoms of individuals. Where we process personal data on the instruction of our customers, they decide the legal basis.
Some information is necessary to create an account or provide a requested feature. If you do not provide it, we may be unable to provide that account or feature. Processing needed for accounts, monitoring, alerts and support does not depend on accepting optional analytics.
Where we use already collected personal data for an additional use, we ask the individual for separate consent, explaining the new use in detail before taking that consent.
We automate monitoring, incident detection and configured alerts. We do not use personal information to make solely automated decisions about individuals that produce legal or similarly significant effects. AI-assisted investigation is not enabled in the production service.
What we do not do. We do not sell personal information. We do not use personal information for advertising. We do not use information received from Slack or Microsoft Teams, or customer monitoring, log or incident data, to train artificial intelligence or machine learning models.
4. Slack, Microsoft Teams and other integrations
We use information received through an integration only to provide the integration features you set up, as described below. We do not share it with anyone except the service providers listed in section 6 that help us run the service.
Slack
You can connect UptimeAgent to your Slack workspace to receive incident alerts and test messages in the channels you choose. You can use our Slack app or your own.
What we access. To set up alerts, we can see your workspace’s channel names, join or create a public channel for alerts and add the person setting it up to that channel. We also look up Slack members’ names and email addresses so we can match them to their UptimeAgent accounts. We keep only the matches and discard the rest. We do not read your Slack messages, private conversations or files.
What we store. Details of the connected workspace and alert channels, an encrypted access key for the connection, who connected it, and when alerts were sent or failed. Our system logs may also record workspace and channel names.
What alerts contain. The monitored website, what failed and where, when it happened, links to the incident or status page, and the names of team members involved. Some alerts also include your workspace alert email address or buttons to acknowledge or resolve an incident. Alerts do not include the content of your website’s responses.
Who can see alerts. Anyone in the Slack channel can see and copy alerts. The acknowledge and resolve buttons act on behalf of the person named in the alert, so do not forward them to anyone outside your team.
Disconnecting. When you disconnect Slack in UptimeAgent, we delete the stored access key and the Slack member matches. Some records, such as alert history, are not deleted automatically when you disconnect or uninstall the Slack app. To see, get a copy of or delete this information, email support@uptimeagent.com. We complete deletion requests within one month of verifying the request.
Messages already delivered to Slack remain subject to the receiving organisation’s settings and Slack’s privacy policy.
Microsoft Teams
You can connect UptimeAgent to a Microsoft Teams channel to receive incident alerts there.
What we access. Only what is needed to post alerts to the channel you choose. We do not read your Teams conversations, files, calendar or any other Microsoft 365 information.
What we store. The connection details for the channel, which we encrypt and treat as a secret; the channel name; who connected it; and when alerts were sent or failed. We never record the connection details in our logs.
What alert cards contain. The incident status, the incident ID, when it was confirmed, the region where it was detected, the name of the team member who owns it, and buttons to acknowledge or view the incident.
Who can see alerts. Anyone in the Teams channel can see and copy alert cards. The acknowledge button acts on behalf of the person named in the alert, so do not forward cards to anyone outside your team.
Disconnecting. When you disconnect Teams in UptimeAgent, we delete the stored connection details immediately. To see, get a copy of or delete other information related to the connection, email support@uptimeagent.com. We complete deletion requests within one month of verifying the request.
Cards already delivered to Teams remain subject to the receiving organisation’s settings and the Microsoft Privacy Statement.
Sign-in
You sign in to UptimeAgent with your email address and password. Connecting an alert destination such as Slack or Microsoft Teams is separate from signing in to UptimeAgent.
5. Cookies and browser storage
Cookies are small files placed in your browser. We also use browser storage (local storage and session storage), which works in a similar way. The table below explains each cookie and storage item used on our website and in the application, and why.
| Cookie or storage | Set by | Purpose | Duration |
|---|---|---|---|
| Authentication session cookie | UptimeAgent | Keeps you signed in and links your browser to your server-side session. | Up to 24 hours, or until you log out |
| Security cookies | UptimeAgent | Protect sign-in and account requests against misuse and forgery. | Until the browser session ends |
| Local storage | UptimeAgent | Remembers your preferences and onboarding progress. May include your account and alert email addresses. | Until cleared by you, your browser or the application |
| Session storage | UptimeAgent | Holds temporary information needed to complete sign-in and integration setup. | Until you close the browser tab |
| Support chat cookies | tawk.to | Run the support chat widget and remember your chat conversation. | Set by tawk.to; see tawk.to’s privacy policy |
Server-side sessions are revoked on logout. Session validity is separate from how long authentication records are retained.
Your browser settings may let you block or clear cookies and stored site data. Doing so can sign you out or affect features that rely on that storage. Clearing browser data does not delete information already held in account records or by service providers.
Mixpanel analytics and session replay are not active on our production website or application. We do not treat browser Do Not Track signals as a service-wide instruction to stop processing. You can exercise your privacy rights using the contact details in section 10.
6. Support and service providers
We use the following providers and recipients to operate the service:
| Provider or recipient | Information and purpose |
|---|---|
| Amazon Web Services | Hosting, application and authentication databases, monitoring and log storage, backups, operational logs and content delivery. |
| Resend | Recipient addresses, email contents and delivery information for authentication, product and alert emails. Messages can include account, monitor and incident details or action links. |
| tawk.to | Support messages, attachments and visitor, device or page information. In the signed-in application, we also supply name, email, role and workspace context. |
| Slack | Information needed to operate the Slack integration described in section 4. |
| Microsoft | Alert cards sent to the Microsoft Teams channel you connect, as described in section 4. |
| Cloudflare | DNS services and associated operational information. |
| Domain registration lookup services | Registrable domains submitted for domain-expiry checks. |
| Configured monitoring endpoints | Monitoring requests and any credentials or headers you configure for them. |
| Google Fonts | Requests from email clients that load remote font resources included in our emails. |
| Your organisation and configured recipients | Workspace administration, monitoring information, incident details and configured alerts. |
You can contact us at support@uptimeagent.com instead of using support chat. See tawk.to’s privacy policy for its information handling.
Information published through status pages and badges can be viewed and copied by others. Your organisation controls what it chooses to publish.
We may disclose information where necessary to comply with law, respond to lawful requests, protect rights and safety, or establish, exercise or defend legal claims. Information may also be disclosed to relevant parties and professional advisers in connection with a merger, acquisition, restructuring or transfer of our business, subject to applicable legal protections.
7. International processing
Our primary application and authentication databases, check and log storage, and their backups are hosted in AWS Ireland. Monitoring probes and worker logs also operate in the United States, Canada, Germany, India and Australia. Worker logs can contain monitored URLs, check identifiers and results. Some of our service providers process information in the United States.
These locations may have data protection laws that differ from those in your country. When personal information is transferred outside the UK or EEA, we rely on the following safeguards:
| Destination | Safeguard |
|---|---|
| Ireland and Germany (AWS) | Within the EEA. The UK recognises the EEA as providing adequate protection. |
| Canada (AWS) | Adequacy decisions of the European Commission and the UK. |
| India and Australia (AWS) | Standard Contractual Clauses approved by the European Commission, with the UK International Data Transfer Addendum for UK transfers, incorporated in the AWS Data Processing Addendum. |
| United States (AWS, Resend, tawk.to, Slack, Microsoft, Cloudflare and Google) | The EU-US Data Privacy Framework and its UK Extension, under which these providers are certified, and, where the provider offers them, Standard Contractual Clauses in its data processing agreement. |
We also apply technical safeguards, including encryption of information in transit and at rest. You can contact support@uptimeagent.com for more information about these transfers or to request a copy of the relevant safeguards.
8. How long we keep information
Retention depends on the type of information and the feature involved. Our current retention settings and deletion behaviour are set out below.
| Information | Retention and deletion |
|---|---|
| Monitoring check results and daily summaries | Configured to expire after 100 days from the check time or summary day. |
| Customer log streams | Configured to expire after 30 days from the log timestamp. Incident evidence is stored separately. |
| Incident records and saved evidence | Remain with the associated monitor until separately deleted or removed when that monitor is deleted. They have no automatic time-based expiry. Up to 2,000 log lines around an incident may be copied into evidence and retained after the original log stream expires. |
| Slack connection | Kept while connected. The access key and member matches are deleted when you disconnect. Other connection and delivery records are kept until deleted on request. |
| Microsoft Teams connection | Kept while connected. The connection details are deleted immediately when you disconnect. Delivery records are kept until deleted on request. |
| Operational infrastructure logs in CloudWatch | A configured retention period of 30 days. |
| Account, workspace, invitation and email-delivery records | Retained until separately removed; no general automatic expiry is configured. An invitation expiring does not by itself delete its record. |
| Authentication records | Session validity does not determine record retention. Expired authentication records do not have an automatic cleanup process. |
| Notification delivery jobs | Recipient and message information remains while delivery is pending or retrying. Completed or cancelled jobs have a 24-hour retention setting after finalisation; discarded jobs have a seven-day setting. The configured limit of eight delivery attempts does not establish a maximum elapsed retention period. |
| Primary database backups | Retained for seven days from backup creation. |
| Check and log database backups | Retain seven daily snapshots. This is a limit on snapshot count, not a guaranteed seven-day maximum age. |
Expired information is removed by automated background processes, so deletion may take a short time after the retention period ends.
The service providers listed in section 6, such as Amazon Web Services, Resend, tawk.to, Slack and Microsoft, may also hold copies of information they process for us, for example delivered emails, support chat transcripts, or alerts delivered to Slack or Teams. Because these copies sit in the providers’ own systems, they are kept according to each provider’s retention settings and terms rather than the periods above.
You can request deletion at support@uptimeagent.com. Removing a member, deleting a monitor, disconnecting an integration and deleting an account have different effects. These actions do not automatically erase all information from authentication records, queued messages, provider systems or backups.
When assessing a deletion request, we may require additional information to confirm that you are the owner of the account or that you have the right to make such a request. We also consider the information concerned, your authority over it, the rights of other individuals and any applicable legal retention requirement or exception. Information needed to comply with law or establish, exercise or defend legal claims may require separate retention. Where an exception applies, we will explain it as required by law.
9. Security
Our primary AWS data stores and backups use encryption at rest. Public service connections and vendor API calls use TLS to protect information in transit. Authentication uses server-side sessions and password hashing. Stored Slack access keys and Microsoft Teams connection details are encrypted.
Even though we take the utmost care to secure the data we handle, both in transit and at rest, no method of transmission or storage is completely secure. If you suspect any security or privacy issue concerning our service, please report it to support@uptimeagent.com. We will handle it as a priority.
10. Your rights and choices
Depending on applicable law and the circumstances, you may have the right to:
- Access your personal information and obtain a copy.
- Correct inaccurate or incomplete information.
- Request deletion of your information.
- Restrict certain processing.
- Receive qualifying information in a portable format.
- Withdraw consent where processing relies on it, without affecting the lawfulness of earlier processing.
- Appeal a decision about your request where applicable law provides that right.
Right to object: You may object to processing based on legitimate interests on grounds relating to your situation. You may object to the use of your information for direct marketing at any time.
Send requests to support@uptimeagent.com, identifying the relevant account or workspace and what you would like us to do. You do not need to disclose your password. We may request proportionate information to verify your identity or authority, including the authority of an authorised representative.
Where we process information on your organisation’s instructions, we may refer the request to that organisation and assist it in responding. Your rights may be subject to legal conditions and exceptions, including protections for other people’s information.
We respond within the time required by applicable law. Requests are generally free, subject to lawful exceptions. For an appeal, email the same address with “Privacy appeal” in the subject line. Exercising your rights will not result in unlawful discrimination.
You may complain to the UK Information Commissioner’s Office or another competent data protection authority, including the authority in your EEA country of residence, work or the alleged infringement. You do not need to contact us before approaching an authority.
11. Children
UptimeAgent accounts are intended for people aged 18 or older. We do not knowingly solicit children’s personal information for registration. If you believe a child has supplied personal information, contact support@uptimeagent.com so we can investigate and take appropriate action.
12. Changes and contact
We update this policy when our practices or applicable requirements change and revise the date at the top. We provide additional notice of material changes where appropriate or required by law. Continued use of the service does not replace consent where consent is required.
Privacy contact: UptimeAgent, Mozilor Limited
Email: support@uptimeagent.com
Post: 3 Warren Yard, Wolverton Mill, Milton Keynes, MK12 5NW, United Kingdom
Last updated: 12 October 2026 · UptimeAgent is a product of Mozilor Limited.