Settings / Privacy Notes

Safety rule

All data is sample-only

Reviewers should not treat any visible value as real.

Required

Safety rule

Supabase foundation is optional

The app can detect Supabase browser configuration, but the UI still falls back safely when env vars or signed-in sample access are missing.

Sample-only

Safety rule

Deployment stays static-first

Cloudflare Pages can keep serving the sample-first app without requiring live backend reads at build time.

Protected

Developer Verification

Optional Supabase sample-read check

Local sample fallbackdashboard_command_center_summaries

This screen helps developers confirm the optional signed-in sample-read path without adding full auth UI or changing the local sample fallback behavior.

Supabase env

Not configured

Needs Review

Session

Not detected

Review Later

Sample rows

Not readable

Review Later

Active source

Local sample fallback

Sample

Row count

0 rows

Review Later

Last checked state

Fallback active

Sample

Current detail

Supabase env vars are not configured in this build, so the dashboard is using local sample command-center metadata.

Last checked at

Jun 1, 2026, 8:57 PM

Developer-only routine

Safe sample-read setup

Developer onlySample only

1. Configure local public env vars

Copy `.env.example` to `.env.local`, set `NEXT_PUBLIC_SUPABASE_URL` and `NEXT_PUBLIC_SUPABASE_ANON_KEY`, and do not commit local env files or any secret keys.

2. Create a development test user

Use a safe development-only Supabase project and create one sample-only auth user. Do not use a production or real owner account.

3. Replace the placeholder seed UUID

In `supabase/seed.sql`, replace `11111111-1111-4111-8111-111111111111` with that development test user's `auth.users.id`.

4. Run seed data in a safe sample environment

Apply the dashboard sample-summary migration and seed only in a development/sample Supabase environment. Keep every row fake/sample only.

5. Use a temporary manual sign-in method if needed

Sign in through a safe temporary developer method so this browser gets a valid Supabase session. Do not add production login UI in this step.

6. Verify connected sample rows here

Return to this screen and confirm env configured, session detected, sample rows readable, Supabase sample metadata active, and a row count above zero. Full routine: `docs/SUPABASE_SAMPLE_READ_TESTING.md`.

Page sample-data boundary

No real data, no secrets, no Supabase Auth UI, no storage, no uploads, no real GIS, and no private records are included.