Help articles
Start here
Trying Acervo without an account
Understand the public trial, anonymous allowance, guest result retention, locked actions, and session claim.
On this page
Section links appear after the article loads.
Trying Acervo without an account
Use /try while signed out to process one JPEG, TIFF, or PDF with one to three pages. The document is rejected as a whole if it contains more than three pages. You must affirm the current Terms of Service and Privacy Policy before Acervo authorizes the upload.
Guest processing policy
The trial always uses Standard Acervo OCR and general entity extraction. Premium, Transkribus, institution profiles, team workspaces, and other processing choices are unavailable. Signed-in workspace processing still offers Standard or Premium and, when enabled, an optional public Transkribus OCR model.
Allowance, privacy, and retention
The allowance has three layers. A document carries up to three pages, a guest session can process nine pages, and a network can process 150 anonymous pages in a rolling 7-day window. A document that would cross a remaining allowance is rejected without processing any page, the trial shows a capped session before any upload begins, and a read that fails releases its pages back to the allowance. Acervo stores only a keyed hash of the canonical network address and keeps the minimal allowance ledger for 8 days. Source images follow normal terminal cleanup. Each unclaimed guest result expires 24 hours after that job completes, even when newer jobs remain in the same guest session.
Guest result and locked actions
The guest result uses the same record view as the authenticated processing result. It shows every safe field that view renders, including descriptive metadata, classification and page roles, entities, extracted values, subject headings, confidence, evidence, sensitivity notes, and approved public authority links. Raw OCR, source URLs, provider output, prompts, costs, credentials, private ownership, and workspace data remain private. Editing, adding and removing, downloading, exporting, and configured integration controls stay in their normal locations as locked actions. A locked action is gray, carries a lock, and explains that sign-in is required. Choosing it opens Clerk and does not run the action.
Session claim
The top-right Keep these results control opens sign-in without selecting a locked action. After authentication, the session claim moves every unexpired job into the user's personal workspace using the same jobs and processing results. It does not copy, reprocess, or charge guest work retroactively. If sign-in began from a locked action, Acervo highlights that action on the authenticated result. The user must click it again to run it.