Accounts
Account lifecycle, isolation, and management
Every Telegram account in your workspace is either rented from the platform pool, or owned (uploaded by you).
Rented vs owned
| Capability | Rented | Owned |
|---|---|---|
| Origin | Allocated from platform pool | You upload Telegram Desktop session ZIP |
| Login-code chat (peer 777000) | Hidden | Visible |
| Login codes / 2FA codes | Cannot be read | Visible |
| Proxy | Pinned to rental proxy, cannot change | You attach your own proxy |
| Phone number | Visible but cannot reach SIM | Visible, belongs to you |
| Deletion | Released at subscription end, or $1 permanent delete | Delete from Accounts page |
| Bulk delete | Forbidden | Allowed |
| Telegram bans | Auto-replaced on covered plans | Not refundable |
Why login codes are hidden for rentals: The chat with peer ID 777000 is where Telegram delivers login codes. If a rental holder could read it, they could log in to the underlying phone number from another client. The platform hides that chat so the rental boundary holds.
Account isolation: three layers
| Layer | Enforcement | What it buys you |
|---|---|---|
| Per-account runtime isolation | Structural. By the runtime | Each account runs in its own OS process with own session file, fingerprint, connection, and auth-key. No connection multiplexing. |
| Per-account proxy isolation | Structural. By the runtime | Each account pinned to one dedicated proxy. No sharing. |
| Tenant-to-tenant on rented accounts | Data-lifecycle. Allocation rule + wipe | Only accounts with times_allocated = 0 are rented. After release, chats wiped and row retired. |
Pristine accounts only: The platform only rents accounts that have never been used by another tenant. `times_allocated` is incremented on every rental. Combined with chat-wipe at release, this means you are always the first user of any pool rental.
Account lifecycle states
| Status | Meaning | Outbound send budget |
|---|---|---|
| importing | Session being prepared | 0/hr |
| inactive | No proxy attached | 2/hr fallback |
| warming | First 14 days, four stages | 0 > 25/hr by stage |
| active | Full automation eligible | 30/hr + global 10/sec ceiling |
| cooldown | Temporary throttle after flood-wait | 0/hr |
| paused | You paused or proxy removed | 0/hr |
| banned | Terminal. Auto-replaced on covered plans | - |
| error | Non-recoverable bootstrap failure | - |
Health score
| Band | Breaker | What it can do | Recovery |
|---|---|---|---|
| 80-100 | CLOSED | All automations | +5 per healthy tick |
| 50-79 | CLOSED | Refuses new bulk-send. DMs/replies unaffected | +5 per tick |
| 25-49 | CLOSED | Bulk send + group joins refused | +5 per tick |
| 1-24 | CLOSED/HALF_OPEN | Outbound paused. Connection stays open | Auto-clears on recovery |
| 0 | OPEN | Suspended | Auto-replaced (rentals) or contact support (owned) |
Score decreases: -20 for health-check failure, -30 for auth-key error, pinned to 0 on confirmed Telegram ban.
Active-session enforcement
Every 6 hours, the platform checks each rented account for unknown Telegram sessions. Unknown sessions trigger a notification with two actions: It's me (approve) or Terminate (kill the session).
Connection rules
- Rental proxies pair only with rental accounts
- Your own proxies pair only with your owned accounts
- Crossing streams is refused
- One proxy = one account at a time
- Extra rental proxies can be purchased for additional rental accounts
FAQ
Can I read login codes for an owned account? Yes. Owned accounts have no redactions.
Can I read login codes for a rental account? No. Hidden to protect the rental boundary.
Can I delete a rental account? Via $1 permanent delete under Billing, or released at subscription end.
What happens at subscription expiry? 5-day grace window with full access. After grace, chats wiped and account retired.
My uploaded account got banned. Refund? No. You supplied the session. Rental bans on covered plans are auto-replaced.
Can I move an account from rented to owned? No. They are fundamentally different.