Impressive Scroll

Go to Stories Builder
Your email is not verified yet. We sent a verification link to . If it is not in your inbox, please check your spam or junk folder, since verification mail is often filtered there.

Profile

Your account details. Email is your sign-in and cannot be changed here.

Change password
Danger zone

Permanently delete your account, all your stories, and any published pages. This cannot be undone.

Credits

Credits are spent when you create or publish beyond your free allowance. Packs are one-time purchases that never expire and are non-refundable.

Buy credits

Loading...

History

AI Provider Profiles

Save one or more profiles, then choose a primary and an optional fallback. Generation uses the primary, and automatically falls over to the fallback on any failure. Keys are write-only and never shown again.

Vision (OCR) Provider Profiles

Used to read text from scanned PDFs and images that users upload. Same setup as above: save profiles, then pick a primary and an optional fallback. Use vision-capable models on OpenAI-compatible endpoints. Keys are write-only and never shown again.

Accounts

Every registered user. Promote or remove admins, reset a password, disable or delete an account. You cannot lock yourself out or remove the last administrator.

Story settings and pricing

Caps and credit costs for registered users. Administrators and gifted accounts are never charged credits (gifted accounts still obey the file size cap).

Generation limits

How many stories registered users may generate, and the AI output ceiling. Administrators are never limited.

The most stories a user can generate within the window, as an abuse and cost guardrail. Example: 50 (a user is blocked after 50 until the window resets).
How long the window above lasts before the generation count resets. Example: 24 (the cap is per rolling 24 hours).

Ceiling on how much the AI can write per story. Higher allows longer stories but costs more per generation. Example: 4000 (roughly a 12 to 16 block story).
Free credit mode

Pick one. New accounts get either a recurring allowance that refills, or a single trial grant that never refills.

Recurring allowance
Credits each user is topped back up to at the start of every window, in recurring mode. Example: 3 (refills to 3 each period).
How often the recurring allowance refills. Example: 30 (credits refill every 30 days).
One-time trial
One time credits granted when an account is created, in trial mode. These never refill. Example: 3.
Credit costs
Credits charged to create a standard story. Example: 1.
Credits charged to create a premium story (more blocks or images than the standard caps). Example: 2.
Credits charged the first time a story is published online. Re-publishing the same story is free. Example: 1.
Credits charged to apply a personal logo to published stories. Example: 2.
Branding logo
Image types a user may upload as their branding logo, comma separated. Example: jpeg,jpg,png,webp.
Largest logo file a user may upload. Example: 150 (a 200 KB logo is rejected).
Tiers and limits

A story is premium when it exceeds the standard block cap or the standard image limit. Re-publishing the same story is always free.

Block count that separates standard from premium. At or below this is standard. Example: 5 (a 6 block story bills as premium).
Largest size for a finished, published story file (not the upload limit). Protects bandwidth and storage. Example: 768.
Image blocks allowed in a standard story. Going over makes the story premium. Example: 1.
Image blocks allowed in a premium story. Example: 2.
Fewest blocks the AI is asked to produce for a generated story. Example: 5.
Most blocks the AI is asked to produce. Higher gives longer stories but costs more. Example: 10.
Saved stories

How many stories a regular account can keep, and the price to extend that limit. Admins and gifted accounts are unlimited. This cap only blocks creating new stories past the limit; it never deletes existing ones.

Saved stories a regular account may keep before it must extend. Example: 10.
Slots added each time a user extends. Example: 10.
Credits taken from the user's balance for each Z extra slots. Example: 1 (one credit adds Z slots permanently).
Document uploads

Controls for the "Build from a file" option in the draft panel. These bound what users can upload and how much of a long file the AI reads.

Largest file a user can upload to build a story from. Higher allows bigger source files but uses more of the user's device to parse. Example: 3 (a 10 MB file is rejected).
Max pages read from a scanned PDF or image with AI vision. Higher reads more of a scan but costs more. Example: 20 (a longer scan is rejected).
When an uploaded file is long, the AI first shrinks it to at most this many tokens, then writes the story from that. Higher keeps more detail but costs more. Example: 1800 (about 6 to 7k characters).

Playground

Generate test stories to evaluate how the model drives the block set and how each block renders in the final HTML. Runs are not charged. The result opens in an isolated frame.

Generate

Payments (PayPal)

Credit packs are one-time purchases and never expire: 20 credits for $20, 50 for $50, 100 for $100. Connect a PayPal REST app to accept payments. The secret is write-only and never shown again.

Live processes real PayPal payments; Sandbox uses PayPal test accounts to trial the flow without real money. Example: Live (after your PayPal app is approved).

Promo codes

A promo code grants bonus credits when a user completes any credit purchase, so the code doubles as a marketing channel tag. Codes only pay out on a completed purchase; an unused code costs nothing.

Create or update a code
Credits added to the buyer's balance when this code is redeemed during a purchase. Example: 5.

Channel report

CodeBonusDescriptionUses in rangeCredits in rangeTotal usesStatus
No codes yet.

Analytics

Generation activity, drawn from the generation log.

Loading...

Email

Optional. Configure a provider so the app can send mail. Resend and Zoho ZeptoMail are supported. The key is write-only and never shown again.

Send a test

Backup and restore

A backup is a compressed snapshot of all data (accounts, settings, providers, generation log, email settings) stored in your R2 bucket. It includes credentials, so a restore returns the app to its exact prior state. Keep downloaded copies secure. Restore is destructive and replaces all current data.

Requires an R2 bucket bound as IMPSCRL_R2.

Scheduled backups

Automatic backups run from a daily Cron Trigger (add one in the Worker dashboard, for example 0 3 * * *). Each frequency is independent and self-prunes: daily keeps the last 7, weekly (every Sunday) keeps the last 4, monthly (the 1st) keeps the last 12. Manual backups are never auto-deleted.

Backup records
Data cleanup and optimization

Hard-deletes accounts that have stayed disabled past the grace window (set in the Email verification section below), along with their published stories in R2. PayPal payment records are kept as the financial trail and remain searchable below, even after the account is gone. Payments past the retention window are purged, then the database is optimized. Runs after scheduled backups complete.

Scheduled cleanup

Independent of backups, and always runs after the backup step on the same Cron Trigger. Daily runs every day, weekly runs every Sunday, monthly runs on the 1st.

How long PayPal payment records are kept before being purged. Minimum 7 years for US record-keeping. Example: 7.
Financial records

Search retained PayPal payments by email or name within a date range. Records for deleted accounts are marked. Leave the search box empty to list everything in the range.

Email verification

New sign-ups must verify their email. An unverified account is reminded one day before the grace window ends, disabled when it ends, then deleted after the delete window. Administrators are exempt, and auto-disable runs only when an email provider is configured.

Days a new account may stay unverified before it is disabled. Example: 7.
Days a disabled, unverified account is kept before permanent deletion. Example: 30.
Bot protection (Cloudflare Turnstile)

Optional, off by default. When enabled, a Turnstile challenge appears on sign in and registration. It fails open: if the widget cannot load or Cloudflare is unreachable, people can still sign in.

Public Turnstile site key from your Cloudflare dashboard. Safe to expose in the page. Example: 0x4AAAA...
Private Turnstile secret key from Cloudflare, used server side to verify the challenge. Never shown again after saving. Example: 0x4AAAA... (write only).
Render cache

After deploying a new engine (scrollkit.js) or other site assets, refresh to make them live immediately everywhere. Saving any setting in the admin panel already refreshes caches automatically; the engine and gallery are always rebuilt from the latest files.