What Happens When a Subscription Ends

Your logger keeps working and your data is kept. What stops is your view of it — and your alerts.

Every subscribed logger shows the date it's paid through in the Subscription column on the Devices page — Ends followed by a date, or Renews followed by a date if it's set to renew automatically. The subscription runs to that date and stops there.

A subscription can end for several reasons: you unsubscribed the logger, a renewal payment didn't go through, or a free trial finished without a plan being paid for. What happens next is the same in every case.

1. What ends, and what doesn't

Your logger is unaffected. It keeps taking readings on its schedule, keeps uploading them, and keeps its name, folder, and configuration. Nothing about the hardware changes and nothing needs reconfiguring later.

Your data is unaffected. Everything the logger has recorded is kept, including everything it records while it isn't subscribed.

What stops is your access to it. While a logger isn't subscribed, its data isn't shown to you — not in ZENTRA Cloud, not in downloads or exports, and not through the API.

Alerts stop too, and this is the part to plan around. A logger without a subscription doesn't trigger alerts. Readings are still arriving and still being kept, but nothing is being watched, so no notification is sent — and an alert that would have fired is not sent later once you subscribe again. Data can be caught up on. A notification you needed at the time can't be.

You can still see that the logger is reporting. On the Devices page, expanding an unsubscribed logger shows its sensors and readings blurred, with a Subscribe link above them — and the time of its most recent measurement, unblurred. That timestamp is a useful signal on its own: it tells you the logger is still collecting and still uploading, even while the readings themselves are out of view.

2. Withheld is not deleted

Blurred readings aren't missing readings. The values are there and are still arriving — what's in place is a restriction on reading them while the logger isn't paid for.

Subscribe the logger again and all of it comes back at once, including every reading taken while it wasn't subscribed. There's no gap left behind, nothing to repair, and nothing you need to ask us to recover.

The exception is alerts, which run in the moment and can't be replayed.

3. Getting it back

Subscribe the logger again from the Devices page, the same way you subscribed it the first time — see Subscribe a device.

Your data becomes visible again once the payment clears, not when you select Checkout.

If the subscription ended because a renewal payment didn't go through, the loggers are already waiting in your cart and you only need to fix the payment method — see What happens if a renewal payment fails.

If you unsubscribed a logger and changed your mind, and its Ends date hasn't passed yet, re-subscribing costs nothing — it's still paid for. See Unsubscribe a device.

4. Readings from before you subscribed

The same principle works backwards. Once a logger has a subscription, its full history is shown to you, including readings it took before it was ever subscribed to anything.

You don't lose the beginning of a record by subscribing a logger late, any more than you lose the middle of one by paying late.

5. Avoiding an unplanned ending

• Keep a working default payment method on file, or enough Available Balance to cover the renewal. Balance is always spent first, so an organization holding enough of it renews without a card being involved.
• Check your renewal date. Your Billing page shows when the next charge is due and what it's estimated to be, under Annual Renewal.
• Watch loggers with their own dates. A logger that renews before your organization's annual renewal date is listed separately on the Billing page, under Next Invoice.