Scree Privacy Policy

Updated 3 November 2026. This notice describes the forthcoming consent-first Mac App Store release of Scree, the macOS Disk Space Analyzer from Forethought Studio SASU. Our legal notice identifies the publisher and its registered address. For privacy questions or requests, use our contact page.

The short version

File scanning and duplicate comparison happen on your Mac. Scree does not automatically upload your scan tree or file contents. Crash and hang reporting through Sentry starts only after you choose to share reports and includes an installation identifier. Declining leaves every Scree feature available. Feedback is sent only when you click Send; its optional scan diagnostics can contain folder paths. These reports are not anonymous.

Local scans and permissions

Scree reads the disk or folder you choose and builds a map of allocated space. Saved scan snapshots, file and folder metadata, and bookmarks that remember your selected folders are stored locally. The App Store app uses macOS permission grants for the folders you choose. Full Disk Access can allow reading additional protected locations, but does not replace those grants or override every system restriction.

Scree has no app account, advertising or advertising identifier. Its configured automatic reporting is for diagnosing crashes and hangs, rather than product usage analytics. Scanning and duplicate comparison do not require you to send feedback or keep crash reporting enabled.

Paid purchase through Apple

Scree will be a paid download: USD 4.99 for a one-time lifetime purchase, with every feature included and no in-app purchases, trial or subscription. Apple processes the App Store payment. Forethought Studio does not receive your payment card details from that purchase. Apple handles refund requests; the developer cannot issue refunds. Apple's handling of purchase and payment information is covered by Apple's privacy information. The app uses Apple's Standard EULA.

Automatic crash and hang reports

On first launch, choose Share crash reports or Don't share. Sentry does not start, create its installation identifier or send reports before you choose to share. Your consent is the basis for this optional automatic reporting. Closing the prompt without choosing leaves reporting off. A preference saved by an older version does not replace this choice.

When a reporting endpoint is configured and reporting is enabled, Scree uses Sentry Cocoa to capture fatal crashes and uncaught exceptions, plus hangs while the app is active. Reports help diagnose and fix failures. A crash report can be cached on your Mac and delivered on a later launch.

Reports can contain:

• Event identifiers, timestamps, severity, app version and build, release and environment, and SDK details.
• Exception text and types, thread names and stack traces, stack-frame details and loaded software image paths.
• macOS version, build and kernel, architecture, hardware model, memory and runtime state, locale and time zone when available, and app activity context.
• A persisted random Sentry installation identifier and an app/device hash. Reports can be linked to the same installation across launches even though Scree has no account.
• Approximate country, city and region derived by Sentry from the connection IP address. This location can remain with the report even when the IP-address field is empty.
• Diagnostic breadcrumbs, message parameters, tags and extra diagnostic fields when present.

The app disables automatic performance tracing, session tracking, metrics, SDK logs, MetricKit, network and file instrumentation, failed-request capture and swizzling. It does not set an email address or advertising identifier for Sentry. The receiving service necessarily processes a connection IP address; disabling default personal-information fields in the SDK does not establish that no IP address is processed.

To withdraw consent, open Scree > Settings or Help > Send Feedback and uncheck Automatically send crash and hang reports. Scree saves the choice, cancels pending reporting requests and shuts down the reporter. Reports a service has already received cannot be recalled by this switch. Checking it again gives consent and restarts reporting when an endpoint is configured. This choice does not require sending a feedback message. Turning reporting off does not erase reports already delivered or the reporter's local cache. Cached reports may be delivered if you enable reporting again.

Path redaction and its limits

Before sending a Sentry event, Scree replaces the account's home-directory prefix with ~ in the event's covered message, exception, thread, stack-frame, loaded-image, breadcrumb, tag, fingerprint and extra fields. Remaining path components, including file and folder names, can survive. Arbitrary SDK context and user fields are not recursively redacted, and the installation identifier is retained. This is not anonymization.

Feedback you choose to send

Opening Help > Send Feedback does not send a message. Clicking Send submits your message, the payload format version, app version and build, macOS version and locale to our feedback service. An email address is optional and is included only if you enter one, so that we can reply. A build without a configured feedback endpoint disables sending; you can use our contact page instead.

The attachment checkbox starts checked when a scan is available. If you leave it checked, feedback also includes a scan summary and debug block: scanned folder path and status, app build date, unreadable-folder count and up to 25 sampled unreadable folder paths, aggregate space totals when available, display threshold and view area. These fields are not a full file inventory or file-content attachment. Uncheck the attachment box to omit both scan fields.

The feedback builder replaces home-directory prefixes with ~ in the message, email, environment strings and attached diagnostics. Remaining path components and any other identifying details you write can still be sent. An email address is stored with the message and attached diagnostics when provided. The service also records a receipt time, record identifier and source connection IP address; the address seen by the service can depend on its proxy configuration.

Feedback is used for support and to investigate reported problems. Received feedback can be copied into our private issue queue for triage. Do not include passwords, payment details or file contents that you do not want to share.

When you choose Send, you consent to our processing of the message and the disclosed diagnostic fields for these purposes. You can withdraw this consent through our contact page. Sending feedback, supplying an email address and attaching scan diagnostics are optional; every Scree feature remains available without them.

Recipients, storage and deletion

Sentry (Functional Software, Inc.) receives automatic crash and hang reports as our processor under our accepted Data Processing Addendum. It must follow our lawful instructions, maintain confidentiality and security, assist with privacy rights and deletion, and require equivalent protection from its subprocessors. These are binding protections consistent with this notice's handling of personal diagnostic data and applicable data-protection requirements. Our feedback service receives the messages and diagnostics you submit. These services and their network providers process the technical connection data needed to receive requests. Apple separately processes your App Store transaction.

Our Sentry organization is configured for EU data storage. This does not mean that all processing stays in the EU: Sentry and its subprocessors may process data in the United States and other countries. The accepted DPA provides for the EU-U.S. Data Privacy Framework and, where that framework does not apply, the European Commission's Standard Contractual Clauses. You can read the DPA and Sentry's subprocessor list, or contact us for a copy of the applicable safeguards.

Local scan snapshots and folder bookmarks remain on your Mac. Turning off reporting stops the reporter in the app; it does not erase server records or copies already made for issue investigation. On 3 November 2026, our Sentry subscription page showed the Developer plan. Its documented retention for new error reports is 30 days. Retention is assigned when a report is received; older reports keep their original period after plan changes. Sentry's security policy states that individual events are deleted after their applicable retention period and its backups are deleted 90 days after creation. Those Sentry backups are separate from our feedback backups and private issue copies described below.

Our feedback service's daily cleanup deletes feedback records older than 180 days regardless of the number of records. Configuration can shorten this age window but cannot extend it. This is an age cutoff applied by a scheduled job, rather than a promise that deletion occurs at an exact time; failed jobs can delay cleanup. Associated receipt records are deleted with the expired feedback.

Backups, service logs and private issue-queue copies have separate lifecycles and are not covered by that feedback-database age cutoff. Feedback database backups rotate through up to seven daily and four weekly copies; there is no separate age cap for this database's backup files. Issue copies support investigation and recording the resolution. We review the personal information in issue copies when an investigation is resolved and when handling a privacy request, removing information no longer needed unless a legal obligation or unresolved legal claim requires it. Closing a task does not automatically erase its historical copies. There is no uniform fixed age limit stated here for service logs. We check relevant live records, issue copies and identifying log entries when handling a deletion request; older backups remain subject to the rotation described above.

To request access, correction or deletion of personal data associated with a report, use our contact page. Give the app version and build, approximate report time and whether it was a crash, hang or feedback message. An email address supplied with feedback can help locate that message; automatic crash reports do not include a reply email. If this is not enough, we request only the additional information needed to locate the records and confirm your right to act. Do not send another scan, passwords, full file contents or identity documents unless a proportionate check specifically requires them. The local reporting switch does not send us a deletion request. If you contact us to withdraw consent for stored personal data, we also assess erasure where consent was its only legal basis. We process the information needed to handle a data-rights request to meet our applicable legal obligations.

Your choices and rights

You can turn off automatic reporting, leave your feedback email blank, omit the scan attachment, or choose not to send feedback. Depending on applicable law and the circumstances, you may have rights to access, correct, erase or restrict processing of your personal data, object to processing, and receive a portable copy. You can also complain to your data protection authority. Contact us through the studio contact page about these rights.

This website and policy updates

This app notice does not describe all processing on forethought-studio.com. The studio website uses shared theme scripts and website analytics. See the website privacy policy for website visits and contact-form processing. Changes to this app notice will be posted here with an updated date.

The language picker saves only your language choice in this browser. Explicit language links always take priority. Without browser storage, the links still work, but your choice is not remembered on the default page.