Privacy
Your information is not the product.
Hammer On collects limited information to organize events, communicate with participants, review submissions, respond to concerns, and work with community partners. This page explains what we collect, why we use it, and the choices available to you.
What we collect
Organized by where it comes from, not by legal category. Nothing here is collected unless the corresponding form or system is actually used.
When someone RSVPs
- Email address
- Event or route
- Specific occurrence / date
- Selected run distance, where applicable
- Optional group-lead preference
- Required policy-acknowledgment record
- Optional updates consent
When someone submits an event or concern
- What you enter in the form
- Contact details you supply for follow-up
- Event context
- Optional supporting files, if enabled
When someone contacts the club or proposes a partnership
- Name
- Organization
- Role
- Website
- Proposed support or inquiry details
When someone uses the website
- Basic server logs
- Device and browser information
- Approximate location derived from an IP address, if applicable
- Consent-aware analytics events
- Cookies or local storage the site actually uses
No precise geolocation. No sensitive categories. Confirmed technical data only.
Why we use it
- Registering and managing event participation
- Sending required event information or operational changes
- Managing capacity and distance-group counts
- Reviewing proposed Service Miles and Field Work events
- Responding to safety or conduct concerns
- Reviewing partnership inquiries
- Maintaining site reliability and security
- Understanding aggregate site and event usage when permitted
- Sending optional club updates only after explicit consent
- Meeting legal, safety, and recordkeeping obligations
Specific purposes only — no catch-all “any business purpose” clause.
What others can see
- Public event surfaces show aggregate RSVP or attendance counts only.
- Names and email addresses never appear in a public attendee list.
- Submitted events are not public until approved.
- Concern reports are never published as event content.
- Partnership contacts are not public unless the partner separately approves attribution.
Photo practices are documented once the media-consent approach is approved.
Email, distance, acknowledgment version, timestamp, and occurrence — held privately for operations and never rendered on a public page.
RSVP counts and post-run attendance stay separate records.
Who helps us operate
Limited information may be processed by vendors we use for:
- Website hosting
- Database and form storage
- Email delivery
- Analytics
- Security
- File storage
- Payment processing, if sponsorship payments are later enabled
Providers are named here only once implementation choices are final.
Providers receive information only as needed to perform their service, under the applicable agreements.
Information may also be disclosed when reasonably necessary for safety, legal compliance, fraud prevention, protection of rights, or an organizational transaction.
Partners do not get the list
We do not sell personal information.
Sponsors, event hosts, and community partners may be acknowledged publicly, but sponsorship never provides access to participant email addresses or other personal information. Information goes to a host only when operationally necessary, disclosed on the event page, and permitted by the participant or applicable policy.
Event information is not marketing consent
Tied to the event you RSVP’d to: confirmation, meeting details, schedule or weather changes, cancellation.
Upcoming runs, Service Miles, Field Work, and occasional notes. Unchecked by default, separate from policy acceptance, unsubscribe in every send.
Not sent. If this ever changes, it will require its own separate, explicit consent — never bundled into an RSVP.
How long we keep information
| Category | Kept for | Why |
|---|---|---|
| Upcoming-event RSVP records | Until the event passes, then rolled into the attendance record | Operational |
| Completed-event attendance records | TBD — pending approval | Community history + safety review |
| Optional email consent records | Until withdrawn, plus a proof-of-consent window | Email compliance |
| Event submissions | TBD — pending approval | Review + scheduling |
| Partnership inquiries | TBD — pending approval | Relationship management |
| Concern reports | TBD — pending legal review | Safety, fairness, legal obligation |
| Policy acknowledgments | Kept with the RSVP record for the same period | Proof of acceptance |
| Technical logs | Short rolling window — TBD | Reliability + security |
| Backups | Rolling cycle — TBD | Disaster recovery |
No “forever” and no false precision — a period marked TBD is resolved internally before this page publishes.
How we protect it
Hammer On uses reasonable administrative, technical, and organizational safeguards appropriate to the information it maintains. No online system can guarantee absolute security.
Access controls, limited permissions, secure transport, vendor review, backups, and incident response are described here only once each is implemented.
Your choices
- Ask what information is associated with your email
- Correct inaccurate information
- Delete eligible information
- Withdraw optional communications consent
- Ask a privacy question
- Appeal or escalate a denied statutory request where the law requires it
We may need to confirm that you control the email address in question — usually by replying from it. No account is required, and we do not ask for government ID by default.
Children
Adult participation at launch.
We do not knowingly collect information from children under 13 without an approved parental-consent process. A specific minimum event age publishes only once leadership approves it; family or youth events would require their own guardian-consent and data-handling design.
Tell us the email involved and what you want done. That is the whole form.
State of residence is asked only where a statutory right depends on it. No account, no ID upload.
Questions and changes
Material changes are announced on this page with a new version and effective date, and where required we will notify participants directly before the change takes effect.