Our Claims, and How to Check Them
Last updated: August 11, 2026.
This page exists because we got a claim wrong in public, and we would rather show you our working than ask you to trust us.
Our standard now: we do not make claims about who was first. A "first" claim is a statement about history that neither we nor you can verify, because it depends on knowing when every competitor shipped every feature, and ship dates are exactly what you cannot see from outside a company. Everything below is present tense, about Storia, and testable by you today. Where a claim needs an account to verify, we say so instead of blurring it.
1. What you can check right now, without an account
- The Wedding DNA quiz is free and needs no signup. Open storia.ph/quiz in a private window. You will not be asked to create an account, give a card, or join a list to finish it.
- It generates an AI moodboard, also without an account. Finish the quiz in that same private window and the reveal produces images generated for your answers at request time, not pulled from a stock gallery. Run it twice with different answers and compare.
- Our prices are published, and the packages are one-time. storia.ph/pricing lists Bronze PHP 4,995, Silver PHP 9,995, Gold PHP 24,999, and Bespoke by custom quote. Each is a one-time purchase active through your wedding, not a recurring subscription. There is no hidden tier above these.
- Layon, our Wedding DNA companion, will not name you a vendor. Layon is reachable from the reveal page without an account. Ask it to recommend a photographer and it will decline to name one, then help you screen candidates instead: what fits your style, a hedged price band, when to book, what to ask before you pay a deposit. That is deliberate. We take no money for placement and never will, and our vendor revenue is fixed contracts rather than commission, so there is nothing for a recommendation to be bought with.
- Our Filipino wedding glossary is open. storia.ph/glossary is free to read, no account, no email gate.
2. Built for Filipino weddings, specifically
This is the part we would point at first. Storia models seven ceremony types as first-class objects, and each one carries its own timeline tasks, not a relabeled Catholic checklist. The counts below are the cohort-specific tasks that ship today, on top of 43 shared across every ceremony type.
| Ceremony type | Own tasks | Examples of what is modelled |
|---|---|---|
| Catholic | 11 | Canonical interview, publication of banns, Pre-Cana seminar, arranging the cord, veil, coins and candle, pamamanhikan |
| Muslim | 10 | Wali (marriage guardian), Mahr, two male Muslim witnesses, filing with the Shari'a Circuit Court |
| Chinese-Filipino | 7 | Auspicious date consultation, tea ceremony room, ang pao, lauriat caterer, double happiness decor |
| Iglesia ni Cristo | 6 | Locale registry signing, "patotoo" certificate from the locale Minister, pre-marriage seminar |
| Christian | 4 | Confirming your pastor is an authorized solemnizing officer, church pre-marriage counseling, pamamanhikan |
| Interfaith | 4 | Dispensation requirements, finding officiants comfortable with a blended ceremony, communicating the format to both families |
| Civil | 3 | Choosing your officiant, deciding which Filipino traditions to include, optional personal vows |
Beyond the timeline, ninong and ninang are modelled in the seating chart and the planning milestones rather than being typed into a notes field, the wedding website supports a separate ceremony and reception venue because most Filipino weddings have both, and cash gifts support GCash and bank transfer because that is how guests here actually give.
How to check this one: it needs an account, so we are not asking you to take it on faith. Ask us for a walkthrough at hello@storia.ph and we will show you the live product rather than a deck.
3. What needs an account, stated plainly
These are real and shipped, and you cannot verify them from outside. We would rather label them than let them sit next to the checkable claims and borrow their credibility.
- Hiraya, our planning companion, proposes changes to your timeline and guest list and applies them once you approve. It asks for consent separately for each of those areas rather than once for everything.
- AI wedding website generation, section by section, from your Wedding DNA rather than from a blank template.
- Paperwork tracking for PSA documents, CENOMAR, the local civil registrar, and the marriage license, routed by ceremony type. Muslim couples marrying under PD 1083 are routed through the Shari'a Circuit Court and NCMF rather than the local civil registrar, because that is the actual path and getting it wrong costs a couple months.
4. What we are not claiming
- Not first. We withdrew that claim, and we are not reinstating it in a narrower form.
- Not best, not only, not leading. Superlatives we cannot substantiate on demand are exactly the exposure RA 11967 §7 is concerned with, and the burden of proof sits with us, not with the reader.
- Nothing about when a competitor shipped anything. We cannot see that, so we do not assert it. We previously did, using a competitor's domain registration date. A registration date shows only that a site could not have existed earlier. It says nothing about when a feature shipped, and we were wrong to treat it as if it did.
- No vendor prices as facts. Cost figures anywhere on Storia are guided ranges, and they vary by region, season, and supplier.
5. The claim we withdrew
From 2026-05-13, Storia claimed to be the first AI SaaS-driven wedding-planning platform in the Philippines, defined by four criteria it had to meet at once: couple-facing and wedding-specific, SaaS rather than a service or directory, AI as the load-bearing engine rather than a writing add-on, and built for the Philippines rather than localized after the fact.
We withdrew that claim on 2026-08-06. The notice we published then said a competitor had been "confirmed" to meet all four criteria and to have shipped before our cutoff. That was not established. We corrected it on 2026-08-08. We are not asserting the claim, and we are not asserting it was correct either. On 2026-08-11 we retired the claim permanently rather than rewrite it into something narrower.
The full account, including what we got wrong and why, is in our blog post "We Retracted Our First AI Wedding Platform Claim" at blog.storia.ph. This record is kept here per our RA 11967 (Internet Transactions Act of 2023) §7 retraction commitment.
6. How this page is kept honest
The withdrawal in August was partial. It landed on our blog and left this page and a shared Wedding DNA page still asserting it, live, for two days. The cause was ordinary: the claim lived on ten different files and nothing checked that they agreed with each other.
That is now enforced rather than remembered. Every load-bearing public claim is listed in a registry alongside every file that carries it and the wording that is banned. A check runs before any code is committed: retired wording on any carrier blocks the commit, and a change that touches one carrier is told which siblings it left behind.
Rewriting this page on 2026-08-11 also meant re-checking every product claim on it against what is actually running, one line at a time. Several descriptions of what our ceremony-specific timelines contain had drifted from what they actually contain, and were corrected against the shipped tasks. Two claims were nearly deleted as unsupported and both turned out to be real once we looked in the right place, which is its own lesson: not finding something is not the same as it not being there, and we would rather check twice than remove something true.
7. Challenge anything on this page
If a claim here does not match what you find in the product, tell us. Email hello@storia.ph with the subject line "claims challenge" and what you checked. We commit to a substantive response within 14 days, and to correcting the page within 48 hours of confirming an error. Corrections stay visible on the page rather than being edited away, as they are in sections 5 and 6.