Dear users,
We are devastated to inform you that due to an extremely unfortunate chain of events, our entire database, including all user data, has suffered severe corruption and is unrecoverable.
Even our backups, which we believed would protect us in such a scenario, were affected due to a critical configuration mistake. Professional data recovery specialists are currently working on every possible fragment, but it appears the core users table is lost permanently.
What we managed to recover
- A large portion of report data (but very scattered and difficult to reassociate)
- Lot's of logs and some payloads
Unfortunately we currently have no reliable way to automatically match recovered payloads and logs back to the correct accounts — this is only possible with your help.
Next steps & only realistic paths forward
At this moment we see only two options:
- End the project here, or
- Perform a full database wipe and restart — but give existing users the chance to reclaim what's theirs first.
How to prove ownership
To protect your payloads from being incorrectly claimed by others, we kindly ask you to prove ownership of your account and payloads. The most effective way is to provide:
- Your previous alerts / notifications
- Payload domains / identifiers you controlled
- Any upgrade / subscription transaction proof
- Anything else that clearly ties you to specific payloads
Current status
- New registrations are temporarily disabled
- All existing payload domains remain active
- New reports are still being collected
Once everyone has had reasonable time to submit proof and reclaim their payloads/upgrades, we will block new incoming payloads from being automatically registered — giving priority to legitimate previous owners.
We are truly sorry this happened. This felt like a perfect storm of Murphy's Law in action — something we considered practically unthinkable before today. We are taking every step to make sure nothing like this can ever happen again.
With sincere apologies,
The ezXSS/ezpe team
ACCOUNT RECOVERY