Settings

Settings is where you manage your account, configure the cadence at which scans run, set your preferred language, and review your subscription. Most users open Settings once during onboarding and then rarely come back — but the features here are what turn Regulatory Snapshot from “a tool I open when I think of it” into “a service that delivers a briefing to my inbox every Monday.”

Why this matters

The best regulatory-tracking tool in the world is useless if you forget to use it. Settings is the workshop where you take the manual scan loop (open the app, run a scan, read it) and turn it into a routine (a fresh briefing waiting for you every Monday morning).

Your account

Account management runs through your account menu in the top-right of the dashboard chrome. From there you can:

• Update your name, email, and password.
• Manage Single Sign-On if your organisation uses it.
• Sign out of this device or all devices.
• Delete your account (this is permanent and deletes all your snapshots; tread carefully).

Your account is synchronised across devices. If you sign in on your phone, you will see the same snapshots and the same language preference you have on your laptop.

Language preference

Snapshot supports seven UI and content languages: English, French, German, Spanish, Italian, Mandarin, and Japanese. Use the language picker in the dashboard chrome to switch.

Your language preference is saved on your account, so it travels with you. Two things to know:

• The first switch of a snapshot into a non-English language triggers a translation pass — you will see a brief overlay. The result is cached on the snapshot so subsequent switches are instant.
• Audio briefings respect the dashboard language at the time you generate. Switching language in the middle of generating an audio job doesn’t retroactively change the language; you need to switch first, then generate.

See Studio for the multi-language audio details.

Scheduled scans

If you find yourself running the same configuration every week, set up a scheduled scan and Snapshot will run it for you on a cadence.

The Scheduled Scans tab in the dashboard lists your active schedules and lets you create new ones. A schedule includes:

• A configuration — same shape as a manual scan (jurisdictions, areas, horizon, and any Advanced settings).
• A cadence — typically weekly or fortnightly. Monthly is supported but less useful — regulators move faster than a month.
• A notification preference — whether Snapshot should email you when the scan completes, and what kind of summary to include.

Each run produces a regular snapshot in My Snapshots, with full change tracking against the previous run. See What’s changed since last scan for how the change overlay works.

[!NOTE] A scheduled scan is just an automated manual scan. The output is identical. There’s no separate “scheduled snapshot” type — every run lands in the same My Snapshots list as scans you ran by hand, and the same Studio exports work on it.

Email reports

If a scheduled scan is configured to email a digest, Snapshot will send you a short message when the run completes. The email typically contains:

• The headline from the executive narrative (“Bottom Line Up Front”).
• The change counts (X new · Y updated · Z removed).
• A link back to the dashboard for the full read.

The email is intended as a “you don’t need to open the app today, here’s the gist” notification — not a replacement for the dashboard. If something material moved, you click through.

[!NOTE] Email is on a per-schedule basis, not a global account setting. Different schedules can have different email preferences — you might want a weekly summary for your bank-wide scan and silent runs for a niche topic you only check occasionally.

Notifications

Beyond email, the dashboard surfaces a toast when a scan you started manually completes. There is no push notification, no SMS, no Slack integration today. If you want a scheduled scan’s output delivered somewhere other than the dashboard or your inbox, email is the route — point it at a shared mailbox your team monitors.

Billing

Regulatory Snapshot is a paid service. Your subscription tier determines:

• How many scans you can run per month.
• How many scheduled scans you can have active at once.
• How many languages you can produce content in.
• Whether higher-cost AI model tiers are available to you.

For current pricing and tier comparison, see the pricing page on the marketing site at regsn.app/pricing .

[!NOTE] Your current tier is shown on the billing screen in the account menu. If you hit a limit (say, you’ve used your monthly scan allowance), the wizard’s run button will be disabled and the summary rail will tell you why. Upgrading is a 30-second flow and the new tier takes effect immediately.

Costs to be aware of

Even within your tier, two things can drive costs up:

• Very wide scans (lots of jurisdictions, lots of areas, long horizon) use more model time per run. The wizard’s summary rail shows a live cost estimate.
• Higher model tiers in the Advanced drawer (where available) cost more per scan than the defaults. The default tiers are tuned for “good briefing, reasonable cost”; the higher tiers are worth it for high-stakes scans but you wouldn’t run them weekly.

If you’re running scans on a high cadence, the per-scan cost adds up — keep an eye on the cost estimate in the wizard and the monthly summary on the billing screen.

Data retention

Your snapshots are retained on your account indefinitely while your subscription is active. If you delete a snapshot, it is gone — there is no recycle bin. Studio exports tied to that snapshot are deleted with it.

If you cancel your subscription, your snapshots and exports remain readable for a grace period (per the subscription terms) and then are removed. Export anything you want to keep before that grace period ends.

Security

Snapshot uses Clerk for authentication, which supports standard email-password sign-in, magic links, SSO (SAML/OIDC), and multi-factor authentication. Your scans and exports are scoped to your account — no one else on Snapshot can see them, and there’s no shared workspace today.

If you need to share a scan with a colleague, the standard pattern is to download the artefact from Studio (tearsheet PDF, audio MP3, etc.) and share it through your usual channel — email, Teams, Slack. The artefact’s eight-character ident travels with the file, so anyone receiving it has a stable reference back to the underlying scan if questions come up.

A common pitfall

[!WARNING] If you change your language preference during an audio generation job, the in-flight job will still use the language it started with. To produce a French audio briefing, switch the language first, then hit the generate button. Switching mid-job has no effect on the running render.

Beyond the basics

A non-obvious pattern that experienced users land on: point a scheduled scan’s email at a shared mailbox. Compliance teams often want the Monday-morning digest to reach a desk distribution rather than one person — pointing the schedule at [email protected] (or a Teams channel email connector) means the digest is in the team’s queue automatically, regardless of who’s on holiday or whose laptop is on. Different schedules can point at different recipients, so a niche-topic scan can stay private to you while the firm-wide one goes to the team.

Where to go next

• What’s changed since last scan — change tracking on recurring scans.
• Studio — language-aware exports.
• FAQ — common questions about billing, retention, and security.