SimSweep privacy policy

Last updated: October 1, 2026

Effective date: October 1, 2026

SYVR Studios LLC ("SYVR Studios," "we," "us," or "our") operates the SimSweep desktop application, the optional SimSweep companion mod for The Sims 4, and the SimSweep website at simsweep.com.

The current SimSweep desktop app does not require a SimSweep account, Google sign-in, email sign-in, or an in-app billing portal. Most app data stays on your computer.

1. Who we are

SYVR Studios LLC is a Colorado limited liability company.

Contact:

• Email: info@syvr.dev
• Website: syvr.dev

2. Data SimSweep stores locally

SimSweep stores app data on your device so the desktop app can work without a login.

Local data can include:

• detected Sims 4 folders, including Mods, Tray, Saves, and game install paths
• scan results, browse rows, issue counts, and local SQLite data
• package index and thumbnail caches
• settings, theme choices, accessibility options, and notification choices
• local mod profiles, whitelist entries, sort manifests, and backup manifests
• save health analysis and save backup metadata
• crash bundles waiting for you to send or dismiss them
• heartbeats, usage events, and reports waiting to be sent
• local analytics snapshots used by the in-app Analytics view
• companion session recaps and live Game Link state

Uninstalling SimSweep may not remove every local data file. You can clear some caches from Settings, and you can remove the app data directory manually if needed.

3. Access data

Paid desktop access is verified through Patreon or through local keys issued by SYVR.

When you choose Connect Patreon, SimSweep opens Patreon OAuth in your browser, receives the local callback, and asks the SimSweep Worker to verify membership. The app may receive and cache:

• Patreon display name
• Patreon membership status
• resolved SimSweep tier: Free or Decrypt. Installations that held the retired Override tier may still report the value override, which grants the same access as Decrypt.
• verification timestamps
• OAuth tokens needed to refresh the Patreon check

The Patreon cache is stored locally by the desktop app. SimSweep does not receive or store your Patreon password.

When you activate a giveaway, trial, or staff key, SimSweep sends the key to the Worker for validation and stores the resulting local status. Do not enter a key unless SYVR gave it to you directly.

4. Scan and file data

SimSweep reads files in the Sims folders you configure. It parses .package, .ts4script, Tray, and optional Save data to classify files, find conflicts, detect broken references, identify duplicates, and build diagnostics.

SimSweep does not upload your actual .package, .ts4script, Tray, or Save files.

The current desktop app writes scan data locally. It may contact the Worker for supporting data such as malware signatures, risk tiers, known creators, and update checks.

The current desktop app does not include an extension bridge or a browser-driven download flow, and it does not submit content-source metadata to the Worker. Downloading creator mods inside SimSweep is a separate feature and does not send browsing or content-source data.

Older SimSweep versions (4.0.x) can still submit content-source metadata to a legacy service. The current app does not, and the legacy surface is scheduled for retirement.

5. Bug reports and diagnostics

Bug reports are voluntary. If you send one, SimSweep sends the text you entered plus the selected category, current app page, app version, operating system, and any screenshots you attached.

Bug reports go to Vital, our own analytics and error tracking service (see section 9), where we sort them and follow up. Depending on your version of SimSweep, a report goes straight to Vital, or to the Worker, which keeps a copy and passes one on to Vital. Every report, including one about a file flagged as malware, carries your install ID, so a deletion request reaches it too. A report includes an email address only when you choose to include your Patreon account with it.

If diagnostics are included, the snapshot can include:

• CPU, RAM, GPU, OS, and free-space information
• detected folder paths
• a capped Mods folder listing with relative file paths, file sizes, and modified times
• last scan summary fields such as total packages, health score, conflicts, threats, broken files, and scan date
• other app diagnostic state

If you have connected Patreon and choose to include it, a bug report also carries the email on your Patreon account, when available. Versions that send bug reports to the Worker also send your Patreon display name. Versions that send them straight to Vital don't send it anywhere. Including your Patreon account is optional, off until you turn it on (SimSweep asks once, and the report window shows a checkbox you can change at any time), shown in the report window before sending, and used only to match your report to you and respond to it. With the option off, the report's name and email fields are sent blank.

6. Crash reports

Automatic crash reporting is controlled in Settings > Diagnostics.

SimSweep watches for an unclean app exit. On the next launch it can show a crash banner, and that report is sent only if you choose to send it. When automatic crash reports are on (the default), SimSweep also sends a report on its own when the WebView2 display fails, the window freezes for 5 seconds or more (at most once an hour), a scan stops to protect memory or because it stalled, or SimSweep fails to start (a startup report sent this way has no log lines). When they are off, SimSweep sends none of these and deletes any that are waiting to be sent.

A crash report can include:

• crash kind, app version, timestamps, and deduplication hash
• recent simsweep.log lines
• scan phase and memory snapshot when a scan was active
• optional Mods file count
• operating system and platform details
• the panic message and code location (file and line) when SimSweep itself crashed, with any line that names one of your files or folders left out
• memory and graphics details, WebView2 version, whether The Sims 4 was running, and the size of your Mods library
• for WebView2 failures: the failure kind, exit code and reason, runtime versions, the recovery SimSweep tried, and the rollout group it belongs to
• for window freezes: how long the freeze lasted and which kind of operation was running
• recent app diagnostic events (event codes, not text)

Crash reports do not include your mod files. They are not tied to a SimSweep account because the current desktop app has no account system.

Crash reports go to Vital (see section 9), which groups them by kind and app version. Depending on your version, they go straight from SimSweep or through the Worker. Before a report leaves your computer, SimSweep removes email addresses, tokens, and user names in folder paths from it, and recent versions also leave out any line that names a file or folder.

7. Companion mod data

The companion mod is optional.

Current companion builds write local JSON event files under .simsweep/companion/events. SimSweep reads those files, shows live Game Link data, and removes processed events. SimSweep can write command files under .simsweep/companion/commands. Older companion builds can still use the localhost TCP socket on 127.0.0.1:27220.

Companion data can include:

• game mode, household, lot, sim, and session state
• health snapshots, exceptions, resets, and route failures
• performance metrics
• CAS outfit and worn CC data
• Build/Buy session events
• pack reports and mod footprint data

Game Link data is displayed locally in the desktop app. Session recap data can be stored locally.

8. Telemetry

SimSweep can send a daily heartbeat. It uses a generated install ID, not a SimSweep account. It can include the app version, platform, operating system version, processor architecture, your tier, your theme and whether you picked it, how paid access was last checked and how often it fell back to the older check, your automatic crash report setting, whether safe mode is on, your hardware acceleration setting, your graphics adapter and driver, the WebView2 runtime mode and version, which features you used, and which failures happened and how often. Depending on your version, SimSweep sends it straight to Vital (see section 9), or to the Worker, which keeps a copy and passes one on to Vital. We use it to count active installs and to see which versions, platforms, and features are in use and which errors happen.

SimSweep also sends usage events. These are short records of which screens you open and which actions you use, such as starting a scan, changing a setting, opening the bug report window, or seeing an error message. Each event has a name, a time, and a few fixed values, such as the screen name, the kind of error, or a count rounded into a range (for example, 11 to 100 conflicts). Usage events never include file names, folder paths, search text, or anything you typed. Each batch also carries the install ID, app version, platform, operating system version, a random ID for the current app session, and whether it came from a release build or a development build. Depending on your version, SimSweep sends them straight to Vital, or to the Worker, which holds them only until they reach Vital.

For heartbeats, usage events, and crash reports, Vital stores the install ID and the country of your connection (Cloudflare looks the country up from your IP address). Vital never stores your name, email address, or IP address.

You can turn the daily heartbeat off in Settings > Privacy. When it is off, the app stops optional heartbeat collection before it creates a durable ping or sends a request. The same setting turns off usage events. Heartbeats and usage events waiting to be sent are deleted when you turn it off.

The in-app Analytics page uses local snapshots and scan history.

The SimSweep website uses Vercel Web Analytics for page views and selected conversion events. When your browser does not send the Global Privacy Control signal, the website can record:

• standard page-view details, including the time, page path and route, referrer, filtered query values, approximate country, region, and city, browser and operating system details, device type, and analytics script version
• the landing page and standard UTM campaign values from the website address
• the platform, displayed app version, and page placement when you click an installer download
• the page placement and selected billing view when you click a Patreon join link

Campaign values are limited in length and stored in session storage for the current browser tab. The website does not add an email address, SimSweep account, or durable campaign identifier to these events. When your browser sends Global Privacy Control, the website does not load Vercel Web Analytics or store campaign attribution. Vercel explains its standard analytics fields in its Web Analytics privacy documentation.

9. Services we use

SimSweep can use these services:

SYVR Studios runs Vital itself. Heartbeats, usage events, crash reports, and bug reports reach it through Cloudflare, straight from SimSweep or through the Worker, depending on your version. They are stored in Germany, and nightly backups stay in Cloudflare R2 for 30 days.

If you leave SimSweep through a link to a creator site, Patreon, Discord, GitHub, or another third-party site, that site's own privacy policy applies.

10. Data retention

Local data stays on your computer until you clear it, uninstall the app, or delete the app data directory.

Data sent to SYVR is retained only as long as needed for the reason it was sent:

• bug reports and diagnostic snapshots are kept for support and debugging
• crash reports are kept for crash triage and deduplication
• Patreon verification data is kept as needed to verify paid access
• creator-submitted archives are kept while SimSweep hosts the mod and for the applicable withdrawal, complaint, unsafe-mod, or legal-hold period
• rights-attestation records for new creator uploads are kept as immutable evidence
• anonymous telemetry may be kept in aggregate form
• data in Vital: usage events for up to 13 months, crash details for up to 6 months, bug reports for up to 180 days, and summary counts (including the first day and app version each install ID was seen) until you ask us to delete them

Some records may be kept longer if required for security, abuse prevention, accounting, or legal compliance.

11. Your rights

You can contact us to request access, correction, export, or deletion of personal data we hold about you.

Because most SimSweep data is local, we may not have a server-side copy to delete. We can help identify where local app data is stored. A deletion request also covers the data we keep in Vital, and once we act on it, Vital refuses new data from that installation. An access or export request covers Vital too.

For privacy requests, contact:

• info@syvr.dev
• info@simsweep.com with the subject "Privacy Request"

We respond within the time required by applicable law.

12. Security

We use HTTPS for Worker and Vital traffic, local access caching for the desktop app, and access controls on backend services.

No system is perfectly secure. If we learn of a data breach that affects your personal data, we will notify you as required by law.

13. Children

SimSweep is not directed at children under 13.

On first launch, SimSweep asks the player to confirm that they are at least 13 years old before anything can be accepted. SimSweep saves only that confirmation outcome. No birth date is requested, stored, or transmitted. An installation blocked under an earlier age check stays blocked and sends nothing to SYVR. SYVR has an operator process to delete data tied to an identified under-13 request.

If you believe a child under 13 sent us personal data, contact us and we will delete it where required.

14. Changes

We may update this policy. If a change is material, we will notify users through the app, the website, or another reasonable channel.

15. Contact

SYVR Studios LLC

• Email: info@syvr.dev
• Website: syvr.dev