OpenHood V1 — Legal and Privacy Review Checklist

A. Business identity and contact — must supply

• Founder-provided legal operator name and entity type: DESIGNED FOR HUMAN LLC. Verify exact registered spelling before publication.
• Jurisdiction of registration and public business contact/address requirements: [JURISDICTION / APPROPRIATE CONTACT].
• Founder-provided privacy/support contact: gcrisostomo@designedforhuman.com. Confirm the inbox is monitored and can receive support and privacy requests before publication.
• Founder-provided company website: https://www.designedforhuman.org/ (homepage verified accessible; this is not an OpenHood Privacy Policy or dedicated support page).
• Public OpenHood support URL: [HTTPS SUPPORT PAGE URL]. Create/verify a page with visible contact instructions; the existing company homepage alone may not be sufficient for App Store support metadata.
• Final app name (“OpenHood” vs. “OpenHood Garage”), developer name, and App Store bundle ID verified.
• Geographic distribution and target users/age groups confirmed.
• App terms and privacy policy dates populated.

B. Actual data practices — inspect Release build

• Inspect every third-party SDK, Swift Package, linked framework, and privacy manifest.
• Inspect URLSession, networking, webviews, crash tooling, push services, and tracking/advertising identifiers.
• Confirm whether analytics, tracking pixels, cookies, optional scripts, or advertising SDKs are present; remove or obtain required consent before use if applicable.
• Confirm exactly what vehicle information is collected or processed: VIN, nickname, mileage, vehicle details, maintenance records, and notes.
• Confirm whether Glovebox stores metadata only or actual attachments/files.
• Confirm whether OBD/symptom inputs, possible-cause results, quotes, and mechanic contacts remain entirely local.
• Confirm whether feedback_v1.json stays on-device, is shared manually, or is forwarded by email/webhook; ensure confirmation copy matches reality.
• Verify every external Phone, Maps, Share, or website action and which data is passed to that service.
• Check iOS backups and any excluded-from-backup file attributes; do not promise that backups are erased by the app.
• Check logs, crash reporting, debug builds, seeded data, and actual Release configuration.
• Confirm encryption/file-protection implementation before using security claims.
• Inventory data categories for App Store Connect privacy questions; answer based on real practices, including integrated third parties.

C. User controls and deletion — engineering verification

• Verify users can edit and delete relevant vehicle records where represented in UI.
• Implement and test Profile → Your Data → Delete All OpenHood Data, with confirmation and cancel controls.
• Audit all persisted paths (garage_v2.json, glovebox_v1.json, maintenance_v1.json, quotes_v1.json, mechanics_v1.json, feedback_v1.json, plus preferences and any diagnosis data); update as storage evolves.
• Verify deletion leaves no app-owned local data that the UI promises to erase.
• Ensure deletion resets onboarding and active-vehicle state correctly.
• Describe backup/restore and shared/exported data limitations accurately.
• Determine whether operator holds any user data externally and create a real response process for data/privacy requests if so.

D. Content, safety, and consumer protection — high-priority release blockers

• Remove unsupported “Safe to drive” assertions and distinguish safety urgency from diagnostic certainty; do not imply vehicle inspection.
• Check OBD code definitions against a reliable, legally usable source; document supported and unsupported codes.
• Review possible-cause ordering/“likelihood” or percentages; remove false precision without validated basis.
• Verify source, location relevance, recency, and license for every repair-price benchmark; do not call sample model values verified regional market rates.
• Ensure maintenance due/overdue status reflects actual user entries or clearly labeled estimates rather than unsupported assertions.
• Do not assert “No open recalls” unless a verified, current source has actually been queried.
• No fake shop endorsements, demo reviews, demo maps, live roadside promises, or unimplemented actions in public V1.
• Include appropriately placed mechanic-inspection and safety limitations without treating disclaimers as a substitute for accurate app behavior.
• Test accessibility (VoiceOver, Dynamic Type, color contrast, focus, readable warnings, tap targets).

E. Legal terms and publication

• Determine whether to use Apple's Standard EULA plus supplemental app-use terms or a legally reviewed custom EULA.
• Counsel review: disclaimers, injury/property-damage risk, warranty and liability language, consumer rights, age applicability, and governing-law/disputes considerations.
• Review jurisdiction-specific privacy rights and notices for launch markets; do not assume a U.S.-only legal template covers all regions.
• Review intellectual-property and license obligations for Figtree, Google Material Symbols, any custom graphics, data sources, and third-party content.
• Confirm V1 has no payments, subscriptions, refund obligations, or marketing email workflows; revisit before enabling any.
• Remove ALL [PLACEHOLDER] text, internal warnings, and draft banners before making public.
• Host approved OpenHood Privacy Policy at a stable, public, working HTTPS URL (e.g., a dedicated page under the company domain; URL must be created and tested, not inferred from the homepage).
• Link Privacy Policy accessibly within the app and in App Store Connect metadata.
• Decide whether to host Terms publicly as well; ensure in-app and online versions match.
• Populate support contact information and confirm it works.
• Confirm legal document change/version procedures and future review owner.

F. TestFlight-specific checks

• Install and test a Release-like build on a physical iPhone, not just simulator.
• Confirm DEBUG-only shop directory, maps, roadside, reset tools, and sample data are not reachable.
• Confirm no invented cookie banner or tracking-consent prompt appears in native V1 without a real need.
• Verify TestFlight feedback process; do not mistake locally saved feedback for feedback received by the team.
• Test data persistence across quit/relaunch and deletion/uninstall behavior; document meaningful beta limitations.
• Prepare beta review notes, a monitored support contact, and representative screenshots.
• Confirm TestFlight distribution approvals before inviting external testers.

G. Release-blocking decisions and owner signoff

Apple guidance to consult

• App Review Guidelines — privacy policies and permissions
• App Store Connect — app privacy and privacy policy URL
• Apple Standard Licensed Application EULA
• Minimum terms if adopting a developer custom EULA

Approval: [COUNSEL NAME / DATE] • [PRODUCT OWNER / DATE] • [ENGINEERING DATA AUDIT SIGNOFF / DATE]