Data security and data handling
What this page covers
This page explains how WebHammers handles Files, datasets, Configurations, Runs, and user data during normal Tool use.
It is written from a user workflow perspective. It explains what to consider before importing a File, saving a Configuration, running a Tool, sharing a Team Configuration, or distributing an output File.
The short version
- 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 Field names from your data files.
- You should follow your organization's policies before using sensitive or regulated data.
What runs on your machine
When you run a Tool, WebHammers processes the selected File or dataset on your machine. In practical terms, this means the Tool applies the selected Configuration and Rules where you are using WebHammers, rather than sending the File somewhere else for Tool processing.
During normal Tool use, you choose or import a File, select a Configuration, run the Tool, review the result, and download or use the output that the Tool creates. The original source File should be kept separately when you need to preserve the unchanged data.
What WebHammers servers store
WebHammers servers store Configurations so they can be reused, shared, and managed. A Configuration saves the settings that tell a Tool how to process a File or dataset.
This section focuses on Configuration information users may see or manage during normal WebHammers workflows. It does not claim this is the only information WebHammers may store for account, billing, support, website, or other product operations.
A saved Configuration may include information such as:
- the Tool the Configuration belongs to
- the Configuration name and description
- Tool settings
- Rule settings
- selected Fields
- Field names from your File
- Configuration revision or history information
- Team ownership or sharing information, when the Configuration belongs to a Team
Do not put sensitive details in Configuration names, descriptions, Field names, or Rules unless that is appropriate under your organization's policies.
Files, datasets, and Configurations
| Item | What it means | What to check |
|---|---|---|
| File | The source File you import into WebHammers | Confirm the File is appropriate to use |
| Dataset | The data being reviewed, previewed, transformed, or processed during Tool use | Preview or review results when available |
| Configuration | Saved Tool settings and Rules | Review Field names before saving or sharing |
| Output File | The result produced after a Run or export | Check the output before sharing |
A File is the source file you provide, such as a CSV file from a reporting system or spreadsheet export.
A dataset is the data after it is loaded, previewed, transformed, or reviewed in WebHammers.
A Configuration is the saved setup for a Tool. It lets you reuse the same Tool settings and Rules with a similar File later.
Field names and Configuration metadata
Configurations may include Field names from your Files. Field names are often useful because they tell WebHammers which Fields the Rules should use.
Examples of Field names include:
Customer IDInvoice DateAmountRegionOrder Status
Field names may look harmless, but they can still reveal business meaning. For example, a Field named Termination Reason, Claim Status, or Restricted Account Flag may reveal more context than your organization wants shared broadly.
Before saving or sharing a Configuration, review the Field names, Rule values, Configuration name, and description.
During a Run
A Run applies the selected Tool, Configuration, and Rules to the selected File or dataset.
Before starting a Run, check that:
- the selected Configuration matches the task
- the File or dataset contains the expected Fields
- the Rules reflect the current business requirement
- the output will be appropriate for the intended audience
Where the Tool provides preview or review features, use them before relying on the output. Some Tools provide a preview before running, while others are best tested by running a small representative File first and reviewing the output.
After a Run completes, check the output File or result before using it for reporting, import, sharing, or another downstream process.
Team Configurations and sharing
Team Configurations are used when several people need access to the same saved Tool setup.
When you select a Team context, Tool pages can show Configurations for that Team. Team roles shown in WebHammers include Admin, Editor, Runner, and Viewer. Admin and Editor users can create and edit Team Configurations, Admin, Editor, and Runner users can run Team Configurations, and Viewer users can view Team Configurations but are not allowed to run them.
Before saving or using a Team Configuration, check that:
- the correct Team is selected
- the Configuration name and description are appropriate for the Team
- Field names and Rule settings are appropriate for Team visibility
- the Configuration reflects a workflow the Team is allowed to use
Avoid saving sensitive Field names or business-specific assumptions in shared Configurations unless that is appropriate for the Team.
Sensitive or regulated data
Follow your organization's rules before using sensitive, confidential, regulated, or restricted data in WebHammers.
Good practices include:
- confirm that the File is appropriate to use in WebHammers
- use only the Fields needed for the task
- review Field names before saving a Configuration
- review Field names before sharing a Configuration with a Team
- preview results before running or exporting when the Tool supports preview
- review output Files before distributing them
- avoid using production data in a way that violates your organization's policies
If you are not sure whether a File is appropriate to use, ask your WebHammers administrator, manager, data owner, privacy contact, security contact, or other internal support contact before proceeding.
What this page does not claim
This page explains WebHammers data handling from a user workflow perspective. It is not a legal, compliance, privacy, or security promise.
This page does not make legal, privacy, security, or regulatory compliance claims. It also does not replace your organization's data handling, privacy, security, contractual, or compliance requirements.
If your organization has specific requirements for sensitive, confidential, regulated, or restricted data, review those requirements before using sensitive data.
Practical checklist
- Confirm the File is appropriate to use in WebHammers.
- Review Field names before saving a Configuration.
- Review Configuration names, descriptions, and Rule settings before sharing.
- Preview results before running or exporting when available.
- Check output Files before sharing them.
- Use Team Configurations only when the settings are appropriate for the Team.
- Follow your organization's policies for sensitive or regulated data.
Common questions
Does WebHammers upload my File for Tool processing?
WebHammers jobs run on your machine. Your data stays on your machine during Tool processing.
This statement applies to Tool processing. It does not replace your organization's review of account, billing, support, website, or other non-Tool interactions.
What information is saved in a Configuration?
A Configuration saves Tool settings and Rules so the Tool can be reused. A Configuration may include the Configuration name, description, selected Fields, Field names, Rule settings, output settings, revision information, and Team sharing information when the Configuration belongs to a Team.
Can Field names be saved?
Yes. A Configuration may include Field names from your data files. Review Field names before saving or sharing a Configuration, especially if the Field names reveal sensitive business meaning.
Should I use sensitive data in WebHammers?
Only use sensitive, confidential, regulated, or restricted data when that use follows your organization's policies. WebHammers documentation does not replace your internal data handling, privacy, security, or compliance requirements.
What should I check before sharing a Configuration with my Team?
Check that the correct Team is selected, the name and description are appropriate, the Field names are appropriate for Team visibility, and the Rules reflect a workflow the Team is allowed to use.
What should I review before exporting results?
Review representative Records, confirm the intended Configuration was used, check whether sensitive Fields are included, and confirm the output File is appropriate for the next person or system that will receive it.