Privacy

Litecky Editing Services runs a small marketing site for an academic-editing practice. We collect the minimum needed to keep the site working and to reply to inquiries. We do not sell or share visitor information, and we don't run advertising on the site.

Cookies

The public site sets no cookies for visitors. The CMS editor at /admin uses session cookies for the editor login only; those cookies are not used by the public pages.

Analytics

The site uses two cookieless, privacy-first analytics tools so we can see what pages people read and whether anything is broken:

• Cloudflare Web Analytics — first-party, aggregate page-load metrics provided by our hosting platform. No cookies, no cross-site tracking, no personal identifiers.
• Plausible Analytics — an independently-hosted analytics product that records aggregate pageviews and (optionally) form-submission events. We proxy it through this site's own origin, so requests do not go to a third-party host from your browser. No cookies, no cross-site tracking, no personal identifiers. See Plausible's data policy for details.

Contact form

When you submit the contact form, the information you enter (name, email, the message body, and the dropdown selections) is sent to us so we can reply. We process the message through Resend (a transactional email provider) and it lands in our inbox at [email protected]. We do not store form submissions in a separate database; the message lives in our email until we delete it.

The form uses Cloudflare Turnstile, a challenge that helps us tell humans from bots without using tracking cookies or showing image puzzles. Turnstile evaluates a short signal from your browser; it does not identify you personally.

Error reports

When something on the site breaks, the browser may send a short error report to Sentry so we can fix it. We strip cookies, authorization headers, and email addresses from those reports before they are stored. Error reports are kept for a limited time and used only for debugging.

Editor login (CMS)

Editing site content requires signing in at /admin with GitHub. This login is only available to a small number of authorized accounts (currently Ahnie and Verlyn). The authentication uses PKCE-protected OAuth; we receive only the information GitHub returns for editor identity and repository access. Visitors never see or interact with this surface.

Questions or requests

Reach us at [email protected] for any privacy question, or to request deletion of a form submission we still hold.