Privacy policy

Who this policy is from

The Goodrich Mill, LLC ("The Goodrich," "we," or "us"), owner and operator of the historic site at 106 N Main Street, Farmland, Indiana 47340, and the website at thegoodrichmill.com.

What you give us, and why

Loft reservations

Loft bookings on our Reserve page are handled by our reservation partner, Kairvio, embedded on the page. Kairvio collects the information needed to complete the reservation — typically your name, email, phone number, event date and details, and payment information — and shares the booking details with us so we can host you. We use this information only to confirm and carry out your reservation. Payment card information is handled by Kairvio's payment processor; we never see or store full card numbers. See Kairvio's privacy policy for their practices.

Donations and brick sponsorships

When you sponsor a brick or contribute to the Preservation Fund, payment is handled by Stripe. We never see or store your full payment card information. Stripe provides us with the name, email, amount, and — for brick sponsors — the dedication you want engraved. We use this information to fulfill the sponsorship and send confirmation. See Stripe's privacy policy for theirs.

Vendor and event-day rentals

When you sign up to vend at one of our events, the form on our Rent page collects your name, business name, contact details, the products or services you intend to bring, and your typed signature on the vendor agreement. The signed agreement is retained as a business record. Payment is handled by Stripe.

Email and direct contact

If you email thegoodrichmill@gmail.com or call us, we'll keep the record of that conversation to reply and, if relevant, continue the discussion. Outbound transactional emails (booking confirmations, donation receipts, vendor confirmations) are sent through Resend.

What the site records on its own

To operate the site, troubleshoot problems, and document misuse, the site records the following on every page load and form submission. This is first-party logging — no third-party advertising trackers, no cross-site profiling, no data sold to anyone.

One first-party cookie

We set a single first-party cookie, gm_sid, when you load any page on the site. It contains a randomly-generated identifier (no name, no email, no readable information) and is used to associate the page views from the same browser into a single "session" so we can tell whether the same visitor is loading multiple pages or many different visitors are loading one. It lasts up to 365 days and is set with the SameSite=Lax attribute. We use no third-party tracking cookies and no advertising trackers.

Page-visit log

For every page load, the site records: the page path, your IP address, your browser's user agent string, the referring URL (if any), the timestamp, your approximate geographic location (country, region, city, and timezone) as inferred by our hosting provider from your IP, the gm_sid session identifier, a per-visit short SHA-256 hash computed from a fixed set of browser-environment properties (preferred languages, screen and viewport size, network type, graphics renderer name as reported by your browser, locale, and whether automation indicators such as navigator.webdriver are present) that is used to detect when the same browser changes IP, and the relevant request headers (Accept-Language, the User-Agent Client Hints Sec-CH-UA-* headers, and the navigation-context Sec-Fetch-* headers) when sent by your browser. The session identifier is also embedded in the HTML of each page you load (as a comment near the bottom of the document) so that a saved or shared copy of a page retains its origin context. These records are accessible only to the site owner.

Form-submission log

Every submission to a public form endpoint on this site is captured in full, including any submissions that fail validation or never complete. The captured row includes the submission timestamp, your IP address, your country/region as inferred from your IP, the form path, the HTTP method and content type, the response status code, and the submitted payload itself (with secret-shaped fields such as passwords or tokens automatically removed). For the public-facing forms — brick sponsorships, Preservation Fund donations, and vendor sign-ups — this means the form contents (name, email, donation amount, engraving text, business details, typed signature, etc.) are stored alongside the request metadata.

Page-content snapshots

On a daily schedule, the site captures the HTML of every public page so that the published content of the site at any given date can be reconstructed if it is ever changed or removed. Snapshots are written only when a page's content has actually changed since the last capture. These snapshots do not include your visit data — they record what the site itself published, not who looked at it.

Security records

When a visit appears to come from a known abusive source, an automated probe, a honeypot endpoint, or a form whose hidden bot-detection field has been filled in, the event is logged as a security record. The site also maintains a tamper-evident hash chain of certain records so that any subsequent modification of those records would be detectable. Security records and the hash chain are retained as part of our operational evidence and are not subject to the retention windows below.

How long we keep things

• Loft, donation, brick-sponsorship, and vendor records — kept indefinitely as business and preservation records. The engravings themselves are permanent.
• Inquiry correspondence — kept for as long as it is useful to the conversation, and for a reasonable period afterward.
• Page-visit logs — up to 12 months, then automatically purged.
• Session correlations (gm_sid activity) — up to 12 months, then automatically purged.
• Form-submission payload bodies — up to 90 days. After 90 days the form contents are removed from the audit row; the metadata (timestamp, IP, path, status) is retained up to 24 months.
• Page-content snapshots — up to 24 months.
• Security records and the hash chain — retained indefinitely as part of our operational evidence.

Who we share information with

We don't sell, rent, or trade your information. We share it only with the service providers we use to operate the site:

• Netlify — site hosting
• Supabase — database hosting for the records described above
• Kairvio — loft reservation and booking platform
• Stripe — payment processing
• Resend — transactional email (booking confirmations, receipts, vendor confirmations)
• Google (Gmail) — our inbound email provider
• Law enforcement or courts — only if legally required, or to investigate, document, or report misuse of the site

Your choices

You can, at any time:

• Ask us what information we have about you
• Ask us to correct anything that's inaccurate
• Ask us to delete your inquiry records or your visit history
• Withdraw a pending booking request

For any of these, email thegoodrichmill@gmail.com. We'll respond within a reasonable time. If we can't fulfill a request (for example, tax or legal records we're required to keep, or security records preserved as evidence of misuse), we'll explain why.

Children

Our site is not directed to children under 13, and we do not knowingly collect information from children under 13. If you believe we have, please contact us and we'll delete it.

Changes to this policy

If we change how we handle information, we'll update this page and adjust the "Last updated" date at the top. Significant changes will be announced on the site.

Contact

Governing law

This policy is governed by the laws of the State of Indiana. Any dispute arising from it will be resolved in Randolph County, Indiana.