Information we collect
- Account information, including your email address and password hash.
- Monitor names, target URLs, status-page content, settings, and regional check results.
- API-key hashes and integration settings, such as a Slack webhook you choose to provide.
- Subscription and transaction identifiers from Stripe when you use a paid plan.
- Basic request, device, diagnostic, and security logs produced by the service and hosting provider.
Payment-card details are entered with and processed by Stripe; realuptime does not receive the complete card number. We do not currently run third-party advertising trackers or product analytics on the service.
Why we use information
- Operate monitoring, public status pages, alerts, APIs, and account features.
- Authenticate users, enforce plan limits, prevent abuse, and investigate failures.
- Process subscriptions and respond to billing or support requests.
- Improve reliability and comply with valid legal obligations.
Cookies
realuptime uses a session cookie to keep signed-in users authenticated. It is used for account access, not advertising. Your browser may let you block cookies, but account features will not work without the session cookie.
Service providers and disclosure
Information is handled by providers that help operate the service, including Fly.io for hosting and Stripe for billing. If you configure Slack, alert information is sent to the webhook you provide. We may also disclose information when required by law, to protect the service or its users, or as part of a business transfer. We do not sell personal information.
Public status pages
A public page can expose the page name, component names, incident text, monitoring state, latency, regions, and timestamps. Do not place secrets, private endpoints, personal information, or confidential incident details on a public page.
Retention and deletion
Account and configuration data is retained while needed to provide the service. Monitoring results are currently retained without a fixed customer-facing deletion schedule while the history and retention system is being built. Operational logs may be kept for a shorter period based on troubleshooting and security needs. To request account access, correction, or deletion, contact us. Some records may be retained when required for security, billing, or legal reasons.
Security and international processing
We use technical and operational safeguards appropriate to the current service, but no internet service can guarantee absolute security. realuptime and its providers may process information in countries different from your own.
Children
realuptime is a business and developer tool and is not directed to children under 13. Contact us if you believe a child has provided personal information.
Changes and contact
We will update this page when our data practices materially change. Privacy questions and data requests can be sent to josefranco0213@gmail.com.