Will Marq overwrite my notes?

Yes, and that's the point: Granola is the source of truth. Every time a meeting changes in Granola (new AI summary, updated transcript, edited title), Marq re-fetches it and rewrites the corresponding .md file.

So don't edit Marq's files directly. If you want extra notes on a meeting, edit the meeting in Granola. Anything you type into the .md after Marq writes it gets replaced on the next sync of that meeting. We picked this boring, predictable model on purpose. The alternative, merging your edits with Granola's, would corrupt notes in ways neither side could detect.

How does file naming work?

By default: YYYY-MM-DD_meeting-title.md (slugified), for example 2026-07-13_Design-review.md. You can set a custom template in Settings using {date} and {title}.

If two meetings would produce the same filename, Marq appends -2, -3, and so on. It never silently overwrites one with the other. Each meeting maps to exactly one file for its lifetime, identified by its granola_id in the frontmatter.

What if I rename or delete a meeting?

Rename a meeting in Granola and the file gets renamed too. Marq tracks the rename and removes the old file. Delete a .md yourself and the next sync re-creates it; to stop syncing a meeting, delete it in Granola, not on disk.

What if I move my output folder?

Pick a new folder in Settings and Marq automatically moves every file it has synced into the new location. Files you added manually (not tracked by Marq) stay where they are.

What about transcripts? Which Granola plan do I need?

You can sync meeting summaries on the free Granola tier. Transcripts are a paid Granola feature. If your plan includes them, Marq fetches and renders them under a ## Transcript section (you can toggle this off in Settings if you only want summaries).

Where are my Granola tokens stored?

In a plain JSON file at ~/.config/marq/oauth.json, with 0600 permissions, readable and writable only by your user account. Marq does not use the macOS Keychain.

This is a deliberate tradeoff: a plain file is simpler, survives rebuilds without Keychain prompts, and is easy to inspect or delete. The cost is that the token isn't encrypted at rest, so any process running as you could read it.

Does Marq phone home?

Barely. Marq sends exactly two anonymous events so we can count installs and know that syncing works:

app_installed, sent once ever, the first time you run a release build (includes the app version and your macOS version). And sync_completed, sent after a sync finishes, with the counts of files created, updated, and skipped, plus whether the sync was manual or scheduled.

Never sent: note content, meeting titles, filenames, file paths, your email, or your Granola account. You're identified only by a random ID generated once on your machine (~/.config/marq/telemetry_id), which you can delete anytime. Separately, Marq checks the GitHub releases endpoint on launch for updates. That's a normal update check, not analytics.

What happens if my Granola session expires?

Marq refreshes your access token automatically in the background. If Granola revokes the connection (you signed out, changed your password, etc.), Marq shows a "session expired" prompt and asks you to reconnect. Your meeting files stay on disk untouched.

Does Marq work offline?

It can read what's already on disk, but it can't fetch new meetings without a connection to Granola.

Where do updates come from?

Marq checks for new releases on launch and notifies you in-app. You download directly from us and install with one click. Signed and notarized, and nothing auto-installs without your say-so.