Change log

Editing a hidden post genuinely sends it back for review

September 24, 2026

It never had. The database rule that re-queues an edited post was written to fire when the version number changes, and it fired only when a statement named that column directly — which the app never did. So every edit since the feature was built went unreviewed and nobody could have noticed from the outside. Fixed, and the check that would have caught it now runs against a real database. While we were there: an author can always edit their own post, and the fifteen-minute window came back for everyone else.

Automated screening is on, and it runs inside our own database

September 23, 2026

Every post and response is now checked automatically the moment it is written, by one classifier, and then read by a person. The check runs inside Supabase rather than on the machines that serve the site, so the words never pass through our hosting provider on the way — the only companies that see them are the ones named on Specs & services. The endpoint we use keeps no copy of what we send it. A second check, by a language model, was planned for posts that suggested someone might be in crisis; it is not running, because that company’s terms permit keeping flagged messages for up to two years and those posts would be the most likely to be flagged. A person reads them instead.

Analytics stop loading entirely if your browser asks them to

September 23, 2026

If your browser sends a Global Privacy Control signal, neither analytics tool now loads at all — nothing is sent and no analytics cookie is set. Previously one of the two loaded regardless and we merely withheld the page view, which is not the same thing and our Privacy Policy said otherwise. The policy also now names both tools rather than one, and describes what session replay is limited to: public pages only, with all text masked in your browser before anything leaves it.

A hidden post now says it is hidden, and you can do something about it

September 22, 2026

If something you wrote comes off the board while a person reads it, you see that on the post itself and in an email — what happened, which ground rule it appears to touch, and that you can edit or delete it. Before this it simply became invisible to everyone else and you were not told. Deleting a hidden post also works now; it did not. And every moderation decision is recorded with who made it, which is a record we keep rather than one you see.

A way to tell us things, and a closed door

September 22, 2026

There is now a feedback box on every page and a queue behind it, so writing to us is not an email that gets lost. Separately: joining is by invitation only and always was meant to be — a gap let anyone who had signed up to the waitlist let themselves in, and that is closed. The board is also readable without an account now, showing a small set of posts we wrote ourselves and marked public. No member's writing appears there.

Public-visibility wording corrected, and a roadmap entry for it

September 19, 2026

“Never public” now reads “never public without your say-so” on the Privacy Policy, Terms, How it works and the FAQ. We expect to let members choose, post by post, to make a prayer visible outside the community in a stripped-down form; the roadmap now says so. The default stays members only. Also today: the Accessibility page describes its keyboard and screen-reader support as what we build toward, not what has been verified.

Policy and site copy corrected against what is actually built

September 15, 2026

Our policy pages described audience-picking and group spaces, which we have not built — every signed-in member sees every post today. That is now what they say, with the roadmap linked for what is coming. The Article 9 consent no longer asks you to agree to a choice that does not exist. Sub-processors moved to Specs & services, which was already the more complete list.

Every public page says when it last changed

September 12, 2026

Generated from the code for pages that are their own content; the policy pages carry the policy's own date instead.

Specs page now names the services that read what you write

September 12, 2026

Anthropic and OpenAI screen posts in production. They were listed only as tools we build with.

A public roadmap

September 12, 2026

What we are working on, what comes after, and the open questions we have not answered. No dates, nothing promised.

Site-wide copy review

September 12, 2026

Every page read against what the code actually does. Four claims described features that do not exist and were corrected.

Password strength meter and breach check

September 12, 2026

Minimum raised to 12 characters. New passwords are checked against known breach corpora; no character rules.

Members can invite people

September 12, 2026

Five invitations at a time, and one comes back each time somebody accepts.

Every change now runs the full test suite before it ships

September 11, 2026

Migrations, types, unit tests, the privacy suite and the build, on every push.

Change your password, email address, or username

September 11, 2026

An email change is confirmed at the new address and announced at the old one, with one click to undo it.

Account settings

September 11, 2026

Notification preferences, downloading everything you have written, deactivating, and erasing — all self-serve.

Member profiles

September 11, 2026

Choose how your name appears, write a short bio, set a country, and decide whether other members can see your profile.

The app is ready to be translated

September 11, 2026

Every visible word moved out of the code and into language files. Latin American Spanish is in progress.

A guided tour at /how-it-works

September 10, 2026

Seven chapters showing what the board looks like, who sees what, and what it costs.

Signing up now needs an invitation

September 10, 2026

Accounts are invitation-only while we expand.

Take your writing with you, or delete it

September 9, 2026

Export everything you have written as one file, deactivate without losing it, or erase it for good.

Moderation and reporting

September 8, 2026

Posts go up straight away and are reviewed after. Reporting something never hides it, and a person makes every decision.

The prayer board

September 8, 2026

Post a prayer, respond to anyone, react, save a draft, and mark a prayer resolved. The first version of the product itself.

Team area paused for maintenance

August 31, 2026

Sign-in, password reset, and the internal admin area show a maintenance notice while we reconnect our email delivery. The public site, including waitlist signup, is unaffected.

Site analytics now run on every visit

August 31, 2026

Google Analytics 4 previously loaded only after a visitor accepted a consent banner. It now loads on every page view, and the banner is gone. We still ask Google to shorten IP addresses, we send no ad or profiling signals, and we run no other trackers. Details on our privacy page.

Security & privacy hardening pass

August 19, 2026

Tightened database permissions, added security headers on every response, self-hosted fonts so visits don’t leak to a font CDN, and added a standard security.txt contact so researchers can reach us.

Blog shipped

August 19, 2026

Built the blog — posts, authors, tags, SEO, accessibility checks.

Admin dashboard shipped

July 18, 2026

Internal admin area went live with KPI overview, along with change log and specs page.

Landing page went live

July 18, 2026

Public waitlist landing page is now live at prayergroup.live with double opt-in email confirmation, referral loop, and analytics tracking.

Email delivery wired to Resend

July 18, 2026

Confirmation and welcome emails now send from hello@prayergroup.live via Resend. Supabase auth emails routed through Resend SMTP.

First prototype started

January 22, 2025

First prototype, focused on directory for finding and posting online group prayer events.