Read-only and deletion
An organization without a plan that records events becomes read-only, and Rabolic stops recording its events.
When it happens
| Situation | Events stop | Read-only | Data deleted |
|---|---|---|---|
| The trial ends without a plan | At once | At once | 7 days after the trial ends |
| A canceled plan's paid period ends | At once | At once | 30 days after the paid period ends |
| A payment fails | 7 days later, while Dodo retries | 7 days later | Not while Dodo still retries. If Dodo ends the subscription, as for a canceled plan |
| An organization without a trial (not its creator's first) and no plan | Until it has a plan |
While events aren't recorded, they are dropped and counted. The SDKs get the same answer as over a cap, so they don't retry. The dashboard shows why events aren't recorded instead of an allowance.
What read-only means
- Reports open as usual.
- Nothing can be created or changed, except the plan.
- These still work: choosing a plan, leaving or deleting the organization, and privacy requests (exporting or deleting a person), which are a legal duty.
The dashboard says so in a banner, such as "Events aren't recorded until you choose a plan", "A payment failed" or "Read-only: a payment is overdue".
Getting back
Choosing a plan at any point, including before the data is deleted, restores ingestion at once.
What is deleted
At the deletion date, Rabolic deletes the organization's event data: events, sessions, people and transactions. The organization, its members and its projects stay, so it can subscribe and start again.
Emails
Owners get an email:
- when the trial starts, 24 hours before it ends, and when it ends;
- when access ends: a trial, a canceled plan, or ingestion stopped after a failed payment;
- 2 days before the data is deleted. Data is never deleted sooner than 2 days after that email.
Usage and overage
How Rabolic counts usage against your plan's allowance, usage notices at 80% and 100%, turning overage on with a monthly spending limit, project caps, and what happens to events past the limit.
Limits
Rabolic's limits. Event size (32,768 bytes), names, properties, batches, request size, SDK queue sizes, event age, rate limits, and the rejection reasons ingest returns.