Privacy notice
Last updated: 19 November 2026
This notice is about TaskBeacon ("TaskBeacon", "we", "us"), the service at taskbeacon.io. TaskBeacon is run by a private individual based in Serbia, not by a company; that person decides how your data is used. Questions and requests: support@taskbeacon.io. The operator's full name and postal address are given on written request, to users and to data protection authorities.
What we store
- Your account: username, email address, password (stored only as a hash) or your Google account id if you sign in with Google, your time zone and settings.
- Your jobs: names, schedules, machine names, notes, rules and projects.
- Other people's email addresses you give us: extra alert recipients you add to a job (with whether and when they confirmed they want the alerts) and the people you invite to a project (with their role and whether they get its alerts).
- Website checks (only if you add one): the address and settings you enter, and for each check its time, HTTP status code, response time, error message, and the expiry dates of the site's certificate and domain. The domain expiry date is looked up once a day in the public domain registry (RDAP), which sees only the domain name.
- Pings from your scripts: time, kind (start, finish, fail), the numbers your script chooses to send (for example a row count or a date), the request body as sent (up to 10 KB, e.g. JSON with those numbers, or on a failure the error message and the last 20 lines of output), the sender's IP address, the client's user agent (e.g.
curl/8.4.0) and, if sent, the machine name. We keep them to show the job's history and explain alerts. - Integrations (only if you add one, e.g. Power BI or dbt Cloud): the access details you give (client secret, token or API key), encrypted with a key kept outside the database and its backups and never shown again; the names and ids of what you watch; and for each run its times, status, duration and the error message the tool reports, or for a watched file its name, size and modification time. Who added, changed or disconnected an integration, and when. Disconnect and delete credentials deletes the stored access at once.
- A subscription (only if you buy Pro or Team): the ids Paddle gives your customer record and subscription, the plan, its status, renewal and end dates, and the events Paddle sent us about it. We never see or store card numbers.
- AI apps you connect (only if you connect Claude, ChatGPT or another app in Settings → AI assistants): the app's name, the access you gave it and when you connected; and for each request the app sends, the time, which tool or ready-made prompt it used and whether it worked, to see how the connection is used. Never what you asked the app or what it answered.
- Sign-ins: the time of each sign-in to your account and whether it was with a password or Google, to count how many people use the service.
- Visits to the public pages (home, Pricing, Docs and the like, not the pages inside your account): the page, the time, how long it was visible, how far it was scrolled and whether you clicked or typed on it, the site you came from (or the AI app that sent you to sign in) and any utm_ campaign tags in the address, the browser's language and time zone, the country, the device type, operating system and browser name. The country is looked up from the IP address in a local copy of the free DB-IP database on our server (IP Geolocation by DB-IP), so the address is never sent anywhere, and only the two-letter country code is kept; without that database we guess the country from the time zone. No cookies and nothing stored on your device; the IP address is not stored. Page views on the same day are grouped with a one-way code made from the IP address, the browser and a random value that changes every day and is deleted the next day, so a visitor can't be recognised on another day; a second code made the same way from the IP address alone keeps the site owner's own network out of the numbers. Signed-in users are not counted.
- What we derive: status changes, alerts we sent and daily counts of runs.
- Emails we send you: alerts, reports and account emails go through our email provider.
We never connect to your databases and never read data rows or file contents. Without an integration we only get what your script sends in the ping; with one, only the run metadata listed above.
Why
To tell you when a scheduled job fails, is missed, runs late or sends odd numbers, to show you its history, and to run your account. We do not sell data and do not use it for advertising.
How long
- Ping history: the last 100 pings per job on Free, 1,000 on Pro and Team (for now: 1,000 for everyone; see Pricing).
- Daily run counts, status changes and alert history: 30 days on Free, 12 months on Pro, 24 months on Team (for now: at least 12 months for everyone).
- Your account and jobs: until you delete them. Deleting the account removes all of it at once.
- Sign-ins, the AI app request records and visits to the public pages: 13 months. A sign-in record of a deleted account stays only as an anonymous count.
- Server logs (the address and time of each request, with the IP address, and errors) and the reports browsers send when a page blocks unexpected content: only as long as needed to keep the service running and secure, and not used for anything else.
- Backups: a copy of the database is made every night and an encrypted copy of it is also kept with a second hosting provider; daily copies are kept for 14 days and weekly copies for 8 weeks, so data you delete is gone from all backups within 8 weeks.
Your rights
In Settings → Account → Your data you can download everything we keep about you as a file, and in Settings → Account → Delete account you can delete your account with everything in it. You can also write to support@taskbeacon.io to ask what we hold, to correct it, or to object. If you think we handle your data wrongly, you can complain to a data protection authority: the one in your country, or in Serbia the Commissioner for Information of Public Importance and Personal Data Protection.
Cookies
Only what the site needs to work: a session cookie while you are signed in, a security (CSRF) cookie for forms, and a cookie that remembers light or dark mode if you pick one without an account. No analytics or advertising cookies, so there is no consent banner. The Paddle checkout (only when you subscribe) is Paddle's: see above.
Who processes data for us
- Email delivery and hosting: Hostinger (our mailbox and the server TaskBeacon runs on).
- Backup storage and uptime watch: GoDaddy web hosting keeps the encrypted nightly backup copies (it can't read them; the key stays with us) and checks from outside that TaskBeacon is up.
- Paddle (Paddle.com Market Ltd), only if you subscribe: Paddle is our merchant of record and payment processor. When you open the checkout we pass Paddle your email address and your TaskBeacon account number; in the checkout you give Paddle your payment details and billing address, which Paddle handles under its own privacy notice. The checkout and Paddle's script are loaded from Paddle's servers only on the Pricing and Settings pages while subscriptions are open, and Paddle may set the cookies its checkout needs.
- Fonts are served from our own server, so pages make no request to Google Fonts.
- Google, only if you choose to sign in with Google. Slack, Microsoft Teams, Telegram, Discord, Google Chat, ntfy or your own webhook, only if you add them: the alert text goes to that service. For Telegram we keep the id and the name of the chat you connected.
- For an integration you add, we call that tool's own API (Microsoft, dbt Labs, Fivetran) with the access you gave.
Changes
If this notice changes in a way that matters, we tell you by email before it applies.