LAST UPDATED 2026-09-06

Privacy Policy, because apparently the paperwork found us.

Walking With Camera is Mike Kohlbecker's photography website. WWC Dashboard is Mike's private operational tool for running Walking With Camera. This page explains what the public website collects, what the private Dashboard does with Facebook, Instagram, and YouTube, and how to ask for access, deletion, or help without needing a ceremonial binder.

Plain-English summary: the public website is for visitors. WWC Dashboard is private to Mike. Platform data is used to publish, schedule, verify, and track Mike's own Walking With Camera content. It is not sold, rented, used for ads, or fed into a mystery cauldron labeled "growth hacking."

Who runs this

Walking With Camera and WWC Dashboard are owned and operated by Mike Kohlbecker. The public website is walkingwithcamera.com. The Dashboard is a private Mac application and is not open for public accounts, public registration, or visitor login.

For privacy questions, deletion requests, access revocation help, or accessibility needs, email michael@walkingwithcamera.com. Yes, a real address. No, not a "Contact Our Synergy Team" portal. We are all grateful.

Public website data

The website can collect information you choose to send through the contact or report-issue chatbot: your name if you provide it, email address, subject, message, issue details, and any report attachments you deliberately upload. The server also records the visitor IP address with submitted messages so Mike can identify abuse, troubleshoot delivery, and confirm where the message came from. The paperwork insisted on that sentence wearing sensible shoes.

Messages are sent to Mike by email using Resend. Report attachments are assembled only for the message you submit. In production they use private Vercel Blob storage while the message is being prepared and sent; in local preview they use temporary local storage. The website also loads Vercel Web Analytics and Speed Insights scripts for basic site measurement and performance checks.

The public website does not provide user accounts, sell visitor data, run public Dashboard registration, or let visitors connect their Facebook, Instagram, or YouTube accounts.

WWC Dashboard data

WWC Dashboard is Mike's private operations app for Walking With Camera. It reads local Walking With Camera working files, prepares review plans, schedules or verifies Mike-approved social posts, writes local records, and updates editable website source only when a governed workflow authorizes that work. Translation: it is the little control room behind the curtain, but with fewer blinking movie buttons and more "please do not overwrite the folder."

Dashboard credentials are stored in protected local or service-provider credential storage such as macOS Keychain and platform environment variables. Credential values are not displayed on the public website and should not be placed in public files, logs, reports, captions, or screenshots.

Facebook and Instagram

WWC Dashboard uses Meta's Facebook and Instagram APIs for Mike's own Walking With Camera Page and linked Instagram professional account, currently identified in the implementation as the Walking With Camera Facebook Page and Instagram account @walkingmk.

Facebook use includes Page identity checks, reading future scheduled Page posts, reading recent Page posts, scheduling approved Page photo posts and approved Page video posts, and reading back IDs, schedule times, publication state, attachments, reactions, comments, shares, and available Page or post insight fields needed for WWC's own workflow checks.
Instagram use includes checking the linked Instagram account, confirming required permissions, preparing approved photo or carousel publishing jobs, uploading approved images through a protected backend, publishing at the approved time when the job is ready, reading back media identity, permalink, timestamp, caption, media type, child media IDs for carousels, and collecting available metrics such as likes, comments, shares, saves, reach, views, and plays where the implementation supports them.
WWC Dashboard uses this data to plan, schedule, verify, reconcile, recover, and score Mike's own Walking With Camera content. It does not use Meta API data to profile website visitors or to sell advertising. The spreadsheet gobbledygook has been denied a parade permit.

Implemented status: the current authority treats the combined Meta API workflow as approved and operational through WWC Dashboard and its protected Instagram backend. The Dashboard distinguishes unavailable platform data from zero values and does not automatically retry uncertain publishing requests.

YouTube

WWC Dashboard's YouTube work is for Mike's Walking With Camera YouTube channel. The implemented source uses YouTube Data API access for channel verification, private video upload, thumbnail upload, video read-back, and editable Watch the Walks website entries. The requested scopes shown in source are YouTube read-only and YouTube upload.

Implemented status: WWAS says the YouTube API design is approved, while public scheduling acceptance is not complete. The current implementation is a controlled private-only integration path: Google OAuth is still in External Testing, the API project is unaudited, and production public scheduling is not ready to be claimed. In human words: the YouTube machine has learned to pick up the wrench, but we are not pretending it built the shed.

WWC Dashboard does not collect YouTube Analytics, engagement metrics, comments, or performance scores, and does not add YouTube metrics to WWC's Luna scoring.

Storage and retention

WWC keeps records needed to operate and audit Walking With Camera workflows: message emails, local workflow reports, Facebook and Instagram IDs, schedules, publication timestamps, read-back status, media associations, Instagram job history, metric snapshots, YouTube operation records, editable website change receipts, and local website source records. Some WWAS records intentionally preserve history so Mike can prove what happened and recover safely.

The inspected source does not define one simple universal retention period for all of this data. So this policy does not invent one. Report attachments are cleaned up after delivery when possible, and production attachment cleanup also has a 24-hour cleanup path for expired private Blob items. Meta Luna channel tracking is governed for 365 days by WWAS. Other records are retained as long as needed for Walking With Camera operations, audit, recovery, platform compliance, and Mike's approved workflow history.

Access, deletion, and revocation

Email michael@walkingwithcamera.com to ask what Walking With Camera has from you, to request deletion, to report a privacy concern, or to ask for accessibility help. Mike will handle straightforward visitor requests directly. If a request concerns platform records that must be kept for security, audit, legal, recovery, or platform reasons, Mike will explain the practical limit instead of pretending the delete key wears a cape.

To revoke Meta access, use your Facebook or Instagram account settings and Meta's app/business integration controls, or contact Mike if the request concerns the WWC Dashboard app connection. Meta also requires app developers to provide data deletion information; this section is intended to serve as the deletion instructions for the Walking With Camera Meta app until a separate automated deletion callback is implemented.

To revoke Google or YouTube access, use Google's app permissions page at https://security.google.com/settings/security/permissions. You can also contact Mike at michael@walkingwithcamera.com for Dashboard-specific YouTube access or deletion questions.

Platform policy links

Because the Platform Paperwork Parade brought confetti and a clipboard, here are the important links in one place:

Terms of Service

I did not find a platform rule requiring a separate public Terms of Service page for this private Dashboard homepage request. Google treats Terms of Service as optional in the OAuth app-domain fields when you have them, while the homepage must link to the privacy policy. YouTube API clients must require users to agree to a privacy policy. Since WWC Dashboard has no public users, no public registration, and no public Dashboard access, this request can stop with the Privacy Policy and About WWC Dashboard pages.

If Mike later wants a public Terms page anyway, that can be added as a separate plain page. The paperwork will be very proud of itself and should not be encouraged too much.