Privacy Policy for Hammer

Effective date: February 13, 2026

This Privacy Policy describes how Hammer processes personal data when you use the Hammer desktop app. Hammer is a native macOS IDE for ABAP development.

Beta note: In beta builds, crash reporting is always enabled. In non-beta builds, crash reporting can be turned off in onboarding and in Settings.

1. What Hammer Sends and Why

Hammer primarily communicates with the SAP system you configure. Requests are made directly from your Mac to that SAP system for IDE features like source editing, activation, transport actions, and data browsing.

In short: Hammer sends what is needed to complete the action you choose inside the app.

Hammer does not proxy these SAP requests through Schärpf-operated servers.

2. Crash Reporting and Diagnostics (Sentry)

Hammer uses Sentry for crash diagnostics. If telemetry is enabled, Sentry can receive technical diagnostics such as crash stack traces, app/build version, OS version, and runtime context.

Hammer is configured to avoid sending personally identifying information by default.
Crash diagnostics are processed in Sentry's European region.

3. Manual Issue Reports

If you choose "Report an Issue", Hammer sends your report through Sentry feedback.

Title and description you enter.
Optional contact email.
Optional image attachments you select.
App context string: app version/build, macOS version, and hardware model.

If telemetry is disabled (where that option is available), manual issue submission from inside Hammer is also disabled.

4. Update Checks

Hammer uses Sparkle for updates. The app checks the update feed at:

https://schaerpf.com/Hammer/releases/appcast.xml

Like any web request, update checks can include standard network metadata (for example IP address and user agent) handled by the hosting infrastructure.

5. Data Stored Locally on Your Mac

Credentials and system settings are stored in the macOS Keychain.
Preferences in UserDefaults (for example onboarding state, telemetry level, and UI settings).
Saved Data Browser searches in local app support storage (saved_searches.json).
Optional local log output for troubleshooting.

6. What Hammer Does Not Do

No ad tracking.
No sale of personal data.
No separate marketing analytics SDK in the desktop app.
No account requirement to use core app features.

7. Third Parties

Hammer currently relies on:

Sentry for crash/diagnostic reporting and manual issue feedback.
Sparkle and schaerpf.com (which hosts Hammer update files and the appcast feed) for app updates.

If you click external links (for example feature requests or external documentation), those third-party websites process data under their own policies.

8. Retention

Local data remains on your device until you change or remove it. Crash diagnostics are retained for 30 days and then deleted.

9. International Processing

Your SAP data is processed by the SAP system you connect to. Diagnostic data sent to Sentry is processed by Sentry under their data processing terms and regional setup.

10. Your Controls

In non-beta builds, you can disable telemetry in onboarding or Settings.
You can choose not to send manual issue reports, not to provide an email, and not to attach files.
You can remove configured systems and update local app preferences.

11. Changes to This Policy

This policy may be updated when Hammer functionality changes. The effective date above indicates the current version.

12. Contact

For privacy questions, use the contact details in the legal notice (Impressum): /impressum.html