Privacy

What Fieldstone collects

If you submit the website request form, Fieldstone receives the name, phone number, optional email address, organization and location details you choose to provide, your preferred contact method and time, a short issue description, and structured classifications such as service, urgency, project stage, delivery preference, environment size, and whether sensitive data or a production change may be involved. The site also records a small allow-listed first/last attribution record—such as direct, referral, or a named campaign—with the resulting request. It does not use advertising trackers or sell personal information.

How that information is used

Ian uses request information to evaluate, respond to, schedule, and deliver the Fieldstone service you asked about; maintain the operating record; prevent duplicate submissions and abuse; and meet legal, security, and accounting obligations. A random request token—never your contact details or issue text—is kept in browser session storage only until the form succeeds so a retry does not create duplicate work. For submitted requests, Stone may receive only bounded references and classifications needed for a configured workflow. Passwords, one-time codes, payment-card data, private keys, and other credentials should never be submitted through the public form or chat.

Ask Stone website chat

Stone is an AI assistant, not Ian. The optional Ask Stone page answers one question at a time and sends the question you type to a model provider. Fieldstone may keep a hash of the question, Stone's answer, and bounded usage and error receipts for service audit and abuse control. The chat does not look up customer records, remember earlier questions, book an appointment, create a service request, or authorize work. Use the separate request form if you want Ian to follow up. Do not put contact information, account numbers, credentials, payment details, or remote-access links in chat.

Private Telegram operator bot

Fieldstone's Telegram bot is a private operator channel for Ian—not a customer service channel. Telegram transports and stores bot messages in its cloud under Telegram's own terms and privacy practices. Do not send customer records, credentials, payment data, or other sensitive information through it.

After one-time pairing, Fieldstone accepts requests only from one paired private Telegram account and private chat. It keeps metadata-only replay and delivery receipts with numeric update, user, chat, and message identifiers, delivery status, and timestamps; during the short pairing window it separately stores a one-way hash of the pairing code. Conversation text is processed transiently and is not written to Telegram receipts or audit logs; when a paid provider is separately proved and activated, it receives only Fieldstone's existing code-owned prompt-safe projection. A Telegram message is never an approval for publishing, customer sends, spending, machine access, Git, or deployment.

Storage, providers, and retention

Fieldstone stores its front-office records on its hosted application and uses service providers only to run that application and the requested communication. Telegram is used only for the private operator bot. Records are retained while they are reasonably needed for service, security, audit, legal, and continuity purposes, then deleted or de-identified when no longer needed. Backups may retain deleted data until their normal protected rotation expires.

Your choices

You may ask Ian to correct or delete information that is not required for an active service, security record, legal obligation, or accounting record. To make a privacy request, use the request form on the Fieldstone home page and write “privacy request,” or email ian@fieldstoneiowa.com. Ian may need to verify that the request concerns your information.

Changes

If this policy changes materially, Fieldstone will update the effective date and publish the revised text at this same URL.