Security & Privacy

How Vertex Bridge protects onboarding work

Vertex Bridge is an MVP, but it is built around a simple operating standard: school files, task data, and account workflows should be private by default, visible only to the right people, and handled through authenticated server-side controls.

Authenticated access

Onboarding workspaces, uploads, AI assistance, and internal dashboards require a signed-in Vertex Bridge session. Staff-only areas are restricted to Vertex staff or admin roles.

Private document handling

Uploaded documents are stored in a private Cloudflare R2 bucket. Document download links use submission IDs, not raw storage keys, and the server verifies the user can access the submission before reading from storage.

Encryption in storage and transit

Vertex Bridge uses Cloudflare R2 for file storage and Cloudflare D1 for workflow metadata. These platform services provide encryption at rest, while production traffic is served over HTTPS.

Scoped school data

School users are limited to schools assigned to their account. Internal dashboard data, submission review actions, and client profile updates are available only to authorized Vertex staff.

Safer invites and secrets

Invite links expire, invite tokens are stored as hashes, and application secrets belong in Cloudflare environment secrets rather than client code or repository files.

Guardrailed AI assistance

VertexAI is limited to onboarding guidance from approved task and FAQ context. It should not approve documents, provide legal or financial advice, or ask users to type sensitive bank details into chat.

File Protection Standards

  • Accepted upload types are limited to common document, spreadsheet, CSV, PNG, and JPG files.
  • Uploads are size-limited and screened to reject obvious HTML, XML, SVG, and script-like content.
  • Documents are served as downloads with browser MIME sniffing disabled.
  • Raw R2 storage keys are kept server-side and are not used as public document URLs.

Privacy Standards

  • We collect only the information needed to operate onboarding: account details, school profile fields, task status, upload metadata, and support interactions in the portal.
  • We use uploaded files and task metadata to route onboarding work, record submission status, and support Vertex review workflows.
  • We do not ask clients to type bank account numbers, payroll details, or other sensitive document contents into VertexAI chat.
  • Access to onboarding submissions is limited by role and school assignment.

Current MVP Boundaries

This page describes the security and privacy controls currently represented in Vertex Bridge. Production expansion should add formal retention schedules, audit reporting, malware scanning, incident response procedures, and any compliance commitments required by Vertex Education policies or client contracts.