Editorial Policy

How I Test

Every vault app reviewed here runs on a paid subscription charged to my own card. No free access codes, no review copies, no sponsored placements. Trials run for at least a month on a real marketing stack: CRM integrations active, browser extensions installed and in daily use, team-sharing features exercised with real shared credentials where the manager being reviewed supports it.

Migration reviews are different. The import runs on actual data: a real CSV export from the outgoing manager, imported into the incoming one, tested on the ThinkPad in my South Austin home office and then verified on the MacBook on the other monitor. What breaks gets documented before anything gets written. Fields that drop silently. Extensions that need a full reinstall. Shared vault configurations that require admin permissions the setup docs didn't think to mention. Those observations go into the review because that's what a product page won't tell you and what I was specifically looking for when I went looking.

Notes from each trial go into a shared Notion doc maintained throughout the testing window, not reconstructed afterward. Sticky notes on the cork board above the desk track which trial windows are still open.

Affiliate Relationships

Some links here are affiliate links. Click one, buy the product, I receive a small commission at no extra cost to you. Affiliate relationships don't determine which products get reviewed, in what order, or what the review concludes. Rough subscription costs get mentioned when they're relevant to the comparison; exact prices aren't published because they shift with promotional cycles.

If I paid for a subscription and requested a refund during testing, that gets noted in the review. It has happened.

Scope and Limitations

Testing happens on a Mac and Chrome primary setup, with a refurbished ThinkPad running Windows as the dedicated vault-testing device. Team-sharing scenarios reflect a small marketing team of ten or fewer. Enterprise deployments, managed device environments, and setups administered by dedicated IT will behave differently from what's described here. Those configurations surface different edge cases than a marketing ops manager running her own migrations encounters.

Nothing here is security advice. The perspective is a marketing ops manager who ran the migrations, documented the edge cases, and writes about what she found.

Corrections

Spotted a factual error or want to flag something I missed? The contact page is the right place.