Privacy and AI
A plain-language trace from your browser to generation, fallback, editing, rehearsal, and export.
Implementation reviewed 16 July 2026
Use initials, placeholders, or broad descriptions. The writer intentionally leaves personal fields blank and offers a clearly synthetic sample. Full names, exact locations, health details, secrets, and details about other people are not needed for a useful structure.
Only fields for the active writer are included in the request. Vow requests do not send speech fields, and speech requests do not send vow fields.
The system is instructed to use only facts you supply and not to invent memories, qualities, dates, places, cultural rules, or religious requirements. Automated safeguards can still fail. Treat every generated sentence as a suggestion and remove anything you cannot personally confirm.
Religious and cultural wording on this site is general writing guidance, not officiant, legal, theological, or cultural advice. Verify ceremonial language with an appropriate human adviser.
Generation and export use layered IP, local-session, and instance-wide checks inside each warm serverless instance. Identifying network values are hashed in memory and are not written to application logs. Browser session identifiers can rotate or reset, and separate serverless instances do not share these in-memory counters, so the checks are best effort and do not create a durable per-person, per-IP, or project-wide quota.
There is no durable overall cost ceiling configured in this release. Distributed enforcement through a platform firewall, gateway budget, or shared rate-limit store is a precise deferred P1 infrastructure boundary; until that exists, the site must not describe the current checks as guaranteed global cost control.