Hi all,

In March I posted Ovumcy here. It’s a period tracker I built because I’m on Android, my wife is on iOS, and I couldn’t find a self-hosted option that worked for both of us. That thread got 80 comments and a lot of them were criticism. Most of it was fair, so here’s what came of it, comment by comment.

Strict CSP and CORS (@rimu@piefed.social)

CSP shipped a few days after that thread, with no inline scripts. CORS stays off since everything is same-origin.

“The README looks AI-generated” (also rimu)

You were right. The full disclosure is at the bottom.

Irregular cycles and reminders (@Fmstrat@lemmy.world)

You can now tag cycle factors like stress, illness, travel, sleep disruption and medication change. Stats show which ones come up in longer or shorter cycles. It’s context, not a diagnosis. Reminders come three ways: an in-app banner, a webhook to your own ntfy/Gotify, or a private read-only .ics calendar feed.

Spanish (@baner@lemmy.zip)

Done. French, German and Italian came with it.

Import from other apps (@CameronDev@programming.dev)

Still not there. Not forgotten.

“Why not drip / Mensinator?”

They’re good apps. If one phone is all you need, use them. Ovumcy is for when you want the same data from several devices and already run a server.

Also new since v0.3.1 (now v2.2.1): PostgreSQL besides SQLite, optional OIDC sign-in and TOTP 2FA, and packages for YunoHost, TrueNAS (community catalog) and StartOS (community). Every claim in SECURITY.md now has a named test behind it.

AI disclosure (rule 8)

  • Design: Pair. I decide what the app does and the security model.
  • Implementation: Generated. Claude Code agents write most of the code, one PR per change, directed and reviewed by me.
  • Testing: Generated. CI runs unit tests, Playwright e2e and mutation testing.
  • Documentation: Generated, edited by me.
  • Review: Pair. Automated review agents plus me before every merge.
  • Deployment: Assisted.

I know this sub has mixed feelings about that. All I can offer instead of promises: everything is public, and if you find a hole I’ll fix it and credit you.

If you want to help

  • A ⭐ on GitHub is the easiest way. That’s how people looking for a private cycle tracker find it.
  • Bugs, ideas and missing features go to Issues. Feedback from people who actually track their cycle is the most valuable.
  • Translations are welcome. If your language isn’t there yet, CONTRIBUTING.md explains how.
  • If you know someone who wants a tracker that keeps their data at home, send it their way.
  • Donations are possible too, see ovumcy.com/support, but a star and an honest bug report help just as much.

Repo: https://github.com/ovumcy/ovumcy-web

Site: https://ovumcy.com/

  • SavvyWolf@pawb.social
    link
    fedilink
    English
    arrow-up
    4
    ·
    10 hours ago

    Whoever administers [hosting provider’s servers] can read your records.

    Why not encrypt things locally before they get sent to the server? This is standard practice for most “privacy-first” applications nowadays.

    Counts one anonymous click. No email, no cookie, nothing about you is stored.

    For the “what to work on next”. How do you prevent bots spam clicking buttons multiple times?

    These are just two things that jumped out to me upon browsing your web site. But honestly, using AI to write code that handles such intimate data is a huge red flag to me - you have no guarantees that it is secure.

    • terraincognita@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      9 hours ago

      Good questions, thanks for actually looking at the site.

      Encryption: client-side encryption is for services run by someone else, where you can’t be sure nobody reads or leaks your data. A self-hosted app has a different threat model. The data sits on a machine you control, behind a login and 2FA, and how the server side is protected is described in the docs. So for your own server it was never the goal. The sentence you quoted is about the hosted option, which exists for people who find setting up a server too hard. There someone else holds the data, so the site says it plainly. For those who want client-side encryption anyway, I’m working on a mobile app with encrypted sync. It isn’t released yet.

      The vote counter: you’re right, it can be spammed. That’s the price of collecting nothing about visitors, and I chose that on purpose. So far nobody bothers, bots included. I treat it as a rough signal and still decide myself what to build.

      AI and security: no code comes with guarantees, whoever wrote it. What I can offer is that all of it is public, with tests, fuzzing and static analysis in CI, and a SECURITY.md if you find something. If anything looks wrong, tell me and I’ll fix it.

      • SavvyWolf@pawb.social
        link
        fedilink
        English
        arrow-up
        2
        ·
        5 hours ago

        A self-hosted app has a different threat model.

        I can think of other cases where even if it’s self hosted, you still want this sort of encryption. What about the use case of a mother setting it up for a group of other mums in a group chat. The other mums would still want their data to be private. The hosting provider thing is valid, and I think actually extends further than you think. I may trust my own server, but I don’t know if I trust Linode or Hetzner or whoever I buy my server from to not snoop in my files. There’s also the fact that if I fuck up the configuration on my server, at least they aren’t going to get that data in the breach. (“I” in this case being an abstract person wanting to use the server. I don’t have any use for a tool like this).

        The vote counter: you’re right, it can be spammed.

        That’s fair, just be aware of it. The amount of people that make decisions based on flawed customer data is a big problem for software development.

        What I can offer is that all of it is public, with tests, fuzzing and static analysis in CI

        The recent SSH bug had all of this and let a security exploit slip through. The reason was that people made a sensible sounding but ultimately flawed design decision. Those are the types of errors that AIs love to make and that inexperienced users can let slip through.

        • terraincognita@lemmy.worldOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          5 hours ago

          These are fair, and the misconfigured server one is the strongest. Client-side encryption would limit the damage there, I can’t argue with that.

          The group case is outside what I built this for. It’s meant for a household. If you run it for other people, you become their hosting provider, and the docs say that plainly: the app keeps your records from other accounts and from the network, not from whoever administers the machine.

          The VPS point is true, but it applies to everything on that box, not just this app. If you don’t trust the provider with it, the answer is hardware at home.

          I won’t promise it, but optional encryption for the web version is on my list to look into now.

          On design mistakes: agreed, tests and fuzzing don’t catch a wrong decision. But the SSH example cuts both ways. That code was written and reviewed by very experienced people and it still got through. Nobody is immune, so what matters is whether mistakes get found and fixed in the open. That has already happened here: tonghuaroot reported a hole in the webhook address filter, it was fixed and published as an advisory (GHSA-hg2x-v5cc-m384).