What this site collects, stated plainly.

This site uses Google Analytics 4 (measurement ID G-ZV808XPN3Z) to understand how many people visit, which pages they read, and which campaign links brought them here. Google Analytics sets cookies and receives standard web measurement information: page addresses and titles, referring links, approximate location derived from IP address, device, browser and language, and a randomly generated identifier used to recognise a returning browser.

Standard campaign parameters in a link (utm_source, utm_medium, utm_campaign, utm_content, utm_term, utm_id and placement_id) are carried through internal navigation so that a campaign link stays intact, and are reported to Google Analytics alongside the page view so a campaign can be attributed.

Eight interaction events are recorded. contact_intent is sent when someone presses the button that opens their email application from an inquiry form; it records only the selected inquiry category, and does not mean a message was written, sent, or received. start_pathway_selected records which of the “Start here” links on the home page was chosen, by its visible label. awareness_exercise_started and awareness_exercise_completed record only that the reflective flow on the campaign page was begun and reached its final step. That exercise has no input fields; nothing you think about during it exists anywhere on this site. blog_index_viewed records how many articles were listed, blog_post_viewed records the public address of the article read, and blog_submission_started and blog_submission_completed record only that the submission form was begun and accepted. No field contents from that form are ever sent to Google Analytics.

Two places on this site take what you type and store it, and they are separate systems. The first is the story submission form. If you submit a story or article, the name, email address, title, category, text and optional bio you provide are stored in this project’s private database, marked as pending, and are readable only by Jordan. They are not visible to the public, not visible to other contributors, and not published unless you are told otherwise and the piece is explicitly approved. Your email address is never published. You can ask for a submission to be deleted at any time by writing to jordan@capacityu.org.

The second is the CAPACITY Personal intake form at /personal-intake. That form is hosted and stored through Google Forms under the CAPACITY hUman Google Workspace account, not in this site’s database. It may collect your name, email address, an optional phone number, personal reflections, emotional responses, a description of a significant moment, your expectations, eligibility and safety responses, and follow-up permissions. That information is used only to assess fit, prepare for a CAPACITY Personal session, communicate about scheduling, create an authorized Moment Map, and conduct authorized follow-up. Responses are not automatically published or shared publicly. Jordan is the person who reviews them. You may request deletion by emailing jordan@capacityu.org. Please do not include identifying information about minors, sensitive third-party information, passwords, or anything you do not want stored in Google Forms. CAPACITY Personal currently accepts adults aged 18 and older. The intake is not research consent, medical care, therapy, diagnosis, trauma treatment, or crisis support.

Contact and inquiry forms work differently. They compose a message in your own email application and nothing you typed is transmitted to or stored by this website; you press Send yourself, and from then on it is ordinary email. Newsletter sign-up is not open yet. No email addresses are currently being collected for The Notice.

There is one further form on this site, at /auth. It is the restricted administrator sign-in used only by Jordan to review submissions and drafts. It does transmit an email address and password, to Supabase authentication (Lovable Cloud), which handles the login. It is not a public account system, and visitors have no reason and no ability to create an account there.

Story submissions are also sent to that same Supabase database, through this site’s own server rather than directly from your browser. The server checks the submission and records a one-way hashed fingerprint of the connection, with a timestamp, purely to limit repeated automated submissions. That record contains no message text, no email address, and no stored IP address, and it is deleted after twenty-four hours.

Ordinary web hosting logs may exist at the hosting provider level, as they do for any website. If a mailing list or a working contact channel are added later, this page will be updated first to name the provider and describe what it holds.

If you email a published address, that message lives in ordinary email, handled by the email providers involved.