Scanning & data freshness
How TEASE reads your OnlyFans account — what it scans, how fresh the data is, how you trigger a scan on demand, and the ban-safe discipline that makes it all safe.
Everything TEASE knows about your account — the fans, the conversations, the vault, the revenue — comes from the engine: a single, careful worker that holds one live session to your connected OnlyFans account and reads it the way a human operator would. This page explains what it scans, how fresh the data is, how you ask for a fresh scan on demand, and the discipline that keeps a connected account safe.
Safety is the product
The engine is strictly serial, human-paced, and read-first. It never fabricates requests, never runs parallel bursts, and halts itself the instant the platform pushes back. Freshness is delivered within that safety envelope — never by pushing harder.
What gets scanned
The engine keeps four kinds of data current. Each is a scanner you can read in the panel, and each maps to a deliberate, billable action (see Credits & usage).
Fans & conversations
Harvests DM threads to build the inbox, attribute each fan to a source and country, and compute LTV. New and organic fans are prioritized first.
Content vault
Indexes every media item — title, folder, cover, tags — so search is instant and performance analytics have something to sit on.
Campaigns & links
Reads your tracking campaigns and their claimers, so clicks reconcile to real subs.
Cash & transactions
Reads transactions and payouts — the ground truth every revenue and attribution number reconciles to.
How fresh is the data?
Two things keep your data current, and you can lean on either:
- Continuous background reads. While the engine holds a session it steadily refreshes the highest-value data on a conservative, human-like cadence — freshest and most-active first.
- On-demand scans. When you need something now, press the scanner's button. A requested scan is promoted to run on the very next pass as a dedicated wave, instead of waiting for the next scheduled sweep.
A vault scan runs vault-only: asking for a full content re-index reads your vault and nothing else, so it finishes fast and never churns unrelated data. The same on-demand promotion applies to a fan/DM harvest.
Trigger a scan on demand
Open the scanner
Each surface has its own scanner: Content → Весь контент for the vault, Scaner → Фаны for fans and conversations, Scaner → FTL / Tracking for campaigns. Press the scan button (e.g. «Полный скан», «Разбор»).
Watch the honest phase
The progress reads an honest state, not a spinner that lies:
queued (requested — waiting for the next pass, with a countdown) →
scanning (a wave is running now, with live counters) →
done (finished) or halted (the engine paused itself; see below).
Read the result
When the phase reaches done, the new data is already in the panel — cards, counts, and
analytics update in place. Re-requesting while a scan is in flight is a no-op; the running
wave already covers you.
The ban-safe discipline
The reason TEASE can read a live account continuously without putting it at risk is a set of hard rules the engine follows on every pass:
| Rule | What it means |
|---|---|
| One actor, strictly serial | A single session does one thing at a time — never parallel bursts against the account. |
| Human-paced | Actions are spaced on a human-like cadence, with natural pauses between them. |
| Read-first, passive | The engine reads what the live session already loaded; it never fabricates a request the site wouldn't make. |
| Halt on push-back | A 429, 403, or a challenge halts the session immediately — no retry into a wall. |
| Night rest | An optional quiet window pauses non-urgent work overnight, like a real operator sleeping. |
| Drain, don't idle-spin | After a clean pass the engine winds down gracefully instead of hammering an empty queue. |
This discipline is not tunable into unsafety. There is no "scan faster", no priority override on outbound messaging, and no flag that trades account safety for speed. On-demand scans move your request to the front of the line — they do not make the line move faster.
Watch it run
Two panels make the engine's work fully transparent, and both reconcile to the same billable set as your usage meter.
The request monitor
Монитор движка → Наши запросы shows every deliberate action as it happens, named in plain
language — «Чтение кассы», «Обход кампании», «Отправка сообщения» — with status, latency, and
time. Consecutive pages of one sweep fold into a single row with a × N count, so a long read
reads as one action, not a scary wall of identical lines. Switch to «Всё» to also see the
OnlyFans site's own background traffic, shown for transparency and tagged «фон» — that
traffic is never billed.
The monitor follows the page you picked in the left rail: pin one OnlyFans page and the feed, the chart, the CSV export and «Очистить» all narrow to that page — pin nothing and you see the whole workspace. This monitor covers OnlyFans only: the engine's other platforms keep their own journals, so picking, say, a Fansly account says so on screen and links you to its monitor instead of quietly showing you OnlyFans numbers under a Fansly tile.
Usage
Монитор движка → Тариф и расход rolls the same actions up into credits used vs. your monthly allowance, broken down by action kind and by day, so the feed and the bill always agree.
Next steps
- Credits & usage — what each scan costs and what's free.
- Content vault — search, tags, and performance on the indexed vault.
- Chat & broadcasts — the inbox the fan scan feeds, and safe sends.
- Rate limits — API
429backoff, separate from engine pacing.
Smart Links
One link — /r/<slug> — that holds both your paid subscription and your free trial and decides per visitor which to show: a weighted split with per-country rules. Plus click, subscriber, and revenue performance.
Attribution
Read the Sources leaderboard — revenue by source, country, link, and fan, reconciled to your account net.