Useful measurement. No advertising profile.

Simple site measurement

The public Worker may count the page path and a small, fixed list of actions, such as opening the booking example, starting the 2 a.m. website check, selecting a module, or opening a contact option. Those events go to Cloudflare Workers Analytics Engine with the site name and a short allowlisted detail. Cloudflare keeps Analytics Engine data for three months.

This event dataset does not contain names, email addresses, form contents, precise locations, IP addresses, connection estimates, 2 a.m. check answers or scores, advertising identifiers, or a visitor ID. TowCraft does not combine the counts into a profile of one person.

Cloudflare edge and security data

Like other sites delivered through Cloudflare, each request reaches Cloudflare's network first. Cloudflare processes the IP address, requested address, date and time, browser request headers, cookie header when present, and technical connection information needed to deliver and protect the site. Cloudflare may derive coarse network or location information, such as country, metro area, network provider, protocol, or data center. TowCraft does not copy that request information into its inquiry record or custom event dataset.

Cloudflare also adds Network Error Logging instructions to site responses. A supporting browser may send Cloudflare a report when a network request fails. A report can include the affected address, request method, timing, failure type, protocol, status, referrer, and network or server details. Cloudflare says it uses the reporting IP to derive the network's ASN, country, and metro area, then drops the IP after processing. The current instruction lasts up to seven days in the browser and does not ask the browser to report successful requests.

Turnstile and rate limits

The private inquiry form loads Cloudflare Turnstile only when the visitor gets near or focuses the form. Turnstile uses browser and device signals, small challenges, the single-use verification token, and the connecting IP address to distinguish a person from automated abuse. TowCraft sends the IP address to Cloudflare's verification service but does not save it with the inquiry.

The public Worker also uses the connecting IP as temporary rate-limit keys, configured for five inquiry attempts or 60 event submissions per 60-second window at a Cloudflare location. Cloudflare's distributed counters can be permissive, so these are abuse controls rather than exact accounting. Neither key is written to the inquiry or Analytics Engine. After Turnstile, Cory Studio also uses one-hour, purpose-keyed counters derived from the inquiry email address and a service-wide key to limit repeated delivery. D1 stores only the keyed bucket value, scope, count, and timestamps—not the email address in the counter—and scheduled maintenance removes expired buckets. The Turnstile token expires after five minutes and cannot be reused. Cloudflare handles its provider-side security records under its own privacy and retention terms, described in its Turnstile Privacy Addendum.

Weak connections and page choice

A browser may tell TowCraft that Data Saver is on or that the connection is estimated as 2G-class. TowCraft may then open the smaller low-data page. The site does not download a speed-test file, save the connection estimate, or add it to visitor reports. Because an estimate can be wrong, the low-data page always links to the full site.

If a visitor chooses the full or low-data version, an HTTP-only cookie remembers only that choice for the browser session. It is not used to identify the visitor, advertise, or follow anyone to another site. Choosing “Let TowCraft choose” removes it.

Private site-review requests

When a visitor sends the form, TowCraft receives the name, company, email address, current website if supplied, selected goal and modules, notes, submission time, and the recorded inquiry-consent version. The unchecked confirmation permits TowCraft to answer that request; it is not permission for a mailing list or automated campaign.

The accepted request is stored in Cory Studio, Cory's private owner-only workbench on Cloudflare. Studio then attempts a fixed-destination notification to Cory's verified Gmail inbox. The form sends no automatic reply. TowCraft does not show success until Studio confirms that the private record exists. If delivery fails before then, the entries remain in the browser so the visitor can retry, open an email draft, or copy the message into webmail.

Direct email

Email sent to Cory, hello, or support at towingwebcrew.com passes through Cloudflare Email Routing. Cory Studio privately archives the raw message and searchable mail details on Cloudflare before forwarding the original message to Cory's verified Gmail inbox. This means a direct message can exist in both Cory Studio and Gmail. The sender's email provider also processes the message. Replies are personal, single-recipient correspondence rather than an automated sequence.

Please do not send sensitive records

Do not put passwords, access tokens, private keys, payment-card or bank details, government identification, health information, employee records, dispatch or customer lists, accident records, or other sensitive documents in the form or an ordinary email. A website address and a short description of the problem are enough to begin. Cory will arrange a safer transfer method if later work truly requires private material.

How information is used and shared

TowCraft uses submitted information to answer the request, prepare or deliver requested work, maintain a client relationship, secure the service, keep necessary business records, and comply with law. Information is available to Cory and to service providers only as needed for those jobs. The current public path uses Cloudflare for site delivery, security, storage, routing, and sending, and Google for Cory's Gmail inbox. TowCraft may also disclose information when legally required or when reasonably necessary to protect a person, the service, or legal rights. It is not sold or rented.

Retention schedule

The display-choice cookie lasts for the browser session; the public IP rate keys last for their 60-second limits; a Turnstile token lasts five minutes; and Cloudflare keeps the custom aggregate events in Analytics Engine for three months. Those are technical or provider-enforced windows.

TowCraft's internal manual review targets are 12 months after the last meaningful exchange for a non-client inquiry or direct email, 90 days for a routine TowCraft diagnostic record, two years after closure for an incident case, and three years after closure for a privacy-request record. These are review targets, not automatic deletion promises: Cory Studio does not currently age-delete inquiries, direct mail, or client records, and its Mail Trash control is reversible organization rather than erasure.

Active-client records are reviewed when work closes and at least yearly after that. The target for routine project correspondence and duplicate working copies is deletion within two years after completion. Agreements, invoices, tax support, ownership/delivery evidence, unresolved requests, disputes, incidents, and legal holds follow the specific duty that applies rather than one blanket period. A minimal no-contact record may remain while TowCraft sends business email so an opt-out is not accidentally reversed.

Cory Studio recovery sets are created and retired manually; TowCraft does not claim a verified automatic backup deletion date. When a live record is deleted, the request is kept open for the backup review and must be applied again if an older copy is restored. Backup access is for recovery, not ordinary use. Any extension keeps only what the documented tax, contract, security, dispute, or legal reason requires.

After Cory Studio permanently erases a message or inquiry, it keeps one minimal erasure audit and small, purpose-separated one-way hashes of the random submission, raw-message, or send reference. The audit records the opaque record ID, time and outcome, Cory's operator identity, protected request fingerprints, and handling facts such as the source, storage result, legal-hold check, and Gmail/backup disposition—but no message, attachment, or visitor/client contact details. The replay suppressors contain no name, email address, message, attachment, raw storage key, or readable reference and cannot restore the erased content. They are retained without an automatic expiry while needed to stop the exact erased item from being recreated, forwarded, notified, or sent again.

Access, correction, deletion, or privacy questions

Email hello@towingwebcrew.com with the subject “Privacy request” to ask what TowCraft has about you, correct it, request a usable copy, or ask for deletion. Say which email address or inquiry the request concerns. Cory normally verifies the request through the address connected to the record; do not email an identity document. If stronger verification is genuinely needed, Cory will arrange a safer method.

TowCraft will search the relevant Cory Studio, private raw-email archive, Gmail, client, and backup records; complete the request where reasonably possible; and explain any information that must remain under a legal, security, contractual, tax, or no-contact exception. Moving Studio mail to Trash is only a recoverable first step. A separate owner-confirmed erasure can remove one form inquiry from Studio's live database or one routed email from the live database and raw-email store after Cory checks holds, Gmail, and known backups. Gmail removal is manual, and an encrypted recovery copy may retain a residual record until that copy is retired; an older restored copy must have the deletion applied again before use. Cory will not report deletion complete until the relevant live systems and known backup exception have been checked. Privacy-request evidence is minimized and manually reviewed under the three-year internal target above.

If a browser later retries the exact random reference for an erased form inquiry, Studio does not recreate the erased record or send another notification. The form reports that nothing was stored again and asks the visitor to make an explicit new attempt, which creates a fresh random reference.

Do Not Track and Global Privacy Control

TowCraft's default behavior already matches the privacy choice expressed by Do Not Track and Global Privacy Control: the site has no cross-site advertising, data sale or sharing for targeted advertising, or third-party behavioral profile to turn off. A signal therefore does not need to change a separate setting. Limited first-party measurement, Cloudflare delivery and security, and a form the visitor chooses to send still work as described above.

Other websites

A link to client work or another external resource opens a separate website. That site's privacy information applies after the visitor leaves TowCraft.

Material changes

The date below changes whenever this notice changes. Before or when a material change takes effect, TowCraft will place a clear notice on this page and, when practical and relevant to information already submitted, on the main site. If a change would materially broaden how an existing inquiry or client record is used, Cory will contact the affected person when appropriate and request permission when required. TowCraft will not create a mailing list just to announce routine wording or formatting changes.

Related information

Read TowCraft's accessibility statement or use the low-data privacy page. Provider handling is described in the Cloudflare privacy policy and Google privacy policy. Questions can go to hello@towingwebcrew.com.