Controller and Contact
For WebsiteDown.org privacy, access, correction, or deletion requests, use the contact page.
Data We Process
- Check inputs, such as submitted domains and URLs.
- Technical request metadata needed for reliability and abuse prevention (for example IP address, user-agent, referrer, timestamp, and request outcome).
- Public recent-check feed entries (domain name and check timestamp only, after automated quality filtering).
- Rating data for tools (star value plus anti-abuse identifiers generated from hashed network/request signals).
- Technical request metadata used to operate the checker and prevent abuse.
- Usage analytics through Google Analytics.
Community Reports
You can report that a service works for you or choose a predefined problem type without signing in. We store totals per service and 15-minute interval, rather than a public list of individual reports. These totals contain no name, free text, country, browser fingerprint or plaintext IP address.
To limit spam, we process the IP address supplied by our hosting provider into a secret-keyed network hash. IPv6 addresses are grouped by network prefix. These pseudonymous hashes are used only in temporary quota records: a 30-minute limit per service, a one-minute attempt limit and a rolling 24-hour limit across services. The daily quota stores up to 20 accepted timestamps and service references, without the selected problem type, and expires 24 hours after the last accepted report. The shorter limits expire independently. People sharing a network can share a limit.
The public report view covers up to 24 hours in 15-minute intervals. We retain at most 96 aggregate intervals per service and expire the aggregate key after 24 hours without new reports. Old intervals are removed on the next report; on an inactive page, an older interval can remain stored for less than 48 hours. Public aggregate snapshots are cached briefly. General hosting request logs are separate from this report storage.
For historical graphs, accepted reports also contribute to hourly and daily totals, including the problem categories and working reports. These totals contain no network hashes or individual report records. Hourly history covers up to 90 days and daily history up to 730 days. Storage is capped at 2,160 hourly and 730 daily intervals per service. Older intervals are removed on the next accepted report; inactive hourly and daily series expire 90 and 730 days after their last update respectively. On inactive services, older intervals can therefore remain stored beyond the visible history window, for less than 180 and 1,460 days respectively. This does not extend the retention of temporary network quota records.
Our browser storage remembers the service page and next allowed reporting time, with no visitor identifier. It keeps at most 64 unexpired cooldown hints; expired entries are ignored and removed on a subsequent write. Shared public summaries can also be cached in session storage. You can clear this browser data through your browser settings. Clearing it does not remove the server-side network limit.
Local Browser Storage
"Your recent checks" is stored in your browser using local storage. You can clear this at any time from your browser settings.
How We Use Data
- Run website and IP checks and return results.
- Protect the service from spam, scraping abuse, manipulation, and denial-of-service patterns.
- Compute aggregate ratings and show them on tool pages.
- Measure product usage and improve reliability, UX, and content quality.
Legal Bases
We process data under legitimate interests to operate and secure the service, and under consent where required by law (for example analytics/cookie controls in jurisdictions that require it).
Processors and Infrastructure
- Vercel: hosting, edge execution, and operational logging.
- Upstash Redis (KV): rating aggregates, anti-abuse counters, and related metadata.
- Google Analytics: website usage analytics.
Retention
- Recent checks in local storage remain until you clear browser data.
- Public recent-check feed entries are retained for a limited rolling window.
- Operational logs and security data are retained only as long as needed for reliability, fraud prevention, and legal obligations.
- Short-lived anti-abuse counters expire automatically; aggregate rating records are retained while the rating feature is active.
International Transfers
Data may be processed in multiple regions depending on our infrastructure providers. We rely on provider safeguards where required.
Your Rights
Depending on your location, you may have rights to access, correct, delete, or restrict processing of personal data. You may also object to certain processing activities.
Children
This service is not intended for children below the minimum age required by applicable law in their country of residence. We do not knowingly collect personal data from children where parental or guardian consent is required. If you believe a child has provided personal data, contact us and we will review and remove it where required by law.
Policy Changes
We may update this policy as features and legal obligations change. The effective date appears at the top of this page.