ProBackup's answer

Infrastructure runs on AWS. Backup files are stored in AWS S3 and metadata (IDs, tree structure, webhook registrations) in AWS RDS, encrypted at rest with AES-256 via AWS Key Management Service. Customers can choose from nine AWS regions (Ireland, Frankfurt, London, North Virginia, Montreal, São Paulo, Sydney, Singapore, Tel Aviv). ProBackup connects to each source app through its official API over OAuth, with all tokens AES-256 encrypted using unique initialization vectors. Data in transit is secured via SSL/TLS on port 443, enforced with HSTS. The backup engine is incremental and versioned, creating independent snapshots each cycle.

BillSensor's answer:

Chrome Extension Manifest V3, JavaScript, HTML, CSS for the extension frontend. Node.js and Express for the backend. MySQL for the database. Resend for transactional email. Paddle as the payment processor and Merchant of Record. Hosted on Hostinger.

ProBackup's answer

ProBackup started in 2017 as Momentum Tools, originally built to back up Podio. As more teams moved their operations into a growing range of SaaS apps and hit the same blind spot — that vendors don't protect customer data from customer-side mistakes — the product expanded. In August 2020 it relaunched under the ProBackup brand, adding Asana as the first new platform, and grew steadily from there to cover 20+ apps. A major platform refresh came in September 2023, SOC 2 compliance was achieved in May 2025, and the current version (3.0), with a completely redesigned UI, launched in August 2025. Today ProBackup is a lean, product-led company (ProBackup BV) serving ~2,500 customers.

BillSensor's answer:

I got hit by Adobe's early termination fee after cancelling Creative Cloud. The fee was 50% of my remaining contract value and was buried in a tooltip I'd never seen at sign-up. I spent an hour on chat support and eventually got it waived by referencing a DOJ lawsuit. The whole experience was frustrating enough that I built something to prevent it from happening again. BillSensor started as a personal tool and became a product when I realised the same billing tactics were affecting almost everyone using SaaS tools regularly.

ProBackup's answer

ProBackup is purpose-built for SaaS productivity and CRM apps — not files or servers. It backs up the data living inside Asana, ClickUp, Monday, Airtable, HubSpot, Trello, Notion, Jira, Slack, Podio, and 20+ other tools, fully automatically every 24 hours. The key insight: your SaaS vendor backs up their own infrastructure for their disaster recovery, not to protect your work. If your team — or an AI agent acting inside the app — deletes or overwrites a record, the vendor can't bring it back. That gap is what ProBackup fills. Backups are incremental and versioned, so you get point-in-time recovery and can restore exactly what you need: a single field, a comment, a whole project. Optional Google Drive sync adds a second, independent layer of redundancy you control.

BillSensor's answer:

Most subscription trackers require you to connect your Gmail account via OAuth, which means granting an app permission to read your inbox. BillSensor doesn't ask for that. It reads billing emails passively as you open them in Gmail, with no account connection, no OAuth permission, and no "read and modify your data" prompt.

It's also the only subscription tracker that scores SaaS tools on dark billing patterns. Every detected subscription shows a score from 1 to 10 based on how aggressively that tool uses tactics like hidden cancellation fees, post-cancellation charges, and forced continuity. Adobe scores 9/10. DocuSign scores 9/10. Zapier scores 8/10. No competitor currently offers this.

ProBackup's answer

A few reasons. Breadth: one account covers 20+ platforms, and you can add unlimited apps on any plan. Granularity: restore a single record or an entire board, with point-in-time recovery to any previous day. No setup overhead: backups run automatically every 24 hours — no scheduling, no maintenance. Independent redundancy: unlike tools that dump a new CSV after every cycle, ProBackup syncs to a live Google Sheet you own, so you keep a usable copy even if ProBackup is unavailable. And trust: SOC 2 compliant, AES-256 encryption, isolated key management (no one at ProBackup can read your raw data), and a choice of nine AWS storage regions worldwide. It's a focused, product-led tool — self-serve onboarding, simple UI, transparent pricing.

BillSensor's answer:

Three reasons. First, no Gmail OAuth — competitors like SaaS Subscription Tracker and CostLoop require connecting your Gmail account. BillSensor detects subscriptions without ever requesting inbox access. Second, dark pattern scores — no other subscription tracker rates tools on billing behaviour, which means you don't just know what you're paying, you know which tools are most likely to make it hard to leave. Third, direct cancel links — every detected subscription includes a link to the cancellation page for that tool, so you're not hunting through account menus under time pressure.

ProBackup's answer

Teams that run their daily operations inside SaaS productivity and CRM apps and can't afford to lose that data — typically SMBs and mid-market companies, often without a dedicated IT/backup function. The buyer is usually the admin, operations lead, or team owner responsible for an Asana, ClickUp, Monday, HubSpot, or Airtable workspace who recognizes that accidental deletion, a rogue integration, a departing employee, or an AI agent gone wrong could wipe out work the vendor won't restore. ~2,500 customers today, with a 35% trial-to-paid conversion rate.

BillSensor's answer:

Freelancers, solopreneurs, and small business owners who pay for multiple SaaS tools and want to know about renewal charges before they happen, not after. People who've been hit by a surprise charge from a tool they thought they cancelled. Privacy-conscious users who want subscription tracking without connecting their email account or bank details to a third-party app.

BillSensor's answer:

BillSensor launched recently and is in an early growth stage. Skipping this question for now rather than listing placeholder names.