Privacy
Last updated 15 November 2026
restoredrill.io is run by one person, Ahmad Piran. I decide what happens to the data described here. Write to hello at restoredrill dot io about anything on this page.
Visiting this site
This site sets no cookies, runs no analytics, and loads nothing from other sites. Cloudflare serves it, and like any web host it sees your IP address and the pages you request. A small script from this site puts email addresses together in your browser, so spam bots reading the page do not find them.
Emailing me
Mail to an @restoredrill.io address is forwarded by Cloudflare to a Gmail inbox, where I read it. I keep the conversation for as long as it is useful, and delete it if you ask.
Using the hosted service
If you use the hosted service, I hold:
- An account name, usually your company's, and the email address alerts go to.
- The reports your CLI sends. These are about your drills, not your data. The security page lists what is in them. Personal data is rare in a report. The usual case is
triggered_by_user, which holds whatever name you pass when you run a drill by hand. - The monthly pack PDFs built from those reports.
- Your Slack webhook address, if you gave one. It is stored as you gave it, protected by the disk encryption described on the security page but not encrypted separately, and it is included in the nightly backups. Anyone holding it can post to that Slack channel. You can disable it in Slack at any time.
- A log of which alerts were sent and when. It holds no report contents.
I use this to run the service: to check drills, send alerts and packs, and help you when something breaks. Nothing is sold, shared for marketing, or used to train anything.
Who processes it
| Service | What for | Where |
|---|---|---|
| Fly.io | Runs the service and its database | Frankfurt, Germany |
| Cloudflare | Nightly backups (R2), DNS, this site, email forwarding | Global network |
| Resend | Sends alert and pack emails | United States |
| Gmail, where I read mail sent to me and copies of alerts | United States | |
| Slack | Delivers alerts, only to the webhook you give | Your Slack workspace |
Some of these are outside the EU. Each one has its own data protection terms for such transfers.
How long it is kept
| What | Kept for |
|---|---|
| Reports | 13 months |
| Monthly pack PDFs | 13 months |
| Pack hash records | 36 months. They hold only the customer name, month and file hash, so an auditor can check a pack during a later audit. |
| Alert email address and Slack webhook | Until you leave and ask me to delete them |
| Account name | As long as the pack hash records, because the verification page shows it |
| Nightly backups | 30 days after the data they hold is deleted |
Your rights
You can ask for a copy of the data I hold about you, ask me to correct it, object to how it is used, or ask me to delete it. You can also complain to your data protection authority.
Deletion, and its one limit
When you ask, I delete your alert email address and your Slack webhook straight away, and revoke your CLI's address so nothing new arrives. The account name stays while a pack's verification page can still show it. If it is a person's name, tell me and I replace it with a neutral label.
Reports are different. They are audit evidence, and the service is built so that no one, including me, can remove them before 13 months without it showing. So they stay until their 13 months run out, and are then deleted automatically. If a report contains personal data about you and you ask, I remove that report by hand, and the gap is visible in the hash chain.
Changes
If this page changes, the date at the top changes. If a change affects how your data is used, customers hear about it by email first.