SimSweep privacy policy

Last updated: June 7, 2026

Effective date: June 7, 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
• 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, Decrypt, or Override
• 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 in-app download flow, and it does not submit content-source metadata to the Worker.

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.

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

The bug report form currently sends blank legacy name and email fields because the desktop app no longer has a SimSweep sign-in profile.

6. Crash reports

Automatic crash reporting is controlled in Settings > Diagnostics.

If enabled, SimSweep watches for an unclean app exit. On the next launch it can show a crash banner. The report is sent only if you choose to send it.

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

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.

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 heartbeat to the Worker. The heartbeat uses a generated install ID, not a SimSweep account. It can include app version, platform, OS version, architecture, event name, and selected metadata such as last scan peak memory.

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.

Product analytics calls in the current renderer are no-ops. The in-app Analytics page uses local snapshots and scan history.

9. Services we use

SimSweep can use these services:

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

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.

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 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 checks the date of birth on the device and saves only whether the player is eligible. If the date shows the player is under 13, SimSweep blocks that installation and sends nothing to SYVR. SimSweep never stores or transmits the birth date. 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