Privacy policy

Draft — 28 September 2026. Founding beta.

What Roomy is

Roomy is a Windows application that scans local drives to show you where storage space is used. This policy covers the founding beta build and the associated website. It does not cover third-party sites you navigate to from links here.

Local scanning

Scanning, indexing, every visual view, and the inspector run entirely on your device. Roomy does not upload your file list, file names, paths, or file contents as part of scanning. This is true regardless of whether you opt into local usage notes or Roomy Guide, both described below.

Opt-in local usage notes

Roomy can optionally record small, local usage notes to help us understand which parts of the core loop are used. In the founding beta they work like this:

• Off by default. Nothing is recorded until you explicitly opt in inside the app.
• Stored only on your device (browser/app local storage), never uploaded, in this build.
• Capped at roughly 500 records or 14 days, whichever is reached first, then old records are pruned.
• Never includes full file paths, file contents, free-text filenames or folder names, or any account identifier. A bare drive letter (e.g. C) may be recorded as a coarse signal; a full path never is.
• You can turn this off at any time; turning it off stops new records but does not retroactively erase ones already stored locally until the retention window or an in-app clear action removes them.

Roomy Guide (planned — not in the launch build)

Roomy Guide is an optional, cloud-assisted extra that explains unfamiliar items, summarizes changes, and suggests a review order. It is not part of the launch build: no Guide server is deployed, and the app hides Guide when no server is configured. Nothing is ever sent to Guide unless you turn it on, and even then it would only run after an explicit opt-in. It never authorizes deletion by itself. When Guide launches, it will work like this:

• Minimization: by default, a Guide request sends only the selected item's kind, extension, size in bytes, file count, modified age in days, parent category (from Roomy's local knowledge base), an application identifier where available, up to 12 of the largest children's sizes, and the question you typed. Names and paths are off by default — sent as null unless you explicitly allow them for that request, and when allowed, your Windows user name is redacted to <user> first. File contents are never sent, regardless of settings. See the Guide data page for example requests.
• Provider disclosure: the cloud provider used to process a Guide request will be named in the app's Settings. No provider is committed yet — the processing vendor is still a planning assumption under evaluation, not a final choice.
• Retention: by default, the item metadata, your question, and any free-form text in a Guide request would not be stored — they would exist only for the duration of the request and the one provider call (plus at most one retry) needed to answer it. What would be stored indefinitely, for cost and abuse accounting only, is: a device id, an account id, the endpoint called, token counts, an estimated cost, latency, and an outcome (success / provider error / error) — never file names, paths, or question text, regardless of the retention setting.
• Your identifiers: paths and filenames can incidentally contain personal information (e.g., a folder named after a person). Names and paths are off by default for this reason; if you turn them on for a request, avoid doing so on an item you'd rather not describe, or rename first.

Update checks

Roomy checks for updates when it starts by asking GitHub for the latest release. GitHub sees the request — your IP address and the app version are visible to GitHub — but no file data is sent, and the check only reads a small version file. You can turn this off in Settings → About ("Check for updates when Roomy starts"); it is on by default. Updates are signed, and an update only installs when you click install.

Account, device, license, and trial data

If Roomy Cloud launches to run Guide entitlements, licenses, and trials, it would store a small amount of account data — separate from, and much smaller than, Guide request content:

• Accounts: an account id, an optional email address (only if you provide one), creation date, and — once billing is enabled — a Stripe customer id and a lifetime-purchase timestamp. No account or email is required to use the free local core.
• Devices: a device id, the account it belongs to, a device name and app version you provide, a hashed session token (SHA-256 of a random 32-byte value; the raw token is never stored), and creation/last-seen timestamps.
• Licenses and activations: a license key (format ROOMY-XXXXX-XXXXX-XXXXX-XXXXX), its plan (Lifetime or Guide), status, and — for each device it's activated on — an activation/deactivation timestamp and, for Guide licenses, a period-end date. Up to 3 devices per license by default.
• Trials: an invite code, start/expiry dates, and an ask limit, one row per account. One trial per account; invite codes have a maximum number of uses.
• Subscriptions: once billing is enabled, a Stripe subscription id, plan, status, current period end, and cancel-at-period-end flag — no card details, which Stripe holds directly.
• Guide usage counters: one row per successful Guide ask (account, device, endpoint, source, timestamp) to enforce quotas, plus the cost/latency/outcome telemetry described above. Neither table stores item metadata, names, paths, or question text.

Payment processing

Roomy has no paid tier at launch. When a paid Roomy Lifetime upgrade or Roomy Guide subscription launches, payment is intended to be handled by Stripe as the payment processor. Roomy does not store full payment card numbers on its own servers; Stripe's own privacy policy governs the data it collects to process a transaction.

What we don't do

• We don't sell personal data.
• We don't require an account to use the core local product.
• We don't run cleanup or deletion without your review — see the safety section on the homepage.

Changes to this policy

Because this is a beta, this policy will change as features ship (in particular, once Roomy Guide and payments go live). We'll update the date at the top when it does.

Contact

Roomy is made by Keethesh Mootoosamy. Contact: keethesh15@gmail.com.