How ARADAR works

What ARADAR is for

ARADAR is for managing your reference track library – the music you collect, study, and submit to. It’s not a DAW, not a DJ tool, not a sample browser. The workflow it supports:

1. Import tracks from your library on disk
2. Tag, rate, and organise them into playlists
3. Track which labels release what kind of music (with built-in audio metric aggregations)
4. Match your tracks against label catalogues using loudness and frequency profiles
5. Manage submissions to those labels through a pipeline

Common workflows

ARADAR supports two distinct loops:

• Production reference: filter for a sound you’re chasing → drag the track into Ableton → A/B against what you’re working on.
• A&R targeting: profile labels by their catalogue’s loudness and frequency signatures → match your finished track’s profile to compatible labels → submit and track responses through the pipeline.

The same library data powers both. Most producers use both loops – referencing during the production phase, targeting once a track is finished.

Importing your tracks

Drag a folder onto the Library tab, or use File → Import Folder. ARADAR scans recursively, reads ID3 metadata, and queues each track for audio analysis.

What happens next: indexing. ARADAR treats analysis as a setup phase, similar to how Loopcloud or Lightroom index a new library. A small panel appears in the corner showing progress. Tracks appear in your library only after their analysis completes – you’ll see the library fill gradually rather than all at once. For a large library (5,000+ tracks), this can take several hours; for a smaller batch, minutes. You can quit ARADAR at any time and analysis will resume from where it stopped when you next launch.

Supported formats: AIFF, WAV, FLAC, MP3, and M4A.

Re-importing the same files is safe. ARADAR deduplicates on the file path, so dragging a folder you’ve already imported (or dragging a track out into a DAW and the same file back in later) silently skips anything already in the library. No duplicates appear; the rest of the drop is imported as usual.

What ARADAR imports – and what it skips

ARADAR is for tracking released tracks and demos, not sample libraries. During import three categories are filtered automatically:

• Files that aren’t actually audio when probed (renamed images, corrupt headers).
• Files hosted on remote storage (Google Drive, Dropbox, OneDrive, Box, iCloud) – accessing them would trigger downloads.
• Files shorter than 60 seconds – almost always samples, loops, one-shots, or stems rather than full tracks.

Each skipped file is listed in the import summary sheet under a disclosure so you can spot anything caught by mistake. Keep your sample library outside ARADAR.

Best file format: AIFF

ARADAR reads track metadata (artist, label, genre, year, BPM, key) from embedded ID3 tags. AIFF is lossless, widely supported, and has proper ID3 tag support that every modern DAW writes correctly. When you drag an AIFF from ARADAR into your DAW, it imports instantly without background decoding or stuttering.

WAV technically supports metadata but most music tools don’t write it consistently – WAV tracks often land in the library with empty metadata fields. FLAC works too, but your DAW will likely have to decode it to a temporary WAV file when you drag it in, which slows down your workflow. Avoid MP3 for your reference library if you can.

File permissions and Full Disk Access

macOS protects certain folders (Desktop, Documents, Downloads, external drives, network shares) and requires apps to explicitly request access. ARADAR is intentionally not sandboxed, so it can read your music from anywhere on disk – the trade-off is that for files in protected locations you need to grant Full Disk Access once.

If a track shows in red with “Permission denied”, a banner at the top of the Library tab links straight to System Settings → Privacy & Security → Full Disk Access. If ARADAR isn’t listed there yet, click the + button and add it from /Applications, then toggle it on. Right-click the affected tracks and choose Retry Analysis.

ARADAR also stores a security-scoped bookmark for each imported track. Bookmarks survive renames and moves better than raw file paths, and let ARADAR reach the file on every subsequent launch without re-asking permission per file.

Filter and find

The Library has dropdowns for Label, Key, Year, BPM, and Rating. Combine them – [Label Name] + Fmin + 2024 narrows in seconds. Use the search box for free-text matching. Active filters appear as chips with × to clear each one individually.

You can also seed filters from the Inspector: click any label name in the Label Matches section and that label is added as a library filter without leaving your current view. Useful for spot-checking “what else has this label released?” before deciding to submit.

Ratings

Rate any track or label (0–5) via right-click → Rating, or click the stars in the Inspector panel. The Rating dropdown lets you filter by minimum rating level – set a floor and the library shows only tracks at that level or above.

The Inspector

Click any track row to open the Inspector on the right. It shows:

• Artwork and editable metadata – title, artist, album, label, genre, year, BPM, key, and freeform notes. Edits save to the ARADAR database immediately; the original audio file’s ID3 tags are never modified.
• Star rating – click directly on the stars (0–5) to set.
• Audio Analysis – LUFS Integrated, LRA, true peak, RMS, crest factor, plus the 10-band Frequency Profile chart.
• Label Matches – top labels ranked for this track with their composite match score. Click any label name to add it as a filter on the library, handy for inspecting what else that label has released without losing your current Inspector context.
• Tags – add or remove freeform tags. Tags are searchable and can be used as filters.
• Status – pending / analysed / failed / unreachable, with a Retry Analysis button when relevant.

Drag tracks into your DAW

Click and drag any track from the library directly into Ableton, Logic, Pro Tools, or any other DAW. ARADAR exposes the original file through a secure bookmark – no copies are made, no decoding step, just the source file landing on your timeline.

If the drag seems to do nothing, confirm the track’s status is Analysed. Pending or Failed tracks may not resolve correctly.

Tags

Tags are freeform labels you attach to tracks for any organising scheme that doesn’t fit the built-in fields. Mood (dark, uplifting), purpose (set-opener, peak-time), production state (needs-mastering, pitched), reference category (kick-reference, vocal-reference) – whatever helps you find tracks later.

Adding tags. Open the Inspector and type into the Tags field. Press return to commit each tag. Existing tags auto-complete as you type so you don’t end up with darks, dark, and DARK competing.

Filtering by tag. The Library search box matches tag text. Type #dark or just dark and tracks with that tag surface.

Removing tags. Click the × on any tag chip in the Inspector.

Tags live in the ARADAR database – they don’t write back to the original file’s ID3 tags.

Statistics window

⇧⌘S (or Window → Library Statistics) opens a separate window with an overview of your library:

• Overview – total tracks, total labels, hours of music, average LUFS / crest / BPM across the library.
• Top Lists – your top labels by track count, top genres, top years.
• Distributions – histograms of BPM, key, year, and rating across the library.
• Quality Averages – average loudness and dynamics by year, useful for spotting how your reference collection’s mastering style shifts over time.
• Action Items – tracks needing attention (missing metadata, failed analysis, unrated, untagged). Click any row to jump straight to those tracks in the Library tab with the right filter applied.
• Submissions – pipeline summary by status, average response time, top labels by submission count.

The window is independent of the main one – leave it open on a second monitor while you work.

Themes

Six themes ship with ARADAR. Switch any time from Preferences → Appearance, or from the appearance switcher in the toolbar. Each theme adapts every surface in the app (sidebar, tables, inspector, charts, charts’ band colours, focus highlights).

• Nocturne (default) – deep neutral dark theme, low-contrast, designed for long studio sessions in dim rooms. Recommended for most users.
• Pulse – saturated dark theme with stronger accents. Good if Nocturne feels too restrained.
• Velvet – warm dark theme with reduced blue light. Easier on the eyes late at night.
• Open Air – bespoke light theme for bright rooms, daylight, or screen-sharing.
• System (Light) – system-style light theme using Apple’s native appearance colours. Picks the macOS look when you want the app to blend with the rest of the OS in Light mode.
• System (Dark) – system-style dark theme using Apple’s native appearance colours. The dark counterpart to System (Light) for blending with macOS in Dark mode.

The chart colours, match-score gradients, and frequency-corridor shading are theme-aware, so switching themes doesn’t break the visual language of the data.

Keyboard shortcuts

• Space – Play / pause current track
• ⌘F – Focus search field
• ⇧⌘N – Create new playlist
• ⇧⌘S – Open Statistics window
• ⌘? – Open this help window
• Delete – Remove selected track from library (confirmation required)

What ARADAR measures

ARADAR analyses each track on import using the bundled ffmpeg with ebur128, astats, and a custom FFT-based frequency profiler. Metrics are stored per track and surfaced in the Inspector and the Labels tab aggregations.

Loudness metrics

LUFS Integrated (Loudness Units relative to Full Scale, ITU-R BS.1770). The track’s overall perceived loudness across its duration. Lower values mean quieter, higher mean louder. Stored as a signed dB value where 0 is the maximum theoretical loudness.

LRA (Loudness Range). The difference between the loudest 95th percentile and quietest 10th percentile of a track’s loudness distribution. Higher LRA means more dynamic; lower means more compressed.

True Peak. The highest instantaneous peak in the audio, measured in dBFS (decibels relative to Full Scale). 0 dBFS is digital maximum; negative values indicate headroom. ARADAR measures with the peak=true flag for true peak (oversampled inter-sample peak detection).

RMS Level. Root Mean Square level – the average power of the signal. Calculated across the entire track in the astats Overall section. Lower means quieter on average.

Crest Factor. The ratio of peak amplitude to RMS amplitude. Computed from 10^((peak_dB − rms_dB) / 20). Higher crest factor means more dynamics relative to peaks; lower means more compressed. A pure sine wave has crest factor √2 (~1.41); modern club masters tend toward 3–4; pre-loudness-war recordings can hit 8–12.

Frequency metrics

Frequency Profile. ARADAR computes a 10-band frequency spectrum for each track using a Fast Fourier Transform with a +4.5 dB/octave tilt – the industry-standard slope for tonal-balance analysis. The tilt compensates for the natural high-frequency rolloff of mastered music, so a well-balanced track reads as roughly flat across the bands rather than bass-heavy. The 10 bands cover 20 Hz to 20 kHz logarithmically: deep sub, sub-bass, bass, low-mid, mid, upper-mid, presence, brilliance, air, ultra-high.

Three-band Summary (Low / Mid / High). A simplified roll-up of the 10-band profile into three numbers, used in the Labels tab aggregations and the quick-look deviation bars. Faster to compare across many tracks at once than the full chart.

The Analysis panel

A small floating panel appears in the corner of the app whenever ARADAR is analysing tracks. The panel is intentionally non-dismissible – it disappears on its own when the queue is empty.

The panel shows:

• Progress – how many tracks are done, how many remain, and an estimated time to completion. Early in a run the estimate can be rough; it settles after the first several tracks.
• Current file – the title of whatever track ARADAR is analysing right now.
• Failure warning (when applicable) – if more than 10% of tracks analysed this session have failed, the panel surfaces the count with a click-to-filter link that filters the library to show only failed tracks. From there, right-click any failed track → Retry Analysis (works for multi-selection too).
• Cancel – clicking Cancel opens a confirmation dialog. If you confirm, all pending tracks are removed from your library, useful if you imported the wrong batch by mistake. Completed, failed, and unreachable tracks are untouched. Re-importing after Cancel is the recovery path; there’s no undo.

While the panel is visible, the Import button is disabled. ARADAR processes one batch at a time so the queue stays predictable.

Single-track re-analysis uses a simplified version of the panel – just a spinner and the file name, no ticker – because there’s nothing meaningful to count down. The full panel only appears for bulk imports.

You can quit ARADAR at any time during indexing. On next launch the panel reappears and analysis resumes from where it stopped. Any track that was mid-analysis at quit time is reset to pending and re-attempted.

Troubleshooting analysis

“My library is empty after I imported.” Analysis is still running. Check the panel for progress. Tracks appear in the library as their analysis completes, not all at once. For a 5,000-track import this can take several hours. You can quit and come back; analysis resumes.

“A track shows Failed.” ARADAR tried to analyse the file three times and ffmpeg couldn’t read it. Common causes: corrupted file, format mismatch (e.g., a renamed .wav that’s actually something else), or a permissions issue. Right-click the track → Show in Finder to confirm the file is intact, then right-click → Retry Analysis to try again, or Remove if it’s no longer needed. Multi-selection of failed tracks supports bulk retry.

“A track shows Unreachable.” The file was moved, renamed, or deleted after you imported it. ARADAR’s bookmark to the file no longer resolves. Try right-click → Retry Analysis first; if the file is back in its original location, this will pick it up. If not, right-click → Remove and re-import from the new location. A manual relink option is planned for a future version.

“Indexing seems frozen.” Confirm the panel is still updating the current file. If the same file has been shown for several minutes, that file may be unusually long or there may be an issue with ffmpeg processing it. Wait a few more minutes; if no progress, quit ARADAR and relaunch – the queue will resume and the stuck track will retry.

Reading the frequency profile chart

The Frequency Profile chart in the Inspector shows how a track differs from the selected reference, not the track’s absolute spectrum. The 0 dB horizontal line is the reference – wherever the track’s curve sits on that line, the track matches the reference exactly in that frequency band.

Reading direction:

• Curve above 0 dB → the track has more energy than the reference in that band.
• Curve below 0 dB → the track has less energy than the reference in that band.

Worked example. A bump at L (low band) showing +6 dB means your track is 6 dB heavier in the lows than the reference. To match the reference, you’d reduce the low end of your track – EQ down the low-shelf, turn down the kick or sub, etc.

Conversely, a dip at M (upper-mid) showing -3 dB means your track has 3 dB less upper-mid energy than the reference. To match, you’d boost your track’s mids.

The reference is the fixed target; the track’s curve is what moves relative to it.

Practical reading. A curve sitting roughly flat across the 0 dB line means the track’s tonal balance matches the reference well. Big bumps or dips are tonal differences – sometimes deliberate stylistic choices, sometimes mix issues worth investigating before pitching.

Loudness doesn’t change the chart. ARADAR normalises each track by its own total spectral energy before comparison, so the chart shows tonal shape, not absolute level. A track at −16 LUFS and the same track at −8 LUFS draw identical curves. You don’t need to gain-match tracks before comparing them.

Built-in reference curves

ARADAR ships with five genre baselines and one mathematical reference:

• Electronic, Hip-Hop, Pop/Rock, Acoustic, Orchestral – genre archetypes. Useful for rough tonal sanity checks within each family. Not precise enough for label-level targeting – build a custom curve for that.
• Pink Noise (reference) – mathematical baseline of equal energy per octave. A track that draws a flat 0 dB line against pink has perfectly balanced spectral energy.

Pink is a mastering yardstick, not a genre target. Most modern music shows a low-end drop against it (mastering high-pass + sub-bass roll-off) and a roughly flat upper region (where the +4.5 dB/oct tilt is calibrated to put well-mastered music). Two genuinely different tracks may look similar against pink – that’s expected. Pink reveals mastering balance; the genre curves reveal tonal signature.

Custom reference curves

The built-in genre curves are broad archetypes. For real A&R targeting, you want a reference grounded in actual material – typically a specific label’s catalogue, a sub-genre, or your own production style.

Create a custom curve. In the Library or My Tracks tab:

1. Select 3 or more tracks that represent the sound you want as your reference. (Examples: 10 tracks from a label you’re targeting; 8 tracks from your own released catalogue if you want to compare new productions against your established sound; 15 tracks from a sub-genre like “Berlin techno 2024”.)
2. Right-click → Create Custom Reference Curve…
3. Name the curve (e.g., “Anjunadeep”, “My Sound”, “Mango Alley”).
4. Click Create.

ARADAR computes the median 10-band spectrum across your selected tracks and saves it as a new reference. The minimum is 3 tracks – fewer doesn’t produce a meaningful median.

Use a custom curve. The Reference Curve picker in Preferences → Audio (and in each track Inspector) now shows two sections: Built-in and Custom. Pick your custom curve and the Frequency Profile chart for every track measures deviation against that curve.

Delete a custom curve. Select the curve in the picker → click the inline delete button → confirm. Any tracks or settings using the deleted curve fall back to the default reference.

Editing an existing curve. Not supported – delete and recreate with a different selection if you want changes. The curve is a snapshot of its source tracks at creation time.

The shaded band (corridor)

When you select a custom reference curve, the Frequency Profile chart shows a subtle shaded band around the 0 dB line. This is the ±1 standard deviation envelope computed from the variance of the tracks you used to build the curve.

What it means in plain English. Say you built “Mango Alley” from 8 tracks on that label. Each of those 8 tracks has its own frequency shape – they’re not identical. The median of those shapes is the 0 dB line (the reference). The shaded band shows how much those 8 tracks varied around that median, per frequency band.

How to read it as a producer:

• A track whose curve stays inside the shaded band is tonally in the same range as what that label has released. Within normal catalogue variation. No obvious mismatch.
• A track whose curve goes outside the band in a given region is a noticeable outlier relative to the label’s catalogue. Doesn’t mean it’s wrong – it’s a real difference worth noticing before you pitch.

Tight band = cohesive label or sub-genre. If the source tracks consistently have e.g. heavy lows, the band will be narrow in the low region. Hard to fit if your track doesn’t sit there.

Wide band = broad or diverse source. If the source tracks span lots of different sounds, the band is wide – tonal match matters less, the label takes variety.

Built-in curves don’t show a corridor. By design – they’re either broad genre archetypes or a mathematical pink-noise baseline (not derived from a specific corpus), so a variance band around them wouldn’t reflect any real catalogue’s spread. The corridor is meaningful only when the curve came from an actual set of tracks you picked.

Comparing multiple tracks

When you’ve got a custom reference and need to pick which of your finished tracks to send to that label:

1. In Library or My Tracks, select 2 or more tracks (up to 10).
2. Right-click → Compare Frequency Profiles…
3. A comparison sheet opens with:

• All selected tracks’ curves overlaid on one chart, each in a distinct colour.
• The reference and shaded band visible.
• A list below showing each track and its tonal deviation from the reference (lower = closer match).

Pick the reference in the picker at the top of the sheet – built-in or custom.

Sort the list by tonal deviation to float the best matches to the top. Click any track row to highlight its curve on the chart (others fade).

Practical use: select your last 5 finished tracks → set reference to your target label’s custom curve → the track at the top of the sorted list is your strongest candidate to pitch first.

The Labels tab

The Labels tab shows every label you own tracks from. After audio analysis runs, each label gets a loudness signature (LUFS range, average LUFS, crest factor, RMS) plus a frequency profile (10-band spectrum) computed from its tracks – useful for understanding what the label releases.

Click a label row to open the Label Inspector with the full aggregations and frequency profile. Click View Tracks to inspect the catalogue you have for that label.

A&R workflow

The Library, Labels, and A&R Tracker tabs are designed to work together:

1. Build the library. Import all the tracks you reference, regardless of submission intent. Let analysis complete before moving on.
2. Profile labels. As analysis completes, the Labels tab fills with loudness and frequency signatures per label. Sort by Avg LUFS, Avg Crest, or any of the frequency band averages to find labels that match your production style.
3. Identify targets two ways. From the Labels tab, click View Tracks to inspect what kind of music a label releases. Compare their frequency deviation profile to your own track’s profile in the Inspector – labels with similar tonal balance are stronger match candidates than those with opposing curves. Or use a custom reference curve: pick 5–15 tracks from a specific label, save them as a custom curve, then your own tracks are measured against that label’s sonic identity directly.
4. Compare candidates side by side. Select multiple tracks from your library → right-click → Compare Frequency Profiles. The overlay chart shows which of your tracks best matches a given reference.
5. Create submissions.Right-click a finished track → Add Submission to Label → pick the target label. The submission lands in A&R Tracker with status draft.
6. Track responses. Update submission status (submitted, responded, accepted, rejected) as the conversation progresses. Note response times to learn label behaviour over time.

How label matching works

When you click “Add submission to label” on a track, ARADAR ranks your labels by how well the track matches each one’s profile. Labels appear sorted by composite match score.

The composite score combines four dimensions:

• Frequency profile – 40%. How closely your track’s 10-band frequency balance matches reference tracks in your library whose Label metadata field matches that label’s name. This is the strongest signal – it’s what makes ARADAR different from sorting by genre and BPM. Labels that have analysed tracks in your library get a real frequency score; labels with no tracks in your library show “Freq –”.
• Loudness – 25%. How close your track’s integrated LUFS is to the label’s typical range.
• Tempo – 20%. How close your BPM is to the label’s typical tempo range.
• Genre – 15%. Binary match between your track’s genre tag and the label’s. Smaller weight; the other dimensions do the heavy lifting.

The percentage in each dropdown row is the weighted combination. A 70%+ match means the track is genuinely in the label’s range; below 50% signals significant divergence.

How label data affects score reliability

The frequency dimension carries the most weight (40%), but it needs a handful of the label’s releases analysed in your library before ARADAR has enough data to score it confidently.

The track-count pill. Next to a label’s name in the breakdown you may see a small pill like “4 tracks” or “1 track”. That’s how many analysed tracks ARADAR currently has for that label’s frequency profile. Once a label reaches 8 or more analysed tracks the pill disappears – the profile is considered reliable.

Fewer tracks → softer score. When ARADAR has very few (or no) tracks for a label, it dampens the composite score to reflect lower confidence. This isn’t a penalty against the label – it’s an honest signal that ARADAR doesn’t yet know enough about the label’s sound to be sure of the match. As you analyse and tag more of their releases, both the confidence and the accuracy improve.

Labels with no frequency data at all. ARADAR falls back to LUFS, tempo, and genre. The breakdown shows “Freq –” so you can see the dimension was skipped, not failed. To unlock the full match potential for a label, import a few of their releases and set the Label field on those tracks to match – the profile builds automatically as analysis completes.

Adjusting matching strictness

Preferences → Audio Analysis → Label Match Scoring lets you pick how strict the matching is:

• Lenient – more labels surface as matches. Use if scores feel too low across the board.
• Balanced – default tuning.
• Strict – only confident matches score high. Use if everything looks like a match.

The setting affects how harshly band-level mismatches and thin label catalogues pull the score down. Try Balanced first; reach for Lenient or Strict if your results feel off.

Why a label might rank lower than you expect

If a label you want to pitch to ranks lower in the matching results than expected, ARADAR is telling you the track is off-profile on one or more of the four metrics. The breakdown in the Inspector shows which dimension is dragging the score:

• Freq low – your track’s frequency balance is far from what that label typically releases.
• LUFS far from their range – your master is significantly louder or quieter.
• Tempo outside their pocket – your BPM is outside what their catalogue typically uses.
• Genre missing on your track – the genre dimension can’t contribute (fill the tag in the Inspector to fix).

You can still submit to any label manually by navigating to the Labels tab and adding the submission from there. The matching results are a shortcut for likely matches – not a hard filter. Sometimes a label that ranks low on the metrics is exactly the right home for a track that’s deliberately off-trend.

Submissions pipeline

Right-click any track → Add Submission to Label→ choose a label. The A&R Tracker tab shows your pipeline with submission status, dates, and response tracking. Status moves through draft → submitted → responded → accepted or rejected as the conversation progresses.

Click a submission row to expand it and add free-text notes – useful for tracking who you contacted, what response you got, and any follow-up. Submission timestamps and response times feed the Statistics window’s submission summary so you can spot which labels tend to respond fast.

Free trial

ARADAR includes a 14-day free trial on first launch. During the trial every feature works exactly as it does in the licensed version – importing, custom reference curves, label matching, submissions, exports. Nothing is degraded; this is so you can evaluate the real app, not a stripped-down preview.

A banner above the main UI shows how many trial days remain, with a one-click path to purchase or to paste a license key you already have.

After the trial

When the 14 days run out, your library, ratings, submissions, tags, custom curves, and analysis data stay intact and remain accessible. What’s locked is creating new content:

• Importing new tracks
• Creating new custom reference curves
• Logging new submissions
• Adding new tags

Existing content keeps working – you can still browse, filter, listen, drag into your DAW, and view analysis. The lock is lifted the moment you activate a license.

Buying ARADAR

Click Buy ARADAR from the trial banner or from Preferences → License. The button opens the ARADAR store (shop.aradar.app) in your browser. Lemon Squeezy handles checkout and tax compliance (they’re the Merchant of Record). After purchase you’ll get a receipt email containing your license key.

Activating a license

You have two paths:

1. One-click from the email. The receipt email contains an “Activate ARADAR” button. Click it; macOS hands the link to ARADAR, which opens Preferences → License, prefills the field, and runs activation automatically. If your email client strips custom URL schemes (rare; some corporate Outlook setups do this), use path 2.
2. Manual paste. Copy the license key from the email → Preferences → License → paste into the License Key field → click Activate.

Either way, the License tab confirms with a green success message once activation completes. Status switches to Licensed.

Multi-Mac use (3 activations)

Each license activates on up to 3 Macs – your studio Mac, your laptop, and one spare. You don’t have to use all three; the count is a ceiling, not a quota.

If you hit the limit (e.g. when buying a new Mac), ARADAR shows an “Activation limit reached” message with two options:

• Free a slot from an old Mac – open ARADAR on the Mac you no longer use → Preferences → License → Deactivate This Mac. The slot is released immediately and you can activate on the new Mac.
• No access to the old Mac – email hello@aradar.app with the license key and we’ll free the slot manually.

Offline use

ARADAR validates your license periodically over the internet to confirm it’s still active. If you’re offline (no Wi-Fi, on a plane, etc.) ARADAR keeps working in fully-licensed mode for 30 days without contacting the server. The status badge shows “Licensed (offline N days)” so you know how long it’s been since the last successful check.

After 30 days offline, the app drops back to the “License invalid” state and content-creation features lock – exactly like after trial expiry. The moment you reconnect and ARADAR successfully revalidates, full access is restored. Nothing in your library is touched.

Deactivating before selling or wiping a Mac

Before you sell, give away, or wipe a Mac running ARADAR, open Preferences → License → Deactivate This Mac. This releases the activation slot on the server so you can use it on the next machine without contacting support.

If you forget (e.g. you wiped first), email hello@aradar.app with your license key and we’ll free the slot.

Refunds and receipts

Lemon Squeezy keeps your receipt and order history. The receipt email you receive after purchase has a “View Order” link that opens your order page where you can re-download the receipt, see the license key, or request a refund within the policy window. If you can’t find the email, search your inbox for “Lemon Squeezy” or for the ARADAR store name. For anything beyond what the Lemon Squeezy order page handles, email hello@aradar.app.

Troubleshooting license activation

“License activation fails with ‘Couldn’t reach the license server’.” ARADAR needs an internet connection to activate a license (subsequent validation re-checks can be deferred up to 30 days). Confirm your connection, then click Try Again on the error banner. If your network blocks Lemon Squeezy’s API (api.lemonsqueezy.com), try a different network – corporate firewalls occasionally do.

“License activation fails with ‘Activation limit reached’.” Your license is already activated on 3 Macs. Open ARADAR on one of them → Preferences → License → Deactivate This Mac → activate on the new Mac. If you don’t have access to any of the old Macs, email hello@aradar.app with your license key.

Anything else. Open Preferences → Diagnostics and click Export Log as File. Attach the file to a support email with a short description of what you were doing. Logs reflect the current app session – if you’ve restarted ARADAR since the issue occurred, reproduce it first so the log captures the relevant events.

Logs

ARADAR writes structured logs to the macOS unified log system, viewable in Console.app. Filter by subsystem app.aradar.aradar to see ARADAR events only.

Categories: imports (metadata extraction), analysis (audio analysis pipeline), playback (track load and seek events), database (migrations and writes), bookmarks (security-scoped bookmark resolution), app (application lifecycle).

Privacy

ARADAR is a local Mac app. Your library, ratings, submissions, tags, custom reference curves, frequency profiles, notes, and audio files never leave your machine. There is no telemetry on what you import, how you organise it, what you listen to, or who you submit to.

Three exceptions – narrow, explicit network requests that exist only to support paid use of the app:

1. License activation, validation, and deactivation. When you activate a license, ARADAR sends the license key, the name of this Mac (used by Lemon Squeezy to label the activation slot in their dashboard), and the response identifier to api.lemonsqueezy.com. Validation re-checks the license periodically. Deactivation releases the slot. No library data, audio data, or analysis results are sent – only what’s needed for license bookkeeping. Lemon Squeezy is also the merchant of record for the purchase itself, so they handle your billing details directly.
2. Crash reporting (opt-out). If ARADAR crashes or hits an unhandled error, a crash report is sent to Sentry – stack trace, OS version, app version, the type of error. No file paths, no track names, no license key, no email address. You can turn this off entirely in Preferences → Diagnostics → Crash Reporting. The toggle takes effect immediately.
3. Update checks. Sparkle fetches the appcast feed at aradar.app/appcast.xml periodically to learn whether a new version is available. The appcast and the downloaded DMG are EdDSA-signed; Sparkle verifies the signature before installing anything.

That’s it. No analytics. No usage telemetry. No “phone home” to count active users.