Legal
Privacy Policy
How RELIASTRA collects, uses and protects customer data across its monitoring, evidence and billing systems.
Last updated: August 2026
What we collect
- Account data you provide at registration: name, work email, organization name, and authentication credentials (hashed) or federated identity tokens from Google or GitHub.
- Monitoring data: the endpoint URLs, HTTP methods, headers and expected responses of the dependencies you configure us to check, plus the results of those checks (timing, status codes, regional origin).
- Operational metadata: incident records, correlation results, generated evidence reports, audit-log entries for security-relevant actions, and billing state.
- First-party acquisition attribution: the campaign parameters that brought you to our site (UTM source/medium/campaign and landing path). We use first-party storage only - no third-party advertising cookies.
How we use it
- To run the service: scheduling checks, detecting incidents, correlating vendor failures with your alerts, generating evidence reports, and delivering notifications through the channels you configure.
- To secure accounts: authentication, session management, rate limiting, payout-destination change verification, and abuse prevention.
- To bill accurately: subscription state, usage against plan limits, and payment processing through our payment provider (Paystack). Card details are handled by the provider; RELIASTRA never stores full card numbers.
- We do not sell personal data, and we do not share monitoring data with other customers. Public observatory records only ever show aggregated posture for vendors that have been made public - never customer endpoints or credentials.
Evidence & public data
- Evidence reports belong to the organization that generated them. They are exposed publicly only through explicit share links or verification references created by that organization.
- The public verification endpoint confirms a report exists and binds its checksum - it does not disclose endpoints, headers, or account details.
Retention
- Check history is retained according to your plan (24 hours on reduced post-trial limits up to 90 days on Developer) and is pruned automatically by scheduled jobs.
- Billing records are retained as long as required for tax and accounting compliance.
Your choices & contact
- You may update your organization data in Settings, export or delete dependencies at any time, and request account deletion by contacting support@reliastra.com.
Questions about this policy? Contact support@reliastra.com. If you arrived through the Technical Creator Program, note that creators are additionally covered by the program terms presented at enrollment.
Add one dependency you already own.
RELIASTRA probes the external services your software relies on, confirms a fault deterministically, and keeps a record you can verify later. One plan, $9/month, and a 14-day trial that needs no card.