Plans, Activity, and daily usage
The canonical version always lives at https://tavina.ai/docs/friendly/account-subscription-support/plan-activity-and-usage
Plans, Activity, and daily usage
Tavina’s Settings → Account → Activity view is the subscriber-facing place to understand your current plan, daily usage, and available allowance. It is meant to explain what is happening in clear account language, not to expose provider invoices, raw prompts, secret keys, or internal Tavina cost details.
The values shown in the app are the current source to use for your account. This handbook explains how to read them; it does not define prices, refund terms, tax treatment, cancellation terms, or account-specific exceptions.
What Activity shows
Activity summarizes plan-aware usage by category:
| Category | What it means |
|---|---|
| Tavina tokens | Tavina-funded language-model usage, shown as one aggregate token value. |
| Talk To | Speech-to-text voice input, shown in approved voice-minute units when included. |
| Talk Back | Text-to-speech voice output, shown in approved voice-minute units when included. |
| Integrated applications | Chargeable third-party application actions that count against a plan allowance. |
The default graph period is weekly. You may also see daily, monthly, or custom range views when supported. Category cards can show used amount, remaining allowance, plan state, and the next reset time.
Daily limits and reset times
Included plan allowances are daily allowances. Tavina’s daily windows reset at 00:00 UTC, and the app converts that reset to your local time when it displays the next reset.
If a category reaches its daily limit, Tavina may pause only the affected capability until reset. Reaching one category’s cap should not imply that unrelated categories or your own API-key usage are blocked.
Tavina also runs scheduled background upkeep on your behalf, such as tidying and consolidating memories. These background runs never use up one of your daily turns, and they are reported separately from your own conversations rather than appearing as chats you sent. Their language-model usage is still included when Tavina checks overall daily usage for fair-use warnings.
Current daily quota values are versioned policy values and may change after calibration. The app’s Activity and usage screens are the source of truth for your account, but these are the approved starting daily caps:
| Plan | Tavina-funded LLM turns/day | Talk To STT min/day | Talk Back TTS min/day | Connected-app calls/day | Disk |
|---|---|---|---|---|---|
| Temp (trial) | 30 | 60 | 10 | 25 | 100 MB |
| Medium (base plan) | 500 | 240 | 210 | 250 | 750 MB |
The Medium base plan also includes 300 duplex-voice minutes per day. Image analysis is not subject to a separate daily allowance. Tavina-funded language-model usage is metered in turns; token counts are internal cost telemetry and are not a separate user-facing cap.
Some accounts remain on retired legacy plans (such as Light Duty, Heavy Duty, or Max Duty) that are no longer available for purchase. If your account is on a legacy plan, the app continues to show that plan’s own values, which may differ from the table above.
BYOK usage
BYOK means you are using your own provider key. BYOK activity is shown separately from Tavina-funded usage and should not look like it consumes included Tavina token allowance.
Voice usage
Settings → Identity → Voice shows the subscriber’s real metered voice usage for the day: speech-to-text and text-to-speech seconds alongside the plan’s daily voice limits, sourced from the same metering ledger the quota uses (tavina/tavina#2531), so the readout can never disagree with quota enforcement. The readout resets on the same schedule as the quota window. If metering is temporarily unavailable the field shows a placeholder rather than fabricated numbers; duplex (combined two-way) minutes appear only once that metering exists. If a subscriber asks where the voice numbers come from, explain they are the same numbers the daily quota is enforced against, not a separate estimate.
Do not share provider keys in screenshots or support tickets. Support may ask for visible status, provider name, time window, and error text, but not for secret key values.
Common plan states
Activity and related notices should use distinct states instead of a generic “over limit” label:
| State | Meaning |
|---|---|
| Available | The category is included and still has usable allowance. |
| Warning | You are close to a daily allowance threshold. |
| Daily limit reached | The category’s daily allowance has been used for the current window. |
| Not included | The current plan does not include that category. |
| Trial expired | The account’s trial lifecycle no longer grants trial access. |
| Temporarily unavailable or metering delayed | Tavina cannot safely confirm the current usage state yet. |
On accounts whose grandfathered legacy plan does not include Talk To or Talk Back, those voice affordances may remain visible but unavailable. The app explanation should say: Upgrade your plan to access voice features.
Usage notices
Tavina may send daily-usage notices near important thresholds. These notices should:
- name the affected category;
- show the reset time in your local time;
- link to Activity when available;
- avoid repeatedly notifying you about the same category, daily window, and threshold;
- avoid warning about features that your plan does not include.
A notice about one category does not mean every Tavina feature is blocked.
When to contact support
Contact support if the Activity view appears to show the wrong plan, an included capability is unavailable, a category is shown as limited when you believe it should not be, or the app repeatedly reports stale or unavailable usage.
When reporting a problem, include the visible plan name, category, approximate local time, visible reset time, and the exact visible message. Do not include raw prompts, provider keys, secrets, or sensitive application payloads.