Website privacy notice

This website is a set of plain informational pages plus one contact form. It has no accounts, no comment sections, and no shop — so there is little to tell you, and we would rather tell you that plainly.

What the site’s own pages do not do

• The pages include no analytics, advertising, or tracking scripts.
• Outside the contact form, the pages set no cookies and contain no code that writes to your browser’s storage. (Your browser may cache pages and images in the ordinary way, under your browser’s own settings.)
• Outside the contact form, the pages load no third-party resources: every image, style, and script comes from this domain, and text is displayed using fonts already on your device.
• Outside the contact form, the pages collect nothing you type, because there is nothing to type into.

These statements are about the website’s code. Serving that code to you still involves web hosting, which processes visitor data of its own — described below.

The contact form

The contact page asks for an email address for our reply, a topic, and your message; adding your name is optional. We use exactly that information to reply to you and to resolve what you wrote about — nothing else. There is no mailing list, and the form has no attachments.

When you send the form, your message is delivered to us as an email to our business mailbox. From then on it is ordinary business correspondence: we keep business and support emails for future reference until we manually delete them. We have no fixed retention period or automatic deletion schedule. Correspondence travels through and is stored by the email providers involved — ours and yours — like any ordinary business mail, including those providers’ own storage and backups. The website itself does not keep a copy of your message after handing it to the mail server.

The contact page also uses three supporting mechanisms, described honestly below: a spam-protection check, a hidden spam trap, and short-lived security counters.

Spam protection (Cloudflare Turnstile)

The contact page — and only that page — embeds Cloudflare Turnstile, a third-party check that distinguishes people from automated abuse. Loading the contact page fetches Turnstile’s script from Cloudflare, and the check involves technical signals about your browser, device, and connection being sent to Cloudflare. What you type into the form’s fields is submitted to our server when you press Send; the check itself is about telling people apart from bots, not reading your message. Cloudflare processes the check under Cloudflare’s privacy policy and its Turnstile-specific privacy notice; because it is Cloudflare’s script, its exact behavior is governed by Cloudflare, not by us. Our server then confirms the check’s outcome with Cloudflare’s verification service before accepting your message; to do that, our server sends Cloudflare the check’s one-time result token together with the IP address your request reached our server from. The check requires JavaScript; every other part of this site works without it.

Hidden spam trap

The form also contains one extra field that is hidden from view and from screen readers and cannot be reached with the keyboard, so people leave it empty; automated spam tools often fill in every field. If a submission arrives with that field filled in, our server does not send the message or check it with Cloudflare, and the page says that the message was not sent. The trap field’s contents are not stored or logged.

The contact form’s cookie

The contact page sets one essential cookie, scoped to the contact form’s own path. It holds a random identifier that connects your visit to a short-lived session record kept privately on our server, which protects the form against cross-site forgery, confirms a sent message, and recognizes an accidental repeat of a message just sent. Our contact service uses it only for those protections, not to track you across pages or sites. It is a session cookie: it is meant to last only for the browsing session, though a browser that restores previous sessions can keep it longer — that is browser behavior we cannot override. The matching session record on our server becomes eligible for cleanup after two hours of inactivity; the cleanup itself is triggered now and then by later visits to the contact form, so a record can remain somewhat longer, and we do not promise an exact deletion moment. No other page on this site sets cookies.

Security counters

To keep the form from being flooded, our server keeps short-lived counters of form submission attempts and of messages sent through the form. Per-visitor counters use a keyed technical hash; the site-wide counters hold only totals. The server does not store your IP address or your message in any of these counters, and each counter is deleted automatically as its time window (an hour or a day) passes and new requests come in. This technical expiry is separate from how long we keep correspondence you actually send us, which is described above.

If something goes wrong while the form is being handled, our server also records a short diagnostic entry — a timestamp, the processing stage, and a brief error code. These entries never contain your name, email address, message text, or IP address.

Hosting and server logs

The site is served from NowGo’s hosting account at Hostinger. Hostinger documents that its web hosting automatically records each request in access logs — including the time, the visitor’s IP address, the page or file requested, the request’s size and response time, the browser and device type derived from the user-agent string, and the country derived from the IP address — and provides server-side visitor statistics built from that information. This happens on the hosting infrastructure as part of serving any page. The website’s own code adds no tracking on top of it. Hostinger also documents that, depending on hosting settings, its CDN security feature can run a brief browser check that sets a verification cookie; we have not confirmed whether any such feature is enabled for this site. We have not published a retention period for these logs because we have not confirmed one; Hostinger’s own policies govern how long its systems keep them.

Our apps are covered separately

This notice covers only the website. Our apps do not automatically send the records you keep in them to this website — see the NowGo Baby Tracker privacy policy for how the app itself handles information. If you choose to type or paste information from an app into the contact form, that submission is handled like any other message, as described above.

Changes and questions

If the website gains a feature that changes any of the above, this notice will be updated first, at this same address. Questions are welcome through the contact form.