Verify it yourself

Don't trust us. Check.

Every period app says it respects your privacy. That's a claim, and claims are cheap. This page shows you how to confirm ours in about ten minutes, using tools already built into your browser — no technical background needed.

Last updated 20 August 2026 · Applies to ancientcycle.app · If anything on this page stops being true, it is a bug and we want to hear about it: hello@ancientcycle.app

The claim, stated precisely

Vague promises are unfalsifiable, so here is ours in a form you can actually test:

Your symptoms, moods, energy levels and notes are written to storage inside your own browser and are never transmitted to our servers. We do not receive them, we cannot read them, and there is no column in our database where they could be stored.

What we do hold is listed further down, in full. A privacy page that only tells you the good half isn't worth reading.

Check one — watch the network while you log

This is the test that matters. If we were quietly sending your symptoms anywhere, it would appear here.

  1. Step 1

    On a desktop browser, open the app and press F12 (or right-click → Inspect). Choose the Network tab.

  2. Step 2

    Click Fetch/XHR to filter out images and stylesheets, then press the 🚫 icon to clear the list.

  3. Step 3

    Now log a day. Tick some symptoms, choose a mood, set your energy, type a note. Save it.

  4. Step 4

    Look at the Network list. It should stay empty. No request is made, because the data never leaves the page.

For contrast, log a period start date instead. You'll see a request to Supabase appear immediately — because that one genuinely is saved to our server, and we're not going to pretend otherwise.

Check two — find the data on your own machine

If it isn't on our server, it has to be somewhere. It's here:

  1. In the same developer tools, open the Application tab (Firefox calls it Storage).
  2. In the sidebar, expand IndexedDB.
  3. Open tac-daily-logentries.

There is everything you've logged, sitting in your own browser, keyed by date. You can read it, and so can anyone with your unlocked device — which is the honest trade-off of local storage, and we'd rather you understand it than be surprised by it.

Check three — prove it isn't syncing

Two tests, either of which would expose a hidden sync:

  • Sign in on a different browser or device. Your period dates and charts follow you. Your symptoms and notes do not — they stay on the machine where you typed them.
  • Clear site data (Application → Storage → Clear site data). Your daily log is gone permanently. If we had a copy, it would come back. It doesn't.
This is why the app offers a backup file. Local-only storage means a cleared browser is a lost log, and we'd rather hand you a file you control than quietly keep a copy for your convenience.

What we actually store on our servers

Complete list. Every table, in plain language.

WhatWhy
Period start and end datesDay count, phase, next-period estimate
Average cycle and period lengthImproves the estimate over time
Birth date, time and place, and the charts computed from themCasting your Western, Vedic and Bazi charts
Email address, first name, languageSign-in and, if you opt in, the weekly reading
Your weekly reading textSo it loads instantly instead of recomputing
Reminder on/off settings and when one was last sentSending reminders, and not sending them twice
Subscription status and Stripe identifiersKnowing what you've paid for. We never see your card

What has no home in our database at all: flow intensity, symptoms, moods, energy, and daily notes. There is no column for them. Not an empty one — none.

What else your browser talks to

No page is truly silent, and a privacy page that claims otherwise is lying. Here's every third party:

WhoWhen
Supabase — our database and sign-inWhenever you sign in or save a date, chart or setting
StripeOnly when you open checkout. Card details go to Stripe, never to us

And what you will not find, which you can confirm in the same Network tab:

  • No Google Analytics. No analytics of any kind.
  • No Meta pixel, no TikTok pixel, no advertising tags. This is also why we can't retarget you — a trade we made on purpose.
  • No Google Fonts. Our fonts are bundled with the site, so loading a page doesn't announce your visit to a font server.
  • No session recording, no heatmaps, no third-party chat widget.

The limits of this promise

Things we can't do, stated plainly:

  • We can't protect data on an unlocked device. Local storage means local access. Use a device passcode.
  • We hold your period dates, and could be compelled to produce them. We can't be compelled to produce symptoms or notes, because we don't have them.
  • Clearing your browser deletes your log. Keep a backup file.
  • We are not open source yet. That's why this page exists — until the code is public, the honest substitute is a test you can run yourself in ten minutes. We'd rather give you that than ask for trust.

Found something wrong?

If any check on this page doesn't behave as described, tell us and we'll treat it as a bug, not a complaint: hello@ancientcycle.app

If you're a researcher or journalist and want to run a proper packet capture, get in touch and we'll help rather than hide.