Frequently asked questions
The questions on this page come up regularly. If you have one that isn’t here, the related “Using” page often has the longer answer in context — links at the bottom.
What does Regulatory Snapshot actually cover?
Snapshot does multi-jurisdiction regulatory horizon scanning for financial services. That means: financial regulators across eleven built-in jurisdictions plus anything you add as a custom jurisdiction; ten broad policy areas (banking, capital markets, AML/KYC, payments, data privacy, operational resilience, ESG, crypto, sanctions, research bundling) plus anything you add as a custom area; and a forward-looking horizon of three to thirty-six months.
What it is not: a general legal-news aggregator, a litigation tracker, a sanctions-screening service, or a regulator-news subscription. It’s specifically the “what’s on the horizon for my firm and my topics” view.
How accurate is it?
Snapshot is AI-assisted analysis. The research pulls from primary regulator sites, supranational standards bodies, and authoritative secondary commentary. Every item has a View source link to the underlying document, and every item carries a Likelihood badge (Confirmed / Likely / Possible / Uncertain) telling you how sure the analysis is.
The honest framing is this: Snapshot is excellent at surfacing what’s there — catching consultations, rules, and proposals you might otherwise miss. It is less reliable at fine-grained legal interpretation. Use the briefing as a starting point. Always click through to the regulator’s primary source before quoting a date, a deadline, or a specific obligation in a compliance memo or a board paper.
[!WARNING] Snapshot is not legal advice. Every briefing carries a disclaimer reminding you to verify findings against primary sources before acting on them. The disclaimer’s tone is intentionally cautious — when in doubt, the source link on each item card is your fallback.
How long does a scan take?
A typical scan with 3–5 jurisdictions and 2–4 areas takes between 90 seconds and four minutes. Wider scans (10+ jurisdictions, 5+ areas, 24+ months) can take longer — up to ten minutes for very large configurations. The wizard’s summary rail shows a live cost estimate that correlates roughly with runtime.
Studio exports run separately. A tearsheet or infographic is typically under a minute; an audio briefing is one to four minutes; video is half an hour or more.
How do I share a snapshot with a colleague?
The simplest path is to generate an artefact in Studio (tearsheet PDF, audio MP3, slide deck, infographic image) and share the file through your usual channel — email, Teams, Slack. The eight-character scan ident travels with the file so anyone receiving it has a stable reference back to the underlying scan.
There is no in-app “share a snapshot with another user” feature today. If two of you need to look at the same scan inside the app, you each run it on your own account — or one of you exports the result and forwards it.
Can I rerun the same configuration weekly?
Yes — that’s one of Snapshot’s strongest patterns. Either re-run manually from the My Snapshots tab (use the Re-scan affordance to pre-fill the wizard) or set up a scheduled scan in Settings. Both paths produce regular snapshots with full change tracking against the previous comparable run. See What’s changed since last scan for how the change overlay works.
Does Snapshot work for non-financial regulators?
Snapshot is built and tuned for financial regulators — securities, banking, prudential, AML, payments, market structure, ESG/sustainable-finance disclosure, crypto. It will surface adjacent regulation (data privacy, operational resilience, sanctions, AI accountability) where these intersect with finance, but it is not the right tool for, say, pharma regulatory affairs, healthcare compliance, or environmental permitting.
If you have a non-financial use case, please get in touch — we’d like to hear what’s missing.
What languages does Snapshot support?
The dashboard and content can be translated into seven languages: English, French, German, Spanish, Italian, Mandarin Chinese, and Japanese. The first switch into a non-English language triggers a translation pass; the result is cached on the snapshot so subsequent switches are instant.
Audio briefings respect the same seven languages, with native voices available for each.
Languages your team uses but Snapshot doesn’t support yet (Portuguese, Korean, Arabic, Dutch, etc.) — please tell us; the list grows based on demand.
How much does it cost?
Subscription tiers and prices are on the marketing site at regsn.app/pricing . Within your tier, two things can drive variable costs:
- Very wide scans (many jurisdictions, many areas, long horizon) use more analysis time per run.
- Higher model tiers in the wizard’s Advanced drawer (where available) cost more per scan than the defaults.
The wizard’s summary rail shows a live cost estimate before you run. Your monthly usage is on the billing screen.
Is my data private?
Yes. Snapshot uses Clerk for authentication and your scans, snapshots, and exports are scoped to your account. No one else on the service can see them. There’s no shared workspace or team view today — if you need to share with a colleague, exporting and forwarding the artefact is the path.
We don’t share your scan configurations or outputs with anyone. The research the AI does runs against public regulatory sources; it doesn’t transmit anything from your account to those sources beyond what’s needed for a generic web search.
Can I export the underlying data?
Yes — Studio offers a JSON download that contains the full structured data behind the dashboard, and a CSV download that flattens the regulatory items into a spreadsheet. Both are scoped to a single snapshot and contain everything you saw on the dashboard plus the source URLs. Useful if you want to drop the data into a BI tool or merge it with internal tracking.
What if a regulator I care about isn’t covered?
Two paths:
- Custom jurisdiction. If a country or region isn’t in the default eleven, type it into the Add custom field in the wizard’s jurisdictions step. Examples that work well: South Africa, UAE, Mexico, ASEAN, Cayman Islands.
- Custom area. If a specific regulator or topic isn’t covered by the ten default areas, add it as a custom area in the areas step.
Custom jurisdictions and areas are visually distinguished in the wizard so you can see at a glance which parts of your scan are off the default beat. The analysis treats them as first-class inputs.
What if a scan produces something I think is wrong?
Click through to the View source link on the item card. Nine times out of ten the answer is either (a) the source confirms the finding and the item is correct, or (b) the source is genuine but the analysis’s summary is imprecise — useful signal but check the primary text before quoting.
If you find a substantive error — a misattributed regulator, a wildly wrong date, an item that’s about a different jurisdiction than its label says — please send us a screenshot. Errors of that kind are how we improve the analysis.
[!NOTE] Snapshot is at its most useful when used as a starting point, not a final word. The dashboard surfaces what to look at; the primary source on each item card is what you actually act on.
Where to go next
- Your first scan — the wizard walk-through.
- Reading the dashboard — heatmap, briefing, trends, timeline.
- Studio — exports.
- What’s changed since last scan — change tracking.
- Settings — account, language, scheduled scans, billing.