Privacy

This site sets no cookies and calls nobody

Every page loads one stylesheet and one script, and the timer page loads two more, the pattern model and the timer itself. All of them come from this domain. No web fonts, no tag manager, no analytics, no advertising pixel, no chat widget. Nothing here sets a cookie, because nothing here needs one.

You do not have to take that on trust. Every page ships a Content-Security-Policy header beginning `default-src 'self'`, so your own browser refuses to load a script, an image or a connection from any other host. If we broke the rule by accident, the request would be blocked before it left your device. The enforcement sits on your side, not ours.

The timer stays in your browser

Every number on the contraction timer is worked out inside the page, with no server call anywhere in the timing. Your log is saved in that browser's local storage, on that one device. Local storage is not a cookie. It never rides along with a request, so it does not travel to us or to anyone else. It exists so that reloading the page at three in the morning does not wipe forty minutes of work. Clear everything removes it. We keep no copy, because we never had one.

The email form, and what it writes down

Put an address into the form and this is the whole record created.

• The address, because it is what the one email goes to.
• Which page you came from, and the date and time in UTC.
• A truncated hash of your IP, sha256 cut to sixteen characters. The IP itself is never written down. The hash lets the form count requests from one place, not work out who you are.
• The user agent your browser sends, cut to 180 characters. Every site you open receives that line. It names a browser and a system, not a person.
• Two flags about the row itself, whether you asked for your log by email and whether the address was already on the list.
• Nothing about your pregnancy. No due date, no week count, no contraction. The form never asks and there is no field for it.

That record goes into a plain CSV outside the web root, so no URL points at it, with file permissions set to 600. The form refuses more than twelve submissions an hour from one hashed IP, and carries a hidden field a person never sees and an automated script fills in. The list is never sold, shared or handed to a marketing platform.

Send my log to me

The timer can email your log to you, because reading numbers off a phone with a contraction going is hard. The text is posted once, used to compose one plain text email, and then discarded. It is not written to the CSV, not to a file and not to a server log. The only address it is ever sent to is the one you typed in. Skip the box and nothing leaves the page at all.

The iPhone app

Wavesong is not on the App Store yet, so this is what it is built to do. Sessions, contractions, due date and notes live on your iPhone and in your own private iCloud, under your Apple Account. There is no Wavesong account, no login and no Wavesong server holding any of it. We cannot read your sessions because there is nowhere for us to read them from. Delete the app and the copy on the device goes with it.

Analytics and attribution in the app

Being straight about this matters more than looking clean. The app will ship with third party SDKs: Firebase for analytics and crash reporting, and Meta, Google, TikTok and Apple's own AdServices for attribution, so we can tell which advertising actually brings people in.

The line they are held to is a design rule, not a preference. They record that something happened, never what you logged. An event can say a session started, a paywall was shown, a purchase went through. No event carries a week of gestation, a due date, a phase of the pattern, an interval or a duration. There is no field for any of it.

They do collect what advertising SDKs collect: a device identifier, app version, country, which campaign the install came from. Turn down App Tracking Transparency and the advertising identifier is simply unavailable, and we do not look for a way around it. The App Store privacy labels will say what this page says.

Getting your email removed

Write to support@digitalnafta.com and the row is deleted. A person answers within two business days. No reason needed and no form to fill in. The same address works if you want to know what we hold on you, which for almost everyone is one line in a CSV. There is nothing else to export, because there is nothing else.

Children

Wavesong is for adults in the last weeks of pregnancy. It is not directed at anyone under 13, and we do not knowingly collect anything from a child under 13. If you believe a child has sent us an address, write to support@digitalnafta.com and it is deleted.

When this changes

Last updated 24 August 2026. If what gets stored, where it lives or who can read it changes, the date changes with it and the change is written out here rather than folded in quietly. If the App Store privacy labels ever disagree with this page, one of the two is wrong and we want to hear about it.

Questions people actually ask us

The rest of the legal shelf

• Terms of use. What Wavesong promises, and what it refuses to claim.
• Support. One address, answered by a person.
• The contraction timer. Free, in your browser, nothing uploaded.
• Pricing, in a plain file. The price in writing.

Last checked 2026-08-24