Trust & Privacy
How this site handles your data.
This page is maintained by Michael Schuerman to answer common security and privacy questions about michaelschuerman.co. It describes current, app-visible practices. It is editable content, not an independent certification or third-party audit.
Who runs this site
michaelschuerman.co is a personal professional site owned and operated by Michael Schuerman (Atlanta, GA, USA). For any privacy, security, or data request, contact ms@michaelschuerman.co.
What this site collects
The site collects only what you choose to submit through its forms:
- Sunday Decisions signup: your email address, so the weekly note can be sent.
- Funnel Check: Your entries stay in your browser. If you ask for your results by email, I store your name, email, team name, the numbers you entered, and your results, along with basic device and referral details. A copy of your results comes to me.
- Load-Bearing Score: Your individual answers are not stored. If you ask for your results by email, I store your email and basic device details, and your result is emailed to you and to me.
- Decision Cost Calculator: Your entries stay in your browser until you choose "Send me the number." Then I store your email, your inputs, and the estimate, along with basic device details, so I can follow up with you personally.
- Pattern quiz: Your answers and email are not stored. Analytics records only which pattern you landed on.
- 90-Day Scorecard: Nothing is saved. Your entries disappear when you close the page unless you print or save them.
- Sunday: If you check the Sunday box on the Funnel Check or Load-Bearing Score, your email is added to that list.
- Prayer requests: the request text and an optional name or email if you provide one.
- Voice samples: any voice memo you choose to upload through a form that requests one.
The site does not run third-party advertising trackers or sell data to advertisers.
How submissions are stored
Form submissions are stored in the site's backend database (managed Postgres) and are accessible only to the site owner and authorized server-side functions. Read access to submission tables is closed at the database layer; only server-side code with explicit credentials can retrieve entries.
Calendly is used for booking calls. When you book a call, your booking information is processed by Calendly under its own terms.
Subprocessors and integrations
The site relies on a small number of vendors to operate:
- Lovable: hosting and managed backend (database, edge functions, storage).
- Calendly: call scheduling.
- Resend: transactional email delivery for auto-replies (e.g., Sunday Decisions confirmations).
Each vendor processes only the data needed to perform its specific function.
Cookies and analytics
The site uses lightweight, first-party event tracking to count page views and button clicks (for example, how often a tool is opened). It does not set advertising cookies and does not build cross-site profiles.
Retention and deletion
Email-list entries are retained until you unsubscribe or ask for removal. Tool inputs, applications, and prayer requests are retained for as long as is reasonable to operate the service. To request deletion of anything you submitted, email ms@michaelschuerman.co from the address you used and the entry will be removed.
Security practices
The site is served over HTTPS. Submission tables have row-level security enabled with default-deny policies; only the site owner and explicitly authorized server-side functions can read entries. Secrets and API keys are stored server-side and are never shipped to the browser.
Lovable platform features for hosting, database, edge functions, and storage are used as provided. This site does not claim SOC 2, ISO 27001, HIPAA, PCI, or GDPR certification. Compliance with any specific regulatory framework is the responsibility of the platform vendors and the site owner for the portions each controls.
Reporting a vulnerability
If you believe you've found a security issue, email ms@michaelschuerman.co with a description and steps to reproduce. Please do not publicly disclose the issue until it's been addressed.
Changes to this page
This page is updated as the site changes. The site owner is responsible for keeping it current.