Skip to main content
Cloud sync keeps your notes up to date across your signed-in devices. It is part of Anarlog Pro.

Turn sync on or off

  1. Open Settings → Sync.
  2. Cloud sync starts automatically for a fresh Pro sign-in. If you previously turned it off, turn on Cloud sync to resume.
Sync runs automatically in the background. Use Sync now to send and receive the latest changes immediately. Your notes always remain available locally, even while sync is paused or you are offline. Pause sync when you want changes to remain only on the current device for a while. Resume it to send pending changes and receive updates from your other devices.

What Cloud Sync replicates

Cloud Sync copies end-to-end encrypted notes across your signed-in devices. Anarlog cannot read this data. Each synced device receives:
  • Meeting notes, including titles, memos, and generated summaries
  • Transcripts and speaker assignments
  • Participants, people, and organizations
  • Action items
  • A few preferences: Theme, App icon, Week starts on, and Default sharing
Since 1.4.24, new daily notes, folders, tags, and note-tag assignments stay on the device where you create them. Their sync rollout is deferred to keep meeting-note sync compatible with 1.4.23. Synced applies to the supported data above, not these local-only items. Existing items already synced by Nightly continue using their existing format; use matching app versions on those devices. API keys, model selections, and most other settings stay on the computer where you entered them. After you add a new device, enter each Transcription and Intelligence API key again and choose the models you want on that computer. Anarlog stores those keys in the operating system’s credential store and does not copy them between devices. Also set up on each device:
  • Calendar connections
  • Downloaded local models
  • Device-specific options such as audio devices, autostart, notifications, and recording retention
Saved recordings and file attachments remain on that computer. See Where local data lives. See Data, privacy, and retention for what can leave your computer for hosted AI, sharing, and other features.

Recovery keys

Anarlog creates your first sync key automatically and stores it on your device. An existing synced device transfers the key to new devices through an encrypted package. Anarlog cannot read or recover the key. If you saved a recovery key during an earlier setup, keep it in your password manager. On a new desktop device, Use recovery key instead lets you connect while your other devices are offline.
If you lose every device holding the key and have no saved recovery key, Anarlog support cannot restore your encrypted cloud data. Local notes remain available on devices where they are stored.

Add another device

  1. Install Anarlog and sign in with the same Pro account on the new device.
  2. Keep Anarlog open and sync enabled on an existing synced device. It transfers the key automatically; no approval button is required.
  3. Keep the new device open while it connects and downloads your notes. If all existing devices are offline, setup waits until one comes online.
  4. Re-enter any Transcription or Intelligence API keys you use on this computer, then select those models under Settings → Transcription and Settings → Intelligence.
A device where you explicitly paused sync stays paused until you resume it. Connecting a local library previously used with another account still requires the Connect library choice below. Anarlog 1.4.29 includes five synced devices with Pro, plus any purchased extra slots. Settings → Sync → Devices shows your current usage and limit. If you reach the limit, remove an unused device or choose Get more slots to open your account page and add paid slots to a personal Pro subscription. Each add-on adds one slot. Existing connected devices remain connected if you later remove an add-on. Cloud API & Connectors is a separate, optional feature. If you enable it under Settings → Developers, Anarlog uploads a server-readable copy for remote agents; it does not decrypt or weaken your end-to-end encrypted sync data. See Cloud API and connectors.

Switch accounts while keeping local notes

In 1.4.25, signing in to another account keeps your personal notes and recordings available on this device. Sync waits for your choice in Connect library:
  • Keep using locally leaves the library available without connecting it to the signed-in account.
  • Connect library connects the personal library to that account and brings in its existing notes. Copies already synced to your previous account remain there. Team and shared notes stay with their workspace.
Reconnect integrations for the account you are using. Connecting a different account opts this library into the new account-switching format; older app versions cannot open it. Keep a compatible version installed rather than downgrading after connecting. This is an account-switching choice, not a repair for a delayed sync. Leave your account and recovery key unchanged while investigating a sync error.

Where local data lives

Anarlog keeps your notes, recordings, and settings in its application data folder, next to the local database. You don’t pick a storage folder, so a file-syncing service such as iCloud Drive, Dropbox, Google Drive, or OneDrive never competes with Cloud sync for the same files. Backup tools that snapshot the folder are fine. Earlier versions let you point storage at a custom folder, often an Obsidian vault. The first launch after updating moves the notes and recordings from that folder back into the application data folder and removes only the files Anarlog created there. Your other files in that folder stay where they are. To keep an Obsidian vault or another folder up to date, use the Export every meeting as Markdown automation and choose that folder as its export location. It writes files one way, from Anarlog into the folder.

Fix a blocked sync

  • Sync needs attention / setup required: Open Anarlog on an existing synced device signed in to the same account, or enter a recovery key you saved during an earlier setup.
  • Connecting this device: Open Anarlog on an existing synced device signed in to the same account, or use a previously saved recovery key.
  • Sign in again: Sign out and sign back in, then resume sync.
  • Identity mismatch: Sign in again with the account that owns the synced notes. Check Sync settings before changing local files.
  • Device limit reached: Remove an unused device, then try again.
  • macOS Keychain error: Open Settings → Sync, click Repair Keychain Access, and resume sync.

Sync stays on Connecting or Cloud sync delayed

Both states mean Anarlog is still retrying in the background. Your notes remain available locally.
  • Connecting… means this device has not finished setting up encrypted sync. If setup fails, Anarlog may show Sync needs attention with more detail.
  • Cloud sync delayed means recovery has not finished. Anarlog may be waiting for more synced data or retrying a failed step. An error appears below the status when one is available.
To fix it:
  1. Check that the device is online and that a firewall, VPN, or proxy is not blocking api.anarlog.so. Opening https://api.anarlog.so/ in a browser can return 404 Not Found because there is no page at that address. This alone neither indicates a sync failure nor proves that the app can complete sync.
  2. Check the date and time on this device. A wrong clock makes sync credentials expire immediately; Anarlog reports this as a clock problem.
  3. Keep Anarlog open. A large first download can take several minutes and resumes if the app was closed.
  4. Turn Cloud sync off and on again from Settings → Sync.
  5. If it still does not clear, click Sync now and expand Sync log. Note the time you tried it, the status text, any error, and the app version and operating system on each affected device.
No sync activity yet does not mean that sync has never run. The in-app log contains recent activity from the current app session and can remain empty while encrypted sync is being set up or recovered. Email team@fastrepl.com with those details and any in-app log entries. If the log is empty, include the native app.log from the affected computer. For the stable desktop app:
  • macOS: In Finder, choose Go → Go to Folder and enter ~/Library/Logs/com.hyprnote.stable/.
  • Windows: In File Explorer’s address bar, enter %LOCALAPPDATA%\com.hyprnote.stable\logs.
Staging and the retired Nightly app keep separate logs; use com.hyprnote.staging or com.hyprnote.nightly in place of com.hyprnote.stable. Review logs before sharing them, and never send your recovery key, API keys, or sign-in tokens.
Do not delete your local data or create a replacement recovery key to troubleshoot delayed sync. Keep the existing notes and recovery key until sync completes and you have verified your notes on another device.
If sync is paused during recording or an import, let that activity finish. Anarlog resumes background sync when it is safe to do so.