Sector

Legal

Last updated: April 17, 2026

Privacy Policy Terms of Service Data Attribution Cookie Policy
← Back to home

01 Privacy Policy

Sector ("we", "us", "our") operates the sector.training platform. This policy describes what data we collect, why, and how we protect it.

Data We Collect

When you use the platform, we collect the following:

  • SAP Number — Your employee identification number (4-8 digits), used as your unique identifier on the platform.
  • Display Name — An optional name you provide so teammates can identify you on leaderboards.
  • Drill Performance Data — Station, district, difficulty level, scores, distance accuracy, hints used, and per-street results from each training drill you complete.
  • Computed Statistics — Best scores, street mastery metrics, and aggregated performance data derived from your drills.
  • Timestamps — When your account was created and when you last completed a drill.

We do not collect email addresses, passwords, phone numbers, GPS/location data, IP addresses, or device fingerprints.

How We Use Your Data

  • To provide the training drill experience and track your progress.
  • To generate leaderboards and department-wide performance statistics.
  • To help department leadership identify knowledge gaps and training needs.

Data Storage & Security

Your data is stored in Cloudflare KV, a globally distributed key-value store. Data is encrypted in transit via HTTPS. Each department's data is isolated by city-scoped key prefixes — no cross-department data access is possible.

Authentication uses cryptographically signed cookies (HMAC-SHA256) that expire after 7 days.

Data Retention

  • Your most recent 200 drill records are retained. Older drills are automatically removed.
  • Your profile (SAP number, name, best scores, street mastery) is retained indefinitely while your account exists.
  • Cached department statistics are refreshed every 30 minutes.

Data Visibility

  • You can see your full drill history, scores, and street mastery.
  • Other firefighters in your department can see your name and scores on leaderboards.
  • Department leadership can see a roster view with drill counts, scores, and activity levels per firefighter.

Third-Party Services

The platform uses the following third-party services on the client side:

  • OpenStreetMap / Overpass API — To fetch street and geographic data for drill questions. No personal data is sent.
  • Leaflet.js tile servers — To render maps. No personal data is sent.
  • Google Fonts — To load typefaces. Subject to Google's privacy policy.

No personal data is shared with or sold to any third party.

Your Rights

Canadian Users (PIPEDA)

You have the right to access, correct, or request deletion of your personal data. To make a request, contact us at the address below.

California Users (CCPA/CPRA)

If you are a California resident, you have the right to:

  • Know what personal information we collect and how it is used.
  • Request deletion of your personal information.
  • Opt out of the sale of personal information — we do not sell your data.
  • Non-discrimination for exercising your rights.

U.S. State Privacy Laws

Residents of states with comprehensive privacy laws (Virginia, Colorado, Connecticut, Utah, and others) may have similar rights to access, correct, delete, and opt out. Contact us to exercise these rights.

Contact

For any privacy-related requests, reach us at privacy@sector.training.

02 Terms of Service

By using the sector.training platform, you agree to the following terms.

What This Platform Is

Sector provides a web-based training tool designed to help firefighters build and maintain knowledge of streets, hydrant locations, and district geography. It is a supplementary training aid, not a replacement for official training, standard operating procedures, or on-the-ground experience.

Accounts & Access

  • Access is granted through a department-provided access code and your SAP number.
  • You are responsible for keeping your access credentials within your department.
  • We reserve the right to suspend or terminate access at any time.

Acceptable Use

You agree not to:

  • Share access codes outside your department.
  • Attempt to access data belonging to other departments.
  • Use the platform for any purpose other than training.
  • Attempt to reverse-engineer, scrape, or interfere with the platform's operation.

Data Ownership

  • Drill data and performance statistics generated through your use of the platform are stored and managed by Sector.
  • Departments may request export or deletion of their department's data at any time.
  • Geographic and street data is sourced from OpenStreetMap and is subject to the ODbL license.

Limitation of Liability

The platform is provided "as is" without warranties of any kind. Sector is not liable for:

  • Inaccuracies in street or geographic data.
  • Service interruptions or data loss.
  • Decisions made based on information from the platform.
  • Any direct, indirect, or consequential damages arising from use of the platform.

This tool does not replace official department training. Operational decisions should never be based solely on drill performance within this platform.

Availability

We aim to keep the platform available but do not guarantee uptime. We may modify, suspend, or discontinue the service at any time with reasonable notice to active departments.

Changes to Terms

We may update these terms from time to time. Continued use of the platform after changes constitutes acceptance.

03 Data Attribution

Sector relies on publicly available geographic and municipal data to build training drills. We credit the original sources below in accordance with their respective licenses.

Geographic & Street Data

Street geometry and names are derived from OpenStreetMap, made available under the Open Database License (ODbL). Map tiles are rendered via Leaflet.js using third-party tile providers.

© OpenStreetMap contributors.

Municipal Data Sources

Fire station locations, response zone boundaries, and related operational geography are sourced from municipal open data portals where available. Each dataset is used under the terms of the license granted by its publisher — typically an Open Government Licence or equivalent permitting non-commercial and commercial reuse with attribution.

Sector does not claim ownership of, or exclusive rights to, any municipal open data. Inclusion of a municipality's data on this platform does not imply endorsement by that municipality.

Current Data Sources by Department

  • Halifax Regional Fire & Emergency — Fire response zone polygons and station locations provided by Halifax Regional Municipality via the HRM Open Data Catalogue. Contains information made available under HRM's open data terms.
  • Ottawa Fire Services — Station locations sourced from the City of Ottawa Open Data Portal. Response zone geography is based on publicly observable information and operational knowledge; Sector will migrate to an official open dataset if and when one is published by the City of Ottawa.

This list is updated as new departments are onboarded. If you represent a municipality and have questions about how your data is used, contact us at privacy@sector.training.

Corrections & Removal Requests

If a data source publisher believes data is being used in a manner inconsistent with its license, or requests removal, contact us at privacy@sector.training and we will respond promptly.

04 Cookie Policy

We keep it simple. This platform uses one cookie and it exists solely to keep you logged in.

The Cookie We Set

  • Name: {city}_auth (e.g., ottawa_auth)
  • Purpose: Authentication — verifies you are logged in to the correct department.
  • Contents: A cryptographically signed token containing your city, SAP number, and expiry timestamp. It cannot be tampered with.
  • Duration: 7 days from login.
  • Type: HttpOnly (not accessible to JavaScript), SameSite=Lax.

What We Don't Use

  • No analytics cookies.
  • No tracking cookies.
  • No advertising cookies.
  • No third-party cookies.

Local Storage

The platform stores your SAP number and a session token in your browser's local storage to maintain your session between page loads. This data is cleared when you log out.