Public data standard · Version 1.0 · Effective August 8, 2026
Your working evidence is not our lead database.
Petrichor's upgraded public tools calculate in the browser. Strategic text is not sent to Petrichor, an AI service, analytics, or a booking route unless a user takes a separate, clearly described action that includes it.
What the tools handle
Tier 0: structured metadata
Selections, ranges, dates, public URLs, result bands, and interaction events may be calculated locally. Event analytics may include tool ID, mode, completion, export action, route, referrer, and campaign parameters. It excludes entered values and artifact content.
Tier 1: strategic working data
Claims, assumptions, customer language, competitive observations, and narrative text remain in browser memory by default. Opt-in local save writes a versioned copy to that device's browser storage.
Exports
CSV, JSON, print, facilitator packs, and Workshop Pre-Reads are created on the device. Downloads remain under the user's control. A Pre-Read excludes raw Tier 1 rows unless the user deliberately selects inclusion.
Email and marketing
The current upgraded instruments do not require email for the primary result or export. Any future artifact delivery must state what will be sent. Marketing consent must be a separate, unchecked choice.
Purpose, retention, and access
- Purpose: deliver the requested calculation and artifact; maintain security; measure anonymous starts, completion, artifact use, errors, and paid-route interest; respond to a user-initiated request.
- Local work: session work lasts until the page closes or is cleared. Opt-in local saves remain until the user selects “Start over,” turns off local saving and confirms deletion, clears site data, or removes the browser profile.
- Petrichor systems: the public tools do not persist Tier 1 working data server-side. No Petrichor employee can access browser-only work.
- Analytics metadata: retained for no more than 14 months for portfolio learning and security review. It must not include email, company, names, free text, customer or client data, prompts, or artifact content.
- Access owner: Petrichor Operations. Method, product, and distribution owners receive aggregate metadata only.
Deletion and access requests
Use each tool's clear-data control to delete local work immediately. For data that may have been submitted through another Petrichor form, email strategy@petrichorgrowth.com with the subject “Privacy or deletion request.” Include the email address and form or page involved; do not attach confidential tool exports. Petrichor Operations owns verification and response.
Subprocessors and geography
Public tool pages may use Vercel for site delivery and Google Tag Manager or Google Analytics for non-sensitive event metadata. A tool's deterministic result does not depend on those services. These providers may process technical data in the United States and other locations where they operate. Petrichor will not enable an optional AI, artifact-email, or server-side storage provider for Tier 1 data without updating this notice, defining retention and deletion, and showing an explicit transmission choice in the tool.
Incidents and changes
Petrichor Operations is the incident escalation owner. Suspected exposure, unsafe export behavior, or analytics leakage should be reported to strategy@petrichorgrowth.com with the tool name, method version, and a description that excludes confidential input. Material changes to tool data handling receive a new version and effective date on this page.
Boundaries
This notice describes Petrichor's public tool portfolio. It does not convert a strategy assessment into legal, security, compliance, financial, or professional advice. For the permanent product commitments governing the tools, read the Tool Trust Charter.