Security overview
WebHammers supports careful data preparation by keeping workflows focused, reviewable, and easy to repeat.
Data stays local during processing
WebHammers jobs run on your machine. Your data stays on your machine during Tool processing. WebHammers servers store Configurations so they can be reused, shared, and managed. A Configuration may include information such as the Field names from your data files.
For a practical explanation of Files, datasets, Configurations, Runs, Field names, and Team sharing, see Data security and data handling.
Account access
WebHammers uses email-based access codes for sign-in. A user enters their email address, receives a code, and uses that code to access their account.
Each person who needs access should use their own account so access can be managed more clearly. WebHammers can show trial, monthly, and annual subscription access states on the Account page.
Team access and shared Configurations
Teams can share Tool Configurations so users do not need to rebuild the same workflow by hand. Shared Configurations help teams use a consistent, reviewed approach for recurring work.
Configurations are versioned. When a Configuration changes, earlier versions remain available so teams can recover or compare previous approaches when needed.
Careful data workflows
WebHammers supports careful handling by breaking data work into purpose-built Tools. Instead of making many manual spreadsheet edits, users can complete focused Tool Runs with clearer intent and more predictable results.
Examples include:
- Filterer to keep only the Records needed for a task
- Validator to check values before data moves downstream
- Cleaner and Mapper to standardize data in repeatable ways
- Deduplicator to reduce accidental duplicate records
- Joiner and Splitter to prepare structured outputs with less manual handling
- Data Profiler and Statistics to review quality, completeness, and numeric patterns
- Obfuscator to mask, randomize, or replace sensitive values before sharing data more broadly
Sensitive data handling
Users should treat source files and generated outputs as sensitive whenever they contain personal, customer, financial, operational, or confidential information.
When sensitive values do not need to be visible, use Obfuscator or remove unnecessary Fields before sharing outputs. When only part of a File is needed, use Filterer or Splitter to limit the data included in downstream Files.
Shared responsibility
WebHammers provides tools and workflow controls that support careful data work, but users and organizations still play an important role.
Good user practices include:
- using only the data needed for the Run
- confirming that you are authorized to work with the data
- reviewing Configurations before important Runs
- checking outputs before sharing or uploading them elsewhere
- limiting distribution of sensitive outputs
- using each person's own account rather than sharing access codes or accounts
- removing, filtering, or obfuscating sensitive Fields when broader access is not appropriate