Your park’s data.

What this workspace stores

Park details, member names and email addresses, schedules, operational notes, tasks, guest names and stay dates you enter, supply counts, uploaded files, previous record versions and an activity log. Email-code sign-in verifies the account identity used to check access. Sign-in sessions and rate-limit records are also stored.

Who can see it

Membership controls restrict records to the corresponding park. Owners and managers can access management notes, meeting records, email history and data exports. Staff can access day-to-day operational records and shared files. Direct-message text is visible only to its participants, including in downloadable exports. Photos are shared park files even when attached to a direct message. The service operator administers the application and infrastructure; this is not end-to-end encrypted storage.

Where it goes

Application records use hosted Cloudflare D1 storage; uploads use Cloudflare R2. If direct email is configured, the selected handoff contents and recipient addresses are sent to the email provider. Sign-in codes are sent through Resend. The current implementation also supports Resend for park email. No email is sent merely by creating a note.

Control & retention

Park owners can remove member access immediately. Owners and managers can export records and files. Archiving keeps a record, and previous versions may remain in history. Schedules and their edit history are retained for two years from each shift date, then automatically deleted during daily cleanup. Other records have no automatic expiry. Self-service full account deletion is not yet enabled. Agree deletion, retention and operator contact arrangements before entering customer data in a paid rollout.

Use only what you need

Do not upload card details, identity documents, medical information, confidential employment records or information unrelated to operating the park. Use your reservation system for payments and booking records.

Pilot status

This notice describes the current pilot implementation. The service operator must supply its legal business identity, contact details and approved privacy terms before general customer launch.