Privacy Policy

Last updated: 6 October 2026

This policy explains what personal data Tierguard processes when you use the service and the website, why, for how long, and what rights you have. It applies to the Tierguard website and application at tierguard.dev.

1. Controller

The controller of the personal data described here is Aliaksandr Palazok ("the Provider"), an individual operating from the Republic of Poland. Contact: support@tierguard.dev. A postal address for legal notices is available on request at support@tierguard.dev.

2. What we collect

Account data: the email addresses of the account and its users, a password hash (never the password itself), user roles and creation times.
Projects and configuration: project names and platforms (Xero or QuickBooks), your quota and overage settings, alert recipients, and alert channel targets that the Provider adds on your request. Ingest tokens are stored as hashes; a token is shown once at creation.
Usage events: the usage metadata you send, attributed to the tenant reference you choose. Tierguard is not designed to receive accounting data, and you must not send it.
Alert and delivery records: the alerts generated for your projects and records of delivering them, including recipient email addresses. Alert text can name your project and the tenant references with the highest usage.
Billing identifiers from Stripe: your plan, subscription status and Stripe identifiers. We do not receive or store card numbers.
Technical logs: request logs (IP address, request line, time), application events and errors, and threshold-alert notices that can include tenant references and usage figures. They are kept for about 14 days and are not removed when an account is deleted. One-time link tokens (password reset, verification, email change, invitation) may appear in request paths in those logs.
Operator audit trail: actions taken by the site operator in the back-office are recorded with the IP address. It stays after an account is deleted.

If the tenant references you send identify individuals, you are the controller of that data and the Provider acts as your processor; we recommend opaque identifiers. Contact us if you need a data processing agreement.

We use no analytics and no advertising trackers, and our pages load no third-party scripts, fonts or images.

Messages you send to support@tierguard.dev are received by the operator's mail provider and kept as ordinary email until deleted.

Questions and data requests: support@tierguard.dev.

3. Why we collect it (legal basis)

Providing the service (Article 6(1)(b) GDPR): account, project, token, usage and alert data, and subscription data needed to deliver and bill the plan you chose.
Legitimate interests (Article 6(1)(f)): securing the service, technical logs, the operator audit trail and abuse prevention.
Legal obligation (Article 6(1)(c)): keeping records that tax and accounting law require, mostly held by Stripe as merchant of record.

4. Retention

Usage events are pruned by a scheduled job, by event timestamp, once they are older than the history period of your plan. The history periods are:

Free plan: 7 days
Starter plan: 90 days
Pro plan: 365 days

Events are never deleted inside the project's current billing cycle once a tier is configured for it. A subscription that is past due, unpaid or paused keeps its paid plan's history period. After a paid subscription ends, its history period is kept until 30 days after the end of the last billing period we recorded for your subscription, and the Free plan's period applies afterwards. Pruning removes usage events only; alerts and delivery records stay until the account is deleted.

All other data is kept while your account exists. When the account owner deletes the account, its data is removed from the live service at once, but it can persist in the database file until the space is overwritten, and in backups for about 14 days after that, for as long as backups keep running. Database copies made by hand before upgrades or restores are deleted by the operator once the change is confirmed. Backups are on the same server and are not encrypted at rest.

Some records stay after deletion: technical logs (about 14 days), records held by Stripe, Stripe subscription and event identifiers that carry no account reference, and the operator audit trail. Audit entries older than 365 days are removed by a command the operator runs; this is not automatic.

5. Processors and sub-processors

OVH: hosting of the server, the database and its backups (servers in the European Union).
Resend: delivery of the emails Tierguard sends from alerts@tierguard.dev: alert emails, password-reset, verification and email-change messages, and notices of password or email changes.

Messages you send to the support address are read by the Provider. Slack, webhook and PagerDuty alerts are sent to the target configured for your project, which is your own endpoint or account and not a Provider sub-processor. The alert text, including tenant references, is sent to that target.

6. Independent controllers

Stripe acts as merchant of record and as an independent controller for the payment, tax, fraud-prevention and billing data it collects when you subscribe, under Stripe's privacy policy. Stripe also sends its own payment emails. Tierguard does not see your card details. When you start checkout, Tierguard sends Stripe your account email, account id, the time the account was created, the chosen plan, and fixed internal product labels. Stripe keeps its records after you delete your Tierguard account.

7. Cookies

Tierguard sets only strictly necessary cookies for login and form security. See the Cookie Policy for the full list.

8. International transfers

Our servers are in the European Union. Stripe and Resend may process data outside the European Union under their own terms and transfer safeguards. Alert targets you ask us to configure receive alert text wherever they are hosted.

9. Your rights

You have the right to access, rectify, erase and export your personal data, and to object to processing based on legitimate interests. Most are self-service:

Access and export: the account owner can download in Settings a summary of the account as JSON and the usage events as CSV. Anything beyond that summary is available on request to support@tierguard.dev.
Rectification: change your email address and password in Settings.
Erasure: the account owner can delete the account in Settings (refused while a subscription is live: cancel in Manage billing, and deletion becomes possible once the paid period has ended; if you need it sooner, or cannot cancel, contact support@tierguard.dev). Members can leave an account, and owners can remove members: the person's sign-in is removed, but an alert-recipient entry with their address stays until the owner removes it, and delivery records keep recipient addresses until the account is deleted. For erasure beyond that, email support.
Everything else: email support@tierguard.dev from the address registered on the account. We answer within one month.

You may also lodge a complaint with a supervisory authority; in Poland this is the President of the Personal Data Protection Office (UODO), or the authority in your own country of residence.

10. Security

Passwords and ingest tokens are stored only as hashes, sessions use signed cookies, forms are protected against cross-site request forgery, and the site is served over HTTPS. No system is perfectly secure; report suspected incidents to support@tierguard.dev.

11. Children

Tierguard is a business service and is not directed at anyone under 16. We do not knowingly collect data from children.

12. Changes

We may update this policy. The date at the top shows the latest revision, and we will give notice of material changes on this website.

13. Contact

Questions about this policy or your data: support@tierguard.dev.