Privacy Policy

Delta Force is used by three kinds of account: administrators (“Command Center”), property managers, and vendors. This document covers all three, and also covers people who never hold an account but whose details appear in a building’s records — tenants, on-site staff and owner contacts.

• Name and email address.
• A password hash. Passwords are hashed with bcrypt and are never stored or logged in readable form.
• Session tokens, also stored hashed, so a database copy cannot be used to impersonate anyone.
• For property managers: a Stripe customer identifier and subscription state. Card details are held by Stripe and never reach this system.
• A record of actions taken — work orders raised, quotes decided, proof submitted, payments approved. This is the audit trail the product exists to produce.

Buildings carry tenant, staff and owner-contact records entered by property managers, and work orders carry photographs submitted as proof of completed work. These belong to the building’s owner, not to the person who entered them, and are retained for as long as that building is managed on the platform.

Automated deletion runs daily. These windows are enforced in code, not by policy:

• Expired sign-in sessions: 7 days.
• Password-reset and email-verification codes: 7 days.
• Payment-provider event records: 30 days.
• Notifications: 90 days.
• Resolved correction requests: 365 days.

Work orders, their timelines, proof photographs, inspections and payment records are not deleted on a schedule. They are the compliance record a building owner is paying to have.

An account holder can delete their own account, and an administrator can delete one on request. Deletion removes the name, email address, password hash and payment-provider identifier, ends every active session immediately, and cancels any live subscription.

It does not erase the work itself. Entries the account authored — approvals, inspections, submitted proof — remain, reassigned to an anonymous “Deleted User” record so the audit trail stays intact without naming anyone. A building’s history of who approved what remains verifiable; the individual is no longer identifiable from it.

Data is stored in a Postgres database hosted by Neon. Payments run through Stripe. Proof photographs are stored by Cloudinary. Transactional email is sent by the configured SMTP provider. Nothing is sold, and nothing is shared for advertising.

Requests to access, correct or erase personal data should go to the address published by the operator of this deployment.